Add CLI option: --jump-to-entry key

koppor / jabref

Collection of simple for JabRef issues. Please submit PRs to https://github.com/jabRef/jabref/.

https://github.com/jabRef/jabref/

MIT License

8 stars 13 forks source link

Add CLI option: --jump-to-entry key #540

Closed koppor closed 6 months ago

koppor commented 2 years ago

There should be command line interface (CLI) option to jump to an entry.

Use case: I have TeXStudio opened and want to jump to the respective BibEntry in JabRef.

grafik

In other words: I request the opposite functionality of https://docs.jabref.org/cite/pushtoapplications

The current CLI does not offer it - according to https://docs.jabref.org/advanced/commandline

u7282852 commented 10 months ago

Hi I'm a university student and new to contributing. I would love to work on this issue if possible.

koppor commented 10 months ago

@u7282852 Thank you for choosing JabRef. Here some general hints. Looking forward to your contribution.

As a general advice for newcomers: check out Contributing for a start. Also, guidelines for setting up a local workspace is worth having a look at.

Feel free to ask here at GitHub, if you have any issue related questions. If you have questions about how to setup your workspace use JabRef's Gitter chat. Try to open a (draft) pull-request early on, so that people can see you are working on the issue and so that they can see the direction the pull request is heading towards. This way, you will likely receive valuable feedback.

Additional hint: This month, it's #hacktoberfest.

u7282852 commented 10 months ago

Hi, I just realised that I have been doing my work on the main Jabref/jabref project instead of the koppor/jabref project. Should I clone the correct repository and move my changes over, or can I still open a PR on the main project?

koppor commented 10 months ago

JabRef/jabref is really fine - it is the intention. Thus, just continue. - Please ensure that you reference the issue by the full URL.

We are working to move alle the issues to the other repository, but that takes time.

u7282852 commented 10 months ago

Hi I just submitted a draft pull request for this issue. It turns out I have forked Koppor/jabref though have followed the workspace instructions for the normal project so the pull request seems to be submitted for Koppor/jabref. Let me know if I need to do anything to fix this. Thanks

koppor commented 10 months ago

so the pull request seems to be submitted for Koppor/jabref.

To fix this:

Navigate to https://github.com/JabRef/jabref/pulls
Click on "New Pull Request"
Click on "compare across forks"\
Choose JabRef (1) / main (2) / u7282852 (3) / issue541-jump-to-entry-cli (4) \
Adapt description. Use Fixes https://github.com/koppor/jabref/issues/540 to enable autolinking

Side question: Can you give me a hint how to improve the text so that contributors as you use Fixes instead of Adresses in the PR description?

Maybe, we need to make the text more clear? Longer is not an option I think.

u7282852 commented 10 months ago

Thank you for your help! I will implement these changes. I just assumed "fixed" might be only for issues relating to bugs or problems, considering this is more of a new feature I wrote "addresses" but I will switch them to fixed now.