From: martin rudalics <rudalics@gmx.at>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 25228@debbugs.gnu.org
Subject: bug#25228: 25.1; GNU emacs 25.1: custom-set-faces from init file ~/.emacs ignored
Date: Thu, 22 Dec 2016 18:45:46 +0100 [thread overview]
Message-ID: <585C114A.8020406@gmx.at> (raw)
In-Reply-To: <838tr727oa.fsf@gnu.org>
> I agree, but I'm not sure we have anyone aboard who can tell.
Neither am I.
> Failing that, would unbinding the above solve the problem?
Forcefully.
> If so, we
> could suggest that to people as workaround, until we find a proper
> solution.
Please do that. Maybe in a way that people who simply wonder why their
default font settings all of a sudden get overridden do not have to
understand what's going on. Something like "If you see this happen, put
(define-key special-event-map [config-changed-event] 'ignore)
into your .emacs.".
martin
next prev parent reply other threads:[~2016-12-22 17:45 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-19 10:03 bug#25228: 25.1; GNU emacs 25.1: custom-set-faces from init file ~/.emacs ignored Dr. Werner Fink
2016-12-19 15:09 ` bug#25228: [emacs-bug] " Dr. Werner Fink
2016-12-19 17:37 ` Eli Zaretskii
2016-12-19 18:36 ` martin rudalics
2016-12-19 18:57 ` Eli Zaretskii
2016-12-19 20:20 ` martin rudalics
2016-12-19 20:43 ` Eli Zaretskii
2016-12-20 10:59 ` martin rudalics
2016-12-20 16:11 ` Eli Zaretskii
2016-12-20 16:25 ` martin rudalics
2016-12-20 17:06 ` Eli Zaretskii
2016-12-20 17:28 ` Dr. Werner Fink
2016-12-20 17:34 ` martin rudalics
2016-12-20 17:55 ` Eli Zaretskii
2016-12-20 18:18 ` martin rudalics
2016-12-20 18:39 ` Eli Zaretskii
2016-12-20 18:49 ` martin rudalics
2016-12-20 19:31 ` Eli Zaretskii
2016-12-20 19:11 ` Rostislav Svoboda
2016-12-20 19:24 ` Rostislav Svoboda
2016-12-20 19:34 ` Eli Zaretskii
2016-12-20 21:50 ` Rostislav Svoboda
2016-12-21 7:42 ` martin rudalics
2016-12-21 11:03 ` Rostislav Svoboda
2016-12-21 17:25 ` Eli Zaretskii
2016-12-22 8:35 ` martin rudalics
2016-12-22 11:59 ` Rostislav Svoboda
2016-12-22 17:45 ` martin rudalics
2016-12-20 19:29 ` martin rudalics
2016-12-21 8:11 ` Dr. Werner Fink
2016-12-21 8:47 ` bug#25228: [emacs-bug] " Dr. Werner Fink
2016-12-21 8:56 ` martin rudalics
2016-12-21 11:08 ` Dr. Werner Fink
2016-12-22 8:35 ` martin rudalics
2016-12-22 11:46 ` Dr. Werner Fink
2016-12-22 17:44 ` martin rudalics
2016-12-23 7:20 ` Dr. Werner Fink
2016-12-21 17:24 ` Eli Zaretskii
2016-12-21 17:39 ` Dr. Werner Fink
2016-12-21 18:04 ` Eli Zaretskii
2016-12-21 8:48 ` martin rudalics
2016-12-21 12:08 ` Dr. Werner Fink
2016-12-21 17:34 ` Eli Zaretskii
2016-12-22 8:35 ` martin rudalics
2016-12-22 17:30 ` Eli Zaretskii
2016-12-22 17:45 ` martin rudalics [this message]
2016-12-23 7:29 ` Dr. Werner Fink
2016-12-20 11:18 ` Dr. Werner Fink
2016-12-20 16:15 ` Eli Zaretskii
2016-12-20 16:41 ` Dr. Werner Fink
2016-12-20 16:56 ` bug#25228: [emacs-bug] " Dr. Werner Fink
2016-12-20 17:58 ` Eli Zaretskii
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=585C114A.8020406@gmx.at \
--to=rudalics@gmx.at \
--cc=25228@debbugs.gnu.org \
--cc=eliz@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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).