From: "Ethan Gardener" <eekee57@fastmail.fm>
To: 9front@9front.org, hiro <23hiro@gmail.com>
Subject: Re: [9front] ipso(1) $editor
Date: Fri, 13 Mar 2020 19:33:01 +0000 [thread overview]
Message-ID: <5db8b3ed-e50c-4739-a729-2d02fdfeb6f1@www.fastmail.com> (raw)
In-Reply-To: <50B891AE6E688602941E7E9BA7AE4616@eigenstate.org>
On Fri, Mar 13, 2020, at 5:35 PM, ori@eigenstate.org wrote:
>
> When plumbing, there's no signal that editing is done.
> Scripts often need some way to edit a file and proceed
> on the edited contents.
There is /bin/E for this purpose. It's a little crude, returning after the file is first saved. (It doesn't cover ipso's security concerns.)
This all reminds me I have found the plumber to be a little bit inconvenient on occasion because it acts all Proper GUI: it sends the document to the Appropriate Application instead of opening it near where I'm looking. I've never entirely liked that. Back in the early 00s I had a powerful Emacs setup but abandoned it because I always wanted to start the editor in the terminal I was already looking at. Starting Emacs just took too long. I never did come up with the perfect solution, but subrios with their own plumer instances can help.
next prev parent reply other threads:[~2020-03-13 19:33 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
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 [this message]
[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=5db8b3ed-e50c-4739-a729-2d02fdfeb6f1@www.fastmail.com \
--to=eekee57@fastmail.fm \
--cc=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).