PSPad UNICODE 4.5.0 (2127) beta English

Thank you. Your description clarify one bug I am not able simulate.
Will be corrected in next build

tyzio wrote:

> >What is wrong ? I don't know Tcl/Tk syntax
>
> When backslash appears in code line, the rest of line is
> treated as a command by PsPad (highlighted like comment, etc..)

As I wrote before. I don't know Tcl/Tk syntax. Text in Tcl/Tk after backslash shouldn't be highlighted as comment in any case ?
Can you write some examples ?

> And also I vote for ' indenting like Visual Studio'
> option/function.

Sorry, but Indenting like VS tell me nothing. Its same if I say "go as Ford".
Can you explain me how Indentation in VS work ? I don't use VS.

I'm sorry, i cant find a way to rebuild the error! It happend maybe sporadic. I working 8 hours with your editor per day, and it happend only, if i close pspad. Currently i create backups of my files, before closing pspad. And i hope to find the error, or at least the way to it.

Greetings,
ShiLong

>tyzio wrote:

>> >What is wrong ? I don't know Tcl/Tk syntax
>>
>> When backslash appears in code line, the rest of line is
>> treated as a command by PsPad (highlighted like comment, etc..)

>As I wrote before. I don't know Tcl/Tk syntax. Text in Tcl/Tk after backslash >shouldn't be highlighted as comment in any case ?
>Can you write some examples ?

Hi
Here are some of the cases in which backslash sign is being used by Tcl:
1. as a directories separator - c://temp/emp/mp/p ...
2. as a divide operation - [expr {100/25}]
3. as a regular "text" character - the Date for example - 26/09/2005
and so on.

Ilya.

Exists some rule to say this is comment and this isn't comment ? E.g. space must folow backslash to be comment or backslash must be first char on line or something else ?

Hi,
Tcl uses the pound character, #, for comments. The # must occur at the beginning of a comment. A # that occurs elsewhere is not treated specially.
Some examples:
#Here is a Tcl comment
# Another comment
set x 1 ; # Third comment (the semicolon terminate the previous command)

There is no meaning for space after the #.

set x #ff0000 ; # red color definition
In this example #ff0000 should be black, because it isn't a comment, it is a value.

Backslash continues a comment line onto the next line of the script. In addition, a semicolon inside a comment is not significant. Only a newline terminates comments:
# Here is the start of a Tcl comment \
and some more of it; still in the comment

Regards, Ilya
(Brent B. Welch "Practical Programming in Tcl and Tk" 2'nd edition)

Thank you, this is exactly what I need.
I hope In build 2032 is situation with Tcl comments better. I must exclude numbers and add multiline comment functionality yet

Yes. The / works OK.
Regarding to I need exclude exclude numbers - see my previous message - The # must occur at the beginning of a comment. A # that occurs elsewhere is not treated specially.
So, the key is not numbers or something else - the key is a placement of the #.

Ilya

pspad wrote:
> Author: pspad (---.brno.tiscali.cz)
> Date: 09-24-2005 18:04
> ...
>> And also I vote for ' indenting like Visual Studio'
>> option/function.

>Sorry, but Indenting like VS tell me nothing. Its same if I say "go as Ford".
>Can you explain me how Indentation in VS work ? I don't use VS.

It was explain in Guillaume H. post:
> And one other thing. I'm not sure it was intentionally coded like this, but
> personnally I'd like to have indenting like Visual Studio. That means if a line ends
> with "{" and you press Enter, the next line is indented by one more indentation.
> Then when you type "}" it automatically decrease the indentation by "one
> indent". It just seems natural to me. Crimson Editor also does this (it's not
> updated anymore, this is why I'm switching to PSPad).

I will be glad to have such indent functionality.

Hi again,

There is one more thing with code explorer for Tcl/Tk. Wrong parsing of source and load keywords. I see that you introduce mechanizm for parsing it but it seems bugy. Here are examples:

This is a comment, so it should not be visible in code explorer, but it is.
# source [file join $::env(dir) mainNamespace.tcl]
# load [file join $::env(dir) mainNamespace.dll]

This is not a comment, so it should be visible in code explorer, but it isn't
source [file join $::env(dir) mainNamespace.tcl]
load [file join $::env(dir) mainNamespace.dll]

Also the following examples should be parsed:
source file.tcl
source [file join [pwd] file.tcl]
source $fd
load file.tcl
load [file join [pwd] file.tcl]
load $fd

BTW,
> Author: tyzio (---.delphiauto.com)
> Date: 09-15-2005 18:10
> ...
>>> 3. The capture output in external appl. for highlighter is not
>>> working for TCL interpreter. (In Tools window the capture
>>> output works). Different capture output mehanism?

>>No, its same function. In highlighter settings only compiler catch youtput, not
>>external applications

> So in this case, any change for caputring output function for external appl. in
> highlighter settings, or shortcut for configured tools/application in Tools window e.g. F8, Alt_F8, etc.., or both?

Any change for this??

Thanks