-
-
Notifications
You must be signed in to change notification settings - Fork 223
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
Option to have hashtags as case-insensitive. #1492
Comments
I think maybe when you select one it is case insensitive, eventhough the dropdown has all the permutations that exist, is that right? |
Yes, whenever you remove/modify/add hashtags from a page, the scanner will notice when the page is updated, and remove/modify/add those in the database accordingly. The drop-down is global, so if a tag appears on more than one page, it will remain until all occurrences of it are removed. It was implemented as case-insensitive (without making assumptions about how they want tags to be stored) to keep it simple (it's also the default mode for SQLite), for example I would want #Steven or #Jason to stay that way and not become #steven and #jason. Also, most general users may be confused why they can't find their "DOG" when querying for "dog". I'll see how complicated it would be though and come up with some options |
Just to be clear - I am very happy the match is case-insensitive (as I think it is now). Thanks, |
* stevencohn#1492 Case sensitive stevencohn#1492 * stevencohn#1492 case-sensitive query builder * unused resx
* stevencohn#1492 Case sensitive stevencohn#1492 * stevencohn#1492 case-sensitive query builder * unused resx
Problem to Solve
Loving hashtags. But when people put them in , sometimes it is all caps, mixed, lower, and any other variation. This brings up lots of permutations in the search dialogue.
New Feature/Solution
Have a setting / option to log all hashtags as upper / lower.
Alternative Solutions
Additional Context
THE FINE PRINT This is a hobby project that I started for myself. I'm happy to take requests and will promise to
consider each one carefully but offer no guarantees that I will ultimately agree to their
usefulness or have time to implement any of them. If OneNote offers a "close enough" work-around
then I will probably reject the request - you've been warned!
The text was updated successfully, but these errors were encountered: