From: Sven Wischnowsky <wischnow@informatik.hu-berlin.de>
To: zsh-workers@sunsite.auc.dk
Subject: Re: Clearing the completion listing
Date: Mon, 15 Mar 1999 11:39:37 +0100 (MET) [thread overview]
Message-ID: <199903151039.LAA22933@beta.informatik.hu-berlin.de> (raw)
In-Reply-To: "Bart Schaefer"'s message of Sun, 14 Mar 1999 12:25:49 -0800
Bart Schaefer wrote:
> Seems to me there are a few more zle commands that ought to clear the
> completion listing. The one that I notice most often is kill-whole-line.
> Most history motions should do it, too, since if any of them pull up a
> multi-line entry it's just going to cover up the list anyway (assuming
> always_last_prompt). And kill-buffer, and probably transpose-words, and
> maybe insert-last-word. Any others?
Hadn't thought of them... I'd suggest doing this with another
`ZLE_'-flag.
Let's see:
- beginning-of-buffer-or-history
- beginning-of-line-hist
- down-history
- down-line-or-history
- down-line-or-search
- end-of-buffer-or-history
- end-of-line-hist
- get-line (?)
- infer-next-history
- kill-buffer
- kill-line
- push-input
- push-line
- push-line-or-edit
- run-help
- up-history
- up-line-or-history
- up-line-or-search
- vi-down-line-or-history
- vi-fetch-history
- vi-history-search-backward
- vi-history-search-forward
- vi-open-line-above
- vi-open-line-below
- vi-repeat-search
- vi-rev-repeat-search
- vi-up-line-or-history
Some of them should clear the list only if the history is used. Some
of them already clear the list, and some of those who already clear
the list have not been mentioned.
Any other suggestions?
Bye
Sven
--
Sven Wischnowsky wischnow@informatik.hu-berlin.de
next reply other threads:[~1999-03-15 10:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-03-15 10:39 Sven Wischnowsky [this message]
-- strict thread matches above, loose matches on Subject: below --
1999-03-14 20:25 Bart Schaefer
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=199903151039.LAA22933@beta.informatik.hu-berlin.de \
--to=wischnow@informatik.hu-berlin.de \
--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).