PSPad unicode 5.0.0 (191) English

pspad:

TextInfo uses new comment style - this is a support what was added.
You need to assign new TextInfo synax file in highlighter settings.

Can anyone please explain to me how to do this step by step?

1. Start PSPad
2. Open ".texi" file
3. See "Text" as current highlighter
4.... Do ????

Thank you,
human

Edited 2 time(s). Last edit at 2017-05-04 14:10 by human.

1. Create new user highlighter for texi files
2. Assigh new user highlighter into free slot in highlighter settings
3. Continue with your point 1)

human:

And two minor issues with the COBOL code explorer:

a) in free-form reference format it is possible to have "COPY yourinclude." at column 1 but it isn't recognized there (if it is in column 2 it is shown in the code explorer). All other items beginning in column 1 are shown.

b) in the identification "folder" we have an entry "program-id." this is nice but it would be better to additional have the actual id in (especially when you work with multi-program sources).

Thank you for this Editor!

Hello. I used some example I got from you in the past and I think it's clear for me now.

Thank you for taking care about the user highlighters, I'm still lost...

1. Start PSPad
2. Settings->User highlighter: Create new user highlighter for texi files (I've loaded the file which content I have sent you before and changed the extension to *.texi [was .texi before] + saved it)
3. Settings->Highlighter: Assign new user highlighter into free slot in highlighter settings [second thing that wasn't done before]
4. Open texi file, highlighter in bottom bar is shown as "Texinfo"
5. No actual highlighting is done

And now?

If you want to highlight words, you need to tell PSPad which words has to be highlighted. Have you filled list of keywords in user highlighter?

I suggest you read chapter in help about user highlighter files.

Edited 1 time(s). Last edit at 2017-05-05 10:47 by pspad.

Not sure what the behaviour was before but:
Suppose we have a line with a string:

This is a line which contains "some kind of a string" within quotes.

If we select in this line the word string (by doubleclicking it) and the we use [Ctrl+Shift+Right] the selection expands just before the word "within".

Would it not be better to also stop the selection after encountering a quote? So not only whitespace...

Edited 1 time(s). Last edit at 2017-05-05 10:58 by MadCompie.

In the meanwhile...again a month further with this new version.
Still very stable for us, no more memory fault errors and all our VB scripts still work like a charm!
Good job!

pspad:

If you want to highlight words, you need to tell PSPad which words has to be highlighted. Have you filled list of keywords in user highlighter?

I suggest you read chapter in help about user highlighter files.

Yes, the entries are in, not sure if the problem is that these start with @.
I now read the chapter in help about user highlighter files and the two points mentioned above (use *.ext in user highlighter and how to set the user highlighter to a slot in highlighter options) would have been clear if I did so before.

I was confused by

pspad:

News
TexInfo support in user highlighter

reading it like "it works now" but this was only about the new entry "comment style @c, @ignore", correct?

I've checked this and set (just out of interest to see how it works, if it does at all) the ftTex option. Result on save (I've opened the fdl.texi beforehand): PSPad 5.0.0 (191) hangs. Killed it and restarted, same result: hangs (can't change the setting via GUI). Removed the setting "CodeExplorer=ftTex" from Texinfo.INI and tried to start PSPad - same issue.
Where is the setting for `@c, @ignor` stored?

human, it will be much easier if you will publish Texi highlighter and some source what causes problem. I will try to tune up highlighter for you.

republishing

Texinfo.INI:

;PSPad user HighLighter definition file
[Settings]
Name=Texinfo
HTMLGroup=0
Vectors=0
Label=0
FileType=*.texi
CommentString=
TexInfoComment=1
IndentChar=
UnIndentChar=
TabWidth=0
CaseSensitive=1
DoubleQuote=1
EscString=0
EscChar=\
KeyWordChars=
CodeExplorer=
DocComment=
[KeyWords]
@acronym=
@b=
@c=
@cite=
@code=
@command=
@dfn=
@email=
@emph=
@env=
@file=
@i=
@kbd=
@key=
@option=
@r=
@samp=
@sc=
@strong=
@t=
@url=
@var=
[ReservedWords]
@appendix=
@appendixsec=
@appendixsection=
@appendixsubsec=
@appendixsubsubsec=
@author=
@bye=
@center=
@centerchap=
@chapheading=
@chapter=
@contents=
@detailmenu=
@exampleindent=
@heading=
@headings=
@lowersections=
@majorheading=
@paragraphindent=
@printindex=
@raisesections=
@section=
@setchapternewpage=
@setcontentsaftertitlepage=
@setfilename=
@setshortcontentsaftertitlepage=
@settitle=
@shortcontents=
@shorttitlepage=
@subheading=
@subsection=
@subsubheading=
@subsubsection=
@subtitle=
@summarycontents=
@title=
@titlefont=
@titlepage=
@unnumbered=
@unnumberedsec=
@unnumberedsubsec=
@unnumberedsubsubsec=
@vskip=
\\input=
[KeyWords2]
@anchor=
@asis=
@cartouche=
@cindex=
@columnfractions=
@display=
@enumerate=
@example=
@exdent=
@findex=
@flushleft=
@flushright=
@format=
@ftable=
@inforef=
@item=
@itemize=
@itemx=
@kindex=
@lisp=
@menu=
@multitable=
@node=
@noindent=
@pindex=
@pxref=
@quotation=
@ref=
@smallbook=
@smalldisplay=
@smallexample=
@smallformat=
@smalllisp=
@syncodeindex=
@synindex=
@tab=
@table=
@tindex=
@top=
@uref=
@vindex=
@vtable=
@xref=
[KeyWords3]

This was applied (together with the Texinfo comment option "@c, @ignore" and the CodeExplorer=ftfTex) to the opened file sourceforge.net

I have absolutely no idea why PSPad hangs now (one complete and part of an additional core). Where can I remove the fdl.texi from the "current open" list?