From: Angelo Graziosi <angelo.graziosi@alice.it>
To: Drew Adams <drew.adams@oracle.com>, help-gnu-emacs@gnu.org
Subject: Re: About how misspelled word are displayed
Date: Sat, 13 May 2017 00:14:51 +0200 [thread overview]
Message-ID: <93224ad6-b08b-ad39-6a0e-1e03f42b19ad@alice.it> (raw)
In-Reply-To: <a6b42310-7bc4-414c-bff9-bf54199caee1@default>
Il 12/05/2017 22:41, Drew Adams ha scritto:
>> IOW, we now have not only Customize writing to your `custom-file'
>> or init file; we have also the package system doing that.
>>
>> It's questionable whether that's a great idea - a question that was
>> discussed briefly on emacs-devel@gnu.org:...
>>
>> One of the Emacs maintainers asked there whether we shouldn't use a
>> different file for this. But AFAIK that thread went nowhere.
>>
>> An earlier thread also broached the question somewhat:...
>
> See also this thread, even earlier. As soon as the package system
> started writing to user init files (or `custom-file') people raised
> the question of making it use another file or files.
>
> http://lists.gnu.org/archive/html/emacs-devel/2014-06/msg00375.html
>
Thanks for all your clarification.
Finally I found where to customize: Customize Group: flyspell, and then
I found the flyspell-duplicate/incorrect options. Now my custom.el
(after a few tries) is:
$ cat custom.el
[...]
(custom-set-faces
;; custom-set-faces was added by Custom.
;; If you edit it by hand, you could mess it up, so be careful.
;; Your init file should contain only one such instance.
;; If there is more than one, they won't work right.
'(flyspell-duplicate ((t (:foreground "Gold3" :underline t :weight
bold))))
'(flyspell-incorrect ((t (:foreground "Red1" :underline t :weight
bold)))))
Thanks,
Angelo.
next prev parent reply other threads:[~2017-05-12 22:14 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 [this message]
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=93224ad6-b08b-ad39-6a0e-1e03f42b19ad@alice.it \
--to=angelo.graziosi@alice.it \
--cc=drew.adams@oracle.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).