On 5/28/06, Claes Nästén <[EMAIL PROTECTED]> wrote:
On Sun, May 28, 2006 at 01:17:16PM +0200, Axel Liljencrantz wrote:
> I've just made a few additions to the syntax highligting code.
> Specifically, paremeter expansion operators (like '*', '()', '$') can
> be highligted in an individual color, as can escapes (like '\n',
> '\x70', etc). The code is clever enough to handle escapes within
> quotes correctly, and even to mark invalid escapes as errors.
>
> Current default colors are cyan for operators and blue for escapes.
> Fish has traditionally been a bit conservative when it comes to color
> use (Most types of tokens are uncolored by default) since too much
> syntax highlighting can be a bit distracting, but I think this is neat
> since I find it easier to see the difference between operators and
> non-operators this way.
>
> Bring on the hippie colors?
>
As soon as fish_pager links sure. ;) In fish_pager expand_variable_set
is referenced, available in expand.c. However, expand.o depends on a
lot of other stuff.
Just a heads up.
Thanks.
I moved the function expand_variable_array, which was suddenly needed
by fish_pager from expand.c to common.c. It's a bit of an odd duck any
place you put it, so I thought it was better to move it to common.c
where it can live with the other odd ducks that don't really belong
anywhere, and where it doesn't cause these silly dependency problems.
Everything should work now. And by everything, I mean that fish should
mostly compile.
--
Claes Nästén, <[EMAIL PROTECTED]>, http://www.pekdon.net/
--
Axel
-------------------------------------------------------
All the advantages of Linux Managed Hosting--Without the Cost and Risk!
Fully trained technicians. The highest number of Red Hat certifications in
the hosting industry. Fanatical Support. Click to learn more
http://sel.as-us.falkag.net/sel?cmd=lnk&kid7521&bid$8729&dat1642
_______________________________________________
Fish-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/fish-users
