PSPad unicode 4.5.5 (2405) English

Can something similar be implemented for clips, instead of pressing ctrl+space?
Thanks,
Cristian

Couldn't post bug into bugs forum.

1. create a new file
2. type 12345
3. Search/replace CTRL-H
check regular expressions
find 3
replace \n3

It's looks like pspad continue to search from next line, where found a 3 and insert another \n3 and so on.

martovskiy:

Couldn't post bug into bugs forum.

1. create a new file
2. type 12345
3. Search/replace CTRL-H
check regular expressions
find 3
replace \n3

It's looks like pspad continue to search from next line, where found a 3 and insert another \n3 and so on.

Yes, you are right. But it will be hard to manage it.
You can use your replace from the end with (o)backward direction

Hi Jan,

Using the release 2405 I saw a small bug in code explorer for COBOL programs.
"w-other-var" at line 19 and "end-if" at line 24 are shown as paragraphs, but they are respectively a variable and a reserved word.

(click the Quote link for this post to get the right indentation of the sample program):

identification division.
program-id. test.

environment division.
configuration section.
special-names.
decimal-point is comma.

data division.
working-storage section.
01 wrk-vars.
05 w-var pic is x(10).
05 w-other-var pic is x(10).

procedure division.
start-of-program.
move "aa" to w-var.
display w-var,
w-other-var.

test-paragraph.
if w-var = spaces
display "some text",
end-if.

end-of-program.
stop run.

I tested it and don't see any problem.
Can you attach screenshot and mark what is wrongly highlighted?

I cannot reproduce the issues mentioned in #44.

Speaking of COBOL, the bugs mentioned in forum.pspad.com (#34 - #37) are still there.

human

human:

I cannot reproduce the issues mentioned in #44.

Speaking of COBOL, the bugs mentioned in forum.pspad.com (#34 - #37) are still there.

human

Done. Modifications will be available in the next build

Hi Jan.

Screenshot for wrong COBOL code explorer marked with red ellipses: www.rech.com.br

I am sorry. I missed you wrote about Code explorer. I looked for problems in highlighting

Another COBOL problem:
Using Format->Add/Remove Comment sets * in column 1, not in column 7

human