From: Bart Schaefer <schaefer@brasslantern.com>
To: zsh-workers@zsh.org
Cc: Daniel Shahaf <d.s@daniel.shahaf.name>
Subject: Re: Unexpected behavior for completion funcion _remote_files()
Date: Thu, 3 Nov 2016 08:37:37 -0700 [thread overview]
Message-ID: <161103083737.ZM14522@torch.brasslantern.com> (raw)
In-Reply-To: <20161103145909.GA13594@fujitsu.shahaf.local2>
On Nov 3, 2:59pm, Daniel Shahaf wrote:
} Subject: Re: Unexpected behavior for completion funcion _remote_files()
}
} > + [[ args[-1] = -- ]] && args[-1]=()
That's an obvious typo, it should be $args[-1] ...
Hardly seems worth sending a patch.
prev parent reply other threads:[~2016-11-03 21:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-06 14:34 Yoshio Hanawa
2016-09-06 15:55 ` Oliver Kiddle
2016-09-06 17:26 ` Yoshio Hanawa
2016-09-06 22:16 ` Daniel Shahaf
2016-09-12 15:30 ` Oliver Kiddle
2016-11-03 14:59 ` Daniel Shahaf
2016-11-03 15:37 ` Bart Schaefer [this message]
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=161103083737.ZM14522@torch.brasslantern.com \
--to=schaefer@brasslantern.com \
--cc=d.s@daniel.shahaf.name \
--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).