-
-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
Settings in Searching: suggest to separate these from autocompletion #6625
Comments
Thanks to @calixtus this should be fixed now in the latest master We would like to ask you to use a development build from https://builds.jabref.org/master and report back if it works for you. Please remember to make a backup of your library before trying-out this version. |
I am now testing the Portable version of:
The GUI elements I would expect based on Rework search bar #6682 are not visible for me. Please let me know if I can do additional tests. |
@jhh931 Please install the latest version (18.07) |
The buttons should be visible if you click on the search bar in the most recent development version. Remember to always backup your data before using a development version. |
Check: in V 18.07, the buttons appear when clicking on the search bar. (This version does have another issue w.r.t. files linked to my entries; should I report this?) |
Please open a new issue for the problem with the linked files |
Done: |
JabRef 5.0 under Windows 10.
Usability of Jabref is reduced for me by the following issue related to searching (i.e. searching for entries within the current library).
The options for using RegEx or not and searching case-sensitive or not are only available via Auto-complete:
![Untitled](https://user-images.githubusercontent.com/20792626/85201098-03e48780-b2fd-11ea-83e3-03924edcdcf7.jpg)
. I don't see the logic behind that; having these available adjacent to the search bar, irrespective of using autocomplete or not, (as it used to be, see below) makes more sense to me.
The text was updated successfully, but these errors were encountered: