Closed maikol-solis closed 3 years ago
Various Emacs 27.1 builds on openSUSE seem to behave strangely. A few bugs I can reproduce nowhere else have been reported on our Discord. I'm not aware of any straightforward fix (and am not familiar with openSUSE), unfortunately, but i'm told there are multiple sources for 27.1 on openSUSE, so I'd suggest installing 27.1 from another source. If that doesn't work, then I'll have to hope that other openSUSE users can pitch in.
I found this reference (https://build.opensuse.org/package/show/editors/emacs#comment-1287071) mentioning the need of --no-x-resources
. I tested it and now doom-emacs seem good.
The message Package cl is deprecated
is still present, though.
I confirm the same issue is happening with me, openSUSE Tumbleweed. I am running it with --no-x-resources
as @maikol-solis mentioned
It's fixed https://bugzilla.opensuse.org/show_bug.cgi?id=1175372.
I tested the latest version (https://build.opensuse.org/package/show/editors/emacs [revision 285]) and for the moment the fonts and icons seems OK.
I will close the issue.
[...] i'm told there are multiple sources for 27.1 on openSUSE, so I'd suggest installing 27.1 from another source.
I want to clarify this a bit, in case it helps in the future. openSUSE is a project with two distributions Leap
and Tumbleweed
. In each of them there is one official Emacs package. Leap gets one "Service Pack" a year which could upgrade Emacs, in reality this was not the case recently (Leap still ships Emacs 25) while Tumbleweed is a rolling release and gets new Emacs versions relatively quickly.
What happens now is that Leap users also want Emacs 27 (or 26 previously) and add an additional repository. This additional repository is most likely from OBS. OBS is a build service that is used to build the distributions but also allows anyone to build their own packages, for many different Linux distributions.
There are different projects (basically namespace in OBS) that build Emacs 27, one of which is the "devel" project for Tumbleweed. This is often used, as it has to be maintained to keep Tumbleweed up to date. It's the one that was used by the first report on Discord, on a Leap system. I guess you could call this semi-official, but the only tested version of Emacs in Leap is still 25. On Tumbleweed this is basically a pre-QA version that is changing more quickly than the version in the official repo, but generally pretty close (few days delta). For that reason many TW users only noticed the issue after the official package was updated while Leap users noticed it earlier.
Then there are "home"-projects, these have various levels of quality and are not recommended for consumption. While using one might work fine, here you are on your own pretty much. In the context of Emacs, there is one that I've used that is pretty reliable, but it is still a version of Emacs maintained by someone (in this case an Emacs upstream contributor) in their personal Emacs project.
I hope this clarifies the openSUSE situation a bit, in the end only "one" Emacs build was broken (on different distros, which are technically multiple builds from the same source with the same recipe).
@hlissner btw, you can always ping me in openSUSE related issues
What did you expect to happen? Start a emacs with smooth fonts and with
all-the-icons
rendered properly.What actually happened? The fonts and the icons are completely broken.
There are two weird messages when I started with
emacs --debug-init
Error during redisplay: (clear-minibuffer-message) signaled (void-function timerp)
Package cl is deprecated
Also
(find-font (font-spec :family "all-the-icons"))
returnsnil
, butAdditional details:
Screenshots
![d2](https://user-images.githubusercontent.com/4078489/90419034-2f70bd80-e073-11ea-8f65-104740461c97.png)
*Message*
buffer withemacs --debug-init
doom doctor
Steps to reproduce:
.emacs.d
,emacs-doom
.System information: