| 1 |
On Thu, Jan 25, 2001 at 10:32:29PM -0600, Bryce Porter wrote: |
| 2 |
> I have been working on an awesome bash prompt theming mechanism. I could |
| 3 |
> easily make a format to make color prompts using strings like $red for |
| 4 |
> red text, etc. And then i could even write a few sample bash prompt |
| 5 |
> themes. I have all the ANSI colors defined already, and assigned to thier |
| 6 |
> own unique variable. |
| 7 |
> Sounds like a cool idea to me. |
| 8 |
> |
| 9 |
> Bryce |
| 10 |
> |
| 11 |
> > Hmmm... I'm just thinking aloud here; I'm not even sure if it's a useful |
| 12 |
> > idea, nor am I sure |
| 13 |
> > that I can explain it satisfactorialy :/ |
| 14 |
> > Ok, from the users perspective, it would look like this: A default |
| 15 |
> > configuration skeleton would |
| 16 |
> > be installed (a default ~/.bashrc etc), as it is currently. The user |
| 17 |
> > would then be able to apply, um, "themes" to their configuration - for |
| 18 |
> > example I like the highlight colour to be red, so I would find myself |
| 19 |
> > going through ~/.pinerc, ~/.lynxrc etc making them all look the same... |
| 20 |
> > the same applies to things like prompts, shells, editor of choice, my |
| 21 |
> > favorite mail program, /etc/hosts etc etc. |
| 22 |
> |
| 23 |
|
| 24 |
*sigh* That's not what I meant at all ;) |
| 25 |
|
| 26 |
Colouring a prompt was just an example; I was trying to portray a system |
| 27 |
whereby everything could be configured from one central datafile... I'll try |
| 28 |
to explain it again if anybody wants? |
| 29 |
|
| 30 |
- Tom |
Archives