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

Enter in global search should open the selected entry #617

Closed
HainesB opened this issue Jan 1, 2016 · 4 comments
Closed

Enter in global search should open the selected entry #617

HainesB opened this issue Jan 1, 2016 · 4 comments

Comments

@HainesB
Copy link

HainesB commented Jan 1, 2016

It is possible to bring up the search field with C-f to enter a search term. But it is not obvious how to activate "search globally" except with the use of the mouse. When the global search button is clicked with the mouse, it returns a message that "No results found" even though a "Search results" window pops up that displays the search term.

Context (added by @koppor): Opened global search:

grabbed_20160408-080008

In that window, when the ENTER key is hit, instead of the entry being displayed in the main window, the next item in the Search results window is selected, the same as the down arrow. So the only way to display the selected search result is to double click it with the mouse, for the operation does not seem bound to any keys.

@koppor koppor changed the title Version 3.1 limitations of searches from keyboard Enter in global search should open the selected entry Apr 8, 2016
@koppor
Copy link
Member

koppor commented Apr 8, 2016

In short:

@koppor
Copy link
Member

koppor commented Apr 8, 2016

@HainesB The latest development build (http://builds.jabref.org/master/) does not show the popup "no search results found" any more. - Your first concern is tracked at #573. - I reformulated your request to describe the last concern. - I hope that I understood everything now and that it is OK for you to update your description.

@teertinker
Copy link
Contributor

#825
-> a double-click does (e.g. after a global search in bib2.bib) not even show the entry in case the result refers to an entry that has been filtered away in a previous local search (e.g. bib1.bib)

@koppor
Copy link
Member

koppor commented Sep 11, 2016

Thank you for reporting this issue. We think, that is already fixed in our development version.
Please use a development build from http://builds.jabref.org/master
The fix will be included in the next release.

We are well aware, that cursor up and cursor down does not work as expected in the global search dialog. @bartsch-dev takes care.

@koppor koppor closed this as completed Sep 11, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

6 participants