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

Bug: comment after "{" gets repeated #50

Closed
aureliojargas opened this issue Aug 28, 2019 · 1 comment
Closed

Bug: comment after "{" gets repeated #50

aureliojargas opened this issue Aug 28, 2019 · 1 comment
Labels
Milestone

Comments

@aureliojargas
Copy link
Owner

$ ./sedsed.py -e '5{ # foo' -e '}'
5 {                                    ;# foo
    # foo
}
aureliojargas pushed a commit that referenced this issue Aug 29, 2019
The previous test/parsing/comment* files were too simple.

Now I've added corner cases, bug raising samples (using ";", see
issues #49 and #50) and a more complete coverage.
aureliojargas added a commit that referenced this issue Aug 29, 2019
The previous test/parsing/comment* files were too simple.

Now I've added corner cases, bug raising samples (using ";", see
issues #49 and #50) and a more complete coverage.
aureliojargas added a commit that referenced this issue Aug 29, 2019
The previous test/parsing/comment* files were too simple.

Now I've added corner cases, bug raising samples (using ";", see
issues #49 and #50) and a more complete coverage.
aureliojargas added a commit that referenced this issue Sep 22, 2019
The previous test/parsing/comment* files were too simple.

Now I've added corner cases, bug raising samples (using ";", see
issues #49 and #50) and a more complete coverage.
@aureliojargas
Copy link
Owner Author

Fixed by the new sedparse parser, see #52.

$ ./sedsed.py -e '5{ # foo' -e '}'
5 {                                    ;# foo
}

@aureliojargas aureliojargas added this to the v2.0 milestone Nov 19, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant