From: Michael Albinus <michael.albinus@gmx.de>
To: ken <gebser@mousecar.com>
Cc: help-gnu-emacs@gnu.org
Subject: Re: can't see existing directory on remote machine... workaround
Date: Sat, 10 Oct 2020 11:00:30 +0200 [thread overview]
Message-ID: <87mu0uh2vl.fsf@gmx.de> (raw)
In-Reply-To: <36b6f1d9-f5ae-688b-7839-b2ccaa3ac9b1@mousecar.com> (ken's message of "Fri, 9 Oct 2020 14:19:17 -0400")
ken <gebser@mousecar.com> writes:
Hi Ken,
>>
>>> I found a workaround... I change the default, inserting "scp:" ... e.g.,
>>> "/remo:~/dir/dir2/" -> "/scp:remo:~/dir/dir2/". I doubt, however, that
>>> this workaround will change the emacs code.
>>>
>>> "/remo:~/dir/dir2/"
>> I don't know whether adding "/scp:" counts as a workaround. But for sure
>> "/remo:~/dir/dir2/" is not remote directory, a leading connection method
>> (like "scp") is mandatory.
>>
>
> Well, then it should have been put in place automatically by emacs and
> it wasn't.
"Emacs" doesn't put anything in place automatically. Which package do
you have in mind, which shall "put in place" this automatically?
IOW, could you pls give us a reproducible scenario, starting with
"emacs -Q"?
Best regards, Michael.
next prev parent reply other threads:[~2020-10-10 9:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-08 15:17 can't see existing directory on remote machine ken
2020-10-08 15:43 ` can't see existing directory on remote machine... workaround ken
2020-10-08 17:31 ` Michael Albinus
2020-10-09 18:19 ` ken
2020-10-10 9:00 ` Michael Albinus [this message]
2020-10-11 12:17 ` ken
2020-10-11 14:00 ` Michael Albinus
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=87mu0uh2vl.fsf@gmx.de \
--to=michael.albinus@gmx.de \
--cc=gebser@mousecar.com \
--cc=help-gnu-emacs@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.
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).