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: Wed, 27 Mar 2024 19:37:00 -0400 [thread overview]
Message-ID: <CAFsbZ7a1TNPmZ4POjSUL7ojkf7LcLB1i9QHiFfR_FT_iKaMF3A@mail.gmail.com> (raw)
In-Reply-To: <86v859hr60.fsf@gnu.org>
which bash builds are supported on windows?
On Tue, 26 Mar 2024 at 12:52, Eli Zaretskii <eliz@gnu.org> wrote:
>
> tags 70012 notabug wontfix
> thanks
>
> > From: Sam Steingold <sds@gnu.org>
> > Date: Tue, 26 Mar 2024 12:25:13 -0400
> >
> > Windows emacs 29.2
> > Msys2 bash dirs returns something like "/c/foo" for "c:/foo" and (file-directory-p "/c/foo") returns nil even
> > though "c:/foo" is a directory.
> > Thus shell-resync-dirs goes into an infinite loop.
>
> Sorry, the native Windows build of Emacs is not supposed to support
> MSYS- or Cygwin-specific magic in file names. We cannot support that
> without significant complications in the low-level code, and even if
> that code can be made to work, users are not supposed to give up
> top-level directories named /x (where 'x' is a letter).
>
> If you want these names supported, try the Cygwin or Cygw32 build
> instead (but I'm not sure even those builds support /c/foo/bar file
> names).
>
> This is not a bug, and we should not even try fixing it. IOW, using
> MSYS Bash in shell buffers is not supported in the MS-Windows build.
--
Sam Steingold <http://sds.podval.org> <http://www.childpsy.net>
<http://steingoldpsychology.com>
next prev parent reply other threads:[~2024-03-27 23:37 UTC|newest]
Thread overview: 8+ 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 [this message]
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
2024-10-05 1:19 ` Stefan Kangas
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=CAFsbZ7a1TNPmZ4POjSUL7ojkf7LcLB1i9QHiFfR_FT_iKaMF3A@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 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.