From: Kurtis Rader <krader@skepticism.us>
To: Zsh Users <zsh-users@zsh.org>
Subject: "unsetopt multifuncdef" breaks tab completion
Date: Tue, 27 Oct 2015 18:46:52 -0700 [thread overview]
Message-ID: <CABx2=D9c=LxzLcAuNiZKcpgpdNp4ydrDv4pBuC4ycugZWpy3VA@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1214 bytes --]
There was a recent thread about how someone executed
$ git add foo().bar
and was surprised to end up with three functions named "git", "add", and
"foo". So I decided to add
unsetopt multifuncdef
to my ~/.zshrc as one person who replied suggested to avoid that surprising
behavior. Imagine my surprise when a few days later I rebooted my computer
and found that any attempt to perform tab-completion resulted in this error:
_main_complete:143: parse error near `()'
I'm sorry but that's the final straw to break this camel's back. I've
either personally experienced, or read about others experiencing, too many
problems of that nature. I'm going to switch to a shell whose behavior is
not impossible to understand or predict.
http://www.skepticism.us/2015/10/its-time-to-replace-zsh-with-a-saner-shell-because-unsetopt-multifuncdef-breaks-tab-completion/
P.S., Yes, I understand I could simply file a bug report to make the
standard completion code robust in the face of a user unsetting that
option. The point is that this is not an isolated incident. It reflects a
fundamental problem with zsh trying to be all things to all people.
--
Kurtis Rader
Caretaker of the exceptional canines Junior and Hank
next reply other threads:[~2015-10-28 1:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-28 1:46 Kurtis Rader [this message]
2015-10-28 2:15 ` Bart Schaefer
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='CABx2=D9c=LxzLcAuNiZKcpgpdNp4ydrDv4pBuC4ycugZWpy3VA@mail.gmail.com' \
--to=krader@skepticism.us \
--cc=zsh-users@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).