From: "Mikael Magnusson" <mikachu@gmail.com>
To: zsh-workers <zsh-workers@sunsite.dk>
Subject: "show" completion et al spammy when binaries don't exist
Date: Sat, 12 Jan 2008 21:57:35 +0100 [thread overview]
Message-ID: <237967ef0801121257s6a478358k897be96f607b7408@mail.gmail.com> (raw)
I was looking at another window while writing and typed
show show gi<tab>
instead of git show gi<tab> and got the following:
% show show gi_mh:1: command not found: mhpath
_mh:1: command not found: mhparam
_mh:1: command not found: mhpath
_mh:1: command not found: mhparam
_mh:1: command not found: mhpath
_mh:1: command not found: mhparam
_mh:1: command not found: mhpath
_mh:1: command not found: mhparam
show show gi<cursor here>
---- no match for: `sequence' or `corrections'
After the error messages the prompt wasn't redrawn correctly, but I
think that is expected. In _mh all commands are called with 2>
/dev/null, but that doesn't help much since zsh is the one to print
the messages. Which leads me to ask, is the stderr output of
completion scripts ever wanted in the terminal? Maybe it should be
redirected more centrally? Putting
which mhpath >& /dev/null || return
on the first line of _mh fixes the problem, I don't know if some other
method would be preferred. It seems _git also suffers from this
problem. Typing apt-get install <tab> repeatedly inserts a space. Are
these sort of things to be considered as problems, or am I stupid to
press tab after a command I don't have?
--
Mikael Magnusson
next reply other threads:[~2008-01-12 20:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-12 20:57 Mikael Magnusson [this message]
2008-01-14 9:49 ` Peter Stephenson
2008-01-14 16:11 ` Bart Schaefer
2008-01-14 16:16 ` Peter Stephenson
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=237967ef0801121257s6a478358k897be96f607b7408@mail.gmail.com \
--to=mikachu@gmail.com \
--cc=zsh-workers@sunsite.dk \
/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).