From: Mark Lee Smith <netytan@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Chords, ^, _, ^B and scroll with mouse wheel in p9p sam
Date: Sat, 28 May 2016 10:04:37 +0000 [thread overview]
Message-ID: <CAK-yzPNXHatG=wc6mHLvghXdoGFtg9054Cj7FOTtBtx7LjUTRw@mail.gmail.com> (raw)
In-Reply-To: <d1fce912c0704b7905616eeba7ecedd6@debpi>
[-- Attachment #1: Type: text/plain, Size: 929 bytes --]
What would you think about moving the named pipe from samterm into sam? It
doesn't make much sense if you think of the named pipe as an alternative to
the plumber. If you're using it for scripting a long-running sam process
then maybe it's useful? It should also allow samterm to connect (or
reconnect) to an already running sam process, possibly on a remote machine,
wihich would be great for long running sessions, and/or
unstable/intermittent connections. It could even simplify some of the logic
and further decouple sam from samterm etc. I still need to look in to that
a bit more.
Just a thought :).
I'll probably end up implementing that in my local version of sam anyway.
All the best,
Mark
On Fri, 27 May 2016 at 20:06 <trebol55555@yandex.ru> wrote:
> I did that before, and I don't know why but It didn't work.
> Then after reading your mail I gave it a try again, and its working!
>
>
>
[-- Attachment #2: Type: text/html, Size: 1290 bytes --]
next prev parent reply other threads:[~2016-05-28 10:04 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-27 17:11 trebol55555
2016-05-27 17:46 ` Mark Lee Smith
2016-05-27 18:04 ` trebol55555
2016-05-28 10:04 ` Mark Lee Smith [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-05-31 1:34 trebol55555
2016-05-30 16:35 trebol55555
2016-05-26 22:03 trebol55555
2016-05-27 20:57 ` Mark Lee Smith
2016-05-27 21:42 ` Tobias Kreisel
2016-05-27 22:16 ` Ethan Grammatikidis
2016-05-27 22:37 ` stanley lieber
2016-05-28 15:25 ` Ethan Grammatikidis
2016-05-27 23:09 ` Kurt H Maier
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='CAK-yzPNXHatG=wc6mHLvghXdoGFtg9054Cj7FOTtBtx7LjUTRw@mail.gmail.com' \
--to=netytan@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).