bug-gnu-emacs
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

bug#38750: Segmentfault on Emacs 26.3


From: Robert Pluim
Subject: bug#38750: Segmentfault on Emacs 26.3
Date: Sun, 29 Dec 2019 22:05:25 +0100

>>>>> On Thu, 26 Dec 2019 19:25:44 +0200, Eli Zaretskii <eliz@gnu.org> said:

    >> From: c4droid <c4droid@foxmail.com>
    >> Date: Thu, 26 Dec 2019 20:14:13 +0800
    >> Cc: hekinami <zoubibo@amiunique.net>
    >> 
    >> * Phenomenon
    >> GNU Emacs crashed with a segmentation fault by initializing with a font
    >> change setting.
    >> * Environment
    >> 1. Linux Mint 19.2
    >> 2. GNU Emacs 26.3 (Compiled from source)
    >> * How to reproduce
    >> 1. Use the specified .emacs.d (Latest commint 248995b)
    >> $ git clone --depth 1 https://github.com/hekinami/dotemacs ~/.emacs.d
    >> 2. Run emacs to initialize .emacs.d
    >> $ emacs # Be waiting for the completation of packages installing 
patiently
    >> 3. Create a file (Just because of a miss of the configuration)
    >> $ mkdir -p ~/.emacs.d/contents/organizer/fin
    >> $ touch ~/.emacs.d/contents/organizer/fin/fin.ledger
    >> 4. Revise .emacs.d/settings.org
    >> From:
    >> #+BEGIN_SRC emacs-lisp
    >> (use-package all-the-icons
    >> :ensure t) ;; M-x all-the-icons-install-fonts
    >> #+END_SRC
    >> To:
    >> #+BEGIN_SRC emacs-lisp
    >> (use-package all-the-icons
    >> :ensure t
    >> :config
    >> (set-fontset-font t 'unicode (font-spec :family "all-the-icons") nil 
'append)
    >> (set-fontset-font t 'unicode (font-spec :family "file-icons") nil 
'append)
    >> (set-fontset-font t 'unicode (font-spec :family "Material Icons") nil 
'append)
    >> (set-fontset-font t 'unicode (font-spec :family "github-octicons") nil 
'append)
    >> (set-fontset-font t 'unicode (font-spec :family "FontAwesome") nil 
'append)
    >> (set-fontset-font t 'unicode (font-spec :family "Weather Icons") nil 
'append)) ;; M-x all-the-icons-install-fonts
    >> #+END_SRC

    Eli> Another manifestation of bug#38569?

Could be. Could you try the latest emacs-27, Iʼve just pushed a change
for 38569 there?

Thanks

Robert





reply via email to

[Prev in Thread] Current Thread [Next in Thread]