-
Notifications
You must be signed in to change notification settings - Fork 19
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Package SERAPEUM does not exist #133
Comments
How does sbcl get started by Emacs? What usually tells it to load that package? It sounds like the startup process under Alive isn't including something. |
In Emacs, it is initialized by 'M-x slime'. It's a three-way thing, Emacs, SBCL, and Slime. With Slime setting up the port/repl. I execute '(ql:quickload "serapeum") in the repl, along with other requirements… Seems to me that you are making the assumption that the file is ready to compile before that is the case. I.E., I have yet to execute the three needed Quickload calls before compiling the file. |
Ok, gotcha. That's a difference in philosophy between Emacs and Alive. Alive shows you errors as you type. The only way to get the errors is to compile the file, which it does with a temp file to keep from littering fasl files everywhere. It's telling you your code won't run because the dependencies haven't been loaded, which is correct. Doing the quickload command at the repl should get the error to go away. |
Actually, now that I think about it, where is the message getting printed? Does the side panel come up or is it being prevented from starting? The message about the temp file shouldn't be written anywhere. |
Just tried it, apparently it does mention the temp file in the message. I thought it only printed that the package isn't found. Not sure there's a good way to get it to not do that. |
I will attempt the quickloads in the repl and recompile…
…On Sun, Feb 12, 2023 at 9:11 AM nobody-famous ***@***.***> wrote:
Just tried it, apparently it does mention the temp file in the message. I
thought it only printed that the package isn't found. Not sure there's a
good way to get it to not do that.
—
Reply to this email directly, view it on GitHub
<#133 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAHE7PVPWIMHTTZOO5OLTJTWXEDTLANCNFSM6AAAAAAUY34JVA>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
After quickloading, the file compiles correctly in repl, but the display
does not clear of red squiggly lines. Since the entire file is thus
decorated, it is pretty much not usable.
…On Sun, Feb 12, 2023 at 9:27 AM Hugh S. Myers ***@***.***> wrote:
I will attempt the quickloads in the repl and recompile…
On Sun, Feb 12, 2023 at 9:11 AM nobody-famous ***@***.***>
wrote:
> Just tried it, apparently it does mention the temp file in the message. I
> thought it only printed that the package isn't found. Not sure there's a
> good way to get it to not do that.
>
> —
> Reply to this email directly, view it on GitHub
> <#133 (comment)>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/AAHE7PVPWIMHTTZOO5OLTJTWXEDTLANCNFSM6AAAAAAUY34JVA>
> .
> You are receiving this because you authored the thread.Message ID:
> ***@***.***>
>
|
Ah, yep. It wasn't auto updating the diagnostics. I added a fix for that. The new version should work. |
Much thanks! Am looking forward to the comparison of writing code in both
editors.
…On Mon, Feb 13, 2023 at 10:04 PM nobody-famous ***@***.***> wrote:
Ah, yep. It wasn't auto updating the diagnostics. I added a fix for that.
The new version should work.
—
Reply to this email directly, view it on GitHub
<#133 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAHE7PTTGDYNEABZQDHM3DLWXMG6JANCNFSM6AAAAAAUY34JVA>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
This, on a READ error. Which is nonsense since I develop in EMACS without a problem. Suggestions? Here is what hits the PROBLEMS screen after startup:
READ error during COMPILE-FILE:
Package SERAPEUM does not exist.
The text was updated successfully, but these errors were encountered: