You are here: PSPad forum > Developer forum - new builds > PSPad unicode 5.0.0 (191) English

PSPad unicode 5.0.0 (191) English

Goto Page: Previous1 2 3

#21 Re: PSPad unicode 5.0.0 (191) English

Posted by: pspad | Date: 05/05/2017 15:31 | IP: IP Logged

Here is fixed Syntax file for TEXI

Quote:
;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=ftUnknown
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=
@contents=
@detailmenu=
@end=
@exampleindent=
@group=
@heading=
@headings=
@chapheading=
@chapter=
@lowersections=
@majorheading=
@page=
@paragraphindent=
@printindex=
@raisesections=
@section=
@setcontentsaftertitlepage=
@setfilename=
@setchapternewpage=
@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]

PSPad hangs in case when @ isn't included in Keyword chars field. I must find a reason and fix it. This highlighter works. I added about 2 keywords from your license file

Options: Reply | Quote | Up ^


#22 Re: PSPad unicode 5.0.0 (191) English

Posted by: human | Date: 05/08/2017 06:37 | IP: IP Logged

pspad:
PSPad hangs in case when @ isn't included in Keyword chars field. I must find a reason and fix it.

Thanks for the feedback and the extended syntax file (I guess it is shipped with the next full install). It is good that you found a way to reproduce the bug.
I suppose after the fix the highlighter will just not work when the @ is removed - but I wonder in general why this field exists, shouldn't the "allowed chars in keywords" be derived from the keywords actual in the syntax file?

Can I do something for ftTexinfo or is this completely up to you?

Options: Reply | Quote | Up ^


#23 Re: PSPad unicode 5.0.0 (191) English

Posted by: pspad | Date: 05/08/2017 07:54 | IP: IP Logged

It's fixed in the yesterday build.
Use syntax file content I provided in add abbove

Options: Reply | Quote | Up ^


#24 Re: PSPad unicode 5.0.0 (191) English

Posted by: human | Date: 05/08/2017 08:29 | IP: IP Logged

using build 203 it even works without the "@" in "KeyWordChars=".
Thank you for the fix and "speed up in Code Explorer" sounds good in general.

Question: Is the field KeyWordChars still needed or can it be dropped completely, with the "allowed chars in keywords" being derived from the keywords actual in the syntax file?

Second question: Can I somehow add a code explorer for this or do you have to code a ftTexinfo?

Options: Reply | Quote | Up ^


#25 Re: PSPad unicode 5.0.0 (191) English

Posted by: pspad | Date: 05/08/2017 08:53 | IP: IP Logged

Let the @ char in keywords char, cause it's really part of keywords.

Code explorer isn't user definable.
I need to know what should be code explorer content and I will add it

Options: Reply | Quote | Up ^


#26 Re: PSPad unicode 5.0.0 (191) English

Posted by: human | Date: 05/08/2017 09:52 | IP: IP Logged

pspad:
Let the @ char in keywords char, cause it's really part of keywords.

Question: Is the field KeyWordChars still needed in general in PSPad or can it be dropped completely from the application, with the "allowed chars in keywords" being derived from the keywords actual in the syntax file instead? (Note: Texinfo currently needs the @, otherwise keywords within the text aren't highlighted).

pspad:
Code explorer isn't user definable.
I need to know what should be code explorer content and I will add it

Hierarchical nodes in Texinfo (that I'm aware of):
[@part ->] [@chapter ->] [@section | @unnumberedsec ->] [@subsection]
[@part ->] [@appendix ->] [@section | @unnumberedsec | @appendixsec | @appendixsection ->] [@subsection]
No need to distinguish between both variants via single "main" nodes.

And ideally another node for the includes: @include | @verbatimcinlude

See www.gnu.org for the details

Edited 1 time(s). Last edit at 05/08/2017 09:53 by human.

Options: Reply | Quote | Up ^


Goto Page: Previous1 2 3





Editor PSPad - freeware editor, © 2001 - 2017 Jan Fiala
Hosted by Webhosting TOJEONO.CZ, design by WebDesign PAY & SOFT, code Petr Dvořák