From: hiro <23hiro@gmail.com>
To: 9front@9front.org
Subject: Re: [9front] ipso(1) $editor
Date: Fri, 13 Mar 2020 18:28:40 +0100 [thread overview]
Message-ID: <CAFSF3XMCQf5PaxOJvjD5aS6EdsV4=SusbSMDAfdtxdNDe_97EQ@mail.gmail.com> (raw)
In-Reply-To: <9E11075B-CE74-4317-AD3B-9720D3BCFA42@quintile.net>
ah, then ipso as it is now is likely the wrong program for these kinds
of customizations.
it seems particularly made not for usuability but security.
On 3/13/20, Steve Simon <steve@quintile.net> wrote:
>
> i was suggesting the plumber use $editor rather than having its own private
> view of the users editor of choice.
>
> however i think sl is saying $editor does not exist on plan9, but only on
> *nux.
>
> the problem with using the plumber is that ipso starts ramfs to keep the
> editors temporary buffers safe and private. it also keeps the extracted
> factotum secrets file there. if you use the plumber then the secrets are/may
> be more exposed; particularly if you run it on a cpu server - though that
> has its own problems.
>
> -Steve
>
>
>> On 13 Mar 2020, at 4:31 pm, hiro <23hiro@gmail.com> wrote:
>>
>> what if you want it to open in your already open editor and not in
>> some new window? what's the problem with using the plumber? i must be
>> misunderstanding something?
>>
>> On 3/12/20, ori@eigenstate.org <ori@eigenstate.org> wrote:
>>>> maybe i brought this notion with me from unix, but i was pretty sure at
>>>> least some plan 9 programs check for $editor in the environment.
>>>
>>> I don't think it's currently a widespread convention, but
>>> I'd like it to be. I'm in support of documenting it and
>>> patching programs to use it.
>>>
>>>
>
>
next prev parent reply other threads:[~2020-03-13 17:28 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <EE136F7DAFC0826091FA862A624F0BF5@ewsd.inri.net>
2020-03-12 2:10 ` ori
2020-03-13 16:30 ` hiro
2020-03-13 16:39 ` Stanley Lieber
2020-03-13 16:42 ` hiro
2020-03-13 17:18 ` Steve Simon
2020-03-13 17:28 ` hiro [this message]
2020-03-13 21:23 ` Silas McCroskey
2020-03-13 22:04 ` Stanley Lieber
2020-03-13 23:44 ` Ethan Gardener
2020-03-14 0:55 ` Stanley Lieber
2020-03-14 11:20 ` Ethan Gardener
2020-03-13 17:35 ` ori
2020-03-13 19:33 ` Ethan Gardener
[not found] <362DF8C1B0A64514457A3CC11BA305F7@ewsd.inri.net>
2020-03-12 2:24 ` Trevor Higgins
2020-03-12 2:29 ` sl
2020-03-13 16:45 ` Ethan Gardener
2020-03-13 17:04 ` hiro
2020-03-13 17:08 ` Ethan Gardener
2020-03-13 17:12 ` hiro
2020-03-13 17:14 ` Ethan Gardener
2020-04-13 1:13 ` ori
2020-04-13 1:31 ` hiro
2020-04-13 3:31 ` Anthony Martin
2020-04-13 3:35 ` ori
2020-04-13 3:47 ` ori
2020-04-16 10:18 ` Ethan Gardener
2020-04-16 16:05 ` Steve Simon
2020-04-17 19:53 ` ori
2020-04-18 10:51 ` Ethan Gardener
2020-04-22 11:03 ` hiro
2020-03-11 15:22 Stanley Lieber
2020-03-11 22:16 ` [9front] " Steve Simon
2020-03-12 1:49 ` sl
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='CAFSF3XMCQf5PaxOJvjD5aS6EdsV4=SusbSMDAfdtxdNDe_97EQ@mail.gmail.com' \
--to=23hiro@gmail.com \
--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).