unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Vitalie Spinu <spinuvit@gmail.com>
To: "Stephen J. Turnbull" <stephen@xemacs.org>
Cc: 'Eli Zaretskii' <eliz@gnu.org>,
	Drew Adams <drew.adams@oracle.com>,
	emacs-devel@gnu.org
Subject: Re: font-lock-maximum-decoration should be 2 by default?
Date: Sun, 19 Aug 2012 13:47:12 +0200	[thread overview]
Message-ID: <87r4r385of.fsf@gmail.com> (raw)
In-Reply-To: <874nnzrvc2.fsf@uwakimon.sk.tsukuba.ac.jp> (Stephen J. Turnbull's message of "Sun, 19 Aug 2012 20:10:21 +0900")

  >> "Stephen J. Turnbull" <stephen@xemacs.org>
  >> on Sun, 19 Aug 2012 20:10:21 +0900 wrote:

  > Vitalie Spinu writes:
  >> It's easy to get sick of too much customization. It's another well know
  >> paradox of human pshychology -- we want more choose but too much choice
  >> is bad for you

  > And the experiments you cite were conducted on a sample of Emacs
  > users?  Surely not!  The point is that Emacs users *are* different
  > (this is nearly a tautology), 

 The full spectrum of Emacs users is broader than you seem to
 think. It's not only hardcore programmers, like you are. I met a guy
 who was using Emacs only for org-mode to organize himself! I also won't
 be surprised that the majority of Emacs users don't actually know
 enough elisp to be able to write useful scripts. As one of the
 developers of ESS, I see users which have no clue of how to customize
 even basic things in Emacs. They are still able to happily use
 ESS/Emacs, but they all rely on defaults. And this is why defaults are
 so important. So knowing elisp, or even the ability to customize things
 is not a prerequisite for an Emacs user at all.

  >> >> 3) Developers which would like to capture 30% of salad lovers will try
  >> >> to find workarounds. That is, add redundant, mode-specific
  >> >> font-lock customization, or mess with
  >> >> font-lock-maximum-decoration.
  >> 
  >> > This is true, but I'm not sure if it's a problem.
  >> 
  >> It's a problem in light of yours (2). Everyone wants a consistent
  >> interface.

  > But who decides what "consistent" means?  The highlighting appropriate
  > for C is surely different from that for Lisp or Perl or Haskell.  Some
  > will be common, I suppose, such as for literal strings.  But what
  > about Perl "barewords"?  What does consistency mean for something that
  > doesn't exist in most languages?  Should shell commands be highlighted
  > differently depending on whether they're builtins, system commands, or
  > shell functions and aliases?

Consistent in customization interface, not in that fontification is set
by default. If there is variable font-lock-maximum-decoration that
should be it. No X-mode-maximum-font-lock, foo-mode-best-font-lock or
boo-mode-try-this-font-lock-level etc.

  > That kind of thing has to be decided by the mode developers, although
  > the Emacs maintainers often will offer suggestions, and for modes in
  > core Emacs will add/adjust to their own taste.  And in the end the
  > dirge "Why do the defaults always suck?" applies anyway.

:)



  reply	other threads:[~2012-08-19 11:47 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-17 12:29 font-lock-maximum-decoration and how to make a default font-lock lower than maximal? Vitalie Spinu
2012-08-17 14:29 ` Eli Zaretskii
2012-08-17 14:42   ` Vitalie Spinu
2012-08-17 15:57     ` font-lock-maximum-decoration and how to make a defaultfont-lock " Drew Adams
2012-08-17 19:49       ` font-lock-maximum-decoration should be 2 by default? Vitalie Spinu
2012-08-17 20:26         ` Eli Zaretskii
2012-08-17 20:53           ` Drew Adams
2012-08-18  6:59             ` Eli Zaretskii
2012-08-19  2:32               ` Jason Rumney
2012-08-19  3:13                 ` Drew Adams
2012-08-19  3:34                   ` Jason Rumney
2012-08-19  4:39                     ` Drew Adams
2012-08-19 10:50                     ` Vitalie Spinu
2012-08-19 16:46                   ` Eli Zaretskii
2012-08-19 17:33                     ` Drew Adams
2012-08-19 10:34                 ` Andreas Schwab
2012-08-19 16:48                   ` Eli Zaretskii
2012-08-17 20:50         ` Drew Adams
2012-08-17 22:47           ` Vitalie Spinu
2012-08-18  7:03             ` Eli Zaretskii
2012-08-18 10:10             ` Vitalie Spinu
2012-08-21 17:31               ` Stefan Monnier
2012-08-22 16:50                 ` Vitalie Spinu
2012-08-26 18:27                 ` Drew Adams
2012-08-18  5:10         ` Stephen J. Turnbull
2012-08-18 10:03           ` Vitalie Spinu
2012-08-19 11:10             ` Stephen J. Turnbull
2012-08-19 11:47               ` Vitalie Spinu [this message]
2012-08-19 13:23                 ` Stephen J. Turnbull
2012-08-17 17:36     ` font-lock-maximum-decoration and how to make a default font-lock lower than maximal? Eli Zaretskii
2012-08-21 17:24 ` Stefan Monnier
2012-08-26 18:26   ` font-lock-maximum-decoration and how to make a default font-locklower " Drew Adams

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

  List information: https://www.gnu.org/software/emacs/

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

  git send-email \
    --in-reply-to=87r4r385of.fsf@gmail.com \
    --to=spinuvit@gmail.com \
    --cc=drew.adams@oracle.com \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=stephen@xemacs.org \
    /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 public inbox

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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).