> > This looks very annoying. Too bright.
> Oh, I'm really sorry! I just forgot to switch to default color scheme.
Applied. Thank you!
--
Regards,
Pavel Roskin
___
Mc-devel mailing list
[EMAIL PROTECTED]
http://mail.gnome.org/mailman/listinfo/mc-de
Vlad Romanenko wrote:
> Hello, Pavel!
>
>
>>This looks very annoying. Too bright.
>
> Oh, I'm really sorry! I just forgot to switch to default color scheme.
>
> You know, the reason I started working on MC syntax files was I didn't'
> like its default colors. I prefer colors from pascal.synta
Pavel Roskin wrote:
>>
>>>The question about comments may be for me. I remember that I just scanned
>>>the web for SQL files and checked sources of PostgreSQL and MySQL.
>>>PostgreSQL uses "--". MySQL uses "#". Take MySQL source and look for
>>>*.test files.
>>>
>>
>>It's very bad - # has not
Hello, Pavel!
> This looks very annoying. Too bright.
Oh, I'm really sorry! I just forgot to switch to default color scheme.
You know, the reason I started working on MC syntax files was I didn't'
like its default colors. I prefer colors from pascal.syntax (I use
console, not a terminal). So I
On Wed, 18 Sep 2002, Andrew V. Samoilov wrote:
> Pavel Roskin wrote:
> >
> > The question about comments may be for me. I remember that I just scanned
> > the web for SQL files and checked sources of PostgreSQL and MySQL.
> > PostgreSQL uses "--". MySQL uses "#". Take MySQL source and look
Pavel Roskin wrote:
>
> The question about comments may be for me. I remember that I just scanned
> the web for SQL files and checked sources of PostgreSQL and MySQL.
> PostgreSQL uses "--". MySQL uses "#". Take MySQL source and look for
> *.test files.
>
It's very bad - # has not special s
> > But how those possible changes will be syncronised with CoolEdit?
> > Or you think we don't need any compatibility / syncronisation
> > with CoolEdit anymore?
I'd like Paul Sheer to be informed. I think he is too busy with other
stuff, so the syntax code in Cooledit is not actively maintaine
Hello!
> I can't hightlight quoted document-here parts in the sh like
> cat << 'EOF'
> $$$
> EOF
The problem is quite deep.
It would be nice to understand any word, not just EOF. But this would be
hard to implement. I don't think we should do it.
I tried to add this rule:
context exclusive
Walery Studennikov wrote:
> On Wed, Sep 18, 2002 at 06:56:15PM +0300, Andrew V. Samoilov wrote:
>
>>Also I want to add case insensitive keywords to the editor syntax
>>engine, but I have some ideas how to change syntax file syntax.
>
>
> But how those possible changes will be syncronised with
On Wed, Sep 18, 2002 at 06:56:15PM +0300, Andrew V. Samoilov wrote:
> Also I want to add case insensitive keywords to the editor syntax
> engine, but I have some ideas how to change syntax file syntax.
But how those possible changes will be syncronised with CoolEdit?
Or you think we don't need a
Hi!
I can't hightlight quoted document-here parts in the sh like
cat << 'EOF'
$$$
EOF
Also I want to add case insensitive keywords to the editor syntax
engine, but I have some ideas how to change syntax file syntax.
Possibly solution are:
1) make contextes case insensitive by adding case-insens
Hello, Vlad!
> This time I'd like to contribute a syntax file for M4 macroprocessor
> with autoconf support.
> (m4.syntax attached)
This looks very annoying. Too bright. Please try using the same
conventions as in C files. In particular, comments should be brown, and
that applies to dnl too.
Hello!
This time I'd like to contribute a syntax file for M4 macroprocessor
with autoconf support.
(m4.syntax attached)
Put these lines in Syntax:
file (..\*\\.m4$|configure.in) M4\sMacroprocessor\sSource
include m4.syntax
And add a line to syntax/Makefile.am
Pavel, I'm sorry, but I m
13 matches
Mail list logo
