Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

# syntax no longer works with tags containing spaces #2984

Closed
KatrinIhler opened this issue Jan 16, 2024 · 2 comments
Closed

# syntax no longer works with tags containing spaces #2984

KatrinIhler opened this issue Jan 16, 2024 · 2 comments

Comments

@KatrinIhler
Copy link

In my latest version (7.12.2) the # syntax no longer works with tags containing spaces - instead of setting my existing tag, it creates a new tag with the first half and leaves the second half in my task title. I can still set existing tags with spaces via the drop down though.

I know this was discussed in #2856 and I was in favor to make the tag matching less sensitive (though mainly in regards to URLS), but I wonder if this change was intentional, and if it was, if there is still a way to set tags with spaces by using quotation marks or something.

Copy link

Thank you very much for opening up this issue! I am currently a bit overwhelmed by the many requests that arrive each week, so please forgive me, if I fail to respond personally. I am still very likely to at least skim read your request and I'll probably try to fix all (real) bugs if possible and I will likely review every single PR being made (please, give me a heads up if you intent to do so) and I will try to work on popular requests (please upvote via thumbs up on the original issue) whenever possible, but trying to respond to every single issue over the last years has been kind of draining and I need to adjust my approach for this project to remain fun for me and to make any progress with actually coding new stuff. Thanks for your understanding!

@johannesjo
Copy link
Owner

Thanks for opening this up! Yes this was intentional to simplify the short syntax code and avoid all sorts of edge cases, but also because it makes sense to me conceptually. If somebody wants to tackle this, I am alright with adding support again, but probably won't work on it myself.

@Jagdfalke Jagdfalke removed the bug label Mar 28, 2024
@Jagdfalke Jagdfalke closed this as not planned Won't fix, can't repro, duplicate, stale Mar 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants