Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: PATCH: complete probes for dtrace completion
- X-seq: zsh-workers 48245
- From: Jun T <takimoto-j@xxxxxxxxxxxxxxxxx>
- To: zsh-workers@xxxxxxx
- Subject: Re: PATCH: complete probes for dtrace completion
- Date: Thu, 25 Mar 2021 10:58:12 +0900
- Archived-at: <https://zsh.org/workers/48245>
- Archived-at: <http://www.zsh.org/sympa/arcsearch_id/zsh-workers/2021-03/E3DF913B-B0A7-422D-9124-3F588F358339%40kba.biglobe.ne.jp>
- In-reply-to: <60652-1616629351.828535@4m9W.f13N.UI31>
- List-id: <zsh-workers.zsh.org>
- References: <35706-1616539392.227174@49wn.5333.Rj93> <C8039B3F-B36A-427F-ABA6-C1A7E7E3D9EB@kba.biglobe.ne.jp> <60652-1616629351.828535@4m9W.f13N.UI31>
> 2021/03/25 8:42、Oliver Kiddle <opk@xxxxxxx>のメール:
>
> Since 5.0.8, _call_program sends stderr to /dev/null by default and
> requires 2>&1 to preserve it. Were you actually getting the errors
> dumped from _dtrace?
Sorry, I have a vague memory that I got the warning after
'dtrace -n<TAB>' but I can't reproduce it (by removing 2>/dev/null).
(Just my memory is wrong, or I did something wrong with 'sudu zsh'.)
Messages sorted by:
Reverse Date,
Date,
Thread,
Author