9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Russ Cox <rsc@swtch.com>
To: plan9port-dev@googlegroups.com
Cc: Ron Minnich <rminnich@gmail.com>, micah <micah@cnm-vra.com>
Subject: Fwd: [9fans] p9p acme: incredibly slow typing in tag line for file.
Date: Tue, 14 Jul 2009 13:28:32 -0700	[thread overview]
Message-ID: <dd6fe68a0907141328s29f2ae96rafc5dd9e13d90c32@mail.gmail.com> (raw)
In-Reply-To: <b3b4f6f30907141246g4474145x8bfc40e2c8d7dae7@mail.gmail.com>

moving to plan9port-dev.
http://bitbucket.org/rsc/plan9port/issue/5/acme-typing-at-1-char-sec-on-ubuntu-904

Subject: [9fans] p9p acme: incredibly slow typing in tag line for file.
------------------------

From: ron minnich <rminnich@gmail.com>
Date: Sun, Jun 28, 2009 at 1:04 AM
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>


I am unable to type at more than about one char per second (I am not
making this up) in p9p acme in the tag line for a file. Only for file
tag lines, not other tag lines, and it's all fine in the actual file
window.

This is ubuntu 9.04. Any hints welcome.

thanks

ron


----------
From: Jason Catena <jason.catena@gmail.com>
Date: Sun, Jun 28, 2009 at 10:35 PM
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>


I just pulled down the latest versions with hg, compiled, and don't
see this problem on my Ubuntu 9.04 box.  No appreciable difference in
typing rate for tags for files, directories, or shell-output windows,
or their bodies.

I have seen this kind of response time, but for the whole interface,
because I exported an X-display through VPN from Red Hat to Windows XP
with Cygwin/X.

Does the same delay occur if you write into the tag file under
/mnt/acme?  I don't actually know the source code base that well, but
it seems like it would help narrow things down if writes to the tag
file showed up faster than input from the display.

Jason Catena


----------
From: Russ Cox <rsc@swtch.com>
Date: Mon, Jun 29, 2009 at 8:46 AM
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>


The file tags tend to get redrawn in full after every
change rather than incrementally like the body does.
It has to do with the tag resize calculations, which
I haven't gotten quite right.

That said, you should be able to redraw the tag
more than once per second.  Is this with a remote
X or some other high latency connection to the
underlying graphics?

Russ

----------
From: ron minnich <rminnich@gmail.com>
Date: Mon, Jun 29, 2009 at 12:53 PM
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>


Right on my laptop. But ubuntu 9.04 is known to have "X issues" and I
did not know if this was another one.

ron


----------
From: Micah Stetson <micah@cnm-vra.com>
Date: Tue, Jul 14, 2009 at 12:46 PM
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>


Has anybody figured this one out?  I just updated to Ubuntu 9.04 and
I'm seeing exactly the behavior Ron describes.  Typing in a file tag
(not a column tag) takes a noticeable amount of time per character --
varying between maybe 200ms and 1000ms by my guess.  Sometimes I get
the same delay in win and directory window tags, sometimes not.  In
any case, typing in the window body is fast.  Also, resizing the acme
window takes far too long -- maybe a couple of seconds.  I think the
time is linear in the number of files I have open in acme.  Somebody
asked whether writing to acme/n/tag was slow as well -- it doesn't
look like it.  Acme's still usable, since most of my text entry is in
window bodies, but it sure is a pain.

Thanks for any help anybody has to offer,

Micah


      reply	other threads:[~2009-07-14 20:28 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-28  8:04 ron minnich
2009-06-29  5:35 ` Jason Catena
2009-06-29 15:46 ` Russ Cox
2009-06-29 19:53   ` ron minnich
2009-07-14 19:46     ` Micah Stetson
2009-07-14 20:28       ` Russ Cox [this message]

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=dd6fe68a0907141328s29f2ae96rafc5dd9e13d90c32@mail.gmail.com \
    --to=rsc@swtch.com \
    --cc=micah@cnm-vra.com \
    --cc=plan9port-dev@googlegroups.com \
    --cc=rminnich@gmail.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).