From: Ray Andrews <rayandrews@eastlink.ca>
To: zsh-workers@zsh.org
Subject: Re: completion problem with '291' ok with '274'.
Date: Tue, 10 Feb 2015 22:10:25 -0800 [thread overview]
Message-ID: <54DAF251.4040702@eastlink.ca> (raw)
In-Reply-To: <150210202035.ZM16595@torch.brasslantern.com>
On 02/10/2015 08:20 PM, Bart Schaefer wrote:
> OK, with those settings the first thing you should see (on the first TAB)
> is something like:
>
> torch% ./zsh
> Completing executable file or directory
> zsh* zsh-5.0.3* zsh-5.0.5* zsh.old*
> zsh-5.0.2-dev-0* zsh-5.0.4* zsh-5.0.7*
>
> The second TAB does nothing because it is selecting the first match in
> the list, which is just "zsh". The third tab should advance to the
> second match in the list (which in my case is "zsh-5.0.2-dev-0").
Right, it's like that with 274 but with 291 the first TAB gives me a new
prompt or it crashes. I understand the 'nothing' TABS.
#autoload -U compinit && compinit
... and all is well.
autoload -U compinit && compinit
return
... and I still have the problem, (the return skips all 'style' lines.)
> It's -H or --hold with two leading hyphens (there's your inconsistency
> again ... X11/Xorg apps standardize on long names with a single hyphen,
> other apps use the GNU convention of double hyphens).
I'll stick with real xterm for now so that there's no confusion.
(Somehow, that inconsistency doesn't bother me, I'd not be expecting
consistency there. That's worth thinking about. Presumptuous double
standard?)
Should work to just do
xfce4-terminal gdb /usr/local/bin/zsh-5.0.7-293-g0209635
and then at the "(gdb) " prompt, type "run". Then when it crashes you'll
be back at the (gdb) prompt, type "where".
Output:
Starting program: /usr/local/bin/zsh-5.0.7-293
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/i386-linux-gnu/i686/cmov/libthread_db.so.1".
TAB here:
pts/5 HP-w5--5-Debian1 root /usr/local/bin 3$ l zsh[Inferior 1 (process 19073) exited normally]
(gdb) where
No stack.
(gdb)
next prev parent reply other threads:[~2015-02-11 6:40 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-10 22:36 Ray Andrews
2015-02-11 2:35 ` Bart Schaefer
2015-02-11 3:39 ` Ray Andrews
2015-02-11 4:20 ` Bart Schaefer
2015-02-11 6:10 ` Ray Andrews [this message]
2015-02-11 16:28 ` Bart Schaefer
2015-02-11 17:40 ` Ray Andrews
2015-02-11 20:54 ` Bart Schaefer
2015-02-11 23:29 ` Ray Andrews
[not found] ` <CAH+w=7Yx5FX4ZOB=EKbNULy86+Q+czDM-YA90-j3H=X4v2eS0w@mail.gmail.com>
[not found] ` <54DC0675.4040808@eastlink.ca>
[not found] ` <CAH+w=7YisQBt_UJLjv4pmohvE0BL9Wr0TFye9Kio=b4NxH5Niw@mail.gmail.com>
[not found] ` <54DC34EF.4010204@eastlink.ca>
2015-02-12 5:30 ` Bart Schaefer
2015-02-12 9:25 ` Peter Stephenson
2015-02-12 16:43 ` Bart Schaefer
2015-02-12 17:01 ` Peter Stephenson
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=54DAF251.4040702@eastlink.ca \
--to=rayandrews@eastlink.ca \
--cc=zsh-workers@zsh.org \
/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).