Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Some character literals throws paredit out of whack #563

Closed
PEZ opened this issue Feb 20, 2020 · 0 comments
Closed

Some character literals throws paredit out of whack #563

PEZ opened this issue Feb 20, 2020 · 0 comments
Labels
highlight Syntax highlighting, rainbow parens, such things paredit Paredit and structural editing parsing

Comments

@PEZ
Copy link
Collaborator

PEZ commented Feb 20, 2020

The lexer doesn't produce the right tokens for character literals. Which causes problems with literals for brackets, like \(, since it throws the matching of brackets off.

Something like this, for instance:

(def open-close [\) \(])

😢
@PEZ PEZ added paredit Paredit and structural editing parsing highlight Syntax highlighting, rainbow parens, such things labels Feb 20, 2020
@PEZ PEZ mentioned this issue Feb 20, 2020
Merged
20 tasks
@PEZ PEZ closed this as completed in 6f338ad Feb 23, 2020
PEZ added a commit that referenced this issue Mar 6, 2020
@PEZ
Tokenize character literals correctly
2478f6f 
Fixes #563
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
highlight Syntax highlighting, rainbow parens, such things paredit Paredit and structural editing parsing
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@PEZ