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

Jump to specific line of occurrence with denote-find-backlink #471

Open
johkneisl opened this issue Oct 27, 2024 · 2 comments
Open

Jump to specific line of occurrence with denote-find-backlink #471

johkneisl opened this issue Oct 27, 2024 · 2 comments

Comments

@johkneisl
Copy link

Between the two major options to visit backlinks

  1. Use denote-backlinks, visit the backlinks’ buffer, follow a backlink.
  2. Use denote-find-backlink, select a backlink from the minibuffer.

I'm seeing a difference in behavior after following a backlink.

(1) The backlink buffer opens the referenced file at the exact location of the outgoing link, which is useful.
(2) With denote-find-backlink, I just land at the top of the file, which is less useful.

I think it would be convenient to have the behavior of (1) in (2).
I hope I was able to make clear what I mean, I'm happy to provide some screenshots or more explanations if necessary.

@protesilaos
Copy link
Owner

protesilaos commented Nov 4, 2024 via email

protesilaos added a commit that referenced this issue Nov 4, 2024
The idea is for us to then use this information in 'denote-find-backlink'
(or related) to jump to the position of the match, rather than simply
visit the corresponding file.

This is a preliminary response to what johkneisl requested in issue
471: <#471>.
@protesilaos
Copy link
Owner

I forgot to update this thread at the time. I did make some changes to the backlinks-with-context branch. I still need to review the functionality before mergin it into main. I hope to do this soon.

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

No branches or pull requests

2 participants