emacs-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Modified remote file name syntax


From: Michael Albinus
Subject: Re: Modified remote file name syntax
Date: Tue, 14 Mar 2017 10:57:24 +0100
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/26.0.50 (gnu/linux)

Tino Calancha <address@hidden> writes:

Hi Tino,

> On Tue, 14 Mar 2017, Michael Albinus wrote:
>
>> Tino Calancha <address@hidden> writes:
>>
>>> I see following error in *Async Shell Command*:
>>> (maybe someone suspect something)
>>>
>>> Warning: arch-dependent data dir
>>> '/usr/local/libexec/emacs/26.0.50/x86_64-pc-linux-gnu/': No such file
>>> or directory
>>> Warning: Lisp directory '/usr/local/share/emacs/26.0.50/lisp': No such
>>> file or directory
>>> Warning: Could not find simple.el or simple.elc
>>> Gtk-Message: Failed to load module "pk-gtk-module"
>>> Gtk-Message: Failed to load module "pk-gtk-module"
>>>
>>> The new Emacs instance shows the *scratch* buffer and the error:
>>> Cannot open load file: No such file or directory, mule-util
>>>
>>> Following also works fine.
>>> M-& which ~/bin/emacs -Q
>>>
>>> If i checkout the commit right before yours, that is
>>> f591765e2b6b9ec3fa3ff647c77a10c984f78133
>>> i don't reproduce the issue.
>>
>> Did you run "make bootstrap"? My commit changes autoloads; while working
>> on the patch I was urged several time to run a bootstrap in order to
>> bring Emacs in a proper state.
> Yes i did.  The problem still arise.

I have no further idea. However, messages like "Warning: Lisp directory
'/usr/local/share/emacs/26.0.50/lisp': No such file or directory" look
very suspicious.

If you run this constellation prior my patch (everything works fine),
could you check in the running Emacs where simple.el and other files are
located according to M-x locate-library ?

It seems also to me, that /usr/local/share/emacs/26.0.50/lisp should not
be in game. I suppose, that you haven't run "make install" yet;
everything at /usr/local/share might not contain the recent changes.

Best regards, Michael.



reply via email to

[Prev in Thread] Current Thread [Next in Thread]