Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: PATCH: Avoid \e in C code; building on Solaris 11
- X-seq: zsh-workers 52395
- From: Bart Schaefer <schaefer@xxxxxxxxxxxxxxxx>
- To: Zsh workers <zsh-workers@xxxxxxx>
- Subject: Re: PATCH: Avoid \e in C code; building on Solaris 11
- Date: Sat, 9 Dec 2023 16:29:48 -0800
- Archived-at: <https://zsh.org/workers/52395>
- In-reply-to: <18413-1702163086.421549@hzMt.-XQg.ucw2>
- List-id: <zsh-workers.zsh.org>
- References: <50885-1702060132.779123@YSiF.CgC_.vGLi> <CAH+w=7ZuvPdqnTVvpZmhW=khZekc6DiTxM6ai6Hi0cmDnfNh5A@mail.gmail.com> <CAH+w=7Yx4CcaZt2qFG_69mtrJRQT=gWFoajb5aMA5EQV5AUATw@mail.gmail.com> <18413-1702163086.421549@hzMt.-XQg.ucw2>
On Sat, Dec 9, 2023 at 3:04 PM Oliver Kiddle <opk@xxxxxxx> wrote:
>
> Incidentally, I tried whether the new ${ print -x4 $foo } form might
> also work here and it results in an extra trailing blank line in each
> case. Is that difference expected?
Yes, ${ ... } is defined to not strip trailing newlines the way $(...)
does. I first had the new form too but decided $(...) was more
obvious than using "print -n". If you don't need current-shell
semantics, it's a toss-up whether a subshell or a temp file read/write
is going to be more efficient.
No objection to the diff_arg patch on my part.
Messages sorted by:
Reverse Date,
Date,
Thread,
Author