From: Sean Whitton <spwhitton@spwhitton.name>
To: emacs-devel@gnu.org
Cc: Protesilaos Stavrou <public@protesilaos.com>
Subject: New ELPA package: transient-cycles
Date: Fri, 08 Apr 2022 17:25:25 -0700 [thread overview]
Message-ID: <87tub33xxm.fsf@melete.silentflame.com> (raw)
Hello,
I would like to add my package transient-cycles to GNU ELPA:
<https://git.spwhitton.name/dotfiles/tree/.emacs.d/site-lisp/transient-cycles.el>.
The package does not have a git repository of its own. For several
reasons I would prefer to keep it that way, and manually sync new
versions to elpa.git. So I believe what I need to do to elpa.git is add
the line
("transient-cycles" :url nil)
to elpa-packages, and push a new branch externals/transient-cycles
containing the single file transient-cycles.el. And then the scripts
should be able to extract the commentary and changelog. Is that right?
Here is the beginning of the package description:
> Many commands can be conceptualised as selecting an item from an
> ordered list or ring. Sometimes after running such a command, you
> find that the item selected is not the one you would have preferred,
> but the preferred item is nearby in the list. If the command has been
> augmented with transient cycling, then it finishes by setting a
> transient map with keys to move backwards and forwards in the list of
> items, so you can select a nearby item instead of the one the command
> selected. From the point of view of commands subsequent to the
> deactivation of the transient map, it is as though the first command
> actually selected the nearby item, not the one it really selected.
--
Sean Whitton
next reply other threads:[~2022-04-09 0:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-09 0:25 Sean Whitton [this message]
2022-04-09 2:55 ` New ELPA package: transient-cycles Stefan Monnier
2022-04-09 17:41 ` Sean Whitton
2022-04-09 22:45 ` Stefan Monnier
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=87tub33xxm.fsf@melete.silentflame.com \
--to=spwhitton@spwhitton.name \
--cc=emacs-devel@gnu.org \
--cc=public@protesilaos.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).