From: Bart Schaefer <schaefer@brasslantern.com>
To: zsh-workers@zsh.org
Subject: Re: Tab-completion problem through ssh when files start by dash (_remote_files:compadd:80: bad option: -@)
Date: Sat, 15 Apr 2017 08:59:57 -0700 [thread overview]
Message-ID: <170415085957.ZM22500@torch.brasslantern.com> (raw)
In-Reply-To: <20170415011902.GB12706@fujitsu.shahaf.local2>
On Apr 15, 1:19am, Daniel Shahaf wrote:
}
} The "-R remote-func" option seems to be the most obvious method of
} injection. I'm not sure whether it requires a literal function name, or
} whether an anonymous function would be accepted too.
It's remove-func, not remote-func ... and it does have to be a literal
function name, it is not "eval"'d.
next prev parent reply other threads:[~2017-04-15 15:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-13 17:47 Antoine Amarilli
2017-04-15 1:19 ` Daniel Shahaf
2017-04-15 15:59 ` Bart Schaefer [this message]
2017-04-16 19:08 ` Antoine Amarilli
2017-04-16 20:14 ` Daniel Shahaf
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=170415085957.ZM22500@torch.brasslantern.com \
--to=schaefer@brasslantern.com \
--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).