9front - general discussion about 9front
 help / color / mirror / Atom feed
From: sirjofri <sirjofri+ml-9front@sirjofri.de>
To: 9front@9front.org
Subject: Re: [9front] wloc - rc doesn't work because of pid
Date: Wed, 11 May 2022 11:06:18 +0000 (UTC)	[thread overview]
Message-ID: <fc98c271-0a81-4236-8dbb-e9a9927ae4e5@sirjofri.de> (raw)
In-Reply-To: <1A18E2DECEF098E18AA850ABA3BFB26D@prosimetrum.com>

As the man page states it, I'd expect to be able to use wloc to 
reconstruct the windows (not exactly the programs) I have open currently.

See this scenario:

I have an acme window open and an rc window. I run wloc > myriostart.

The next time I try to reconstruct that window layout with rio -i 
myriostart.

The result is, one acme window. No rc window, since it's impossible to 
run rc with a pid as an argument.

You can say it's a feature or a bug, whatever you want. Imo this way wloc 
is only partially reliable.

More things to reconsider: what if I relabel the acme window? It's still 
an acme window, but with a different name, and I get no windows since the 
label doesn't name a program.

What if I relabel the acme window with some existing program? For 
example, stats? I get a huge stats window and not an acme window at all.

What if I relabel my acme window to fshalt? 🤔😂 ... Ok that's probably 
your own fault then...

In the end, when using wloc and programs you download from anywhere else, 
always check the labels of your windows.

sirjofri

  reply	other threads:[~2022-05-11 11:08 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-11  8:44 sirjofri
2022-05-11  9:49 ` umbraticus
2022-05-11 11:06   ` sirjofri [this message]
2022-05-11 11:08     ` sirjofri
2022-05-11 11:45       ` mkf9

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=fc98c271-0a81-4236-8dbb-e9a9927ae4e5@sirjofri.de \
    --to=sirjofri+ml-9front@sirjofri.de \
    --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).