Stefan Monnier <monn...@iro.umontreal.ca> writes: > I don't know why it fails to find a writable directory. Maybe
> emacs --debug-init` would help > or > emacs -e '(message "%S" comp-native-load-path)' > might help track down the origin of the problem. % emacs --debug-init Cannot find suitable directory for output in ‘comp-native-load-path’. % emacs -e '(message "%S" comp-native-load-path)' Cannot find suitable directory for output in ‘comp-native-load-path’. If instead I run: % emacs -q --no-site-file -e '(message "%S" comp-native-load-path)' then Emacs opens a window and starts, but just produces the error message: command-line-1: Symbol’s function definition is void: \(message\ \"%S\"\ comp-native-load-path\) Trying to run the same elisp with M-: in that running Emacs just says: defalias: Cannot find suitable directory for output in ‘comp-native-load-path’. Looks like I may need a build with your patch before I can figure out what's going wrong with that variable, since Emacs seems to be so broken that it doesn't know how to introspect itself. 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. -- Russ Allbery (r...@debian.org) <https://www.eyrie.org/~eagle/>
