Column search suggestions

[sochtends]

First, if Author is selected, the search wheel turns for very long time. If Bibtex key is selected, it is quite fast.
Second, if no column is selected, it does not search at all. It would be better if the search is still performed, by Bibtex Key or by Author by default.

Is your suggestion for improvement related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]

Describe the solution you'd like
A clear and concise description of what you want to happen.

Additional context
Add any other context or screenshots about the feature request here.

[leitianjian]

Hi, Thanks for your suggestions.
I wonder whether you are describing the function of jumping to an entry in the main table with the same value as the typed key?

[sochtends]

Hi leitianjian,

Indeed, I refer to the recently added feature of searching within the main table by typing name. If a particular column is selected, i.e. there is an arrow up or down next to the column name, then the search is performed. But if no column is selected, nothing happens. It would be better if it still does the search by bibtex key for example.

[leitianjian]

Great idea!
Thanks for your further explanation. I know your idea now, I will try to satisfy your requirement. However, it seems a little difficult. Because from your description, I think you need to search bibtex key by default, which is going to filter entry not related. It is a little different than a simple jump.

[sochtends]

I am not quite sure I follow you. But I would prefer it doing exactly the same as Bibtex Key selected. It is probably something that you refer as a jump. It is not a filtering what I would like to have. i would say that it should scroll along the table to the corresponding bibtex key.

[leitianjian]

Thanks for your clarification. However, I think a simple jump should not be used when the list is not sorted. For example, the first entry with bibtex key 602...., 200th entry with 602.... too, where to jump when you typed 602?

[github-actions]

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!