From: "Bart Schaefer" <schaefer@candle.brasslantern.com>
To: zsh-workers@sunsite.auc.dk
Subject: Re: PATCH: Re: TAB and PS2 and multiline buffers and vared
Date: Mon, 22 May 2000 16:52:57 +0000 [thread overview]
Message-ID: <1000522165258.ZM29917@candle.brasslantern.com> (raw)
In-Reply-To: <200005221444.QAA20403@beta.informatik.hu-berlin.de>
On May 22, 4:44pm, Sven Wischnowsky wrote:
} Subject: Re: PATCH: Re: TAB and PS2 and multiline buffers and vared
}
} Bart Schaefer wrote:
}
} > On May 22, 1:25pm, Sven Wischnowsky wrote:
} > } Subject: PATCH: Re: TAB and PS2 and multiline buffers and vared
} > }
} > } Bart Schaefer wrote:
} > }
} > } > The situation is different in vared (again with a multiline buffer).
} > } > Sometimes it beeps and then asks me whether I want to see all 2200
} > } > possiblities, other times it just beeps and refuses to insert anything.
} > } > Whether it asks or just beeps seems to depend on whether I started out
} > } > on vared of a value containing newlines (e.g. vared functions[foo] vs.
} > } > vared foo).
} > }
} > } Hm. Is that with the current CVS version?
} >
} > Yes. (Well, current at the time I sent the mail.)
}
} I don't understand why it's completing commands then... Hm.
I've just tried comparing zsh with all patches up to but NOT including
11503, against zsh including 11503, and I see no differences between
those (maybe 11493 had an effect?). So then I compared zsh including
11503 against zsh patched up to 11471 (e.g. code-wise should be identical
to -pre-4). The newer zsh does NOT show the behavior above; the older
one does.
Since the newer version doesn't have the bad behavior, the following is
mainly for information, in case a light bulb goes on above Sven when he
sees it.
The test case was to run `vared functions[_complete_debug]', scroll up
to the line `local w="${(qq)words}"', then type ^E ESC RET to open a
line, and begin completing on that line.
If I immediately type ^X?, both versions beep at me. Comparing the xtrace
output, the ONLY difference shown (other than line numbers) is the value
assigned to the _saved_colors local, which is irrelevant. Both versions
output the string from _message.
If I start the test again from a fresh PS1, but type TAB and then ^X?,
zsh-11502 produces the same xtrace as before, but zsh-11471 has this
additional fragment:
+_main_complete:41:if: [[ tab automenu-unambiguous == tab* && _complete_debug != *list* ]]
+_main_complete:42:then cursh: zstyle -T :completion::::: insert-tab
+_main_complete:43:then cursh cmdand cursh: [[ ::: != :* || -z functions[_complete_debug] ]]
+_main_complete:44:then cursh cmdand cursh cmdor: zstyle -t :completion:vared:::: insert-tab
+_main_complete:46:then: compstate[insert]=automenu-unambiguous
In this particular test they also both output the message, so I still
don't know exact steps to reproduce sending it into command completion.
--
Bart Schaefer Brass Lantern Enterprises
http://www.well.com/user/barts http://www.brasslantern.com
next prev parent reply other threads:[~2000-05-22 16:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-05-22 14:44 Sven Wischnowsky
2000-05-22 16:52 ` Bart Schaefer [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-05-31 9:53 Sven Wischnowsky
2000-05-25 7:57 Sven Wischnowsky
2000-05-25 15:20 ` Bart Schaefer
2000-05-22 11:25 Sven Wischnowsky
2000-05-22 14:27 ` 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=1000522165258.ZM29917@candle.brasslantern.com \
--to=schaefer@candle.brasslantern.com \
--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).