Fix: lispworks no-break-space #108
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Other implementations use #\No-break_space while Lispworks uses #\no-break-space. Thanks to @ijitai for reporting the bug.
|
ping @ijitai to test this no-break-space fix? |
|
#\No-break_space works as expected in this case. |
|
thanks. Are you using both char codes in LispWorks?? In LW 7.1.2 one works, not the other. |
|
Both works in LW 8.0, maybe they added #\No-break_space for compatibility reasons. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Other implementations use #\No-break_space while Lispworks uses #\no-break-space.
I have no Lispworks implementation set up, so can you @ijitai or anyone with access to Lispworks confirm this works now?
Closes #99