From: Julius Schmidt <aiju@phicode.de>
To: 9front@9front.org
Subject: Re: [9front] rio exit menu
Date: Sun, 9 Dec 2018 21:38:07 +0100 (CET) [thread overview]
Message-ID: <alpine.LNX.2.00.1812092136580.1142@phi> (raw)
In-Reply-To: <CEC99320ABD6383A4A107B33427B362D@wopr.sciops.net>
I'm opposed to this change.
I would kill too many rios by accident :)
On Sun, 9 Dec 2018, qwx wrote:
> Hello,
>
> Currently, rio hides an 'Exit' entry in mouse menu 3 unless argv[0] contains
> the string ".out".
>
> The inlined patch below removes the check and exposes the entry.
>
> While potentially dangerous, it is more convenient than manually killing a
> given rio, and several people including me have been using this or similar
> patches for a while.
>
> What do you think? Would anyone else like to see this merged?
>
> Thanks,
>
> qwx
>
>
> diff -r 49bd5e4c9bde sys/src/cmd/rio/rio.c
> --- a/sys/src/cmd/rio/rio.c Wed Feb 07 18:53:08 2018 +0000
> +++ b/sys/src/cmd/rio/rio.c Thu Feb 15 23:00:00 2018 +0100
> @@ -125,10 +125,6 @@
> Image *i;
> Rectangle r;
>
> - if(strstr(argv[0], ".out") == nil){
> - menu3str[Exit] = nil;
> - Hidden--;
> - }
> initstr = nil;
> kbdin = nil;
> maxtab = 0;
>
next prev parent reply other threads:[~2018-12-09 20:38 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-09 20:26 qwx
2018-12-09 20:38 ` Julius Schmidt [this message]
2018-12-09 20:53 ` [9front] " Steve Simon
2018-12-09 21:01 ` Stanley Lieber
2018-12-09 21:03 ` hiro
2018-12-09 21:29 ` qwx
2018-12-13 8:56 ` Ethan Gardener
2018-12-13 10:44 ` Ethan Gardener
2018-12-09 21:38 kvik
2018-12-09 21:40 ` Steve Simon
2018-12-09 21:55 ` Kurt H Maier
2018-12-09 22:04 ` Steve Simon
2018-12-09 22:07 ` Kurt H Maier
2018-12-09 22:28 ` Stanley Lieber
2018-12-11 21:24 ` Ethan Gardener
2018-12-11 21:34 ` hiro
2018-12-11 21:54 ` Ethan Gardener
2018-12-11 23:11 ` Ethan Gardener
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=alpine.LNX.2.00.1812092136580.1142@phi \
--to=aiju@phicode.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).