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

Rebol lexer has incorrect lexer definition #4572

Closed
ClaudiaFrank opened this issue Jun 10, 2018 · 5 comments

Comments

Projects
None yet
3 participants
@ClaudiaFrank
Copy link
Contributor

commented Jun 10, 2018

Description of the Issue

stylers.(model).xml contains an incorrect entry which corrupts the xml

Steps to Reproduce the Issue

  1. Open stylers.xml and goto rebol lexer
  2. Check value "TAG { <TITLE HEIGHT=100> }"

Expected Format

"TAG { &lt;TITLE HEIGHT=100&gt; }"

Actual Format

"TAG { <TITLE HEIGHT=100> }"

Debug Information

Notepad++ v7.5.6 (64-bit)
Build time : Mar 19 2018 - 00:23:17
Path : D:\Repositories_cf\Builds\Release\x64\notepad++.exe
Admin mode : OFF
Local Conf mode : OFF
OS : Windows 7 (64-bit)
Plugins : PluginManager.dll PythonScript.dll

ClaudiaFrank added a commit to ClaudiaFrank/notepad-plus-plus that referenced this issue Jun 12, 2018

@ClaudiaFrank

This comment has been minimized.

Copy link
Contributor Author

commented Jul 18, 2018

seems to be fixed already

@ClaudiaFrank

This comment has been minimized.

Copy link
Contributor Author

commented Jul 18, 2018

seems to be fixed already

@ne0fyt

This comment has been minimized.

Copy link

commented Dec 6, 2018

This bug remains in Notepad++ v7.6 and still needs to be fixed.

@chcg chcg reopened this Dec 7, 2018

@chcg

This comment has been minimized.

Copy link
Contributor

commented Dec 7, 2018

chcg added a commit to chcg/notepad-plus-plus that referenced this issue Dec 7, 2018

@chcg chcg added the bug label Dec 7, 2018

@chcg

This comment has been minimized.

donho added a commit that referenced this issue Dec 9, 2018

@chcg chcg closed this Dec 10, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.