From: "Ethan Gardener" <eekee57@fastmail.fm>
To: 9front@9front.org
Subject: Re: [9front] [PATCH] rio: add -label wctl param; improve window(1)
Date: Thu, 14 May 2020 14:28:58 +0100 [thread overview]
Message-ID: <fc352331-1711-4a73-b2e3-c3084b5095d4@www.fastmail.com> (raw)
In-Reply-To: <AA875B8F23C43D0E6E24C4A428E0FF57@a-b.xyz>
On Wed, May 13, 2020, at 2:14 PM, kvik@a-b.xyz wrote:
>
> You see that the initial argument list stays the same as it is being
> passed along, that is until another round of evaluation inside the
> rc -c subshell where the next layer of quotes is stripped.
>
> In the argument parsing sense removing the recursive call to window -x
> is the same as skipping the call to 'once' in the above example.
>
> > window -r 268 0 868 400 -scroll rc -c \
> > '''label -f kprint; echo kprint; tail -f /tmp/kprint'''
> > window -r 0 0 128 128 colorclock_l
> > window -r 0 124 128 252 rc -c \
> > '''font=/lib/font/bit/dejavusans/unicode.12.font; stats -Ime'''
>
> These commands run as expected with the patch.
Ah, you're quite right. Thanks for the examples and testing.
>
> > Now I think of it, I don't really agree with window(1) setting the label
> > at all, but it's a minor point.
>
> I'm not a fan of automatic labeling either. Ideally the programs would
> set the label themselves if the user didn't request a name, but I don't
> think this is easily accomplished.
It looks like it's one of those things which ends up a little untidy whichever option is chosen.
next prev parent reply other threads:[~2020-05-14 13:30 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-13 10:20 kvik
2020-05-13 13:34 ` [9front] " Ethan Gardener
2020-05-13 13:14 ` kvik
2020-05-14 13:28 ` Ethan Gardener [this message]
2020-05-14 12:20 ` kvik
2020-05-16 12:22 ` cinap_lenrek
2020-05-16 11:53 ` kvik
2020-05-16 18:04 ` cinap_lenrek
2020-05-16 14:04 ` cinap_lenrek
2020-05-16 16:08 ` kvik
2020-05-16 20:30 ` cinap_lenrek
2020-05-16 19:05 ` kvik
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=fc352331-1711-4a73-b2e3-c3084b5095d4@www.fastmail.com \
--to=eekee57@fastmail.fm \
--cc=9front@9front.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.
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).