From: "Felix E. Klee" <felix.klee@inka.de>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Lars Magne Ingebrigtsen <larsi@gnus.org>, 32359@debbugs.gnu.org
Subject: bug#32359: [PATCH] Add svg-path
Date: Fri, 2 Aug 2019 12:43:33 +0200 [thread overview]
Message-ID: <CA+m_8J3ovU9FiddWW3ss3W19vb7c9HFvr+yqJ2O8Qk=6wi5s5A@mail.gmail.com> (raw)
In-Reply-To: <83ftmkgjdu.fsf@gnu.org>
On Fri, Aug 2, 2019 at 8:40 AM Eli Zaretskii <eliz@gnu.org> wrote:
> Please review the followup change in the documentation I made
The definition of SVG paths is a good addition IMO.
> In particular, you cannot add a @node without also adding a @menu and
> mentioning that node in a few other menus.
Now that “SVG Path Commands” is a subheading, isn’t the menu
superfluous? I find it confusing to the reader.
For comparison, have a look in `searching.texi`:
@subsubheading Literals
There is no menu for “Literals”.
next prev parent reply other threads:[~2019-08-02 10:43 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-03 11:07 bug#32359: [PATCH] Add svg-path Felix E. Klee
2018-08-03 13:05 ` Eli Zaretskii
2018-08-23 15:50 ` Felix E. Klee
2018-08-23 17:23 ` Eli Zaretskii
2018-08-24 9:15 ` Felix E. Klee
2019-06-23 22:15 ` Lars Ingebrigtsen
2019-06-24 14:32 ` Felix E. Klee
2019-06-24 14:39 ` Lars Ingebrigtsen
2019-07-12 14:35 ` Felix E. Klee
2019-07-12 16:02 ` Lars Ingebrigtsen
2019-07-15 13:34 ` Felix E. Klee
2019-07-15 15:12 ` Lars Ingebrigtsen
2019-07-15 20:40 ` Felix E. Klee
2019-07-15 20:48 ` Noam Postavsky
2019-07-16 10:32 ` Felix E. Klee
2019-07-15 21:13 ` Felix E. Klee
2019-07-16 6:05 ` Lars Ingebrigtsen
2019-07-16 10:31 ` Felix E. Klee
2019-07-16 13:46 ` Lars Ingebrigtsen
2019-07-24 7:49 ` Felix E. Klee
2019-07-24 14:30 ` Eli Zaretskii
2019-07-30 17:46 ` Felix E. Klee
2019-07-31 20:31 ` Lars Ingebrigtsen
2019-08-01 13:23 ` Felix E. Klee
2019-08-02 6:40 ` Eli Zaretskii
2019-08-02 10:43 ` Felix E. Klee [this message]
2019-08-02 11:57 ` 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='CA+m_8J3ovU9FiddWW3ss3W19vb7c9HFvr+yqJ2O8Qk=6wi5s5A@mail.gmail.com' \
--to=felix.klee@inka.de \
--cc=32359@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=larsi@gnus.org \
/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.