unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Paul Pogonyshev <pogonyshev@gmail.com>
To: Filipp Gunbin <fgunbin@fastmail.fm>
Cc: 58758@debbugs.gnu.org
Subject: bug#58758: dired command ! fails in a remote directory
Date: Tue, 25 Oct 2022 10:56:08 +0200	[thread overview]
Message-ID: <CAG7BparZYobXabSa_J2h4t0aOb_0nnUoY0D-ziR0ACWJfeTK=g@mail.gmail.com> (raw)
In-Reply-To: <m2mt9ktzqv.fsf@fastmail.fm>

[-- Attachment #1: Type: text/plain, Size: 1043 bytes --]

Rebuilt Emacs from the latest Git commit, doesn't happen anymore. Maybe it
got fixed as a side-effect of this commit (06.10):

87301f2623 Better support for remote file names in dired

Paul

On Tue, 25 Oct 2022 at 04:15, Filipp Gunbin <fgunbin@fastmail.fm> wrote:

> On 24/10/2022 17:01 +0200, Paul Pogonyshev wrote:
>
> > GNU Emacs 29.0.50 (build 1, x86_64-pc-linux-gnu, GTK+ Version 2.24.33,
> > cairo version 1.16.0) of 2022-09-14
> >
> > To reproduce:
> >
> > 1. $ emacs -Q /ssh:ANY-REMOTE-DIRECTORY-WITH-FILES
> > 2. Move point to a file, let's say it is called XYZ
> > 3. Run ! "ls" RET -> 'ls' gives an error, because it gets a Emacs-style
> > remote path, which it of course doesn't understand.
> >
> > So, Emacs command doesn't fail per se, but it invokes shell commands in
> > such a way they cannot succeed.
> >
> > For comparison, M-! "ls XYZ" RET works fine.
> >
> > Paul
>
> I cannot reproduce this with latest master, ssh-ing to Debian Bullseye.
>
> Perhaps you should give more details about your target machine.
>
> Thanks.
>

[-- Attachment #2: Type: text/html, Size: 1543 bytes --]

  reply	other threads:[~2022-10-25  8:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-24 15:01 bug#58758: dired command ! fails in a remote directory Paul Pogonyshev
2022-10-25  2:15 ` Filipp Gunbin
2022-10-25  8:56   ` Paul Pogonyshev [this message]
2022-10-25 10:10     ` 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

  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='CAG7BparZYobXabSa_J2h4t0aOb_0nnUoY0D-ziR0ACWJfeTK=g@mail.gmail.com' \
    --to=pogonyshev@gmail.com \
    --cc=58758@debbugs.gnu.org \
    --cc=fgunbin@fastmail.fm \
    /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).