[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#34908: Push mark in xref-push-marker-stack
From: |
Eli Zaretskii |
Subject: |
bug#34908: Push mark in xref-push-marker-stack |
Date: |
Wed, 20 Mar 2019 07:59:09 +0200 |
> From: Juri Linkov <juri@linkov.net>
> Cc: 34908@debbugs.gnu.org, joaotavora@gmail.com, dgutov@yandex.ru
> Date: Tue, 19 Mar 2019 22:59:18 +0200
>
> >> Shouldn't xref-push-marker-stack push the mark like all normal commands do?
> >
> > Fine with me to add that (I think etags.el-based M-. did this), but
> > please make sure the manual and NEWS are updated with this
> > information.
>
> I don't want to advertise this fix because the primary way to get back
> for xref should be ‘M-,’.
Well, it must be in NEWS, since this is a change in behavior.
As for the manuals, it might be okay not to mention that, although I
admit I don't understand your reasoning: something that is not a
primary use doesn't automatically mean it shouldn't be documented.
> Setting the mark is only needed for users who expect that every
> significant change in position should leave a trace in the global
> mark ring.
I believe most of our commands that move to a far away position do set
the mark.
bug#34908: Push mark in xref-push-marker-stack, Eli Zaretskii, 2019/03/19