From: "Felix E. Klee" <felix.klee@inka.de>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 32359@debbugs.gnu.org
Subject: bug#32359: [PATCH] Add svg-path
Date: Fri, 24 Aug 2018 11:15:33 +0200 [thread overview]
Message-ID: <CA+m_8J3Fu0S-cwh8dnbNPYCxnko=xQbEgd=KQNqWtiuytcxwWQ@mail.gmail.com> (raw)
In-Reply-To: <83zhxd9euu.fsf@gnu.org>
On Thu, Aug 23, 2018 at 7:23 PM, Eli Zaretskii <eliz@gnu.org> wrote:
> I think it would be better simply to explain those in plain English,
> not by adding code.
OK. Still the aliases do increase readability. They are not made up.
They are based on the “names” listed in the [specs][1].
For now, I am considering creating a separate package `svg+.el'. This
would allow me to play with various approaches, possibly with user
feedback. If that all works, one could merge the additions into Emacs.
[1]: https://www.w3.org/TR/SVG11/paths.html
next prev parent reply other threads:[~2018-08-24 9:15 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 [this message]
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
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
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='CA+m_8J3Fu0S-cwh8dnbNPYCxnko=xQbEgd=KQNqWtiuytcxwWQ@mail.gmail.com' \
--to=felix.klee@inka.de \
--cc=32359@debbugs.gnu.org \
--cc=eliz@gnu.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 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).