From: cinap_lenrek@felloff.net
To: 9front@9front.org
Subject: Re: [9front] [PATCH] rio: add -label wctl param; improve window(1)
Date: Sat, 16 May 2020 22:30:36 +0200 [thread overview]
Message-ID: <82412A1ACD62CDC4DB0267615A344641@felloff.net> (raw)
In-Reply-To: <B3B51AC595309F8391CE0AF78402B421@a-b.xyz>
> It's not an issue per se, but it seems we are only doing it the
> roundabout way because of wanting to label the new window while missing
> the -label parameter to do so. We also do the environment cleanup, but
> this only affects the -m case so it can be moved there.
yeah. sorry. i agree it can be simplified.
> I'd argue that the label is a window property just like the others we
> are already setting through the 'new' wctl. I see no reason why it
> should be handled specially from the rest, or alternatively why other
> parameters shouldn't be set in a similar fashion by writing to /dev/wctl
> in new window's namespace.
maybe, but parsewctlmsg() in this form is not up to the task. you can't
have labels with spaces in them for example.
i said -cd has the same issue. if you have a directory that has a space
in it you'r fucked.
> Yes, the field parser is janky and could be helped with a rewrite in
> terms of getfields(2). I can do it independently of this other stuff.
ok.
--
cinap
next prev parent reply other threads:[~2020-05-16 20: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
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 [this message]
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=82412A1ACD62CDC4DB0267615A344641@felloff.net \
--to=cinap_lenrek@felloff.net \
--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).