Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#54984 - [emacs] It is impossible to set the default font from ~/.emacs

Attached to Project: Arch Linux
Opened by Vorbote (vorbote) - Sunday, 30 July 2017, 23:08 GMT
Last edited by Jürgen Hötzel (juergen) - Sunday, 17 March 2019, 13:56 GMT
Task Type Bug Report
Category Upstream Bugs
Status Closed
Assigned To Jürgen Hötzel (juergen)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

This is "Emacs bug#25228 - custom-set-faces from init file ~/.emacs ignored" <https://debbugs.gnu.org/cgi/bugreport.cgi?bug=25228>, not yet fixed in master, btw. The font settings in gsettings or in gconf override whatever font options are set using the provided option tools in Emacs. The quickest fix is to compile Emacs with "--without-gconf --without-dconf".
This task depends upon

Closed by  Jürgen Hötzel (juergen)
Sunday, 17 March 2019, 13:56 GMT
Reason for closing:  Fixed
Additional comments about closing:  Also see: https://bugs.archlinux.org/task/59887
Comment by Thiago Perrotta (thiagowfx) - Monday, 31 July 2017, 10:36 GMT
This sounds like an upstream bug.
Comment by Vorbote (vorbote) - Monday, 31 July 2017, 11:19 GMT
Did you *actually* read the bug report? Of course it is an upstream bug. I'm reporting the upstream bug tracker discussion and A SOLUTION that does not require patching?

Geez, some people think bug trackers work like facebook.
Comment by Thiago Perrotta (thiagowfx) - Monday, 31 July 2017, 11:28 GMT
https://wiki.archlinux.org/index.php/Reporting_bug_guidelines#Upstream_or_Arch.3F

Your response sounds too emotional for a simple bug report. It would have helped to /explicitly/ state that it is an upstream bug.

Also, https://git.archlinux.org/svntogit/packages.git/tree/trunk/PKGBUILD?h=packages/emacs: 'gconf' is currently a dependency. Suggesting to remove it as a fix it is like suggesting to remove gtk3 (and use gtk2 instead). It's better to call it a 'temporary workaround' instead.
Comment by Vorbote (vorbote) - Monday, 31 July 2017, 14:49 GMT
Meh. I'm not emotional but I certainly find interventions that violate https://wiki.archlinux.org/index.php/Code_of_conduct#Ineffective_discussion_.28.22bikeshed.22.29 a nuisance.

And both your first and second comments violate https://wiki.archlinux.org/index.php/Code_of_conduct#Correctness because,

1. You did not read the bug report; just blabbed whatever. You even go to the length of trying to justify yourself by arguing that "removing dconf is like removing gtk3", see below. Please engage brains before touching keyboard.

2. Have you every packaged emacs? I package emacs master and emacs pretest in AUR. Take that as you may.

Neither gconf nor dconf are really necessary besides being an indirect dependency on the GTK+ version used for a graphical toolkit, besides reporting the font used by the desktop environment and should be overridable by using the "normal" (custom-set-faces '(default)) array in .emacs. This was broken sometime in H2 last year and I did not notice because I used to use (set-frame-font) and (set-menu-font) for years until I forgot to copy my .emacs to a fresh install this past weekend.
Comment by Eli Schwartz (eschwartz) - Monday, 31 July 2017, 15:05 GMT
Thiago, the bug description made it clear that this is a workaround for an upstream bug. There is no need to be redundant about it, Scimmia and I are quite capable of deducing explicitly stated facts and fixing the Category.

Pedro, you are emotionally overreacting to this in a rather extreme way. You need to stop with the personal attacks and hysteria, which are several times more distracting than what you are replying to. Justifying it with the Code of Conduct is somewhat hypocritical -- consider that https://wiki.archlinux.org/index.php/Code_of_conduct#Do_not_flame is also a rule.
Comment by Thiago Perrotta (thiagowfx) - Tuesday, 01 August 2017, 18:10 GMT
Hi Eli, I'm sorry for my redundancy in this case then. I just tried to (implicitly) highlight that it would overload the bug wranglers if we started to report (low-priority?) upstream bugs here. Of course, this is a gray area, it's not always clear (in terms of usefulness vs awareness) when to duplicate a bug report here. I won't express my point of view about this here because I realize it is not the appropriate place but, again, sorry if you think my comment was not useful and thanks for your professional conduct.

Loading...