From: "Bart Schaefer" <schaefer@brasslantern.com>
To: zsh-workers@math.gatech.edu
Subject: PATCH: Re: PATCH: for Re: REC_EXACT and AUTO_MENU, and compctl -U too
Date: Tue, 23 Jun 1998 11:43:49 -0700 [thread overview]
Message-ID: <980623114349.ZM449@candle.brasslantern.com> (raw)
In-Reply-To: <199806220645.IAA08265@beta.informatik.hu-berlin.de>
On Jun 22, 8:45am, Sven Wischnowsky wrote:
} Subject: PATCH: for Re: REC_EXACT and AUTO_MENU, and compctl -U too
}
} Sounds very reasonable. And if we want to do it in the drastic way you
} described, the patch is pretty simple.
There's a missing blank line in Sven's patch, which causes it to fail.
The corrected patch follows.
*** Src/Zle/zle_tricky.c.old Mon Jun 22 08:23:18 1998
--- Src/Zle/zle_tricky.c Mon Jun 22 08:26:36 1998
***************
*** 2246,2252 ****
{
Compctl cc = NULL;
int oloffs = offs, owe = we, owb = wb, ocs = cs, oll = ll, isf = 1;
! int t, sf1, sf2, ooffs;
char *p, *sd = NULL, *tt, *s1, *s2, *os = NULL;
unsigned char *ol = NULL;
--- 2246,2252 ----
{
Compctl cc = NULL;
int oloffs = offs, owe = we, owb = wb, ocs = cs, oll = ll, isf = 1;
! int t, sf1, sf2, ooffs, um = usemenu;
char *p, *sd = NULL, *tt, *s1, *s2, *os = NULL;
unsigned char *ol = NULL;
***************
*** 2266,2271 ****
--- 2266,2272 ----
if (unset(COMPLETEINWORD) && cs != we)
cs = we, offs = strlen(s);
+ usemenu = um;
ispattern = haswhat = lastambig = 0;
patcomp = filecomp = NULL;
menucur = NULL;
***************
*** 2413,2418 ****
--- 2414,2420 ----
*delit = 1;
*s = '\0';
offs = 0;
+ if (isset(AUTOMENU)) usemenu = 1;
} else
*delit = 0;
*** Doc/Zsh/compctl.yo.old Mon Jun 22 08:36:59 1998
--- Doc/Zsh/compctl.yo Mon Jun 22 08:42:43 1998
***************
*** 353,359 ****
tt(-K) option) which can examine the word components passed to it
(or via the tt(read) builtin's tt(-c) and tt(-l) flags) and
use its own criteria to decide what matches. If there is no
! completion, the original word is retained.
)
item(tt(-y) var(func-or-var))(
The list provided by var(func-or-var) is displayed instead of the list
--- 353,362 ----
tt(-K) option) which can examine the word components passed to it
(or via the tt(read) builtin's tt(-c) and tt(-l) flags) and
use its own criteria to decide what matches. If there is no
! completion, the original word is retained. Since the produced
! possible completions seldom seldom have interesting common prefixes
! and suffixes, menucompletion is started immediatly if tt(AUTO_MENU) is
! set and this flag is used.
)
item(tt(-y) var(func-or-var))(
The list provided by var(func-or-var) is displayed instead of the list
--
Bart Schaefer Brass Lantern Enterprises
http://www.well.com/user/barts http://www.brasslantern.com
prev parent reply other threads:[~1998-06-23 18:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-06-22 6:45 Sven Wischnowsky
1998-06-23 18:43 ` 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=980623114349.ZM449@candle.brasslantern.com \
--to=schaefer@brasslantern.com \
--cc=zsh-workers@math.gatech.edu \
/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).