From: Bart Schaefer <schaefer@brasslantern.com>
To: zsh-workers@sunsite.dk
Subject: Re: prompt themes
Date: Wed, 4 Jun 2003 17:21:44 +0000 [thread overview]
Message-ID: <1030604172144.ZM18214@candle.brasslantern.com> (raw)
In-Reply-To: <5.2.1.1.0.20030604050554.025f6070@pop1.mail.com>
On Jun 4, 6:01am, Dirus wrote:
}
} ><snip> It should
} >probably also do a preview even if there isn't a prompt_X_preview function
} >- there isn't for most.
}
} The problem here is we don't know how many parameters the themes
} take.
If the theme doesn't work with zero parameters, it's broken. If there is
no preview function, don't try to guess at parameters; preview whatever
the defaults are.
[Regarding help]
}
} I see your point. Using cat is pretty straight forward, and I am happy
} to leave it alone. :) The only advantage to using $REPLY here would be
} that if you intended on using the help string without directly echoing
} it to the screen.
If you want a description that isn't meant to be displayed as-is, add
another one; don't overload use of the help function.
See prompt_bart_help in prompt_bart_setup for a good reason why not.
} >There's probably quite a few aspects of the prompt theming that could
} >be improved. Making colour schemes independent of specific fonts would
} >be one example. <snip>
}
} Maybe you mean making color schemes independent of specific themes?
No, he means exactly what he said. There are some fonts that have half-
tone special characters, and some of the themes rely on those fonts to
get a "fade" effect from one color to another.
} One problem I noticed the other day is if one prompt sets PS3, PS4, or
} RPS1, then those vars won't get reset when changing prompts, even when
} setting the prompt to "off".
It's a general shortcoming that themes only change the parts of the prompt
that they're interested in; "off" is just another theme with a silly name.
To really have "prompt off" mean what it seems to mean, the theme system
would have to save and restore the original values of all the variables.
} There do seem to be some problems with the distributed themes descriptions
} too, for example adam1 (correct me if I'm wrong) says it requires an 8 bit
} font when it doesn't.
The usual case of the doc not keeping pace with other changes. It did
require an 8bit font at one time.
next prev parent reply other threads:[~2003-06-04 17:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-03 16:55 Dirus
2003-06-04 9:41 ` Oliver Kiddle
2003-06-04 13:01 ` Dirus
2003-06-04 15:01 ` Oliver Kiddle
2003-06-04 17:21 ` Bart Schaefer [this message]
[not found] <6134254DE87BD411908B00A0C99B044F03A0B5FA@mowd019a.mow.siemens.ru>
[not found] ` <1030123180207.ZM12877@candle.brasslantern.com>
[not found] ` <20030124211240.GD6160@io.com>
2003-02-03 11:24 ` Prompt themes Clemens Fischer
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=1030604172144.ZM18214@candle.brasslantern.com \
--to=schaefer@brasslantern.com \
--cc=zsh-workers@sunsite.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).