From: DervishD <raul@pleyades.net>
To: schaefer@brasslantern.com, zsh-workers@sunsite.dk, raul@pleyades.net
Subject: Re: About menu selection (again)
Date: Tue, 13 Aug 2002 20:50:31 +0200 [thread overview]
Message-ID: <3D5954F7.mail1L21A9GN@viadomus.com> (raw)
In-Reply-To: <1020813150050.ZM30758@candle.brasslantern.com>
Hi Bart :)
>} It works because compctl is loaded!. I don't know how it gets
>} loaded, but it is :????
>Normally zsh/zle and zsh/compctl are both loaded as soon as zsh is ready
>to print the prompt.
Well, when my login zsh starts, the only modules that are loaded
are zsh/zle and zsh/main. zsh/compctl is not there. Maybe I'm not
invoking any builtin in my rc's so compctl is autoloaded :??
>messed-up module_path, but
>that can't be it because you've said you're using a static link.
Yes, they are statically linked. I'm having an idea... What if I
configured compctl prior to compilation as being statically linked
but NOT autoloaded (I mean, with load=no in the .mdd file)? I don't
have the mdd that I used for compilation, I'm afraid :((( But this
can be the problem, true?
>} Well, the fact is that if I load compctl and after that complist,
>} all works OK, so I'm happy with this. Why I must load compctl is just
>} curiosity ;))
>If you're willing to look at it that way, OK. Me, I'd be worried that it
>means something else is broken, too.
Yes, you are right, because if something is wrong, then other
fails will arise sooner or later... Just that I have bigger problems
than that ;))) Fortunately zsh works fine always ;))
Thanks for your help again, Bart.
Raúl
next prev parent reply other threads:[~2002-08-13 18:42 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-11 20:47 DervishD
2002-08-12 6:01 ` Bart Schaefer
2002-08-13 13:16 ` DervishD
2002-08-13 15:00 ` Bart Schaefer
2002-08-13 18:50 ` DervishD [this message]
2002-08-13 18:55 ` More information on why compctl is not loaded DervishD
2002-08-14 2:27 ` About menu selection (again) Bart Schaefer
2002-08-16 12:08 ` DervishD
2002-08-16 12:05 ` Sven Wischnowsky
2002-08-17 17:26 ` Bart Schaefer
2002-08-19 7:40 ` Sven Wischnowsky
2002-08-20 11:58 ` Sven Wischnowsky
2002-08-20 15:07 ` Bart Schaefer
2002-08-20 15:21 ` Sven Wischnowsky
2002-08-18 16:29 ` DervishD
2002-08-18 23:07 ` 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=3D5954F7.mail1L21A9GN@viadomus.com \
--to=raul@pleyades.net \
--cc=schaefer@brasslantern.com \
--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).