Stefan Monnier <monn...@iro.umontreal.ca> writes: >>> emacs -e '(message "%S" comp-native-load-path)' > > Sorry, that should have been: > > emacs --eval '(message "%S" comp-native-load-path)' > > (which you can then try with `-q` and friends if needed). > >> I'm a bit mystified as to why everyone else on Debian isn't seeing this. >> I would have assumed it must be something in my startup files that is >> incompatible with the latest release of Emacs, except I thought -q >> --no-site-file should completely disable loading anything from my local >> configuration. > > My crystal ball suggests maybe your ~/.emacs.d is marked as read-only?
I don't know if this helps, but in addition to the recent issue we've identified where not having emacs-el installed can cause emacs from the current 28 packages to segfault on startup, people just figured out that if you try to install emacs via "su apt install emacs" (note the lack of a "-" argument to su) from a non-root account, emacs can end up failing for that account because the install ends up creating root-only directories (for I think the eln files, etc.) in ~. I'm not sure whether that's something that we'd expect to support (i.e. apt installs via sudo without -i or su without -), but I wanted to mention it since it's been reported (I think) more than once, and in case it indicates something that emacs might want to change (use of USER vs HOME, etc.). No personal position there right now either way. Thanks -- Rob Browning rlb @defaultvalue.org and @debian.org GPG as of 2011-07-10 E6A9 DA3C C9FD 1FF8 C676 D2C4 C0F0 39E9 ED1B 597A GPG as of 2002-11-03 14DD 432F AE39 534D B592 F9A0 25C8 D377 8C7E 73A4
