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.

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

One more fixmas indentation fix and improvement on previous fix #543

Closed
wants to merge 3 commits into from

Conversation

skids
Copy link
Contributor

@skids skids commented Sep 29, 2015

No description provided.

Treat actual backslash sequences inside a heredoc similarly to
interpolated strings so they do not cause indentation in the
middle of a line (but only when they include vertical whitespace.)
Note that this should probably not cause Windows issues
as \r\n is a blank line and as such is ignored, but this
bears testing (and appreciation of crafty language designers.)
When writing spectests for 12db6c0 I noticed a corner case that was
not giving visually consistent results.  Also now that we delete
from the front the code was not arranged very logically.  Refactor
to take advantage of rx features and take substrings of the original
input rather than splitting/rejoining character-by-character.

The corner case was that a tab appearing in the uncut portion of
the whitespace would not move during an uneven dedent.  Now, enough
space is removed from the front to assure the remaining tabs notch
in one tabstop, then extra padding is added to the end to compensate
for their movement.
@skids
Copy link
Contributor Author

skids commented Sep 29, 2015

Worth noting is that $?TABSTOP seems destined to be a (localizable)
compile-time constant, which is necessary for heredoc, but not so great
for users of .indent who may want to change behavior at runtime.

@zoffixznet
Copy link
Contributor

ping does this still need to go in or can this PR be closed?

There are some conflicts.

@JJ
Copy link
Collaborator

JJ commented May 6, 2020

Well, there were conflicts already in 2016. I don't think this can be fixed, closing.

@JJ JJ closed this May 6, 2020
@AlexDaniel
Copy link
Contributor

This PR claims to resolve RT#125543 but it is already closed: Raku/old-issue-tracker#4378
So I guess there's no need in this indeed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants