-
-
Notifications
You must be signed in to change notification settings - Fork 2
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
Added: example .sbclrc file #9
Comments
The format statement on line 79 of the example .sbclrc produces this error: (SB-FORMAT::FORMAT-ERROR-AT* "*** reminder: we now disable the interactive debugger. Remove this setting from ~/.sbclrc when using Slime or another IDE. *****" 81 "No matching closing slash" NIL) I simply removed the ~/ and it goes away. I believe the ~/ is a format directive? How can we escape a forward slash in a format string? I tried googling, and surprisingly found nothing to help me. Using a preceding \ doesn't seem to work as I would have expected? Not a big deal, but I'm really curious if format can handle printing a literal ~/ in its output? |
aaargh the fail. Thanks for the report. Only Yes, with https://lispcookbook.github.io/cl-cookbook/strings.html#structure-of-format
|
Thanks Vincent! I changed the code to this (but I like your solution better):
So for completeness, what you are suggesting would look like this:
|
Another suggestion, while we're on the topic of the .sbclrc file, I changed the hard-coded reference to the user folder in the quicklisp section to use (user-homedir-pathname) instead, as per this cl-cookbook page:
but not sure how portable this is? Works on my MacOS setup. Haven't tested on Windows. |
spot-on again. I wonder why Quicklisp hardcodes the user name. It should be portable on implementations (it's in a SBCL file anyways), and it's better than "/home/user/" for Windows. |
Here is an example
~/.sbclrc
file that you can use.https://github.com/vindarel/common-lisp-course-in-videos/blob/master/.sbclrc
You don't strictly speaking need one to use SBCL, you can start without it.
It includes the snippet that we saw to disable the interactive debugger, which can be useful when trying things out in the terminal.
The text was updated successfully, but these errors were encountered: