[9fans] Acme pathname completion UX

[9fans] Acme pathname completion UX

[dexen deVries]

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.

-- 
dexen deVries

[[[↓][→]]]


``One disadvantage of the Univac system is that it does not use Unix, a 
recently developed program which translates from one computer language to 
another and has a built-in editing system which identifies errors in the 
original program.'' - student newspaper

Re: [9fans] Acme pathname completion UX

[erik quanstrom]

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