9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] 9front sam in plan9port.
Date: Sat, 21 May 2016 11:33:10 -0700	[thread overview]
Message-ID: <bc1a21094815b99d7ddf55ab0c525f69@lilly.quanstro.net> (raw)
In-Reply-To: <1ee1d8513eef08d58b8f475113fdf716@lrsb.attlocal.net>

On Sat May 21 11:32:04 PDT 2016, sl@9front.org wrote:
> > The plan9port version also has chording if in its samterm/main.c you
> > change #define chording 0 to #define chording 1.
>
> It was also marked as being buggy, which is why it remains disabled by default.

i believe rsc found the reason for this later.  the bug was that it caused protocol lock.
i don't recall what the details of the bug or the fix were.

- erik



  reply	other threads:[~2016-05-21 18:33 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 [this message]
2016-05-21 18:41           ` sl
2016-05-21 18:41         ` Mark van Atten
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
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

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=bc1a21094815b99d7ddf55ab0c525f69@lilly.quanstro.net \
    --to=quanstro@quanstro.net \
    --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).