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

allow specifying shortcut for Custom Search Engines + URL bug in CLion #4

Open
peter-joo opened this issue Jul 22, 2022 · 0 comments
Open

Comments

@peter-joo
Copy link

peter-joo commented Jul 22, 2022

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 :(

@peter-joo peter-joo changed the title allow specifying shortcut for custom search engines + URL bug in CLion allow specifying shortcut for Custom Search Engines + URL bug in CLion Jul 22, 2022
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

1 participant