From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] Acme pathname completion UX
Date: Wed, 30 Jan 2013 10:15:49 -0500 [thread overview]
Message-ID: <edd70be1519046b5d64eaa53c0ba1aac@brasstown.quanstro.net> (raw)
In-Reply-To: <79998333.PGz1e9Ah4n@coil>
On Wed Jan 30 05:05:02 EST 2013, dexen.devries@gmail.com wrote:
> what is the point of the ^F pathname completion appending one space after the
> pathname is completed? is it only to indicate successful completion?
>
> once the space is appended, performing a right-click on the pathname often
> requires moving the mouse over the pathname. if there was no space appended,
> the (empty) selection would remain next to the last character of pathname and
> right-click anywhere would acquire it.
(i don't know the reasons behind the completion behavior.
but if the completion isn't the end of the command, then the space is helpful.)
is the question really, why doesn't acme extend selections to the left over spurious
whitespace when pointing in the right margin?
that behavior might be worth a shot.
- erik
prev parent reply other threads:[~2013-01-30 15:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-30 10:04 dexen deVries
2013-01-30 15:15 ` erik quanstrom [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=edd70be1519046b5d64eaa53c0ba1aac@brasstown.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).