From: sl@stanleylieber.com
To: 9front@9front.org
Subject: Re: [9front] ipso(1) $editor
Date: Wed, 11 Mar 2020 21:49:19 -0400 [thread overview]
Message-ID: <20200312014919.pAMCELFtxtDeW-_urtba_JR8V8Rr4iczfXeqiTFqHzM@z> (raw)
In-Reply-To: <A4653451-5917-4A45-8E00-C87C9DD6FEFF@quintile.net>
> i added the code to ipso to look at the plumbing rules. at that time
> there was no $editor. if 9front has a $editor i would suggest you use
> it and modify the plumber to respect it too (it it doesn't already).
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.
haha:
mars2; cd /sys/src/cmd
mars2; grep editor */*
abaco/plumbing:editor = acme
acme/dat.h: Buffer *elogbuf; /* log of pending editor changes */
dict/movie.c: ED, /* editor */
dict/oed.c: Ed, /* editor's comments (in [...]) */
hg/hgeditor:# If you want to pass your favourite editor some other parameters
hg/hgeditor:HGTMP="${TMPDIR-/tmp}/hgeditor.$RANDOM.$RANDOM.$RANDOM.$$"
postscript/README: LDFLGS common link editor options - used to build LDFLAGS in the
postscript/postscript.mk:# LDFLGS common link editor options - used to build LDFLAGS in the
spell/list:coeditor n
spell/list:creditor n
spell/list:editor n
spell/list:editorial n,a,na
spell/list:expeditor n
mars2; cd /rc/bin
mars2; grep editor *
ipso:editor = (acme -c1)
ipso:edexp=`{grep '^editor=' /mnt/plumb/rules >[2]/dev/null}
ipso: editor = sam
ipso: Warning: The editor will display the secret contents of
ipso:if(~ $edit yes) $editor `{for(i in $files) basename $i}
newt:if(~ $#editor 0)
newt: editor=hold
newt: eval $editor /tmp/post
newt: echo editor: $editor
mars2;
sl
next prev parent reply other threads:[~2020-03-12 1:49 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-11 15:22 Stanley Lieber
2020-03-11 22:16 ` [9front] " Steve Simon
2020-03-12 1:49 ` sl [this message]
[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
[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
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=20200312014919.pAMCELFtxtDeW-_urtba_JR8V8Rr4iczfXeqiTFqHzM@z \
--to=sl@stanleylieber.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).