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 18:27:10 +0200 [thread overview]
Message-ID: <yw.86shkam469.fsf@zoho.com> (raw)
In-Reply-To: 8479790d-443e-48fc-a59b-f14a917fafab@default
Drew Adams wrote:
> Just use a separate `custom-file'.
> Customize does not _want_ to fiddle with your
> init file, but if you do not tell it another
> file to use instead (`C-h v custom-file')
> then your init file wins.
>
> For simple stuff, yes, you can code such
> customizations by hand. But why do that
> (except to practice and learn more, which can
> be a fine reason)?
>
> And for stuff that is not so simple, it is
> better to rely on Customize. It knows the
> customize code better than you/we do.
OK, so when it gets not so simple, one should
not rely on Customize anymore. But if one
cannot solve so simple things without relying
on Customize, how can one be expected to solve
things that are not so simple suddenly?
Apart from the principle, Customize is not
easier than to put a couple of lines of code
into a text file. Customize is much more
complicated and I don't want to ever rely on
complicated stuff, and certainly not for doing
simple things.
--
underground experts united
http://user.it.uu.se/~embe8573
next prev parent reply other threads:[~2017-05-12 16:27 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 [this message]
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
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.86shkam469.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).