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

Issue - update v7.5 break style for windows registry file #3936

Open
AnotherDimension-Ex opened this issue Nov 28, 2017 · 3 comments
Open

Issue - update v7.5 break style for windows registry file #3936

AnotherDimension-Ex opened this issue Nov 28, 2017 · 3 comments

Comments

@AnotherDimension-Ex
Copy link

The update v 7.5 read windows registry file (.reg) as plain text for all styles excepted the default style.

What couse the issue "langs.xml" file.

Screen shot.
https://i.imgur.com/Wh7olcU.jpg

Try to chose Twilight theme.

Test code save as .reg

Windows Registry Editor Version 5.00

; This is test 

[HKEY_CLASSES_ROOT\.reg]
@="regFile"
@Cyrillev91
Copy link
Contributor

Hi,

.reg file use now registry language
The update process no update langs.xml and stylers.xml files.

If you do not modify this files

  • close notepad++
  • rename langs.xml to langs_sav.xml (in your profile directory sample in windows 7 : D:\Users<user>\AppData\Roaming\Notepad++)
  • remame stylers.xml to stylers_sav.xml
  • open notepad++

if you have customized these files

  • manually merge the langs.xml file with langs.model.xml into langs.xml.
  • manually merge the stylers.xml file with stylers.model.xml into stylers.xml.

xxxx.model.xml files are in install directory (example C:\Program Files (x86)\Notepad++)

@AnotherDimension-Ex
Copy link
Author

AnotherDimension-Ex commented Nov 29, 2017

Thank you for the reply,

Nevermind, the new update v7.5 is just missing styling for registry files (for the Twilight theme and the other themes except the default style)

You just need to update the Twilight theme and add these lines.

Twilight.xml

<LexerType name="registry" desc="Registry" ext="">
	<WordsStyle name="DEFAULT" styleID="0" fgColor="F8F8F8" bgColor="141414" fontName="" fontStyle="0" fontSize="" />
	<WordsStyle name="COMMENT" styleID="1" fgColor="5F5A60" bgColor="141414" fontName="" fontStyle="0" fontSize="10" />
	<WordsStyle name="VALUE NAME" styleID="2" fgColor="9B703F" bgColor="141414" fontName="" fontStyle="0" fontSize="" />
	<WordsStyle name="STRING" styleID="3" fgColor="CDA869" bgColor="141414" fontName="" fontStyle="0" fontSize="" />
	<WordsStyle name="HEX DIGIT" styleID="4" fgColor="7F0B0C" bgColor="141414" fontName="" fontStyle="0" fontSize="" />
	<WordsStyle name="VALUE TYPE" styleID="5" fgColor="00007F" bgColor="141414" fontName="" fontStyle="1" fontSize="" />
	<WordsStyle name="ADDED KEY" styleID="6" fgColor="9B703F" bgColor="141414" fontName="" fontStyle="0" fontSize="" />
	<WordsStyle name="REMOVED KEY" styleID="7" fgColor="808040" bgColor="141414" fontName="" fontStyle="0" fontSize="" />
	<WordsStyle name="ESCAPED CHARACTERS IN STRINGS" styleID="8" fgColor="7D8187" bgColor="141414" fontName="" fontStyle="1" fontSize="" />
	<WordsStyle name="GUID IN KEY PATH" styleID="9" fgColor="7B5F15" bgColor="141414" fontName="" fontStyle="0" fontSize="" />
	<WordsStyle name="GUID IN STRING" styleID="10" fgColor="7B5F15" bgColor="141414" fontName="" fontStyle="0" fontSize="" />
	<WordsStyle name="PARAMETER" styleID="11" fgColor="0B6561" bgColor="141414" fontName="" fontStyle="0" fontSize="" />
	<WordsStyle name="OPERATORS" styleID="12" fgColor="9B703F" bgColor="141414" fontName="" fontStyle="1" fontSize="" />
</LexerType>

Thanks.

@klepp0906
Copy link

klepp0906 commented May 20, 2020

Bless your soul for this. Now my only issue is the atrocious problem with markdown and twilight theme : P

cant believe you posted this in 2017 and its yet to be merged/updated. Does nobody use twilight theme to be triggered by this yet? lol

here i thought everything was trending towards darkmodes

any way to stop it from double semi-colon on the comments? it should be only a single semi colon for regfile

found it in the langs.xml

further convoluting the update process to ensure that minor adjustement doesnt need to be re-done perpetually

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

No branches or pull requests

3 participants