From: Emanuel Berg <moasen@zoho.com>
To: help-gnu-emacs@gnu.org
Subject: Re: About how misspelled word are displayed
Date: Fri, 12 May 2017 23:07:43 +0200 [thread overview]
Message-ID: <yw.86fug9n5r4.fsf@zoho.com> (raw)
In-Reply-To: 557766eb-48c0-4eaf-8c08-459b2376da8c@default
Drew Adams wrote:
> Yes, it can be difficult to find out which
> things to customize. That's unrelated to the
> question of whether to use Customize or Lisp
> to set them.
One of many reasons it is preferable to write
code rather than to use Customize is that using
Customize you get tangled into a jungle of
unrelated things and that way it is difficult
to find out which things to customize.
> IOW, we now have not only Customize writing
> to your `custom-file' or init file; we have
> also the package system doing that.
At least some of us do.
> But if you mean the former (decided by you
> but not necessarily coded by you) then the
> previous discussion applies: Why not use
> Customize to do that?
1. counter-educative
2. unpleasant (hitting buttons instead of typing)
3. imprecise
4. inflexible
5. ungeneralizable and ineffective (learing a UI instead of learning to edit files)
6. dependent (relying on a tool instead of your own skills)
7. the lamer's choise
> Whatever face appearances you decide on,
> Customize will save them to your `custom-file',
> leaving your init file alone.
If it is bad enough for my init file, I don't
want it anywhere else either.
--
underground experts united
http://user.it.uu.se/~embe8573
next prev parent reply other threads:[~2017-05-12 21:07 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-12 9:49 About how misspelled word are displayed Angelo Graziosi
2017-05-12 13:09 ` Kaushal Modi
2017-05-12 14:07 ` Angelo Graziosi
2017-05-12 14:14 ` tomas
2017-05-12 14:27 ` Emanuel Berg
2017-05-12 15:16 ` Drew Adams
2017-05-12 16:27 ` Emanuel Berg
2017-05-12 17:32 ` Drew Adams
2017-05-12 18:00 ` Emanuel Berg
2017-05-12 21:15 ` tomas
2017-05-12 21:28 ` N. Raghavendra
2017-05-12 22:08 ` Drew Adams
2017-05-13 14:15 ` N. Raghavendra
2017-05-13 14:59 ` Emanuel Berg
2017-05-13 15:07 ` Emanuel Berg
2017-05-13 15:22 ` Emanuel Berg
2017-05-13 15:34 ` N. Raghavendra
2017-05-13 15:54 ` Emanuel Berg
2017-05-13 17:59 ` Drew Adams
2017-05-14 13:07 ` N. Raghavendra
2017-05-12 19:30 ` Angelo Graziosi
2017-05-12 20:34 ` Drew Adams
2017-05-12 20:41 ` Drew Adams
2017-05-12 22:14 ` Angelo Graziosi
2017-05-12 23:42 ` Emanuel Berg
2017-05-13 0:22 ` John Mastro
2017-05-13 9:53 ` Emanuel Berg
2017-05-12 21:07 ` Emanuel Berg [this message]
2017-05-12 19:57 ` Angelo Graziosi
2017-05-12 20:56 ` 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
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=yw.86fug9n5r4.fsf@zoho.com \
--to=moasen@zoho.com \
--cc=help-gnu-emacs@gnu.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.
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).