Stefan Monnier writes:
>
> 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` directo
I think what we want in Debian is no native compilation when installing
Emacs. There is really no benefit for most people to caching the eln
files in ~root, and there are possible bad effects as demonstrated by
this bug.
Attached is a proposed patch to emacsen-common. I'll reassign this bug
there
Stefan Monnier 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'
Stefan Monnier 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
On Mon Aug 22, 2022 at 14:53:57 -0700, Russ Allbery wrote:
> Control: severity -1 important
>
> Adam Lackorzynski writes:
>
> > I had the same issue. Turned out my personal .emacs.d/eln-cache
> > directory and its folders belonged to root:
>
> > $ ls -la $HOME/.emacs.d/eln-cache
> > total 16
Russ Allbery writes:
> For what it's worth, this is the first package that I recall having
> trouble with during installation, and I've been using Debian for quite a
> while. :)
>
> That doesn't mean you're wrong -- you've got a good point and I should get
> in the habit of using -.
Oh, I don't
Rob Browning writes:
> Possibly, but I'd assumed the installation processs should expect a
> "normal" root environment, and if so, "su" without the dash wouldn't
> qualify. Otherwise, random user .bashrc changes (that su doesn't reset)
> could affect the install.
For what it's worth, this is th
Russ Allbery writes:
> Oh, good catch! The same thing was true of mine.
>
> I think the dates were when I upgraded Emacs. Let me take a guess: are
> you also old-school and use su from a regular user account when installing
> new packages? HOME gets overridden by su, but LOGNAME and USER do no
Control: severity -1 important
Adam Lackorzynski writes:
> I had the same issue. Turned out my personal .emacs.d/eln-cache
> directory and its folders belonged to root:
> $ ls -la $HOME/.emacs.d/eln-cache
> total 16
> drwxr-xr-x 4 root root 4096 Aug 21 19:32 .
> drwx-- 4 adam users 4096 Au
On Fri Aug 19, 2022 at 11:42:30 -0700, Russ Allbery wrote:
> Package: emacs-lucid
> Version: 1:28.1+1-1
> Severity: grave
> X-Debbugs-Cc: r...@debian.org
>
> The 28.1 version of emacs-lucid fails on startup with a cryptic error
> message:
>
> % emacs
> Cannot find suitable directory for output
Stefan Monnier 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 out
Stefan Monnier writes:
> Russ Allbery [2022-08-19 11:42:30] wrote:
>> The 28.1 version of emacs-lucid fails on startup with a cryptic error
>> message:
>>
>> % emacs
>> Cannot find suitable directory for output in ‘comp-native-load-path’.
>>
>> Running emacs -q allows it to start, but it still re
Package: emacs-lucid
Version: 1:28.1+1-1
Severity: grave
X-Debbugs-Cc: r...@debian.org
The 28.1 version of emacs-lucid fails on startup with a cryptic error
message:
% emacs
Cannot find suitable directory for output in ‘comp-native-load-path’.
Running emacs -q allows it to start, but it still re
13 matches
Mail list logo
