Skip to content

Don't spuriously set mark on xref push #865

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

Merged
merged 1 commit into from
Sep 12, 2015
Merged

Conversation

purcell
Copy link
Member

@purcell purcell commented Sep 11, 2015

This fixes #863, whereby jumping to the definition of a symbol in the
same file was incorrectly activating the mark and region. This commit
also simplifies the original code, since the initial position marker can
simply be passed to xref-push-marker-stack. (The haskell-compat shim for
that function is also fixed here accordingly.)

This fixes #863, whereby jumping to the definition of a symbol in the
same file was incorrectly activating the mark and region. This commit
also simplifies the original code, since the initial position marker can
simply be passed to xref-push-marker-stack. (The haskell-compat shim for
that function is also fixed here accordingly.)
gracjan added a commit that referenced this pull request Sep 12, 2015
Don't spuriously set mark on xref push
@gracjan gracjan merged commit ec14cc3 into master Sep 12, 2015
@gracjan
Copy link
Contributor

gracjan commented Sep 12, 2015

Nice. So I have learned something about xref-push today. Thanks.

@purcell
Copy link
Member Author

purcell commented Sep 12, 2015

👍

@gracjan gracjan deleted the no-set-mark-on-xref-push branch September 15, 2015 12:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Jumping with M-. within the current buffer marks a region
2 participants