2022-04-06 spacemacs | Clojure Slack Archive

spacemacs

Drew Verlee 2022-04-06T16:52:28.915049Z

When i start emacs I can't do anything for about 20 seconds while it seems to do something relating to fonts

Unicode Fonts - Mapping Unicode Blocks in fontset-default ... done
Unicode Fonts - Mapping Overrides in fontset-default ... done
Unicode Fonts - Mapping Unicode Blocks in fontset-startup ... done
Unicode Fonts - Mapping Overrides in fontset-startup ... done
Unicode Fonts - Mapping Unicode Blocks in fontset-standard ... done
Unicode Fonts - Mapping Overrides in fontset-standard ... done
Starting new Ispell process /usr/bin/aspell with default dictionary...done

practicalli-johnny 2022-05-05T10:23:39.936699Z

I am seeing this unicode-font issue more as I have been restarting Emacs more often recently. I raised an issue to see if anyone else has ideas https://github.com/syl20bnr/spacemacs/issues/15498

practicalli-johnny 2022-05-05T13:06:01.588289Z

I built Emacs 28.1 from source (https://github.com/practicalli/blog/issues/129) and it doesnt have the issue with Unicode These are the steps I took to build Emacs: https://github.com/practicalli/blog/issues/129

Drew Verlee 2022-05-05T19:31:04.627679Z

@johanatan I'll give this a try, as i still don't feel like things are as stable for me as as i get the feeling they are for others.

johanatan 2022-05-05T20:33:44.008559Z

Was that meant for me?

Drew Verlee 2022-05-05T20:34:27.330869Z

It wasn't, sorry.

Drew Verlee 2022-05-05T20:44:44.064329Z

I didn't ask him anything, i think he was trying to see if a different build had an issue. Meanwhile i keep getting small bugs here and there with how i installed emacs. So part of me was thinking this installation might be better. I didn't look into it much, so I'm probably getting ahead of myself.

Drew Verlee 2022-04-06T16:56:32.035039Z

in my init file I see the following config which might be related

;; Support font ligatures (fancy symbols) in all modes
     ;; 'prog-mode for only programming languages
     ;; including text-mode may cause issues with org-mode and magit
     (unicode-fonts :variables
                    unicode-fonts-enable-ligatures t
                    unicode-fonts-ligature-modes '(prog-mode))

commenting that out seems to stop the "Mapping" at startup. Not sure what it was doing for me though 🙂. Well as the comment suggested, my fancy symbols went away. A great darkness has come upon me.

practicalli-johnny 2022-04-06T18:08:13.113189Z

I have seen similar messages and startup time extended, usually after restarting Emacs following a package upgrade. I dont remember seeing the messages at other times, but I rarely restart Emacs outside of a package update (which can be months)

practicalli-johnny 2022-04-06T18:14:58.245419Z

The unicode layer includes a cache, so the font mappings should only update (at Emacs startup) when a font is added or removed, or relevant configuration options are changed. So the mapping shouldnt happen on each Emacs restart.

practicalli-johnny 2022-04-06T18:17:45.281859Z

Is your OS updating fonts when you are not looking?

practicalli-johnny 2022-04-06T18:19:40.248989Z

In the unicode-fonts emacs package, it suggests using customize in Emacs to remove fonts, which may improve startup time https://github.com/rolandwalker/unicode-fonts#startup-speed I havent tried this myself...

Drew Verlee 2022-04-06T19:57:36.999329Z

i'll take a look, sometimes these issues just disappear after another round of updates 🙂

practicalli-johnny 2022-04-06T19:57:30.169969Z

FYI. the latest magit package has changed they way key bindings are defined and this clashes with evil-surround, so using v and s to stage individual lines of a hunk does not currently work. The change was made 12 days ago, so any package earlier than that should work. I simply copied the magit folder from the rollback directory into the elpa directory and restarted Emacs, seems to work okay, although a proper rollback is a safer approach https://github.com/syl20bnr/spacemacs/issues/15448

👍 3

practicalli-johnny 2022-04-11T17:31:07.934229Z

A pull request has been created to remove evil-surround from the git (Magit) layer. This will resolve the issue with the latest magit release https://github.com/syl20bnr/spacemacs/pull/15462

practicalli-johnny 2022-04-15T08:00:48.352279Z

The pull request has been merged to specify fix magit status. There is a more general issue of evil-surround being globally on by default, whereas it should only be for text and programming modes. There may be other modes where evil-surround is useful, if so then a comment on this issue will help https://github.com/syl20bnr/spacemacs/issues/15463

eggsyntax 2022-04-14T20:54:26.234819Z

Thanks for figuring this out, y’all, just came looking to see if anyone was clear on what was going on. Cheers!

sgepigon 2022-04-07T17:07:35.033349Z

Small workaround I found is to call magit-dispatch (with ? key) then do s. So steps are: 1. highlight lines 2. ? 3. s. It’s a bit clunky so rolling back makes a lot of sense too.

practicalli-johnny 2022-04-08T23:56:47.523509Z

A nice little work around, thanks. It seems the plan is to turn off evil-surround globally and only enable it for specific modes. Therefore toggle evil-surround off seems to work SPC SPC evil-surround-mode in the magit status buffer allows staging of a region within a hunk

👍 1

Clojurians Log v2

spacemacs