zsh-workers
 help / color / mirror / code / Atom feed
From: Sven Wischnowsky <wischnow@informatik.hu-berlin.de>
To: zsh-workers@sunsite.auc.dk
Subject: Re: PATCH: prompt theme system improvements
Date: Fri, 19 Nov 1999 13:01:39 +0100 (MET)	[thread overview]
Message-ID: <199911191201.NAA03943@beta.informatik.hu-berlin.de> (raw)
In-Reply-To: Oliver Kiddle's message of Fri, 19 Nov 1999 11:42:22 +0000


Oliver Kiddle wrote:

> ...
> 
> With respect to colour themes. It would be good to have a single way
> for defining colours across zsh. ZLS_COLOURS may be compatible with
> GNU ls but it isn't exactly the most readable way.

Ah. See? I suggested then when I first started participating in the
coloured-completion-lists discussion.

> One possible way would be to use an associative array for colours where the keys specify the context and the values specify the attributes. So for example, you might define:
> zsh_colours[ls_directories]="bold blue on white"
> zsh_colours[prompt_currentdir]="underlined green"

Ick. Maybe we should keep the parameter side more standard and just
use `bold:blue:white' or `bold:fg=blue:bg=white' or something. And
then add a function that uses a mini-language... err, wait, where have 
I heard that before.

I have almost given up dreaming about it, but: stuff like this always
reminds how nice it would be to generalise some of the completion-setup 
stuff to a more general package system. And then allow something like: 
`zstyle 'prompt:...:foreground' bold blue'.

> If different prompt themes use the same context words, you could share colour selections across prompts. It might also lead to a mechanism for defining the colours for different types of completion matches in the lists - not just for files.

...which complist currently can't do because it uses ZLS_* only for
files. But I have already asked: should we change it to allow using
pattern-capabilities for normal matches, too? The only problem I have
with that is that I would like to be able to give such specs per group 
of matches added. And that would require changes to compadd which
doesn't (and, in my opinion, shouldn't) know about complist. Hrm.

Bye
 Sven


--
Sven Wischnowsky                         wischnow@informatik.hu-berlin.de


             reply	other threads:[~1999-11-19 12:08 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-11-19 12:01 Sven Wischnowsky [this message]
  -- strict thread matches above, loose matches on Subject: below --
1999-11-19 11:01 Sven Wischnowsky
1999-11-19 10:34 Sven Wischnowsky
1999-11-19 10:55 ` Tanaka Akira
1999-11-18 14:53 Adam Spiers
1999-11-18 15:43 ` Adam Spiers
1999-11-18 17:51 ` Bart Schaefer
1999-11-19  1:51   ` Adam Spiers
1999-11-19 10:29     ` Tanaka Akira
1999-11-19 11:42 ` Oliver Kiddle

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=199911191201.NAA03943@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).