unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Sean Whitton <spwhitton@spwhitton.name>
To: Jim Porter <jporterbugs@gmail.com>,
	emacs-devel@gnu.org, Philip Kaludercic <philipk@posteo.net>
Subject: Re: New optional Eshell module: em-elecslash
Date: Tue, 19 Apr 2022 08:28:29 -0700	[thread overview]
Message-ID: <87h76pw0rm.fsf@athena.silentflame.com> (raw)
In-Reply-To: <2584c40d-590f-e012-c8c5-d16bf5edbeb2@gmail.com>

Hello,

On Sat 16 Apr 2022 at 11:24pm -07, Jim Porter wrote:

> On 4/16/2022 11:57 AM, Sean Whitton wrote:
>> Here is my new module, which I'd like to install on master.
>
> Cool, this looks like it should be really helpful for making Lisp
> commands and external commands more consistent. This seems similar to an
> entry in Eshell's "Bug and Ideas" section in the manual too:
>
>    @item Make @kbd{/} electric
>
>    So that it automatically expands and corrects pathnames.  Or make
>    pathname completion for Pcomplete auto-expand @samp{/u/i/std@key{TAB}} to
>    @samp{/usr/include/std@key{TAB}}.
>
> The entry is pretty brief, so I'm not sure exactly how it would be
> expected to work in all cases, but it might be some food for thought. If
> nothing else, it'd probably be worth removing (or updating?) that entry.

Thanks, I didn't see this section.

I think that's actually referring to something else -- just general
pathname completion, expansion and correction, not TRAMP prefixes.  I'll
edit it appropriately though.

-- 
Sean Whitton



      reply	other threads:[~2022-04-19 15:28 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-27  2:48 Optional Eshell modules -- to emacs.git or ELPA? Sean Whitton
2022-01-29 11:51 ` 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 [this message]

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=87h76pw0rm.fsf@athena.silentflame.com \
    --to=spwhitton@spwhitton.name \
    --cc=emacs-devel@gnu.org \
    --cc=jporterbugs@gmail.com \
    --cc=philipk@posteo.net \
    /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).