From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Drew Adams Newsgroups: gmane.emacs.help Subject: RE: About how misspelled word are displayed Date: Fri, 12 May 2017 08:16:46 -0700 (PDT) Message-ID: <8479790d-443e-48fc-a59b-f14a917fafab@default> References: <3993ee96-42e7-e597-f7d0-306003faa235@alice.it> <40f5d8bd-8956-b3fa-1818-eb3622f6ff12@alice.it> <20170512141406.GA27429@tuxteam.de> NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Trace: blaine.gmane.org 1494602246 2856 195.159.176.226 (12 May 2017 15:17:26 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Fri, 12 May 2017 15:17:26 +0000 (UTC) To: Emanuel Berg , help-gnu-emacs@gnu.org Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Fri May 12 17:17:19 2017 Return-path: Envelope-to: geh-help-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1d9CJi-0000Zp-Qk for geh-help-gnu-emacs@m.gmane.org; Fri, 12 May 2017 17:17:18 +0200 Original-Received: from localhost ([::1]:54170 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1d9CJo-0001MC-D0 for geh-help-gnu-emacs@m.gmane.org; Fri, 12 May 2017 11:17:24 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:57601) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1d9CJK-0001M3-9E for help-gnu-emacs@gnu.org; Fri, 12 May 2017 11:16:55 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1d9CJH-0004wy-3G for help-gnu-emacs@gnu.org; Fri, 12 May 2017 11:16:54 -0400 Original-Received: from userp1040.oracle.com ([156.151.31.81]:19881) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1d9CJG-0004vu-NL for help-gnu-emacs@gnu.org; Fri, 12 May 2017 11:16:51 -0400 Original-Received: from userv0021.oracle.com (userv0021.oracle.com [156.151.31.71]) by userp1040.oracle.com (Sentrion-MTA-4.3.2/Sentrion-MTA-4.3.2) with ESMTP id v4CFGmbc002859 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Fri, 12 May 2017 15:16:48 GMT Original-Received: from userv0121.oracle.com (userv0121.oracle.com [156.151.31.72]) by userv0021.oracle.com (8.14.4/8.14.4) with ESMTP id v4CFGmFw027247 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Fri, 12 May 2017 15:16:48 GMT Original-Received: from abhmp0013.oracle.com (abhmp0013.oracle.com [141.146.116.19]) by userv0121.oracle.com (8.14.4/8.13.8) with ESMTP id v4CFGlDP008615; Fri, 12 May 2017 15:16:48 GMT In-Reply-To: X-Priority: 3 X-Mailer: Oracle Beehive Extensions for Outlook 2.0.1.9.1 (1003210) [OL 12.0.6767.5000 (x86)] X-Source-IP: userv0021.oracle.com [156.151.31.71] X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.4.x-2.6.x [generic] [fuzzy] X-Received-From: 156.151.31.81 X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Users list for the GNU Emacs text editor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Original-Sender: "help-gnu-emacs" Xref: news.gmane.org gmane.emacs.help:113001 Archived-At: > > Customize will do exactly that for you: use > > Customize and then go look into your > > initialization file. Move the code around to > > your heart's content. Best of both worlds! >=20 > And the next time you use Customize, what will > happen? More ugly code added - more confusion - > no, don't use it - hands of our Elisp! - instead: > (modify-face font-lock-keyword-face "green" "black" nil t) 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. Some user options have special initialization or setting functions that are triggered automatically by Customize. If your hand-written code uses `custom*' functions then it is probably OK. But if not then it risks bypassing those triggers.