Re: [PATCH] Problem with type/ keyword in mc.ext on Solaris

Dmitry Sivachenko wrote: Hello! The file(1) command distributed with Solaris OS is different from Linus/BSD ones. It's output has the following format: filename.ext:Some text instead of filename.ext:Some text The following patch fixed the issue. Please include it into distribution. The pa

Re: Syntax highlighting question

Hello Sasche, [EMAIL PROTECTED] wrote: > thanks fast reply. Correct me if I am wrong. > The `\s' character is a escape for a > white space ` ' in the syntax file. Correctly. > My labels begin all at the start of a line. Other > coders might define labels in another way, it's > matter of taste. F

Re: Re: Syntax highlighting question

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello Frank´ thanks fast reply. Correct me if I am wrong. The `\s' character is a escape for a white space ` ' in the syntax file. My labels begin all at the start of a line. Other coders might define labels in another way, it's matter of taste. For

[PATCH] Problem with type/ keyword in mc.ext on Solaris

Hello! The file(1) command distributed with Solaris OS is different from Linus/BSD ones. It's output has the following format: filename.ext:Some text instead of filename.ext:Some text Thus the following line in mc.ext does not work: type/^gzip Open=gzip -dc %f | %var{PAGER:more}