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

Group names #3075

Closed
mpele opened this issue Aug 4, 2017 · 4 comments · Fixed by #3077
Closed

Group names #3075

mpele opened this issue Aug 4, 2017 · 4 comments · Fixed by #3077
Labels

Comments

@mpele
Copy link
Contributor

mpele commented Aug 4, 2017

JabRef-4.0-dev--snapshot--2017-08-03--master--ea29f5600.jar

Steps to reproduce:

  1. Create group "one"
  2. Create group "two"
  3. Create group "one, two"
  4. Add article to group "one, two"

The article is presented in all tree groups.

@lenhard lenhard added bug Confirmed bugs or reports that are very likely to be bugs groups and removed bug Confirmed bugs or reports that are very likely to be bugs labels Aug 5, 2017
@lenhard
Copy link
Member

lenhard commented Aug 5, 2017

I am not 100% sure, but this behavior might actually be intended.

@tobiasdiez Can you clarify?

@tobiasdiez
Copy link
Member

tobiasdiez commented Aug 6, 2017

Yes this behavior is kind of by design since the group membership is stored as a comma separated list. If you want to use the comma in the group name, you have to change the keyword separator under Preferences > Groups > "When adding/removing keywords, separate them by" (note that this leads to problems if you already have entries belonging to more then one group or have multiple keywords).

With #3077 a proper error message will be displayed when a group name contains the keyword separator.

@retorquere
Copy link

Is the group separator saved in the BibTeX file? I import jabref - generated bibliographies using zotero better bibtex (bbt) and this new groups format is a bit of a challenge.

@tobiasdiez
Copy link
Member

No the keyword separator is only stored in the preferences and not in the bib file (but we probably want to change this at some point).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants