From: erik quanstrom <quanstro@quanstro.net>
To: quanstro@quanstro.net, rsc@swtch.com, 9fans@9fans.net
Subject: Re: [9fans] P9p on Fedora 12
Date: Mon, 30 Aug 2010 08:39:51 -0400 [thread overview]
Message-ID: <1c5d1df7f94e7d87465fb1539a28fd6a@plug.quanstro.net> (raw)
In-Reply-To: <4bd7aaa3effec6d1152b864f1c28bf73@plug.quanstro.net>
On Mon Aug 30 07:41:18 EDT 2010, quanstro@quanstro.net wrote:
> On Mon Aug 30 07:22:48 EDT 2010, rsc@swtch.com wrote:
> > > 1. <insert> in acme on a string like /usr/quanstro/src/
> > > inserts another / for each keypress.
> >
> > I don't know what this means.
> > Acme has no <insert>.
> > I haven't seen this.
>
> oh, sure it does.
>
> /mnt/term/usr/quanstro/plan9/src/cmd/acme/text.c:792,799
> switch(r){
> case 0x06: /* ^F: complete */
> case Kins:
> rp = textcomplete(t);
> if(rp == nil)
> return;
> nr = runestrlen(rp);
> break; /* fall through to normal insertion case */
>
> oddly¸ i see that the arm port has exactly the same bug.
sorry, i take it back. drawterm also has the same bug.
there are several timing bugs, but often what i see
is the +Errors window opening up with just a /
in the body. (but sometimes the / is inserted in
the original space.) Undo in +Errors yields the normal
completion list. texttype() really does get
Kins then '/'.
it turns out that x helpfully yields this if i hold down
the insert key
<insert>//////////////////////////////////////////////
x has a brand new bug.
modern linux systems can be a good example of how better can be
the opposite of working.
- erik
next prev parent reply other threads:[~2010-08-30 12:39 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-22 9:56 Pavel Klinkovsky
2010-02-24 10:13 ` Pavel Klinkovsky
2010-02-24 16:07 ` David Leimbach
2010-03-01 9:49 ` Pavel Klinkovsky
2010-03-01 11:04 ` Gabriel Díaz
2010-03-01 12:11 ` Pavel Klinkovsky
2010-03-01 12:37 ` Gabriel Díaz
2010-03-01 12:56 ` erik quanstrom
2010-03-01 13:02 ` Gabriel Díaz
2010-03-01 14:10 ` Pavel Klinkovsky
[not found] ` <d03cbc06-ad77-47f0-b3b5-e78454608057@t20g2000yqe.googlegroups.co>
2010-03-01 14:32 ` erik quanstrom
2010-03-01 13:19 ` Pavel Klinkovsky
2010-03-01 14:35 ` Gabriel Díaz
2010-08-29 23:01 ` fgergo
2010-08-30 3:46 ` erik quanstrom
2010-08-30 11:20 ` Russ Cox
2010-08-30 11:38 ` erik quanstrom
2010-08-30 12:39 ` erik quanstrom [this message]
2010-08-30 16:09 ` Skip Tavakkolian
2010-08-30 17:47 ` erik quanstrom
2010-08-30 18:53 ` Skip Tavakkolian
2010-08-30 23:11 ` Russ Cox
2010-08-30 23:22 ` Charles Forsyth
2010-09-02 19:24 ` Russ Cox
2010-09-03 14:25 ` Russ Cox
2010-09-08 15:37 ` roger peppe
2010-08-30 18:47 ` Russ Cox
2010-09-06 11:47 ` Pavel Klinkovsky
2010-09-06 20:08 ` Russ Cox
2010-09-06 21:48 ` Ethan Grammatikidis
2010-09-06 21:54 ` Ethan Grammatikidis
2010-09-07 8:47 ` Pavel Klinkovsky
2010-09-06 11:45 ` [9fans] [plan9mod] " Pavel Klinkovsky
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=1c5d1df7f94e7d87465fb1539a28fd6a@plug.quanstro.net \
--to=quanstro@quanstro.net \
--cc=9fans@9fans.net \
--cc=rsc@swtch.com \
/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).