Thank you! That would be great and a very useful feature for all international users!

(this is why Jetbrains implemented it, it happens A LOT to be on the wrong keyboard setting when you search for something)

Is it enough if Vomnibar only does search using English-alphabet version, when a current query (from IME) matches nothing?

I need to know it because sometimes a user may do want to search some non-English text (like Chinese titles of web pages).

That could be OK.

This is what JetBrains does, which is even better:

They show both the "selected language alphabet" results and the corresponding "english alphabet" results. So, you always have the "english alphabet" results, even when no result is found on the "selected language alphabet".

You could implement it as you mentioned if that is much easier for you, it will still be a great addition!

Thanks!

Not sure if this has also been reported elsewhere but it is quite similar:

Support case-insensitive search:

Works:

Does not work:

Thanks!

@gdh1995 I have the latest version, I do not see the option to "ignore case" in options (neither does it behave as such automatically).

Can you show us where we select this?

Thanks a lot!

@afilp you may add map g Vomnibar.activate icase or map g Vomnibar.activate icase=true to the "custom key mappings" option - this is a new option used in command mappings, so if you have more than one mapping of Vomnibar.activate*** and you expect they are all case-insensitive, then you need to re-map all of them.

Thanks, it worked!

Where is this process shown in the UI? It seems like hidden.

I thought that this could be a check here (that would apply to all 3 variants, T, b, g):

Thanks a lot, when you have time it would be perfect to also have the "find results even when typing in other language's characters). Thanks!

Well, I think such a usage of icase is too small to add a visible checkbox for it. And it provides some more use cases if it's only a command option - one may have two key mappings: one with icase=false, and the other with icase=true.

As for this issue, I prefer a special checkbox for it, to let more notice it.

But it's really very hard to maintain a list of English characters corresponding to what one types. I haven't got a good idea to implement it. There're also some other features in my TODO list, so maybe "adding it into find mode" will be delayed for months or even years.

Thanks, I will try at some point to implement it up to a point (you know the internals better) in a new branch and show it to you so that you make adjustments, if possible.