From: Juri Linkov <juri@linkov.net>
To: Dmitry Gutov <dgutov@yandex.ru>
Cc: "Mattias Engdegård" <mattiase@acm.org>,
yyoncho <yyoncho@gmail.com>,
38797@debbugs.gnu.org
Subject: bug#38797: 27.0.50; Feature request: provide the opposite of xref-pop-marker-stack
Date: Sun, 24 Oct 2021 10:54:04 +0300 [thread overview]
Message-ID: <87ilxm27wz.fsf@mail.linkov.net> (raw)
In-Reply-To: <0c88bcef-f07d-5a38-fa7d-b0ddd048cb48@yandex.ru> (Dmitry Gutov's message of "Sun, 24 Oct 2021 04:40:09 +0300")
> - Regarding the names of the commands, some alternatives:
>
> * xref-rewind-history? It's a play on "fast forward". A bit cryptic,
> perhaps.
> * xref-go-back and xref-go-forward? xref--history is fine the name of the
> variable, but the purpose of the commands seems obvious enough even
> without "history" in them.
Two different naming conventions are in use already:
Info-history-back
Info-history-forward
help-go-back
help-go-forward
Choosing any of those would be fine.
next prev parent reply other threads:[~2021-10-24 7:54 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-29 18:11 bug#38797: 27.0.50; Feature request: provide the opposite of xref-pop-marker-stack yyoncho
2020-01-23 14:13 ` Dmitry Gutov
2021-10-20 19:12 ` Mattias Engdegård
2021-10-24 1:40 ` Dmitry Gutov
2021-10-24 7:54 ` Juri Linkov [this message]
2021-10-24 12:39 ` Dmitry Gutov
2021-10-24 19:10 ` Juri Linkov
2021-10-24 23:22 ` Dmitry Gutov
2021-10-25 7:44 ` Juri Linkov
2021-10-25 15:18 ` Dmitry Gutov
2021-10-25 17:07 ` Juri Linkov
2021-10-24 13:24 ` Mattias Engdegård
2021-10-25 2:13 ` Dmitry Gutov
2021-10-25 15:49 ` Mattias Engdegård
2021-10-25 17:05 ` Juri Linkov
2021-10-25 18:53 ` Mattias Engdegård
2021-10-25 19:38 ` Dmitry Gutov
2021-10-25 21:29 ` Glenn Morris
2021-10-26 8:06 ` Mattias Engdegård
2021-11-08 18:23 ` Juri Linkov
2021-11-09 8:30 ` Juri Linkov
2021-11-09 13:08 ` Mattias Engdegård
2021-11-09 13:09 ` Dmitry Gutov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87ilxm27wz.fsf@mail.linkov.net \
--to=juri@linkov.net \
--cc=38797@debbugs.gnu.org \
--cc=dgutov@yandex.ru \
--cc=mattiase@acm.org \
--cc=yyoncho@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.