Bad (but legal) line continuations break highlighting

Open
#185 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
javascript, python
Domain
tooling

Research direction

Reproduce the Python snippet with the escaped line continuation and DOS line endings in a supported editor, then trace the syntax-highlighting behavior for those inputs. Done means legal continued strings highlight correctly and files with DOS line endings no longer show red ^M markers on the affected lines.

Written by the indexing model from the issue text.

Description

Image:
Capture

Repro:

    'bad lines are continued \
     like this. do not do it!'

Red ^Ms appear in files with DOS line endings (even though they don't appear on other lines):
Capture

Dominant language
JavaScript
Stars
1.4k
Forks
98
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from MagicStack/MagicPython

All issues in MagicStack/MagicPython

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.