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

On 5/8/21 9:48 AM, Eli Zaretskii wrote:
>> Cc: michael.albinus@gmx.de, emacs-devel@gnu.org, shivers@cs.cmu.edu,
>>   jason.kim@revtera.com
>> From: Jason Kim <jason.w.kim@icloud.com>
>> Date: Sat, 8 May 2021 09:39:48 -0700
>>
>>> Sorry, I don't think I understand.  My understanding was that this
>>> feature is supported by some shells whose names are known in advance
>>> (like zsh), so Emacs could compute the value as appropriate for that
>>> shell without asking the user to set it.  If this is not a good idea,
>>> can you explain why?
>>>
>>
>> Hi, sorry for the confusion -
>> auto-cd feature in zsh is optional. It is not on by default, and I don't
>> know of a good way to detect whether a zsh process tied to a shell
>> buffer has that option turned on.
> 
> Can't you ask zsh itself, by running some command once, when the mode
> is turned on?
> 

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:19 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 [this message]
2021-05-08 17:58             ` Jason Kim

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=2a15023f-94b3-4726-6cc8-d7a8dd8e5aaa@icloud.com \
    --to=jason.w.kim@icloud.com \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=jason.kim@revtera.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).