9front - general discussion about 9front
 help / color / mirror / Atom feed
From: mkf9 <mkf9@riseup.net>
To: 9front@9front.org
Subject: Re: [9front] wloc - rc doesn't work because of pid
Date: Wed, 11 May 2022 16:15:49 +0430	[thread overview]
Message-ID: <4213280c-af69-7b86-b263-b507009a6ebe@riseup.net> (raw)
In-Reply-To: <f369070e-c31f-4f4e-bdaf-f76c39a7c72b@sirjofri.de>

sirjofri wrote:
> One potential other solution for wloc: don't use the full label, but 
> only the first token, which is likely a command without arguments.
> 
> This would fix the rc pid issue and still work the same as always. Of 
> course you lose the ability to reconstruct your programs with arguments 
> (e. g. filenames).
> 
> sirjofri

i had following solution in my mind
if label shows a pid, check what binary? (using proc name?) it's 
running, usually it's rc, but some programs won't change label of 
default window's label.

      reply	other threads:[~2022-05-11 11:48 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
2022-05-11 11:08     ` sirjofri
2022-05-11 11:45       ` mkf9 [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=4213280c-af69-7b86-b263-b507009a6ebe@riseup.net \
    --to=mkf9@riseup.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).