Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.bugs.dist > #1116900
| From | Stefan Monnier <monnier@iro.umontreal.ca> |
|---|---|
| Newsgroups | linux.debian.bugs.dist |
| Subject | Bug#1017739: emacs-lucid cannot start after upgrade |
| Date | 2022-09-12 03:40 +0200 |
| Message-ID | <F4GAx-6WMp-3@gated-at.bofh.it> (permalink) |
| References | (7 earlier) <EWfe9-1G9K-3@gated-at.bofh.it> <EXOWd-2Far-3@gated-at.bofh.it> <F4DsZ-6UUT-5@gated-at.bofh.it> <EWfe9-1G9K-3@gated-at.bofh.it> <F4DsZ-6UUT-5@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
> -"$flavor" --no-init-file --no-site-file -batch -f batch-byte-compile \
> +"$flavor" --no-init-file --no-site-file -batch -f batch-byte-compile --eval='(setq native-comp-speed -1)' \
I don't think `(setq native-comp-speed -1)` does what we need here:
[...]
options of the compiler. The value −1 means disable
native-compilation: functions and files will be only byte-compiled;
however, the ‘*.eln’ files will still be produced, they will just
contain the compiled code in bytecode form. (This can be achieved
[...]
I'm not sure what's the best way to go about disabling automatic native
compilation, but I think `native-comp-deferred-compilation-deny-list`
might work.
Of course, another way to fix this is to actually fix the original
problem where the wrong directory (i.e. `~$USER/.emacs.d` instead of
`$HOME/.emacs.d`) is chosen. This original problem affects other
circumstances where Emacs will write to the `.emacs.d` directory so it
would be good to fix it more generally.
A "quick fix" is to start Emacs with an explicit
`--init-directory` argument.
It's too late to get this fixed for Emacs-28,2, but this really should
be reported as a bug.
Stefan
Back to linux.debian.bugs.dist | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Bug#1017739: emacs-lucid cannot start after upgrade Russ Allbery <rra@debian.org> - 2022-08-19 20:50 +0200
Bug#1017739: emacs-lucid cannot start after upgrade Stefan Monnier <monnier@iro.umontreal.ca> - 2022-08-22 01:40 +0200
Bug#1017739: emacs-lucid cannot start after upgrade Andrea Corallo <akrl@sdf.org> - 2022-08-22 11:30 +0200
Bug#1017739: emacs-lucid cannot start after upgrade Adam Lackorzynski <adam@os.inf.tu-dresden.de> - 2022-08-22 21:30 +0200
Bug#1017739: emacs-lucid cannot start after upgrade Rob Browning <rlb@defaultvalue.org> - 2022-08-23 06:30 +0200
Bug#1017739: emacs-lucid cannot start after upgrade Russ Allbery <rra@debian.org> - 2022-08-23 06:50 +0200
Bug#1017739: emacs-lucid cannot start after upgrade Rob Browning <rlb@defaultvalue.org> - 2022-08-23 07:10 +0200
Bug#1017739: emacs-lucid cannot start after upgrade Adam Lackorzynski <adam@os.inf.tu-dresden.de> - 2022-08-23 11:10 +0200
Bug#1017739: emacs-lucid cannot start after upgrade Stefan Monnier <monnier@iro.umontreal.ca> - 2022-08-23 16:40 +0200
Bug#1017739: emacs-lucid cannot start after upgrade Rob Browning <rlb@defaultvalue.org> - 2022-08-24 04:00 +0200
Bug#1017739: emacs-lucid cannot start after upgrade Stefan Monnier <monnier@iro.umontreal.ca> - 2022-08-24 04:10 +0200
Bug#1017739: emacs-lucid cannot start after upgrade Russ Allbery <rra@debian.org> - 2022-08-24 05:10 +0200
Bug#1017739: emacs-lucid cannot start after upgrade Stefan Monnier <monnier@iro.umontreal.ca> - 2022-08-24 14:00 +0200
Bug#1017739: emacs-lucid cannot start after upgrade David Bremner <bremner@debian.org> - 2022-09-12 00:20 +0200
Bug#1017739: emacs-lucid cannot start after upgrade Stefan Monnier <monnier@iro.umontreal.ca> - 2022-09-12 03:40 +0200
Bug#1017739: emacs-lucid cannot start after upgrade David Bremner <bremner@debian.org> - 2022-09-13 02:10 +0200
csiph-web