From: Sven Wischnowsky <wischnow@informatik.hu-berlin.de>
To: zsh-workers@sunsite.auc.dk
Subject: Re: Something wrong with prompt themes
Date: Tue, 7 Dec 1999 10:10:42 +0100 (MET) [thread overview]
Message-ID: <199912070910.KAA06939@beta.informatik.hu-berlin.de> (raw)
In-Reply-To: Adam Spiers's message of Tue, 7 Dec 1999 01:44:08 +0000
Adam Spiers wrote:
> ...
>
> Eek. I wasn't really aware that there were any particular conflicts
> between completion format styles and prompt themes ... actually that's
> not true, since the `adam2' prompt theme, which I use the most, makes
> user input bold initially, and I use:
>
> compstyle '*:descriptions' format "$fg_bold[white]%d$fg_no_bold[white]"
>
> But I suspect I'm missing more significant issues here. Could you
> give a practical example or two where the extension suggested above
> would be worthwhile?
I didn't mean to say that there are conflicts, I was just wondering if
thought about including defs for the format styles to make them
look-alike with the prompt themes. Probably resulting in a nicer or
more consistent user interface.
> ...
>
> Yep :-) While I'm not convinced more flexibility is needed in this
> (prompt themes) case, there's no denying that a generic customization
> system would be very worthwhile. In my mind, the ideal goal would be
> an extension of compstyle for general zsh customization (excepting
> options, of course, because they're fine left as is), and then to have
> some sort of simple front-end customization program (perhaps something
> like the sort of UI the `dialog' program generates?) which harnesses
> this in a user-friendly way. The upshot behind this would be that
> someone can download, install and have running very quickly a version
> of zsh with all the funky stuff enabled, and actually (roughly)
> understand what all the funky bits do, without having to spend hours
> uploading the zshcompsys man page to their brain. That would be
> great, IMO.
Any suggestions about how this should/could/would look like?
> Back to the topic in hand. These 8-bit characters seem to be causing
> several people to wrinkle up their noses, so I should change something
> I guess.
For me at least: only until I had a look at your screen shots...
Bye
Sven
--
Sven Wischnowsky wischnow@informatik.hu-berlin.de
next reply other threads:[~1999-12-07 9:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-12-07 9:10 Sven Wischnowsky [this message]
-- strict thread matches above, loose matches on Subject: below --
1999-12-06 13:19 Sven Wischnowsky
1999-12-06 16:44 ` Bart Schaefer
1999-12-07 1:59 ` Adam Spiers
1999-12-07 1:44 ` Adam Spiers
1999-12-07 17:54 ` Bart Schaefer
1999-12-06 12:37 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=199912070910.KAA06939@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).