From: Philip Kaludercic <philipk@posteo.net>
To: Eli Zaretskii <eliz@gnu.org>
Cc: susam.pal@gmail.com, emacs-devel@gnu.org
Subject: Re: [NonGNU ELPA] New package: devil
Date: Tue, 09 May 2023 08:58:04 +0000 [thread overview]
Message-ID: <87lehxswyr.fsf@posteo.net> (raw)
In-Reply-To: <83cz39c2e7.fsf@gnu.org> (Eli Zaretskii's message of "Tue, 09 May 2023 11:52:48 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
>> From: Philip Kaludercic <philipk@posteo.net>
>> Cc: emacs-devel@gnu.org
>> Date: Tue, 09 May 2023 08:42:20 +0000
>>
>> > Hello!
>> >
>> > I am the author and maintainer of a new package named Devil. This package
>> > intercepts keystrokes entered by the user and applies translation rules to
>> > translate the keystrokes into Emacs key sequences. It supports three types
>> > of rules: special keys that map to custom commands that are invoked
>> > immediately prior to any translations, translation rules to translate Devil
>> > key sequences to regular Emacs key sequences, and repeatable keys to allow
>> > a Devil key sequence to be repeated by typing the last keystroke over and
>> > over again using a transient map.
>> >
>> > See the README at https://github.com/susam/devil for more details.
>>
>> Looks interesting, here is a diff with a few comments:
>
> Why call this package by such a strange name? It says nothing at all
> about the package's purpose. Would it be possible to rename it,
> please?
I am guessing that this is a pun on "evil-mode", but I am inclined to
agree. At least "evil" stands for "extensible vi layer for Emacs".
> Thanks.
next prev parent reply other threads:[~2023-05-09 8:58 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-09 1:57 [NonGNU ELPA] New package: devil Susam Pal
2023-05-09 8:42 ` Philip Kaludercic
2023-05-09 8:52 ` Eli Zaretskii
2023-05-09 8:58 ` Philip Kaludercic [this message]
2023-05-09 18:19 ` chad
2023-05-09 22:07 ` Susam Pal
2023-05-09 20:56 ` Susam Pal
2023-05-10 6:09 ` Philip Kaludercic
2023-05-10 21:00 ` Susam Pal
2023-05-10 21:56 ` Richard Stallman
-- strict thread matches above, loose matches on Subject: below --
2023-05-11 5:23 Payas Relekar
2023-05-11 6:26 ` Po Lu
2023-05-11 6:33 ` Eli Zaretskii
2023-05-11 6:52 ` Philip Kaludercic
2023-05-11 7:07 ` Eli Zaretskii
2023-05-12 15:02 ` Brian Cully via Emacs development discussions.
2023-05-11 8:09 ` Susam Pal
2023-05-11 8:45 ` Philip Kaludercic
2023-05-11 8:58 ` Eli Zaretskii
2023-05-11 9:08 ` Susam Pal
2023-05-11 9:12 ` Philip Kaludercic
2023-05-11 9:19 ` Susam Pal
2023-05-11 9:34 ` Ruijie Yu via Emacs development discussions.
2023-05-11 10:09 ` Susam Pal
2023-05-11 10:31 ` Susam Pal
2023-05-11 10:36 ` Eli Zaretskii
2023-05-11 8:56 ` Eli Zaretskii
2023-05-12 16:19 ` Jim Porter
2023-05-13 7:10 ` Philip Kaludercic
2023-05-13 9:05 ` Susam Pal
2023-05-15 22:12 ` Richard Stallman
2023-05-17 13:30 ` João Távora
2023-05-17 14:06 ` Philip Kaludercic
2023-05-17 15:41 ` João Távora
2023-05-17 15:46 ` Eli Zaretskii
2023-05-13 22:30 ` Richard Stallman
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=87lehxswyr.fsf@posteo.net \
--to=philipk@posteo.net \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=susam.pal@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).