From: Mike Fletcher <fletch@phydeaux.org>
To: Adam Spiers <adam@spiers.net>
Cc: zsh workers mailing list <zsh-workers@sunsite.auc.dk>
Subject: Re: PATCH: prompt fun
Date: 04 Oct 1999 21:48:41 -0400 [thread overview]
Message-ID: <m2g0zqmvba.fsf@godzilla.phydeaux.org> (raw)
In-Reply-To: Adam Spiers's message of "Tue, 5 Oct 1999 00:36:59 +0100"
>>>>> "Adam" == Adam Spiers <adam@thelonious.new.ox.ac.uk> writes:
Adam> However, there are obviously cons to the single package
Adam> argument too, which is probably shown up at its most absurd
Adam> when k3wl_d0oD ANSI PS1 strings end up inside the main
Adam> source tree. I'm not sure what the best answer is, but my
Adam> instincts would say a compromise - include a few nice
Adam> prompts catering for a wide range of tastes, and then leave
Adam> the rest to the IRC kiddies (hmm, that's me I guess) to work
Adam> on. That was the approach I tried to take with this prompt
Adam> patch.
What if there were some well defined mechanism for packaging a
(for lack of a better term) zsh add-on. Something sort of similar to
the CPAN.pm module for perl (for those not familiar with perl, CPAN is
the Comprehensive Perl Archive Network and CPAN.pm is a module that
will automagically download, compile, and install additional perl
modules). This hypothetical program could be pointed at an
apropriately structured http/ftp site (part of the hypothetical
Comprehensive Zsh ARchive, or CZAR :) and told to grab and install J.
Random Hax0r's k-R4d shell prompts or the most up to date zftp module
source.
Or maybe that's overkill. :)
At the minimum, if there's going to be separately packaged
components something like the glib/gtk+/gnome x-config scripts would
be nice (again for those not familiar, these packages ship with a
shell script that is installed in $(installdir)/bin that can be run to
get compile and link options suitable for linking against the library
in question). After market zsh addins could use zsh-config to find
the location of the Functions directory, or headers for compiling
loadable modules against, or what not.
Just some random thoughts.
--
Fletch | "If you find my answers frightening, __`'/|
fletch@phydeaux.org | Vincent, you should cease askin' \ o.O'
678 443-6239(w) | scary questions." -- Jules =(___)=
| U
next prev parent reply other threads:[~1999-10-05 1:49 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-10-04 18:40 Adam Spiers
1999-10-04 23:14 ` Bart Schaefer
1999-10-04 23:36 ` Adam Spiers
1999-10-05 1:48 ` Mike Fletcher [this message]
1999-10-05 11:31 ` Zefram
1999-10-06 20:58 ` Adam Spiers
1999-10-07 10:43 ` Zefram
1999-10-07 13:29 ` bashprompt license (was Re: PATCH: prompt fun) Adam Spiers
1999-10-07 14:19 ` Bart Schaefer
1999-10-07 15:25 ` Oliver Kiddle
1999-10-07 16:45 ` PATCH: prompt fun Clint Adams
1999-10-07 16:49 ` Zefram
1999-10-07 17:03 ` Clint Adams
1999-10-07 17:06 ` Zefram
1999-10-11 13:19 ` Andrej Borsenkow
1999-10-11 16:39 ` Bart Schaefer
1999-10-11 21:30 ` Adam Spiers
1999-10-11 22:47 ` Bart Schaefer
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=m2g0zqmvba.fsf@godzilla.phydeaux.org \
--to=fletch@phydeaux.org \
--cc=adam@spiers.net \
--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).