From: "Richard M. Stallman" <rms@gnu.org>
Cc: tramp-devel@gnu.org, emacs-devel@gnu.org
Subject: Re: tramp (2.0.51); tramp and file-name-all-completions
Date: Sun, 16 Oct 2005 13:36:47 -0400 [thread overview]
Message-ID: <E1ERCRD-0002MQ-Sz@fencepost.gnu.org> (raw)
In-Reply-To: <m3fyr28nj3.fsf@kfs-l.imdomain.dk> (storm@cua.dk)
I would say these problems are all bugs in tramp.
file-name-all-completions has a simple spec,
and in principle it ought to work "right" for all meaningful args.
If there are some cases where it is just hopeless to ask tramp
to do completion correctly, we could decide on some return value
that means "unable to do the job right".
next prev parent reply other threads:[~2005-10-16 17:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-15 21:42 tramp (2.0.51); tramp and file-name-all-completions Kim F. Storm
2005-10-16 17:36 ` Richard M. Stallman [this message]
2005-10-16 19:56 ` Michael Albinus
2005-10-16 21:43 ` Kim F. Storm
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=E1ERCRD-0002MQ-Sz@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=tramp-devel@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).