unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
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 20:00:39 +0200	[thread overview]
Message-ID: <yw.86o9uylzug.fsf@zoho.com> (raw)
In-Reply-To: 8778c766-ce0a-4b42-939d-96b0f0b49a82@default

Drew Adams wrote:

> 2. For user options and faces, which is what
> Customize is for, it is precisely those whose
> definitions are _not_ so simple that it is
> especially helpful to use Customize and not
> just hand-code assignments etc.
>
> For both simple and complex defcustoms and
> deffaces you _can_ rely on Customize. It is
> for the complex ones that it can be
> especially helpful to use Customize (or its
> functions).

Here is just a difference of opinion. I think
Customize is *more* difficult and confusing
than to write code.

But even if it was simpler, which it isn't,
I wouldn't use it because writing code is much
more enjoyable and interesting.

Also, code opens the door to do anything.
With Customize, or any other code-producing
tool, you can only produce code that is
possible to produce with the tool. And what is
a computer tool? Code! Thus you, as
a programmer, are limited to what some other
programmer thought you should or shouldn't do.

> Knowing this won't stop you from doing
> whatever you want, of course. ;-)

Indeed, if anyone wants to use Customize, do
it. Just as if anyone wants to take their game
to the next level, it is right there.

Remember, "Advance to fast, you catch up with
death. But advance to slow, death catches up
with YOU!"

-- 
underground experts united
http://user.it.uu.se/~embe8573




  reply	other threads:[~2017-05-12 18:00 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 [this message]
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.86o9uylzug.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).