emacs-bug-tracker
[Top][All Lists]
Advanced

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

bug#45462: closed (28.0.50; [feature/native-comp] trailing backslashes i


From: GNU bug Tracking System
Subject: bug#45462: closed (28.0.50; [feature/native-comp] trailing backslashes in comp-eln-load-path are required but shouldn't)
Date: Mon, 18 Jan 2021 12:37:02 +0000

Your message dated Mon, 18 Jan 2021 12:36:38 +0000
with message-id <xjfeeiizajt.fsf@sdf.org>
and subject line Re: bug#45462: 28.0.50; [feature/native-comp] trailing 
backslashes in comp-eln-load-path are required but shouldn't
has caused the debbugs.gnu.org bug report #45462,
regarding 28.0.50; [feature/native-comp] trailing backslashes in 
comp-eln-load-path are required but shouldn't
to be marked as done.

(If you believe you have received this mail in error, please contact
help-debbugs@gnu.org.)


-- 
45462: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=45462
GNU Bug Tracking System
Contact help-debbugs@gnu.org with problems
--- Begin Message --- Subject: 28.0.50; [feature/native-comp] trailing backslashes in comp-eln-load-path are required but shouldn't Date: Sun, 27 Dec 2020 12:00:01 -0300
Steps to reproduce

1) Add "~/test" to comp-eln-load-path.
2) Native-compile file.el.

Expected result: The file gets written to
~/test/28.0.50-arch-hash/filename.eln.

Actual result: The file gets written to
~/test28.0.50-arch-hash/filename.eln.

Arguably comp-eln-load-path should behave the same as load-path and
always treat its entries as directories.



--- End Message ---
--- Begin Message --- Subject: Re: bug#45462: 28.0.50; [feature/native-comp] trailing backslashes in comp-eln-load-path are required but shouldn't Date: Mon, 18 Jan 2021 12:36:38 +0000 User-agent: Gnus/5.13 (Gnus v5.13) Emacs/28.0.50 (gnu/linux)
Mauricio Collares <mauricio@collares.org> writes:

> Andrea Corallo <akrl@sdf.org> writes:
>>
>> Hi Mauricio,
>>
>> f1efac1f9e should fix this, could you give it a try?
>>
>> Thanks
>>
>>   Andrea
>
> I tested 883d937320 and I can confirm this bug is fixed. Thanks!

closing

Thanks!

  Andrea


--- End Message ---

reply via email to

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