From: Sven Wischnowsky <wischnow@informatik.hu-berlin.de>
To: zsh-workers@sunsite.auc.dk
Subject: Re: PATCH: collist v2.0
Date: Tue, 22 Jun 1999 12:35:18 +0200 (MET DST) [thread overview]
Message-ID: <199906221035.MAA24589@beta.informatik.hu-berlin.de> (raw)
In-Reply-To: Peter Stephenson's message of Tue, 22 Jun 1999 10:51:43 +0200
Peter Stephenson wrote:
> It's hard to know what to do. You don't expect to be able to set an option
> only when a module is loaded, so I don't think we can have module-dependent
> options. But zle related options are in the main shell even if zle isn't
> loaded. Maybe we just have to make it an option (menuselect, obviously)
> anyway and make a bigger effort to load complist when necessary, so you
> would get an error from completion the first time if it's not available.
We can make modules autoloadable on options -- triggered by
(|un)setopt. But then there is still the problem with local options
and all that...
> - some new options will list all modules or builtin modules. This is
> probably better but the problem is that with a non-dynamically-linked
> shell you always get no output from running `zmodload' on its own which
> is a little Zen-like. Maybe it should return status 1 in that case as a
> test for dynamic loading, but status 0 when the list includes builtin
> modules.
I'd vote for using the exit status and even let these list-options
accept optional arguments. With arguments they just check if the
modules named are loaded (or can be loaded?).
> And I still think the zle command needs the ability to list builtin
> widgets, too.
Definitely, yes -- see 6775.
> One other thing: I'm still a bit worried about the way undo works, where
> the first time nothing happens if there isn't a suffix to undo. It's fine
> if there is a suffix which you can undo separately, but I'd be tempted to
> make it skip over that if it does nothing. That would make it harder if
> you used undo in programming, however, but I don't think people do.
Maybe an option to undo saying if you want to skip `invisible' undos
or not?
> I've done this and I'll try and get pws-$((N+1)) out at the end of the
> week, particularly since I'm busy next week. There were some other minor
> changes: a tt(no) in the manual was missing a close parenthesis, some
> dependencies for mod_complist.yo needed adding in the Makefile, a nodref
> referred to `The complist module' instead of `The complist Module'. These
> are appended below, but it assmues the name changes.
Oh, yes. I forgot to test-make the docs, sorry.
And thanks!
Bye
Sven
--
Sven Wischnowsky wischnow@informatik.hu-berlin.de
next reply other threads:[~1999-06-22 10:35 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-06-22 10:35 Sven Wischnowsky [this message]
-- strict thread matches above, loose matches on Subject: below --
1999-06-23 8:43 Sven Wischnowsky
1999-06-23 8:59 ` Andrej Borsenkow
1999-06-22 12:36 Sven Wischnowsky
1999-06-22 9:56 Sven Wischnowsky
1999-06-22 8:49 Sven Wischnowsky
1999-06-22 8:25 Sven Wischnowsky
1999-06-22 8:51 ` Peter Stephenson
1999-06-22 17:06 ` Bart Schaefer
1999-06-22 9:04 ` Peter Stephenson
1999-06-22 11:52 ` Andrej Borsenkow
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=199906221035.MAA24589@beta.informatik.hu-berlin.de \
--to=wischnow@informatik.hu-berlin.de \
--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).