zsh-workers
 help / color / mirror / code / Atom feed
From: "Bart Schaefer" <schaefer@candle.brasslantern.com>
To: zsh-workers@sunsite.auc.dk
Subject: Completion no longer enabled in zsh -f
Date: Mon, 7 Feb 2000 04:23:08 +0000	[thread overview]
Message-ID: <1000207042308.ZM7068@candle.brasslantern.com> (raw)

I just built 3.1.6-dev-17, patched up through 9589.  Running "zsh -f":

zagzig% ls <TAB>

Nothing happens.

I just fielded a post from somebody on comp.unix.shells who was confused
because zsh didn't complete anything at all for him.  I pointed him at
compinit but said that plain file completion should still work by default,
which at the moment it doesn't.  This must have started happening after
the patch in 8770; you must run at least one "compctl" command or the
like, or "zmodload compctl", for completion to be active.

The following is the simplest fix I could think of; one shortcoming is
that the compctl module doesn't strictly need to be loaded if the complete
module has been.  However, thanks to the way load_module() works, it is
possible to prevent loading of zsh/compctl by loading zsh/zle (either
explicitly or implicitly) in your init files; zsh/zle is already loaded as
a side-effect of "compinit", so for anyone already using new completion in
their init files, this change is invisible.

Index: Src/init.c
===================================================================
@@ -1021,7 +1021,7 @@
 autoload_zleread(char *lp, char *rp, int ha)
 {
     zlereadptr = fallback_zleread;
-    load_module("zsh/zle");
+    load_module("zsh/zle") && load_module("zsh/compctl");
     return zleread(lp, rp, ha);
 }
 

-- 
Bart Schaefer                                 Brass Lantern Enterprises
http://www.well.com/user/barts              http://www.brasslantern.com


             reply	other threads:[~2000-02-07  4:23 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-02-07  4:23 Bart Schaefer [this message]
2000-02-09  8:56 Sven Wischnowsky

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=1000207042308.ZM7068@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).