Fork me on GitHub
#emacs
<
2021-03-24
>
solf00:03:56

Anyone with a apple M1 computer here? What emacs do you use? I've tried compiling from source, but it segfaults. I've also downloaded a x86 binary which works okay (kinda slow though), except for magit that takes like 3 seconds for any action.

andy.fingerhut00:03:50

I do not have an M1-based Mac, but this web site seems more likely to do a good job for Mac builds of Emacs than some others: https://emacsformacosx.com/

andy.fingerhut00:03:41

You may also want to try MacPorts or Homebrew -- again I do not have an M1-based Mac, so don't know how well those tools support M1's yet, but lots of devs enhancing the build scripts for those things are likely to be early M1 adopters.

solf00:03:03

The one I have is from that website, I don't know why magit is so slow. Supposedly, that issue was fixed on osx. Macports segfaults during compile for me. As for homebrew... I tried installing from that yesterday, but it failed telling me bad CPU. I later learned that it's because I need to manually install rosetta 2 (x86 emulator), so I think I'll try homebrew again

solf00:03:00

All in all, this macbook air is kinda cool, but definitely some rough edges to replicate my clojure dev environment

andy.fingerhut00:03:42

Sorry, bad guesses on my part, sounds like. I am waiting until M1's are out in a bigger screen and memory footprint before I shell out for one, and as a side benefit other devs will hopefully have smoothed things out for me by then 🙂

solf00:03:12

ahah yeah

solf00:03:13

I'm also waiting for a bigger screen and ram. Which is why I took a cheap refurbished air model. From what I've seen, macs retain a lot of resell value, so I hope I'll be able to switch without breaking the wallet. Specially if I resell if after coming back to europe (I'm in singapore right now). Macs there seem a good 30% more expensive

AC01:03:01

I use gnu emacs-27 branch + Mitsuharu Yamamoto’s patches. I had to recently downgrade my version of autoconf to 2.69 because 2.71 caused a sigkill.

AC01:03:16

I don’t know why yet, but 2.7x has some big changes and rewrites some of the build files. no issues building with 2.71 on my intel macs.

solf03:03:12

ooh thanks, maybe the autoconf was my issue too

Lu22:03:37

Hello! This one is for the clojure-lsp users. I am running lsp-rename and after writing the new symbol and hitting enter nothing is renamed and I see no error in the messages buffer.. Any idea? Other lsp commands work just fine so not sure what the problem might be

ericdallo22:03:50

Check cloure-lsp logs

Lu22:03:26

mmm nothing useful I’d say

2021-03-24T22:33:39.628Z  DEBUG [clojure-lsp.main:?] - :hover 14ms
2021-03-24T22:33:39.631Z  DEBUG [clojure-lsp.main:?] - :codeAction 18ms
2021-03-24T22:33:43.670Z  DEBUG [clojure-lsp.main:?] - :rename 4ms

Lu22:03:32

it just ends with a rename

ericdallo22:03:44

what is your clojure-lsp --version?

ericdallo22:03:05

check emacs clojure-lsp stderr buffer as well

Lu22:03:06

I literally just got it so

clojure-lsp 2021.03.21-23.29.19
clj-kondo 2021.03.04-SNAPSHOT

Lu22:03:47

emacs msg and stderr buffers say pretty much nothing.. I wonder If the feature might be conflicting with something else I use

ericdallo22:03:10

I don't know any emacs feature that could conflict with that

ericdallo22:03:53

it could be a lsp-mode issue, to make sure, we need to check client<->server json request/response

Lu22:03:23

hold on I tried in a shadow-cljs project and it worked

Lu22:03:49

to test that I was initially using a fresh lein project.

ericdallo22:03:40

yeah, minimal repros always help to find the issue

Lu22:03:43

Ok I think I figured it out.. when renaming the project dir I needed to kill and reopen all buffers for clojure-lsp to work properly.. I was getting errors like db being nil or server couldn’t start

ericdallo22:03:22

Hum, probably some kind of out of sync with lsp-mode

ericdallo22:03:34

in those cases, lsp-workspace-restart should fix

Lu22:03:37

on dir rename I got again the prompt to point to the new project root but maybe something goes wrong.. anyways thanks for getting back so quickly .. it’s really not a common scenario tbh

Lu22:03:54

oh I see haven’t tried that command

ericdallo22:03:26

glad it works now 🙂

❤️ 3