Talk:Notepad++ Setup

From the CreationKit Wiki
Revision as of 02:04, 6 July 2015 by imported>Lmstearn (→‎Advanced Compiler Pt2)
Jump to navigation Jump to search

Syntax Highlighting Styles

As more options become made available for syntax highlighting styles, moving them out of being embedded in this page into their own subpages would seem appropriate. Does anyone know if it's possible to create subpages that are also files? If not, it would be trivial to embed them into the subpages created for them, but ideally they should be available as files to download.

Default Style

Currently, the default style (the only one currently on the page) does not match the style for syntax highlighting used on the wiki. Would anyone object if I were to alter the styling of this file to match what is used on the wiki?

Syntax Highlighting : Comments

Syntax highlighting doesn't seem to work for multiline comments bounded by SEMICOLON SLASH and SLASH SEMICOLON. Only the first line is displayed as a comment. Does anyone know how to fix this? Proleric 04:13, 6 May 2012 (EDT)

If I remember correctly, Notepad++'s custom language definitions only allow for a single set multi-line comment delimiters, which in this case is already used by curly brackets - {} - for documentation comments. It might be possible to add the non-documentation multi-line comment delimiters though, I'm not sure. I expect if that were done it would be possible to start a comment with one set and end it with another, and they'd have to use the same styling, but that's a small price to pay if it means being able to easily use non-documentation multi-line comments with correct syntax highlighting.
Cipscis 17:12, 6 May 2012 (EDT)
As of Notepad++ v6.4 this can now be handled correctly, and I've added an alternative XML which does so. The solution is to stop using the "Comment" definitions and move them into the more general "Delimiter" section, which allows ";/" to be listed first and take precedence over the plain ";". I also fixed some other bugs I noticed, like the folding keywords ("if" etc) being recognized in the middle of words. I tried uploading my alternative as a file like the other alternatives, but it wouldn't let me because of the XML format, so I just pasted it in instead.
--taleden (talk) 2013-10-01T13:36:42 (EDT)

There is a very serious bug in the Syntax Highlighting XML code which makes notepad++ unable to import. Back on the 10th of February at 5:45 it was good. I can't track down who and when break it. --VikMorroHun (talk) 21:47, 29 September 2012 (EDT)

The import function is broken (at least in my 5.9.8 version). Instead, if the file userDefineLang.xml exists in the Notepad++'s installation folder, or in %AppData%\Roaming\Notepad++ folder (depending of your setup), just append the xml code to the end of file. If it doesn't exist, save the provided code under a file named userDefineLang.xml either in the installation foder, either in %AppData%\Roaming\Notepad++ folder (try first with the install folder, if it doesn't work then try with the %appdata% folder and it should work).
--HawkFest (talk) 21:59, 25 October 2012 (EDT)

Error Reporting

While my Notepad ++ files are being compiled and work in game, even when I introduce intentional errors, my notepad ++ does not report any error and just compiles the script like normal. Is Notepad++ capable of reporting errors like the CK build does, and if so, how does one go about doing that? Thanks! --Iceburg333 (talk) 2013-04-04T14:47:55 (EDT)

Advanced Compiler

I can't make this to function properly, more over the CMD window closes immediately so I can't see where the error occurred. Btw yes, when configuring Notepad to run the command, I've replaced "<SCRIPT DIR>\Papyrus Compiler.bat" by the proper directory and batch file name (and also removed the last argument since I haven't defined any additional import directory yet). Any clue? Note : I've also tried the Papyrus Source code Beautifier section, but it doesn't work either : nothing happens when trying this on an open psc file. --HawkFest (talk) 12:15, 26 October 2012 (EDT)

Try it now- I let Schnusch know of the changes. He may wish to do more.:)--Lmstearn 2015-02-19T08:22:46 (EST)

Advanced Compiler Pt2

When I try the advanced compiler script it tries to use the compiler path with no spaces; i.e. "C:\ProgramFiles(x86)\Steam\steamapps\common\Skyrim\". It removes the "InstalledPathREG_SZ" but the result is not a valid path. "Pushd %Skyrim:~32%" results in "apps\common\Skyrim\". BillF (talk) 2015-07-05T16:49:53 (EDT)

Try pausing the script to see what is inside "%Temp%\SkyrimPath.txt" But I cannot understand why "Pushd %Skyrim:~32%" shouldn't work. That's extracting the pathname after the first 32 characters, (assuming there are 32 junk characters there in the first place.)--Lmstearn 2015-07-06T03:04:55 (EDT)