all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Sean Whitton <spwhitton@spwhitton.name>
To: emacs-devel@gnu.org
Subject: Optional Eshell modules -- to emacs.git or ELPA?
Date: Wed, 26 Jan 2022 19:48:50 -0700	[thread overview]
Message-ID: <87zgnhsxkd.fsf@melete.silentflame.com> (raw)

Hello,

I have a useful Eshell thing that I would like to make more broadly
available but which should definitely not be turned on by default.  The
final implementation will be as an Eshell module which makes an addition
to post-self-insert-hook.

I notice that there aren't any Eshell modules in GNU ELPA.  So, should I
propose this for inclusion in lisp/eshell/em-*.el, or as something new
in GNU ELPA?

One advantage of the former option is that the extension could be
documented in the Eshell manual, whereas otherwise all there can be is
docstrings and the package description, which is markedly less
discoverable.

Thanks!

-- 
Sean Whitton



             reply	other threads:[~2022-01-27  2:48 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-27  2:48 Sean Whitton [this message]
2022-01-29 11:51 ` Optional Eshell modules -- to emacs.git or ELPA? Philip Kaludercic
2022-04-16 18:57   ` New optional Eshell module: em-elecslash Sean Whitton
2022-04-16 19:18     ` Eli Zaretskii
2022-04-16 20:04       ` Sean Whitton
2022-04-16 21:42         ` [External] : " Drew Adams
2022-04-17  6:20         ` Eli Zaretskii
2022-04-17 16:48           ` [External] : " Drew Adams
2022-04-19 16:52           ` Sean Whitton
2022-04-20  0:36             ` Sean Whitton
2022-04-20  6:19               ` Eli Zaretskii
2022-04-20 20:14                 ` Sean Whitton
2022-04-21  6:15                   ` Eli Zaretskii
2022-04-16 21:12       ` Sean Whitton
2022-04-16 22:58     ` Stefan Monnier
2022-04-17  5:02       ` Sean Whitton
2022-04-17  6:24     ` Jim Porter
2022-04-19 15:28       ` Sean Whitton

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=87zgnhsxkd.fsf@melete.silentflame.com \
    --to=spwhitton@spwhitton.name \
    --cc=emacs-devel@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 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.