all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Yuri Khan <yuri.v.khan@gmail.com>
To: Gian Uberto Lauri <saint@eng.it>
Cc: "help-gnu-emacs@gnu.org" <help-gnu-emacs@gnu.org>,
	Emanuel Berg <embe8573@student.uu.se>
Subject: Re: evidence: nano(1) is better than Emacs
Date: Mon, 17 Nov 2014 23:08:14 +0700	[thread overview]
Message-ID: <CAP_d_8UJUAVm-wQLSxhQOub2dpsf+rYVDJz-cc=f6egQ8nxjcg@mail.gmail.com> (raw)
In-Reply-To: <21609.42402.786692.211463@mail.eng.it>

On Mon, Nov 17, 2014 at 1:37 PM,  <saint@eng.it> wrote:

> Can you change the colors in nano?

Can. But it lacks indirection layers.

=== /usr/share/nano/debian.nanorc ===
syntax "apt/sources.list" "sources\.list(\.old|~)?$"
# component
color brightmagenta "^deb(-src)? ((http|file|ftp):/[^
]+|cdrom:\[[^\]]+\]/|cdrom:\[[-a-zA-Z0-9\._\(\) ]+\]/) [^ ]+ .+$"
# distribution
color brightred "^deb(-src)? ((http|file|ftp):/[^
]+|cdrom:\[[^\]]+\]/|cdrom:\[[-a-zA-Z0-9\._\(\) ]+\]/) [^ ]+"
# URI
color brightgreen "(http|file|ftp):/[^ ]+"
[…]
===

So one does not simply change one face and get e.g. all keywords
recolored; instead, one has to copy all the relevant configs and edit
them for each language.



  reply	other threads:[~2014-11-17 16:08 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-15 22:51 evidence: nano(1) is better than Emacs Emanuel Berg
2014-11-16  0:50 ` Bob Proulx
     [not found] ` <mailman.13773.1416099059.1147.help-gnu-emacs@gnu.org>
2014-11-16  7:53   ` Emanuel Berg
2014-11-16  9:19     ` H. Dieter Wilhelm
2014-11-16 17:05     ` evidence: nano(1) is *NOT* " Dan Espen
2014-11-16 21:26       ` Emanuel Berg
2014-11-17 15:17         ` Dan Espen
2014-11-17 22:23           ` Emanuel Berg
2014-11-16 19:26     ` evidence: nano(1) is " Bob Proulx
2014-11-17  7:37     ` saint
2014-11-17 16:08       ` Yuri Khan [this message]
     [not found]       ` <mailman.13896.1416240507.1147.help-gnu-emacs@gnu.org>
2014-11-17 22:14         ` Emanuel Berg

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAP_d_8UJUAVm-wQLSxhQOub2dpsf+rYVDJz-cc=f6egQ8nxjcg@mail.gmail.com' \
    --to=yuri.v.khan@gmail.com \
    --cc=embe8573@student.uu.se \
    --cc=help-gnu-emacs@gnu.org \
    --cc=saint@eng.it \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.