lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Pine.LNX.4.64.0710080005370.16301@fbirervta.pbzchgretzou.qr>
Date:	Mon, 8 Oct 2007 00:11:21 +0200 (CEST)
From:	Jan Engelhardt <jengelh@...putergmbh.de>
To:	Oleg Verych <olecom@...wer.upol.cz>
cc:	Rene Herman <rene.herman@...access.nl>, Willy Tarreau <w@....eu>,
	Ingo Molnar <mingo@...e.hu>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Dave Jones <davej@...hat.com>,
	Krzysztof Halasa <khc@...waw.pl>,
	Medve Emilian-EMMEDVE1 <Emilian.Medve@...escale.com>,
	Helge Deller <deller@....de>
Subject: Re: syntax highlighting, emacs ([PATCH 0/2] Colored kernel output
 (run2))


On Oct 8 2007 00:18, Oleg Verych wrote:
>
>Kind of funny thing with it. One for shell in `mcedit` is much nicer, but
>`emacs` is more powerful as editor(R). But both have highlighting
>problems with non trivial scripts (quoiting, data here, etc). I don't
>know if it will ever be fixed :).

No, it will never get fixed. I use two editors on a day-to-day basis,
and that is mcedit and joe. No fixed rule on which to use. It goes as
far that I have the same syntax highlighting (almost) on both.
Because one thing in one editor is cumbersome in the other.
Perhaps if there was one editor with the hotkeys of *both* (yes,
means duplicates), maybe then I'd be satisfied.

>Emacs have black background by default. I changed foreground to green,
>and it is much nicer for long runs. Blue (or any bright) background
>isn't comfortable, i think.

Actually, blue is perceived as one of the darkest colors by the human
eye. There is a reason that the RGB -> grayscale transformation uses
the following weighting: r=76 g=154 b=26.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ