From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: larsi@gnus.org, stefan@marxist.se, emacs-devel@gnu.org
Subject: Re: woman.el broken?
Date: Tue, 02 Mar 2021 07:18:59 +0200 [thread overview]
Message-ID: <83im6a6sl8.fsf@gnu.org> (raw)
In-Reply-To: <jwvr1kyobg7.fsf-monnier+emacs@gnu.org> (message from Stefan Monnier on Mon, 01 Mar 2021 15:42:09 -0500)
> From: Stefan Monnier <monnier@iro.umontreal.ca>
> Cc: stefan@marxist.se, larsi@gnus.org, emacs-devel@gnu.org
> Date: Mon, 01 Mar 2021 15:42:09 -0500
>
> > Btw, it isn't just letter-case, but also "Foo Bar Baz" as opposed to
> > "foo-bar-baz", right?
>
> It can be anything, really: the pseudo-events used in the easymenu code
> is auto-generated from the menu entry's text, but in the "old-style"
> code, it's generated by hand by the programmer, so it's in general
> impossible to find one from the other. We can at best add heuristics.
Sure. I _was_ talking about heuristics, based on what I see in the
sources. We probably should have this in "Incompatible changes" part
regardless, since heuristics could fail.
next prev parent reply other threads:[~2021-03-02 5:18 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-01 19:39 woman.el broken? T.V Raman
2021-03-01 19:48 ` Lars Ingebrigtsen
2021-03-01 20:02 ` Eli Zaretskii
2021-03-01 20:07 ` Lars Ingebrigtsen
2021-03-01 20:19 ` Eli Zaretskii
2021-03-01 20:25 ` Eli Zaretskii
2021-03-01 20:42 ` Stefan Monnier
2021-03-02 5:18 ` Eli Zaretskii [this message]
2021-03-01 20:47 ` Lars Ingebrigtsen
2021-03-01 21:06 ` Lars Ingebrigtsen
2021-03-01 21:29 ` Lars Ingebrigtsen
2021-03-03 2:23 ` Stefan Kangas
2021-03-03 6:25 ` Eli Zaretskii
2021-03-03 14:19 ` Stefan Kangas
2021-03-03 14:40 ` Eli Zaretskii
2021-03-03 18:46 ` Stefan Kangas
2021-03-06 3:43 ` Stefan Kangas
2021-03-06 8:07 ` Eli Zaretskii
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=83im6a6sl8.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=larsi@gnus.org \
--cc=monnier@iro.umontreal.ca \
--cc=stefan@marxist.se \
/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.