Question about loading libraries

Question about loading libraries

[Michelangelo Rodriguez]

There is a way to load source files by default instead of compiled at
startup?
The problem i have is that i have an error during the initialization,
but the backtrace shows compiled functions that at the moment are
meaningless for me when i try to fix the error.

Regards.
Michelangelo Rodriguez

Re: Question about loading libraries

[Eli Zaretskii]

> From: Michelangelo Rodriguez <michelangelo.rodriguez@gmail.com>
> Date: Wed, 09 Oct 2024 02:36:52 +0200
> 
> There is a way to load source files by default instead of compiled at
> startup?
> The problem i have is that i have an error during the initialization,
> but the backtrace shows compiled functions that at the moment are
> meaningless for me when i try to fix the error.

Specify the .el extension explicitly.  Like this:

  (load "foo.el")

Re: Question about loading libraries

[Emanuel Berg]

Eli Zaretskii wrote:

>> There is a way to load source files by default instead of
>> compiled at startup? The problem i have is that i have an
>> error during the initialization, but the backtrace shows
>> compiled functions that at the moment are meaningless for
>> me when i try to fix the error.
>
> Specify the .el extension explicitly.  Like this:
>
>   (load "foo.el")

Yes, but there is no way to do this _in general_, to say now
I prefer uncompiled, not byte-compiled and not
natively compiled?

I think I've seen something like that, somewhere.

-- 
underground experts united
https://dataswamp.org/~incal

Re: Question about loading libraries

[Andreas Schwab]

On Okt 09 2024, Emanuel Berg wrote:

> I prefer uncompiled, not byte-compiled and not
> natively compiled?

You can temporarily alter load-suffixes.

-- 
Andreas Schwab, SUSE Labs, schwab@suse.de
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE  1748 E4D4 88E3 0EEA B9D7
"And now for something completely different."

Re: Question about loading libraries

[Michelangelo Rodriguez]

Emanuel Berg <incal@dataswamp.org> writes:

> Eli Zaretskii wrote:
>
>>> There is a way to load source files by default instead of
>>> compiled at startup? The problem i have is that i have an
>>> error during the initialization, but the backtrace shows
>>> compiled functions that at the moment are meaningless for
>>> me when i try to fix the error.
>>
>> Specify the .el extension explicitly.  Like this:
>>
>>   (load "foo.el")
>
> Yes, but there is no way to do this _in general_, to say now
> I prefer uncompiled, not byte-compiled and not
> natively compiled?
Yes, that was my question: i know about specifying ".el" as the name of
a library, but the problem for me is that in this case i don't know
which library is responsible for the error, and i think it should be
useful to have an option to specify that we want all libraries loaded as
interpreted code.

Best regards,
Michelangelo Rodriguez