From: "Mattias Engdegård" <mattiase@acm.org>
To: Juri Linkov <juri@linkov.net>
Cc: Dmitry Gutov <dgutov@yandex.ru>, 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: Mon, 25 Oct 2021 20:53:59 +0200 [thread overview]
Message-ID: <50BA01F3-495E-4332-8941-78EF4CC47B9C@acm.org> (raw)
In-Reply-To: <87h7d5xcf6.fsf@mail.linkov.net>
25 okt. 2021 kl. 19.05 skrev Juri Linkov <juri@linkov.net>:
> I took a look at your change, and noticed an asymmetry
> between the names xref-pop-marker-stack and xref-go-forward.
> Shouldn't the name xref-pop-marker-stack be obsoleted,
> and replaced with a new name xref-go-back?
Yes, this was the intention. I have now done that; thanks for reminding me!
> Another question is that in the menu bar currently the order is
> "Forward" and "Back". But more natural order would be
> "Back" and "Forward".
Oh, I didn't realise they had to be given in reverse order. Fixed, thank you.
> The menu contains the item "Back Definition". (BTW, why if the search failed?)
That appears to be a known imperfection in Xref -- I agree it shouldn't be added if the search failed.
> This menu item is too ambiguous. Renaming it to "Go Back" or "Go Forward"
> doesn't make the menu item clearer. Only adding a word "Xref" somewhere
> will disambiguate it. Maybe then "Go Back in Xref" or "Go Back with Xref"?
Maybe, but if we embrace the idea that there really only should be a single back button in the application (which is what other IDEs typically have), then there is no ambiguity. Until then we may need to add "Xref" somehow, but where is the confusion, exactly?
> We need more opinions.
Only if they are well-reasoned!
next prev parent reply other threads:[~2021-10-25 18:53 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
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 [this message]
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=50BA01F3-495E-4332-8941-78EF4CC47B9C@acm.org \
--to=mattiase@acm.org \
--cc=38797@debbugs.gnu.org \
--cc=dgutov@yandex.ru \
--cc=juri@linkov.net \
--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.