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

Issue when searching a regular expression #1505

Closed
olivierfruchart opened this issue Jun 18, 2016 · 5 comments
Closed

Issue when searching a regular expression #1505

olivierfruchart opened this issue Jun 18, 2016 · 5 comments
Labels
bug Confirmed bugs or reports that are very likely to be bugs maintable search status: stale

Comments

@olivierfruchart
Copy link

JabRef version 3.5dev 2016-06-14 on Windows 10

In the search textbox if one types keywords="dzy", then I expect that entries are shown only if there is at least one keyword with this exact sequence. Instead, entries are also select, if one keyword contains a "z", another one a "d" and one with a "y". This behavior remains whetever the search options checked, regular expression on or off.

@Siedlerchr
Copy link
Member

Hi, thanks for your report.
In the 3.4 release on Win7 it works accurate.
Having one entry with keyword dzy and other entries with keyword "d" and "z" and using your search terms it correctly displays only one result.

Did you check the Float/Filter Option in the Search?
It can either hide all other entries or just gray them out. Maybe this is the problem?

@olivierfruchart
Copy link
Author

Hi, thanks for the feedback.
I finally found out the problem. Entries with a tag always appear at the top of the list in the 'float' mode, even if they do not fit the search. In the 'filter' mode they are not visible, which is more consistent. Thus it is not a bug but rather an annoying feature. In my view, tagged entries not fulfilling the search may appear first atop the grayed items, however not at the very top.

@matthiasgeiger
Copy link
Member

Thanks for your feedback!
Yes, if the option "Float marked entries" is activated in the prefs ("Entry Table" tab) the entries are still floating even if they do not match the active search.

@simonharrer I think that @olivierfruchart is right: The marking entries should placed beneath the search hits. WDYT?

@simonharrer
Copy link
Contributor

Yep, this seems to be a bug.

@simonharrer simonharrer added the bug Confirmed bugs or reports that are very likely to be bugs label Jun 20, 2016
@oscargus oscargus added the search label Aug 2, 2016
@github-actions
Copy link
Contributor

This issue has been inactive for half a year. Since JabRef is constantly evolving this issue may not be relevant any longer and it will be closed in two weeks if no further activity occurs.

As part of an effort to ensure that the JabRef team is focusing on important and valid issues, we would like to ask if you could update the issue if it still persists. This could be in the following form:

  • If there has been a longer discussion, add a short summary of the most important points as a new comment (if not yet existing).
  • Provide further steps or information on how to reproduce this issue.
  • Upvote the initial post if you like to see it implemented soon. Votes are not the only metric that we use to determine the requests that are implemented, however, they do factor into our decision-making process.
  • If all information is provided and still up-to-date, then just add a short comment that the issue is still relevant.

Thank you for your contribution!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Confirmed bugs or reports that are very likely to be bugs maintable search status: stale
Projects
Archived in project
Development

No branches or pull requests

6 participants