Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.debian.bugs.dist > #1114299

Bug#1017739: emacs-lucid cannot start after upgrade

From Russ Allbery <rra@debian.org>
Newsgroups linux.debian.bugs.dist
Subject Bug#1017739: emacs-lucid cannot start after upgrade
Date 2022-08-24 05:10 +0200
Message-ID <EXOWd-2Far-3@gated-at.bofh.it> (permalink)
References (4 earlier) <EXDep-2xvk-9@gated-at.bofh.it> <EXNQt-2E31-1@gated-at.bofh.it> <EXO0a-2Eoz-1@gated-at.bofh.it> <EWfe9-1G9K-3@gated-at.bofh.it> <EXO0a-2Eoz-1@gated-at.bofh.it>
Organization The Eyrie

Show all headers | View raw


Stefan Monnier <monnier@iro.umontreal.ca> writes:

> 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).

To be clear, $HOME was pointing correctly at /root.  Emacs ignored $HOME
and instead created $USER/.emacs.d/eln-cache, which was surprising.  (su
without - still changes $HOME but not $USER.)

Or at least I think that's happened, and the correct thing happened when I
overrode $USER (and $LOGNAME) and then did the same thing again with
otherwise the same environment variables.

-- 
Russ Allbery (rra@debian.org)              <https://www.eyrie.org/~eagle/>

Back to linux.debian.bugs.dist | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread


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