From: Michael Albinus <michael.albinus@gmx.de>
To: Kevin Ryde <user42@zip.com.au>
Cc: 5198@debbugs.gnu.org
Subject: bug#5198: 23.1; find-file tramp ipv6 not a wildcard
Date: Sun, 20 Dec 2009 11:40:51 +0100 [thread overview]
Message-ID: <87tyvm6i8c.fsf@gmx.de> (raw)
In-Reply-To: <87my1h5onf.fsf@blah.blah> (Kevin Ryde's message of "Fri, 18 Dec 2009 07:30:44 +1100")
Kevin Ryde <user42@zip.com.au> writes:
> Michael Albinus <michael.albinus@gmx.de> writes:
>>
>> I've added a check in `file-expand-wildcards' to handle this case.
>
> Would find-file-noselect look at
>
> (file-remote-p filename 'localname)
>
> like file-expand-wildcards now too?
No necessarily. It calls itself recursively with the result of
file-expand-wildcards.
> And/or would there be merit in a function that checked if there's
> wildcards in a filename (ie. anything file-expand-wildcards could
> expand), rather than a string-match? It might help if new wildness was
> added one day, like bash style {xx,yy,zz} alternations or something.
Maybe. OTOH, one could introduce it, when the need arises.
Best regards, Michael.
next prev parent reply other threads:[~2009-12-20 10:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <9utyuqomkl.fsf@fencepost.gnu.org>
2009-12-13 0:01 ` bug#5198: 23.1; find-file tramp ipv6 not a wildcard Kevin Ryde
[not found] ` <87d42drb0u.fsf@gmx.de>
[not found] ` <87my1h5onf.fsf@blah.blah>
2009-12-20 10:40 ` Michael Albinus [this message]
2010-01-13 0:51 ` bug#5255: marked as done (23.1.90; Wrong prompt in term) Emacs bug Tracking System
2010-01-07 19:07 ` bug#5334: 23.1.91; Term mode prints "0; user@host:~" before each prompt of an interactive SSH session Scott Bell
2010-01-07 21:37 ` Dan Nicolaescu
2010-01-08 17:03 ` Scott Bell
2010-01-08 19:13 ` Dan Nicolaescu
2010-01-08 19:25 ` Scott Bell
2010-01-13 0:51 ` bug#5334: marked as done (23.1.91; Term mode prints "0;user@host:~" before each prompt of an interactive SSH session) Emacs bug Tracking System
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=87tyvm6i8c.fsf@gmx.de \
--to=michael.albinus@gmx.de \
--cc=5198@debbugs.gnu.org \
--cc=user42@zip.com.au \
/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.