zsh-workers
 help / color / mirror / code / Atom feed
From: "Bart Schaefer" <schaefer@candle.brasslantern.com>
To: "Andrej Borsenkow" <Andrej.Borsenkow@mow.siemens.ru>,
	<zsh-workers@sunsite.auc.dk>
Subject: Suffixes and menu completion vs. menu selection
Date: Fri, 22 Sep 2000 15:47:29 +0000	[thread overview]
Message-ID: <1000922154729.ZM7968@candle.brasslantern.com> (raw)
In-Reply-To: <001901c022f3$1cf94770$21c9ca95@mow.siemens.ru>

On Sep 20,  3:08pm, Andrej Borsenkow wrote:
} Subject: PATCH: _insert_all_matches bindable command
}
} there is subtle difference between menu completion and menu selection - menu
} selection adds space where menu completion does not. E.g.:
} 
} bor@itsrm2% l f*
} fOo   foO   foo
} 
} (selection)
} 
} bor@itsrm2% l fOo
} Completing file
} fOo   foO   foo
} (press `i')
} bor@itsrm2% l fOo i
} Completing file
} fOo   foO   foo
} 
} (completion)
} 
} bor@itsrm2% ls fOo
} Completing file
} fOo   foO   foo
} (press `i')
} bor@itsrm2% ls fOoi
} Completing file
} fOo   foO   foo
} 
} I would really prefer the same behaviour in both cases.

In the case of menu selection, you're actually choosing a match. In the
case of menu completion, you're disambiguating the ambiguous prefix.

You could argue that menu selection should abort, rather than accept, on
self-insert, and thus restore the original string to the command line
before inserting the `i', but it should not both accept a match and
append the inserted character to it without also first inserting the
usual completion suffix.  The current menu selection behavior, though,
is intended to interrupt your typing as little as possible (i.e. you
needn't explicitly hit RETURN to accept the selection).

If you're suggesting that the menu completion menu should include the
suffix for each of the matches, even when that suffix is a space (it
already e.g. appends the slash for directories), that might be another
matter -- but it'd be a change from the way zsh has behaved for years.
If I have `ls f*<TAB>" and that results in `ls fOo ' (note space) plus
a listing, what happens when I press SPACE TAB ?  What visual feedback
is there that `f*<TAB><SPACE><TAB>' is not the same as `f*<TAB><TAB>'?

-- 
Bart Schaefer                                 Brass Lantern Enterprises
http://www.well.com/user/barts              http://www.brasslantern.com

Zsh: http://www.zsh.org | PHPerl Project: http://phperl.sourceforge.net   


      parent reply	other threads:[~2000-09-22 15:57 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1000919021428.ZM30137@candle.brasslantern.com>
2000-09-20 11:08 ` PATCH: _insert_all_matches bindable command Andrej Borsenkow
2000-09-22 15:13   ` Bart Schaefer
2000-09-22 15:47   ` Bart Schaefer [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=1000922154729.ZM7968@candle.brasslantern.com \
    --to=schaefer@candle.brasslantern.com \
    --cc=Andrej.Borsenkow@mow.siemens.ru \
    --cc=zsh-workers@sunsite.auc.dk \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/zsh/

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).