You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
applies for the following versions:
CodeSearch version 1.1.0
CLion 2022.1.3
A)
There is no possibility to set up a shortcut (called Keymap in Clion's setting) for the Custom Search Engine.
For the default search engines the possibility is there.
Having a shortcut to trigger the Custom Search Service is a must to use this plugin.
Right clicking and selecting the Custom Search Service form the context menu is as hard as doing Ctrl-C, Alt-Tab, Ctrl-V on the Browser's search bar. Not convenient.
applies for the following versions:
CodeSearch version 1.1.0
CLion 2022.1.3
A)
There is no possibility to set up a shortcut (called Keymap in Clion's setting) for the Custom Search Engine.
For the default search engines the possibility is there.
Having a shortcut to trigger the Custom Search Service is a must to use this plugin.
Right clicking and selecting the Custom Search Service form the context menu is as hard as doing Ctrl-C, Alt-Tab, Ctrl-V on the Browser's search bar. Not convenient.
B)
Also what's the pattern which is substituted in the desired URL?
In this GIF it seems that the pattern (=selected text) is appended to the end of the Custom Search URL I specified.
https://raw.githubusercontent.com/guojianhua/code-search/master/imgs/add-search-service.gif
But it is not the case, unfortunately.
How it really works?
For example suppose I select/highlight a word called 'epsilon' by double clicking on it.
I would want to go to cppreference.com with this search URL
https://en.cppreference.com/mwiki/index.php?title=Special%3ASearch&fulltext=1&search=epsilon
It doesn't work, by running the Custom Search from context menu CLion/COdeSearch opens the browser with the following URL:
https://en.cppreference.com/mwiki/index.php?title=Special%3ASearch&fulltext=1&search=
The 'epsilon' is not there :(
The text was updated successfully, but these errors were encountered: