Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.bugs.dist > #1114297
| From | Stefan Monnier <monnier@iro.umontreal.ca> |
|---|---|
| Newsgroups | linux.debian.bugs.dist |
| Subject | Bug#1017739: emacs-lucid cannot start after upgrade |
| Date | 2022-08-24 04:10 +0200 |
| Message-ID | <EXO0a-2Eoz-1@gated-at.bofh.it> (permalink) |
| References | (3 earlier) <EWfe9-1G9K-3@gated-at.bofh.it> <EXDep-2xvk-9@gated-at.bofh.it> <EXNQt-2E31-1@gated-at.bofh.it> <EWfe9-1G9K-3@gated-at.bofh.it> <EXNQt-2E31-1@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
> 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.).
You might want to report it, at least so Emacs maintainers are aware of
the problem. And also maybe the startup code can then report a more
specific error when it encounters a `~/.emacs.d/eln-cache` that belongs
to some other user.
Personally I think running something like Emacs as root with $HOME
pointing to some other user's home directory is a "pilot error", but
then again I'm one of those who didn't notice the infamous "su" change
because I never use `su` without `-` (because I simply don't
understand what is its intended semantics).
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