nekkutta Posted February 24, 2023 Share Posted February 24, 2023 >"C:\Program Files (x86)\AutoIt3\SciTE\..\AutoIt3.exe" "C:\Program Files (x86)\AutoIt3\SciTE\AutoIt3Wrapper\AutoIt3Wrapper.au3" /Tidy /in "D:\Users\nekkutta\Documents\AutoIt\df2\scitejumpfix.au3" +>00:33:45 Starting AutoIt3Wrapper (21.316.1639.1) from:SciTE.exe (4.4.6.0) Keyboard:00000409 OS:WIN_10/2009 CPU:X64 OS:X64 Environment(Language:0409) CodePage:0 utf8.auto.check:4 +> SciTEDir => C:\Program Files (x86)\AutoIt3\SciTE UserDir => D:\Users\nekkutta\AppData\Local\AutoIt v3\SciTE\AutoIt3Wrapper SCITE_USERHOME => D:\Users\nekkutta\AppData\Local\AutoIt v3\SciTE >Running Tidy (21.316.1639.1) from:C:\Program Files (x86)\AutoIt3\SciTE\tidy D:\Users\nekkutta\Documents\AutoIt\df2\scitejumpfix.au3 Start D:\Users\nekkutta\AppData\Local\AutoIt v3\SciTE\Tidy\au3.api This is the output from SciTE when I Ctrl-T, and What follows is what I'm guessing is the full debug output from tidy: I_REC$:And?4| 2 cInt(Len(KEYWORDS$) + len($Keyword[0]) + 3): 7 I_REC$:ByRef?4| 2 cInt(Len(KEYWORDS$) + len($Keyword[0]) + 3): 13 I_REC$:Case?4| 2 cInt(Len(KEYWORDS$) + len($Keyword[0]) + 3): 18 I_REC$:Const?4| 2 cInt(Len(KEYWORDS$) + len($Keyword[0]) + 3): 24 I_REC$:ContinueCase?4| 2 cInt(Len(KEYWORDS$) + len($Keyword[0]) + 3): 37 I_REC$:ContinueLoop?4| 2 cInt(Len(KEYWORDS$) + len($Keyword[0]) + 3): 50 only It is printing this for every keyword in SciTE\Tidy\au3.api Tidy is finishing and displaying the Gen_Doc_Show=1, but SciTE is still trying to display all of the console output from tidy, and eventually SciTE crashes with an out of memory error. Checked the AppData\Local\AutoIt v3\SciTE\Tidy\Tidy.ini expandcollapse popup[ProgramSettings] #-->Indent 0 = Tabs >0 = Number of Space tabchar=0 #-->Define the TabSize size tabsize=4 #-->Update Functions/Keywords/Macros/UDFs to Proper case proper=1 * * * Update Constants defined in the "constant Include files" properconstants=0 #-->Update Variables to: 1=UpperCase; 2=LowerCase; 3=First Dim/Local/Global or "First_Seen" Case vars=3 #-->Update Spaces around Delimiters delim=1 #-->Add comment to EndFunc statement e.g. "EndFunc ;==>UDF_Name" endfunc_comment=1 #-->Ingnore EndFunc statement comments. #~ endfunc_comment=0 #-->Remove comments from EndFunc statement. #~ endfunc_comment=-1 #-->Add comment to EndRegion and make it the same as the #Region Comments. endregion_comment=1 #-->Add comment to #CE/#CommentEnd and make it the same as the #cs/CommentStart Comments. ce_comment=1 #--> Tidy commentblock 0=only indent the whole commentblock (default=0) # 1=Tidy inside commentblock # -1=leave whole commentbock alone Tidy_commentblock=0 #-->Ignore EndFunc statement comments. #~ endregion_comment=0 #-->Remove comments from EndFunc statement. #~ endregion_comment=-1 #-->Indent #region sections region_indent=0 #-->Define the default column for inline comments, 0=keep current position icl_pos=0 #-->Generate Documentation file for the Program and optionally Display it with Notepad at the end ot the Tidy run Gen_Doc=1 Gen_Doc_Show=1 #--> Keep x Version of the File before the Tidy run and optionally store them in SubDirectory "\Backup" KeepNVersions=5 #--> Target backup directory which defaults to Scriptdir\Backup. Any other directory needs to exist or else it will use the default directory! backupDir= #--> Remove Empty lines from Script Source 0=none (Default) ; 1=Remove all Empty lines; 2=Remove extra Empty lines,so leave first. Remove_Empty_Lines=0 #--> 1=Show Tidy Errors in Console 9=Debug Output ShowConsoleInfo=1 #--> Run DIFF program at the end of the Tidy run to show the difference between original and new program. #~ ShowDiffPgm=C:\Progra~1\WinMerge\winmerge.exe "%new%" "%old%" #--> End With NewLine: 0=Strip Lastline CRLF; 1=Always end with CRLF (Default) End_With_NewLine=1 and no matter what value I put in ShowConsoleInfo=0|1|9 it outputs all that text to the console, even when running the tidy.exe and selecting the file from the FileOpenDialog. I know it is reading the ini file because Gen_Doc=0|1 makes a difference. Any Idea what is happening here? [size="2"] "Debugging is twice as hard as writing the code in the first place. Therefore, if you write the code as cleverly as possible, you are, by definition, not smart enough to debug it." - Brian Kernighan[/size] Link to comment Share on other sites More sharing options...
argumentum Posted February 24, 2023 Share Posted February 24, 2023 ... get the new one from the beta folder. Follow the link to my code contribution ( and other things too ). FAQ - Please Read Before Posting. Link to comment Share on other sites More sharing options...
nekkutta Posted February 24, 2023 Author Share Posted February 24, 2023 Thank you!! argumentum 1 [size="2"] "Debugging is twice as hard as writing the code in the first place. Therefore, if you write the code as cleverly as possible, you are, by definition, not smart enough to debug it." - Brian Kernighan[/size] Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now