From: Siarhei Zirukin <ftrvxmtrx@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] problem with acme on 9front
Date: Sun, 22 May 2016 09:36:51 +0200 [thread overview]
Message-ID: <CADuwikWoGHR9Zj1L8Bv40QVO8WN0DMnC1yv-Ah9nQ4o+keGMHA@mail.gmail.com> (raw)
In-Reply-To: <CAK-yzPM9dDP4mg6gE3R5t7UAJJW58v08VwWRL_+38jZ85Qv8-Q@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 3424 bytes --]
In 9front's version of sam there are two additional commands that could
help you with "complex" commands, perhaps.
^ Plan 9-command
Send the standard output of the Plan 9 command to the
command window.
_ Plan 9-command
Send the range to the standard input, and send the
standard output of the Plan 9 command to the command
window.
On Sat, May 21, 2016 at 11:52 PM, Mark Lee Smith <netytan@gmail.com> wrote:
> Thanks for the interesting comments.
>
> I've been making an effort to use Sam, in the interest of my own
> understanding. One of the biggest barriers I've hit is that there doesn't
> appear to be a good way to save complex edit commands for later. The man
> page suggests that it's possible to send commands to Sam from shell scripts.
>
> External communication
> Sam listens to the edit plumb port. If plumbing is not
> active, on invocation sam creates a named pipe /srv/sam.user
> which acts as an additional source of commands. Characters
> written to the named pipe are treated as if they had been
> typed in the command window.
>
> B is a shell-level command that causes an instance of sam
> running on the same terminal to load the named files. B uses
> either plumbing or the named pipe, whichever service is
> available. If plumbing is not enabled, the option allows a
> line number to be specified for the initial position to dis-
> play in the last named file (plumbing provides a more gen-
> eral mechanism for this ability).
>
> E is a shell-level command that can be used as $EDITOR in a
> Unix environment. It runs B on file and then does not exit
> until file is changed, which is taken as a signal that file
> is done being edited.
>
> I use Plan9Port on OpenBSD and typically use the plumber with Acme. I've
> changed "editor" to sam, and read the B and E scripts. As I understand it
> the plumbing approach doesn't allows sending arbitrary commands, so I've
> stopped the plumber. I'm unable to find the named pipe and looking at the
> sam source code it's not obvious to me how or whether such a pipe is
> created. Is this capability still present in Sam? Perhaps the plumber has
> completely subsumed this by now? Ultimately what I'd like to know is how
> you go about reusing common commands? Do you snarf and paste them? I was
> thinking that it would be useful to create scripts like "ap" which select
> the current paragraph (name inspired by Vim.) What's the typical workflow
> when using Sam? I don't deny that it's a great editor. Writing several
> thousand words in Sam yesterday was a pleasure.
>
> Maybe I'm completely off base here?
>
> All the best,
>
> Mark
>
>
>
>
>
> On Fri, 20 May 2016 at 22:05 Steve Simon <steve@quintile.net> wrote:
>
>>
>> I started with Sam a sit ran on all the different unixes I used an vi an
>> emacs just felt clunky.
>>
>> I never got into help and when acme replaced that I just never made the
>> transition.
>>
>> I love Sam, though it is because I know it so well.
>>
>> btw, anyone written scripts to allow the plan9 wiki to be edited from
>> Sam? maybe the wiki is outmoded these days?
>>
>> -Steve
>>
>>
>>
>>
[-- Attachment #2: Type: text/html, Size: 4606 bytes --]
next prev parent reply other threads:[~2016-05-22 7:36 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-19 18:30 christophe DAMAS
2016-05-19 18:40 ` Siarhei Zirukin
2016-05-19 19:42 ` Charles Forsyth
2016-05-19 21:51 ` Kurt H Maier
2016-05-20 0:37 ` Lyndon Nerenberg
2016-05-20 1:23 ` Ethan Grammatikidis
2016-05-20 1:32 ` Lyndon Nerenberg
2016-05-20 2:02 ` Ethan Grammatikidis
2016-05-20 2:07 ` Lyndon Nerenberg
2016-05-20 11:58 ` hiro
2016-05-20 12:07 ` Mark van Atten
2016-05-20 15:49 ` Wes Kussmaul
2016-05-20 12:12 ` Brantley Coile
2016-05-20 20:01 ` Steve Simon
2016-05-21 21:52 ` Mark Lee Smith
2016-05-21 23:18 ` erik quanstrom
2016-05-22 7:36 ` Siarhei Zirukin [this message]
2016-05-22 17:28 ` Mark Lee Smith
2016-05-21 17:36 ` erik quanstrom
2016-05-21 18:16 ` Kurt H Maier
2016-05-21 18:28 ` Rob Pike
2016-05-21 19:21 ` Kurt H Maier
2016-05-21 23:14 ` Lyndon Nerenberg
2016-05-19 18:41 ` cinap_lenrek
2016-05-19 19:20 ` Mark Lee Smith
2016-05-19 19:36 ` cinap_lenrek
2016-05-19 20:26 ` Mark Lee Smith
2016-05-19 20:37 ` Lee Fallat
2016-05-19 20:40 ` Aram Hăvărneanu
2016-05-19 20:11 ` stanley lieber
2016-05-19 20:15 ` Charles Forsyth
2016-05-19 20:53 ` stanley lieber
2016-05-19 21:13 ` Mark van Atten
2016-05-19 21:18 ` Lee Fallat
2016-05-21 19:08 ` Mark van Atten
2016-05-21 19:23 trebol55555
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=CADuwikWoGHR9Zj1L8Bv40QVO8WN0DMnC1yv-Ah9nQ4o+keGMHA@mail.gmail.com \
--to=ftrvxmtrx@gmail.com \
--cc=9fans@9fans.net \
/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).