From: Ellenor Bjornsdottir <ellenor-zshw@umbrellix.net>
To: Bart Schaefer <schaefer@brasslantern.com>,
Ray Andrews <rayandrews@eastlink.ca>
Cc: zsh-users@zsh.org
Subject: Re: empty pipes
Date: Fri, 16 Dec 2022 01:17:46 +0000 [thread overview]
Message-ID: <07cdf2f3-34e1-f8bc-53c2-96f492911521@umbrellix.net> (raw)
In-Reply-To: <CAH+w=7aX_mOshwAX8RBABZ=G9RyyzXOckvkh7WzDLFSNGS1DwA@mail.gmail.com>
In the alternative, you can build the string used to execute the
pipeline piecemeal?
On 12/13/22 02:04, Bart Schaefer wrote:
> On Mon, Dec 12, 2022 at 6:02 AM Ray Andrews <rayandrews@eastlink.ca> wrote:
>> BTW, do we have hard spaces?
> That's up to the terminal and the context. Zsh normally doesn't
> output special characters like non-breaking spaces but since you refer
> to ...
>
>> certain columnizing situations
> ... I would presume you're controlling the output, so you could place
> $'\u00a0' wherever you need it.
>
> Most terminals are going to wrap at the right margin even for
> non-breaking spaces, so unless you're using a proportional font for
> some reason, ASCII spaces are likely just as good.
>
--
Ellenor Agnes Bjornsdottir (she)
sysadmin umbrellix.net
jabber: ellenor ~on~ umbrellix.net
prev parent reply other threads:[~2022-12-16 1:19 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-12 3:17 Ray Andrews
2022-12-12 3:40 ` Bart Schaefer
2022-12-12 14:01 ` Ray Andrews
2022-12-13 2:04 ` Bart Schaefer
2022-12-14 13:05 ` Are there zsh error message explanation Xiao Ling XL Chen
2022-12-15 21:18 ` Daniel Shahaf
2022-12-16 3:28 ` Bart Schaefer
2022-12-16 3:53 ` Ray Andrews
2022-12-16 4:07 ` Bart Schaefer
2022-12-16 14:16 ` Ray Andrews
2022-12-16 12:47 ` Daniel Shahaf
2022-12-16 14:00 ` Ray Andrews
2022-12-16 1:17 ` Ellenor Bjornsdottir [this message]
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=07cdf2f3-34e1-f8bc-53c2-96f492911521@umbrellix.net \
--to=ellenor-zshw@umbrellix.net \
--cc=rayandrews@eastlink.ca \
--cc=schaefer@brasslantern.com \
--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).