9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "User &" <homer@awesom.eu>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Sending frequently used command to sam
Date: Mon, 11 Aug 2014 22:46:13 +0200	[thread overview]
Message-ID: <20140811204613.GA52324@shells> (raw)
In-Reply-To: <CADcq26KjpRe_TwiRRoUuOpdw3wHYH9jNC9f+kpNhYuWJsy5FvA@mail.gmail.com>

With no plumber running
  % echo 'B /etc/passwd' > /tmp/.sam.$USER.$DISPLAY
sends text to command window.

Hope this can help!
See $PLAN9/src/cmd/samterm/plan9.c:/^extstart called
from io.c in case plumbstart() fail, as stated in sam(1).

With plumber running:
  % echo /etc/passwd| plumb -i -d edit -a action=showfile
Reading $PLAN/src/cmd/samterm/plan9.c:/^plumbformat, seems
you can't do much but 'showfile' for now :-)

After a quick look to the code, I doubt one can easily have
more than a single command window.

On Thu, Aug 07, 2014 at 01:54:17PM +0200, Yuning Feng wrote:
> I use sam in plan9port. I would like to wrap a sam command '.,$ > pv'
> into a very short one so that I can issue it easily without searching
> back in the command window. A similar command is '?\n\n?,/\n\n/ > pv',
> which might better justify this shortening. To achieve my goal, I have
> two ideas in mind:
>
> 1. If I can open more than one command window, than I can leave the
> string in one of them, and 'send' as needed, but is this possible?
>
> 2. The manual page mentions that sam listens to the edit port of plumb
> or sam.user named pipe. If they are available, I can communicate to
> sam by them. However, for the named pipe, I am not able to find
> sam.user in /tmp/ns.(username).:0, where the font server lives in. For
> the plumb, it is a little magical to me and I scratched my head and
> tried for a while but not getting anywhere.
>
> Hopefully some of you could shed me some light.
>
> Yuning
>



  reply	other threads:[~2014-08-11 20:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-07 11:54 Yuning Feng
2014-08-11 20:46 ` User & [this message]
2014-08-12 15:13   ` Yuning Feng

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=20140811204613.GA52324@shells \
    --to=homer@awesom.eu \
    --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).