From: Thomas Flavel <thomasfl@cogs.susx.ac.uk>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] Re: Themes
Date: Thu Jan 25 21:50:02 2001 [thread overview]
Message-ID: <20010126045046.C26673@tsuny.ctn.cogs.susx.ac.uk> (raw)
In-Reply-To: <Pine.LNX.4.21.0101252228510.9768-100000@x86.dyn.cheapnet.net>; from bporter@advancenet.net on Thu, Jan 25, 2001 at 10:32:29PM -0600
On Thu, Jan 25, 2001 at 10:32:29PM -0600, Bryce Porter wrote:
> I have been working on an awesome bash prompt theming mechanism. I could
> easily make a format to make color prompts using strings like $red for
> red text, etc. And then i could even write a few sample bash prompt
> themes. I have all the ANSI colors defined already, and assigned to thier
> own unique variable.
> Sounds like a cool idea to me.
>
> Bryce
>
> > Hmmm... I'm just thinking aloud here; I'm not even sure if it's a useful
> > idea, nor am I sure
> > that I can explain it satisfactorialy :/
> > Ok, from the users perspective, it would look like this: A default
> > configuration skeleton would
> > be installed (a default ~/.bashrc etc), as it is currently. The user
> > would then be able to apply, um, "themes" to their configuration - for
> > example I like the highlight colour to be red, so I would find myself
> > going through ~/.pinerc, ~/.lynxrc etc making them all look the same...
> > the same applies to things like prompts, shells, editor of choice, my
> > favorite mail program, /etc/hosts etc etc.
>
*sigh* That's not what I meant at all ;)
Colouring a prompt was just an example; I was trying to portray a system
whereby everything could be configured from one central datafile... I'll try
to explain it again if anybody wants?
- Tom
next prev parent reply other threads:[~2001-01-26 4:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20010125175702.447D253C7A@cvs.gentoo.org>
2001-01-25 21:32 ` [gentoo-dev] Re: Themes Bryce Porter
2001-01-25 21:50 ` Thomas Flavel [this message]
2001-01-25 23:31 ` Cymen Vig
2001-01-25 23:41 ` drobbins
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=20010126045046.C26673@tsuny.ctn.cogs.susx.ac.uk \
--to=thomasfl@cogs.susx.ac.uk \
--cc=gentoo-dev@gentoo.org \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox