all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Jim Porter <itsjimporter@gmail.com>
To: Andreas Hiller <andreash8577@gmail.com>, Eli Zaretskii <eliz@gnu.org>
Cc: 20165-done@debbugs.gnu.org
Subject: bug#20165: eshell completion bug in emacs 24.4.1 on windows
Date: Wed, 8 Mar 2023 18:28:13 -0800	[thread overview]
Message-ID: <3f49bcfe-2ec6-eafb-d815-5ead2845533d@gmail.com> (raw)
In-Reply-To: <CAJE=upyGfDQxYw0GHqn9-GdW9=c8mqgjAuVbcKMdq8bFiq0aeQ@mail.gmail.com>

On 3/22/2015 12:34 PM, Andreas Hiller wrote:
> Mainly when i pasting paths from clipboard. Eshell can handle backslash.
> 
> Eli Zaretskii <eliz@gnu.org <mailto:eliz@gnu.org>> schrieb am So., 22. 
> März 2015 um 19:09 Uhr:
> 
>      > From: Andreas Hiller <andreash8577@gmail.com
>     <mailto:andreash8577@gmail.com>>
>      > Date: Sun, 22 Mar 2015 11:34:28 +0000
>      >
>      > There is a problem on path completion in emacs on windows. See
>     following gif:
>      > http://imgur.com/t7T0pBp <http://imgur.com/t7T0pBp>
>      >
>      > It moves the path one char to the left.
> 
>     Why are you using backslashes in Eshell?

This issue is resolved as of Emacs 28.2 (or possibly earlier). On MS 
Windows, if I type "cd C:\Windows" in Eshell and press TAB, it completes 
to "cd c:/Windows/" with the space after "cd" preserved correctly, which 
is what I'd expect.

Closing this issue now, though if there are still problems, just let me 
know.

(Note that since "\" is the escape character in Eshell, you need to be 
careful about using it as the directory separator in general, but I 
don't think that's really a bug; just a thing for MS Windows users to be 
aware of.)





      reply	other threads:[~2023-03-09  2:28 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-22 11:34 bug#20165: eshell completion bug in emacs 24.4.1 on windows Andreas Hiller
2015-03-22 18:08 ` Eli Zaretskii
2015-03-22 19:34   ` Andreas Hiller
2023-03-09  2:28     ` Jim Porter [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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3f49bcfe-2ec6-eafb-d815-5ead2845533d@gmail.com \
    --to=itsjimporter@gmail.com \
    --cc=20165-done@debbugs.gnu.org \
    --cc=andreash8577@gmail.com \
    --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.