9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Mark Lee Smith <netytan@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] 9front sam in plan9port.
Date: Sun, 22 May 2016 17:45:42 +0000	[thread overview]
Message-ID: <CAK-yzPPmBvQ4CtFG1=M+=2pRw0oV03tbUctxPBEO-bN2ZWT2-g@mail.gmail.com> (raw)
In-Reply-To: <CAHUAchzj5fgqWdoC6fkBVpSBSQxGGEMZ65hu4hj1jyHbL61EWA@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1529 bytes --]

This is very cool. I just got it built/running on OpenBSD 5.9. The only
problem seems to be that the code is quite old? (It's very different from
that in Plan9Port's and 9front's version.)

I wasn't able to get it working remotely because the additional 'rsam'
command doesn't seem to be built. I haven't looked at that yet though.

This still uses the named pipe for communicating with sam from the outside,
which is quite useful. I may try to port that to my copy.

This might be obvious, but that you can use this samterm with sam from
Plan9Ports (and presumably 9front). And It will work remotely then.

All the best,

Mark

On Sun, 22 May 2016 at 13:10 Mart Zirnask <martzirnask@gmail.com> wrote:

> There is also a standalone Unix port of sam that includes chording,
> xft, custom colors and a few other hacks. It's a pleasure to work
> with; I've even come to prefer the initial, black and white UI.
>
> http://www.deadpixi.com/an-updated-version-of-sam
>
> On 22 May 2016 at 08:29, Iruatã Souza <iru.muzgo@gmail.com> wrote:
> > This is just a port of the 9front version of sam to p9p. As you can see,
> it
> > hasn't been updated in a while. But I can do that if anybody wants it.
> >
> > Em 21/05/2016 4:50 PM, <trebol55555@yandex.ru> escreveu:
> >
> > #define chording 0      /* code here for reference but it causes
> deadlocks
> > */
> >
> > I suppose the bug is still messing around.
> > I'll give it a try to the 9front version.
> >
> > Thanks for the info!
> >
> >
>
>

[-- Attachment #2: Type: text/html, Size: 2244 bytes --]

  parent reply	other threads:[~2016-05-22 17:45 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-21 19:49 trebol55555
     [not found] ` <CABJnqBTrK38zqn6E+MJE_JbNG2nKv2jqXizZ4g6h=MrpUuxFUg@mail.gmail.com>
     [not found]   ` <CABJnqBSDQoyFH=2=63-=yY2igyab0uZJ9VayRXr=+A=O1SHubA@mail.gmail.com>
2016-05-22  5:29     ` Iruatã Souza
2016-05-22 11:07       ` Mart Zirnask
2016-05-22 12:23         ` trebol55555
2016-05-22 17:45         ` Mark Lee Smith [this message]
2016-05-23  7:25           ` Mart Zirnask
2016-05-23 20:27             ` Mart Zirnask
2016-05-23 21:28               ` Skip Tavakkolian
2016-05-23 21:38                 ` Ryan Gonzalez
2016-05-24  2:27                 ` Dave MacFarlane
2016-05-24  5:02                   ` Matthew Veety
2016-05-22 18:08       ` Mark Lee Smith
2016-05-22 20:15         ` trebol55555
  -- strict thread matches above, loose matches on Subject: below --
2016-05-21 15:35 trebol55555
2016-05-21 15:50 ` James A. Robinson
2016-05-21 16:31   ` trebol55555
2016-05-21 17:07     ` James A. Robinson
2016-05-21 18:25       ` sl
2016-05-21 18:25     ` Mark van Atten
2016-05-21 18:30       ` sl
2016-05-21 18:33         ` erik quanstrom
2016-05-21 18:41           ` sl
2016-05-21 18:41         ` Mark van Atten

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-yzPPmBvQ4CtFG1=M+=2pRw0oV03tbUctxPBEO-bN2ZWT2-g@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).