From: Sven Wischnowsky <wischnow@informatik.hu-berlin.de>
To: zsh-workers@sunsite.dk
Subject: Re: vi editting troubles
Date: Wed, 30 May 2001 09:19:34 +0200 (MET DST) [thread overview]
Message-ID: <200105300719.JAA09515@beta.informatik.hu-berlin.de> (raw)
In-Reply-To: <1010529145811.ZM13318@candle.brasslantern.com>
Bart Schaefer wrote:
> ...
>
> I think anything that eventually calls _main_complete can be left alone as
> long as the surrounding code deals properly with ksh_arrays and the set of
> globbing options.
Yes. While looking again, I found the things in the patch below. That
comment was serverely out of date and in these functions we don't need
to eval _comp_setup (we didn't need to set the options there either
which was what I replaced with the `eval's), because they only set up
$curcontext and call _main_complete.
Bye
Sven
Index: Completion/Base/Widget/_correct_word
===================================================================
RCS file: /cvsroot/zsh/zsh/Completion/Base/Widget/_correct_word,v
retrieving revision 1.2
diff -u -r1.2 _correct_word
--- Completion/Base/Widget/_correct_word 2001/05/29 11:59:51 1.2
+++ Completion/Base/Widget/_correct_word 2001/05/30 07:15:44
@@ -3,11 +3,6 @@
# Simple completion front-end implementing spelling correction.
# The maximum number of errors is set quite high, and
# the numeric prefix can be used to specify a different value.
-#
-# If configurations keys with the prefix `correctword_' are
-# given they override those starting with `correct_'.
-
-eval "$_comp_setup"
local curcontext="$curcontext"
Index: Completion/Base/Widget/_expand_word
===================================================================
RCS file: /cvsroot/zsh/zsh/Completion/Base/Widget/_expand_word,v
retrieving revision 1.2
diff -u -r1.2 _expand_word
--- Completion/Base/Widget/_expand_word 2001/05/29 11:59:51 1.2
+++ Completion/Base/Widget/_expand_word 2001/05/30 07:15:44
@@ -2,8 +2,6 @@
# Simple completion front-end implementing expansion.
-eval "$_comp_setup"
-
local curcontext="$curcontext"
if [[ -z "$curcontext" ]]; then
--
Sven Wischnowsky wischnow@informatik.hu-berlin.de
next prev parent reply other threads:[~2001-05-30 7:20 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-23 3:04 Paul Ackersviller
2001-05-23 4:41 ` 64-bit sparc instructions Bart Schaefer
2001-05-23 9:38 ` Andrej Borsenkow
2001-05-23 16:42 ` Clint Adams
2001-05-23 12:29 ` Clint Adams
2001-05-23 6:28 ` vi editting troubles Bart Schaefer
2001-05-23 7:08 ` Sven Wischnowsky
2001-05-23 9:42 ` Peter Stephenson
2001-05-23 18:18 ` Wayne Davison
2001-05-23 19:31 ` Bart Schaefer
2001-05-29 6:59 ` Sven Wischnowsky
2001-05-29 11:57 ` PATCH: " Sven Wischnowsky
2001-05-29 14:58 ` Bart Schaefer
2001-05-30 7:19 ` Sven Wischnowsky [this message]
[not found] <20010521121334.A24931@flora01.SLAC.Stanford.EDU>
2001-05-21 19:43 ` Peter Stephenson
[not found] ` <010521132805.ZM11030@candle.brasslantern.com>
2001-05-22 1:53 ` nce
2001-05-22 2:31 ` 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=200105300719.JAA09515@beta.informatik.hu-berlin.de \
--to=wischnow@informatik.hu-berlin.de \
--cc=zsh-workers@sunsite.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).