From: Sven Wischnowsky <wischnow@informatik.hu-berlin.de>
To: zsh-workers@sunsite.auc.dk
Subject: More questions (was: Re: PATCH: menu style AND remarks)
Date: Thu, 9 Dec 1999 12:57:38 +0100 (MET) [thread overview]
Message-ID: <199912091157.MAA22089@beta.informatik.hu-berlin.de> (raw)
In-Reply-To: Sven Wischnowsky's message of Wed, 8 Dec 1999 14:43:55 +0100 (MET)
I wrote:
> ... (e.g. by moving some stuff from computil into a general
> utility module -- some things in it, like the style stuff, is really
> completely independent of the completion system).
I thought some more about this... and now I'm beginning to like it.
I would suggest to move comp{display,fmt,styles} into a separate
module (compstyles is the builtin behind _style and compstyle; ugly
name; that's one of the reasons why I'd like to replace it with
something more sensible). The first two would be combined to, say,
`zformat' (both do only some formatting, compdisplay does the
alignment used in displays and compfmt does the %c stuff -- the latter
could do with some more work to support the field width stuff and so on).
And compstyles would be renamed to, say, `zstyle'. This, too, would be
enhanced a bit so that _style isn't necessary anymore, completion
functions would just call zstyle directly, making things faster.
We probably should then also built the listing stuff into it. At least
for now the `compstyle' would still survive, but only act as a very
simple wrapper around zstyle (probably simpler than it is now).
The completion code would use names of the form `:completion:...' and
stuffing that `:completion' in front would be the main task of
`compstyle'. If styles are used elsewhere, they would use different
prefixes (`:prompt'? `:zftp'?) and probably their own *style functions
unless we decide to only use the builtin (i.e. all styles, independent
of the package-prefix) everywhere -- then compstyle would/could/should
be removed, too. I can only see a small problem here: if we don't use
per-package style functions, we might some time come to a point where
we want to make zstyle more convenient or make it know some more about
packages really used. Then we would want to use a (one) shell function
as a wrapper around the builtin and `zstyle' would be a nice name for
it, too. But since stuff like the completion functions would use the
builtin, too, we would have to give it a different name than the
builtin (I want to avoid having to use `builtin zstyle' everywhere).
In short: in this case we probably should use a different name for the
builtin and somewhere (but where?) already define the wrapper function
for the user interface named `zstyle'.
Hm, I hope at least some of you understood what I wanted to say. If
so: any suggestions/opinions?
Bye
Sven
--
Sven Wischnowsky wischnow@informatik.hu-berlin.de
next reply other threads:[~1999-12-09 11:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-12-09 11:57 Sven Wischnowsky [this message]
1999-12-09 12:24 ` Adam Spiers
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=199912091157.MAA22089@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).