From: Sam Steingold <sds@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 70012@debbugs.gnu.org
Subject: bug#70012: shell-resync-dirs broken on windows
Date: Fri, 29 Mar 2024 10:54:10 -0400 [thread overview]
Message-ID: <CAFsbZ7adoiut9H_BsfYh9O4g2EMag2upyVrpoabRunHN_NWRzw@mail.gmail.com> (raw)
In-Reply-To: <86ttkpdvss.fsf@gnu.org>
On Fri, 29 Mar 2024 at 09:14, Eli Zaretskii <eliz@gnu.org> wrote:
> > finally, the following patch fixes the bug for me:
> >
> > --- shell.el~ 2024-03-06 12:13:15.134281800 -0500
> > +++ shell.el 2024-03-28 11:50:32.920026000 -0400
> > @@ -711,6 +711,7 @@
> > ((string-equal shell "ksh") "echo $PWD ~-")
> > ;; Bypass any aliases. TODO all shells could use this.
> > ((string-equal shell "bash") "command dirs")
> > + ((string-equal shell "bash.exe") "command pwd -W")
> > ((string-equal shell "zsh") "dirs -l")
> > (t "dirs")))
> > ;; Bypass a bug in certain versions of bash.
> >
> > may I push it?
>
> That's not really TRT, because it assumes every bash.exe is an MSYS
> program (which might not be true: there's a Cygwin Bash, for example).
I am pretty sure they are compatible in this way.
> And we don't need to make such assumptions:
>
> (w32-application-type (executable-find "bash.exe"))
> => msys
>
> I'm okay with installing the fix after you change it to use
> w32-application-type (and verifying that it works in your case, of
> course: I don't have MSYS2 Bash installed).
done.
> > Incidentally, why do you use `dirs` instead of `pwd` there?
> > you use only the last dir anyway.
>
> I don't know, I'm not familiar with shell.el well enough. Just by
> looking at the code, shell-resync-dirs does need to know all the
> stack, so it could refresh the value of shell-dirstack, no?
nope.
`pwd` is already used for sh and ksh.
only the last line of `dirs` output is ever used.
prev parent reply other threads:[~2024-03-29 14:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-26 16:25 bug#70012: shell-resync-dirs broken on windows Sam Steingold
2024-03-26 16:52 ` Eli Zaretskii
2024-03-27 23:37 ` Sam Steingold
2024-03-28 6:59 ` Eli Zaretskii
2024-03-29 12:17 ` Sam Steingold
2024-03-29 13:14 ` Eli Zaretskii
2024-03-29 14:54 ` Sam Steingold [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=CAFsbZ7adoiut9H_BsfYh9O4g2EMag2upyVrpoabRunHN_NWRzw@mail.gmail.com \
--to=sds@gnu.org \
--cc=70012@debbugs.gnu.org \
--cc=eliz@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 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).