unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Jason Kim <jason.kim@revtera.com>
To: Jason Kim <jason.w.kim@icloud.com>, Eli Zaretskii <eliz@gnu.org>
Cc: michael.albinus@gmx.de, shivers@cs.cmu.edu, emacs-devel@gnu.org
Subject: Re: Small shell-mode patch to handle auto-cd (e.g. shells like zsh)
Date: Sat, 8 May 2021 10:58:39 -0700	[thread overview]
Message-ID: <5f1f7466-c038-d7f6-1743-ca998d2b52e1@revtera.com> (raw)
In-Reply-To: <2a15023f-94b3-4726-6cc8-d7a8dd8e5aaa@icloud.com>

On 5/8/21 10:19 AM, Jason Kim wrote:

Eli,
Hi, I'd like to walk back anything that may seem like a criticism. I did 
not mean to imply any such, and apologies if you were taken aback.

The main point here simply is that AFAIK, the switch is the simplest, 
least intrusive way to get this very small support capability in to 
shell mode, and that additional upgrades are perfectly possible, but 
IMHO not apropos at the moment.

Thanks again,
and hopefully you guys are ok with it.

-Jason


> Sure, I suppose, but why do it? I'm a zsh user and I'm perfectly fine 
> with it as a switch that I can put in my .emacs :-)
> 
> and hijacking comint like that can add glitches, and introduce 
> irreproducibility (I automate creation of shells, pasting commands to 
> comint etc..).
> 
> Auto injecting commands to what should be a user-input space seems a bit 
> wierd just to support this feature, and may not be optimal, because it 
> is unexpected
> 
> I'd be happy to help with this improvement, if that's REALLY what you 
> want but it can add glitches to user's automation of shells, but I don't 
> think its necessary (for now), and I humbly request we punt on it.
> 
> Thanks!
> -Jason
> 



      reply	other threads:[~2021-05-08 17:58 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-05 19:55 Small shell-mode patch to handle auto-cd (e.g. shells like zsh) Jason Kim
2021-05-06  8:10 ` Michael Albinus
2021-05-06  8:23 ` Eli Zaretskii
2021-05-07 16:35   ` Jason Kim
2021-05-07 16:51     ` Jason Kim
2021-05-15  8:20       ` Eli Zaretskii
2021-05-24 17:15         ` Jason Kim
2021-05-24 17:20           ` Jason Kim
2021-05-25  7:38             ` Michael Albinus
2021-05-27 17:09               ` Jason Kim
2021-06-09 11:03                 ` Michael Albinus
2021-05-07 17:39     ` Michael Albinus
2021-05-08  6:36     ` Eli Zaretskii
2021-05-08 16:39       ` Jason Kim
2021-05-08 16:48         ` Eli Zaretskii
2021-05-08 17:19           ` Jason Kim
2021-05-08 17:58             ` Jason Kim [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=5f1f7466-c038-d7f6-1743-ca998d2b52e1@revtera.com \
    --to=jason.kim@revtera.com \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=jason.w.kim@icloud.com \
    --cc=michael.albinus@gmx.de \
    --cc=shivers@cs.cmu.edu \
    /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).