From: Dirus <Dirus@Programmer.net>
To: zsh-workers@sunsite.dk
Subject: prompt themes
Date: Tue, 03 Jun 2003 09:55:04 -0700 [thread overview]
Message-ID: <5.2.1.1.0.20030531101708.025fcc78@valenzud.inbox.email.arizona.edu> (raw)
I had been playing around with prompt themes a bit and I noticed a couple
of things.
prompt_X_preview doesn't print the first or last blank line. This means
the person writing the prompt theme would have to print the blank lines
between sample settings without printing the first or last. Whoever is
writing the function also has to check "if (( ! $#* ));" to see if the user
passed in any parameters himself. Each prompt_X_preview function will have
a lot of duplicate code.
In the interest of consolidating all of the code and logic to one place and
also to make it easier for a person to set up a preview for their theme,
I'd like to create a patch for the prompt theming (and it's themes) that
that causes prompt_X_preview to return a list of settings in $reply (or
$REPLY). (Is the lowercase preferred for an array of values?)
Ideally prompt_X_preview would look like this:
prompt_X_preview() {
reply=' singleparameter "param1 param2" "param1 param2" '
}
Also prompt_X_help could also be changed to set $reply for consistency sake.
Anyone interested in seeing this? Is it best to just send the diffs to the
mailing list? There would be a lot of them, one for each prompt theme and
one for promptinit.
-Dirus
next reply other threads:[~2003-06-03 16:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-03 16:55 Dirus [this message]
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
[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=5.2.1.1.0.20030531101708.025fcc78@valenzud.inbox.email.arizona.edu \
--to=dirus@programmer.net \
--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).