From: Paul Lalonde <paul.a.lalonde@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] [acme] Edit command -- More than one argument?
Date: Tue, 28 Oct 2014 23:08:32 +0000 [thread overview]
Message-ID: <CA+POUVi0F77_mi9ZDZHWF+G92uauRP9gi5W2qia4sS3KiVTTpg@mail.gmail.com> (raw)
In-Reply-To: <2befe3f9781c895241a0eb5ba7128dd9@ladd.quanstro.net>
[-- Attachment #1: Type: text/plain, Size: 1227 bytes --]
Yes, the scroll wheel forward expands to the full size, and backwards
reduces it to one line; this is as designed, and only on the wheel for lack
of a better UI idea.
I can't say that it has any amount of documentation or discoverability :-(
I see what you mean about the "jitter" on expand contract. I can't think
of a way to handle, but if I ever open the source again I'll think about
some sort of hysteresis.
Paul
On Tue Oct 28 2014 at 3:55:39 PM erik quanstrom <quanstro@quanstro.net>
wrote:
> On Mon Oct 27 23:49:06 EDT 2014, paul.a.lalonde@gmail.com wrote:
>
> > What do you mean by resizing flicker? I've never seen it with the
> > multi-line tags. And we do resize the tag by hand - the scroll wheel
> opens
> > and shuts it, in addition to adding/removing the trailing newline.
>
> i didn't realize there was the scroll wheel trick. it doesn't work when
> the tag is empty, or allow one to expand the tag window larger than the
> current tag.
>
> what i mean by "flicker" is that if i modify a file which has
> a tag line that is close to wrapping, then modifying the file
> will often make the tag line too long, and wrapping. Undo
> has the opposite effect.
>
> - erik
>
>
[-- Attachment #2: Type: text/html, Size: 1596 bytes --]
next prev parent reply other threads:[~2014-10-28 23:08 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-27 16:41 sl
2014-10-27 22:54 ` Rob Pike
2014-10-27 23:39 ` Paul Lalonde
2014-10-28 3:41 ` erik quanstrom
2014-10-28 3:49 ` Paul Lalonde
2014-10-28 22:51 ` erik quanstrom
2014-10-28 23:08 ` Paul Lalonde [this message]
2014-10-28 23:47 ` erik quanstrom
-- strict thread matches above, loose matches on Subject: below --
2014-10-27 15:28 Eduardo Alvarez
2014-10-27 15:34 ` Rob Pike
2014-10-27 15:46 ` Ingo Krabbe
2014-10-27 17:09 ` Rob Pike
2014-10-27 17:15 ` lucio
2014-10-27 17:33 ` Ingo Krabbe
2014-10-27 17:33 ` Eduardo Alvarez
2014-10-27 17:35 ` Skip Tavakkolian
2014-10-27 17:29 ` Kostarev Ilya
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=CA+POUVi0F77_mi9ZDZHWF+G92uauRP9gi5W2qia4sS3KiVTTpg@mail.gmail.com \
--to=paul.a.lalonde@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).