From: "Jun T." <takimoto-j@kba.biglobe.ne.jp>
To: zsh-workers@zsh.org
Subject: Re: bug report about zsh
Date: Tue, 21 Aug 2018 02:20:46 +0900 [thread overview]
Message-ID: <F96F21D1-EB8D-44C1-B7F2-B57B883ADB4A@kba.biglobe.ne.jp> (raw)
In-Reply-To: <CAJbOvNxbshEc=YMe5BKUYfM7k3BGfWh=z8Jw7Acw5GnWRuTw_w@mail.gmail.com>
> 2018/08/20 10:56, air azure <blucmt@gmail.com> wrote:
>
> Mount sshfs from an ipv6 server, on zsh you input
> sshfs xxxx@[yyyy:yy::yy]:/zzz ~/remote
>
> zsh report back
> zsh: no matches found: xxxx@[yyyy:yy::yy]:/zzz
[1] (reply to azure) This is not a bug:
As you know, '[...]' on the command line is considered as a
file name generation pattern (glob pattern) like '*' and '?'.
Consider, for example, a pattern f[aio]x. If there are files
named 'fax', 'fix' or 'fox' then the pattern is replaced by
(a list of) those file names. But if none of the files exists
then (by default) bash leaves the pattern as is, i.e.,
echo f[aio]x
will print 'f[aio]x', while zsh gives 'no match found' warning.
You can change this default behavior by
zsh% unsetopt nomatch
But it would be better to escape the pattern, as
zsh% sshfs 'xxxx@[yyyy:yy::yy]:/zzz' ~/remote
or
zsh% sshfs xxxx@\[yyyy:yy::yy\]:/zzz ~/remote
[2] But (to zsh workers)
The current completion function for the sshfs command does not
work well with numeric IPv6 addresses. For example, If we use
zsh% zstyle ':completion:*:sshfs:*:accounts' users-hosts \
'foo@12.34.56.78' 'bar@[12:34::5678]'
then
zsh% sshfs f<TAB>
works but
zsh% sshfs b<TAB>
does not. This is due to the option -s '[:@]' passed to
_combination in _user_at_host.
Do we need to fix this? If so, then how? Can we just remove
the ':' from the pattern [:@] ?
next prev parent reply other threads:[~2018-08-20 17:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-20 1:56 air azure
2018-08-20 17:20 ` Jun T. [this message]
2018-08-20 17:30 ` Bart Schaefer
2018-08-21 3:24 ` Jun T
2018-08-21 10:36 ` Daniel Shahaf
2018-08-22 11:43 ` Jun T
2018-08-22 15:33 ` Sebastian Gniazdowski
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=F96F21D1-EB8D-44C1-B7F2-B57B883ADB4A@kba.biglobe.ne.jp \
--to=takimoto-j@kba.biglobe.ne.jp \
--cc=zsh-workers@zsh.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.vuxu.org/mirror/zsh/
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 NNTP newsgroup(s).