zsh-users
 help / color / mirror / code / Atom feed
From: Ray Andrews <rayandrews@eastlink.ca>
To: zsh-users@zsh.org
Subject: Re: create variable with calculated number of spaces.
Date: Tue, 7 May 2024 07:56:10 -0700	[thread overview]
Message-ID: <255c5dbd-c8d3-4cf7-bcec-6a3c1cfc8e71@eastlink.ca> (raw)
In-Reply-To: <CAN=4vMpQ1UYZC0T6_ago_UgTLE99TWbgG9X=YRybz839iD-8-w@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 874 bytes --]



On 2024-05-06 22:52, Roman Perepelitsa wrote:
> You don't need to "cobble together complicated variables" here. Just
> printf straight away to stdout.
I know, I  mean in other situations where the variable really is 
complicated.  I've seen 'printf  -v' offered previously to do some 
pretty fancy stuff.

>      % n=10
>      % y=${(r:n:: :)}  # n spaces
>      % x='hello'
>      % z=${(r:n:: :)x}  # right-justified x
Jim Murphy offered:

         spacer=${(l:diff:::: :)}

... very much in the same school of thought.  Feels more 'direct', if 
that means anything.  Mark suggests I shouldn't worry so much about 
'economy' -- I tend to not want to use an elephant's worth of 
functionality ( printf ) where a mouses worth will do.  But maybe that's 
not a valid way to think cuz I can't really anticipate how the shell 
will actually get the work done.




[-- Attachment #2: Type: text/html, Size: 1580 bytes --]

      reply	other threads:[~2024-05-07 14:57 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-06 22:03 Ray Andrews
2024-05-06 22:33 ` Mark J. Reed
2024-05-06 22:35   ` Mark J. Reed
2024-05-06 22:38     ` Mark J. Reed
2024-05-06 23:02       ` Ray Andrews
2024-05-06 23:28         ` Mark J. Reed
2024-05-06 23:41           ` Ray Andrews
2024-05-06 23:57       ` Lawrence Velázquez
2024-05-07  5:14         ` Ray Andrews
2024-05-07  5:52           ` Roman Perepelitsa
2024-05-07 14:56             ` Ray Andrews [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=255c5dbd-c8d3-4cf7-bcec-6a3c1cfc8e71@eastlink.ca \
    --to=rayandrews@eastlink.ca \
    --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).