From: Bart Schaefer <schaefer@brasslantern.com>
To: Peter Stephenson <p.stephenson@samsung.com>
Cc: "zsh-workers@zsh.org" <zsh-workers@zsh.org>,
Jan Kryl <jan.kryl@nexenta.com>
Subject: Re: autocompletion is broken in restricted shell
Date: Mon, 8 May 2017 11:03:05 -0700 [thread overview]
Message-ID: <CAH+w=7Y-pOBRPDENTXidtc9ALe6QV1Jis+2UbqOjEdnWB1DAqg@mail.gmail.com> (raw)
In-Reply-To: <20170508174847.6fe6b571@pwslap01u.europe.root.pri>
On Mon, May 8, 2017 at 9:48 AM, Peter Stephenson
<p.stephenson@samsung.com> wrote:
> On Mon, 8 May 2017 11:38:37 +0200
> Jan Kryl <jan.kryl@nexenta.com> wrote:
>> That can be avoided by using 2>&- instead of 2>/dev/null.
>
> I'm not sure if you're realistically going to get an error message from
> there as long as the shell supports that syntax, so it's probably
> reasonable to apply this and see what happens.
Although this won't matter 90+% of the time because "enable" rarely
emits an error, I think it's going to complain when there IS an error:
% () { print -u2 OOPS } 2>&-
zsh: write error
If you're going to get error output anyway, you might as well drop the
2> and get *useful* error output.
However, there are a zillion other places in completion where we
redirect stderr to /dev/null, so changing that single one in compinit
isn't going to fix the general problem.
next prev parent reply other threads:[~2017-05-08 18:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20170508093906epcas5p35e1b5c235b94e4b754107d42c915e638@epcas5p3.samsung.com>
2017-05-08 9:38 ` Jan Kryl
2017-05-08 16:48 ` Peter Stephenson
2017-05-08 18:03 ` Bart Schaefer [this message]
2017-05-10 5:02 ` Bart Schaefer
2017-05-10 8:48 ` 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='CAH+w=7Y-pOBRPDENTXidtc9ALe6QV1Jis+2UbqOjEdnWB1DAqg@mail.gmail.com' \
--to=schaefer@brasslantern.com \
--cc=jan.kryl@nexenta.com \
--cc=p.stephenson@samsung.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).