From: Eli Zaretskii <eliz@gnu.org>
To: Jim Porter <jporterbugs@gmail.com>
Cc: 52286@debbugs.gnu.org
Subject: bug#52286: 28.0.90; [PATCH] Be consistent in naming of separators in context menu
Date: Sun, 05 Dec 2021 12:39:37 +0200 [thread overview]
Message-ID: <835ys349p2.fsf@gnu.org> (raw)
In-Reply-To: <3788dcca-c2bd-99b2-b54d-463e12cd52c0@gmail.com> (message from Jim Porter on Sat, 4 Dec 2021 23:44:07 -0800)
> Cc: 52286@debbugs.gnu.org
> From: Jim Porter <jporterbugs@gmail.com>
> Date: Sat, 4 Dec 2021 23:44:07 -0800
>
> > The first pretest of Emacs 28 is already out, so this problem is
> > already with us, isn't it?
>
> If it's too late to change this, that's ok. I just noticed it while
> working on the patch for bug#52237 and figured it'd be good to file a
> bug about it while there's still a non-zero chance it could be changed.
> It's a pretty minor issue, so I don't really mind if this gets closed as
> wontfix.
>
> If this change *is* ok to merge, I'll happily update the ELisp manual
> with a brief summary of the convention before it gets merged.
I'd like to hear opinions of others. Meanwhile, having the proposed
convention spelled out in the manual would be good to make sure we are
all on the same page regarding the issue.
As for the issue itself: cannot we detect the separators in some more
robust way, one that doesn't depend on how they are named? And if
that's not feasible, perhaps allow anything that has "separator" in
its name to be considered a separator?
Thanks.
next prev parent reply other threads:[~2021-12-05 10:39 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-04 21:57 bug#52286: 28.0.90; [PATCH] Be consistent in naming of separators in context menu Jim Porter
2021-12-05 6:45 ` Eli Zaretskii
2021-12-05 7:44 ` Jim Porter
2021-12-05 10:39 ` Eli Zaretskii [this message]
2021-12-06 2:09 ` Jim Porter
2021-12-06 12:55 ` Eli Zaretskii
2021-12-11 20:52 ` Jim Porter
2022-01-15 18:57 ` Juri Linkov
2022-01-15 19:13 ` Eli Zaretskii
2022-01-15 19:19 ` Juri Linkov
2022-01-15 19:23 ` Eli Zaretskii
2022-01-15 19:25 ` Juri Linkov
2021-12-05 9:37 ` Juri Linkov
2021-12-05 17:52 ` Juri Linkov
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=835ys349p2.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=52286@debbugs.gnu.org \
--cc=jporterbugs@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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).