From: "Bart Schaefer" <schaefer@candle.brasslantern.com>
To: zsh-workers@sunsite.auc.dk
Subject: History bug (Re: Completion debugging)
Date: Sun, 30 Apr 2000 09:31:16 +0000 [thread overview]
Message-ID: <1000430093116.ZM188@candle.brasslantern.com> (raw)
Look at this snippet of "history" output:
21 cd zsh-3.1.6
22 setup_compinit
24 emacs /tmp/zsh149find1 ;: find\ -
24 history
25 emacs /tmp/zsh149find1 ;: find\ -
26 history
28 emacs /tmp/zsh149find2 ;: find\
29 emacs /tmp/zsh149echo3 ;: echo\ foo\
29 history
30 reload _complete_debug
32 emacs /tmp/zsh149find4 ;: 'find -'
32 history
Why are there two of numbers 24, 29 and 32? In each case, the first of the
two was inserted by calling "print -s ..." during completion. Apparently
that doesn't work very well.
--
Bart Schaefer Brass Lantern Enterprises
http://www.well.com/user/barts http://www.brasslantern.com
reply other threads:[~2000-04-30 9:31 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1000430093116.ZM188@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).