Posted by: MegaV0lt | Date: 2017-01-31 15:21 | IP: IP Logged
Updated to the beta 2743 and wonder why comments in script are looking a bit funny now. Please look at the sample:
1: the shebang was usually shown like a comment
2: two ore more # result in red line instead comment
3: # and no space after also not shown as comment
4: # with one or more space in front shoe not as comment (but should)
Es gibt zwei Methoden, fehlerfreie Programme zu schreiben. Aber nur die dritte funktioniert. [Murphy's Computer-Gesetz]
Edited 1 time(s). Last edit at 2017-01-31 15:22 by MegaV0lt.
Posted by: pspad | Date: 2017-01-31 17:12 | IP: IP Logged
Can you please you two make a some deal?
I have 2 different informations how should comment be.
See this link:
Posted by: RANZI | Date: 2018-02-14 07:41 | IP: IP Logged
I have the same problem with version 4.6.2 (2750).
Comments are not highlighted if there are no space between # and the next character.
Please correct this and thank you for your super editor
Posted by: pspad | Date: 2018-02-14 09:07 | IP: IP Logged
This was fixed in version 5. It's available in the PSpad developer forum
Posted by: RANZI | Date: 2018-02-14 09:52 | IP: IP Logged
I test with version 5.0.0 (251).
This problem is fixed.
Only the first line is no commented
Posted by: pspad | Date: 2018-02-16 15:26 | IP: IP Logged
Hello, problem with first line (#!) combination is fixed. Will be available in the next build
Posted by: MikeMuc | Date: 2018-04-19 13:43 | IP: IP Logged
when I check following page: tldp.org
they talk about usage of "Whitespace" in front of the "#" sign to indicate for a comment.
Well I see following always works.
but not with Tab instead of Space
Could the <Tab> be also included in the determination for the corret comment usage? That would be marvelous, as I tend to use <Tab> signs instead of lots of Spaces in scripts.
If I have a Userdefined Syntax I can define a character as the start for a comment. But there is no Userdefined Syntax file like BASH.INI in the /Syntax directory. Maybe I use my time once to create one, just to see if it works then.
Posted by: pspad | Date: 2018-04-19 19:36 | IP: IP Logged
It shouldn't be big problem, I will add TAB as white space too.
Posted by: pspad | Date: 2018-04-20 08:04 | IP: IP Logged
MikeMuc:Could the <Tab> be also included in the determination for the corret comment usage? That would be marvelous, as I tend to use <Tab> signs instead of lots of Spaces in scripts.
Done. It will be available in next build