Hi, 1. The "UNIX shell script" highlighter must be case sensitive!
All shell-internal commands are lowercase, so a variable named "TEST" or "Test" does not interfere with the shell command "test" - but the highlighter shows the "Test" and "TEST" variables in dark blue anyway. Rather annyoing... :-/ 2. The "UNIX shell script" highlighter should have the "escaped string" setting, if possible only for double quoted strings! A double quoted string like "She said \"Hi\"" stops being a double quoted string before the 'H' - that makes the highlighter falsely show the "Hi" as outside the string... :-/ Related problem: In single quoted strings, the '\' character does NOT escape a single quote, so for single quoted strings, the actual behavior of the syntax highlighter is correct. 3. If possible: Single and double quoted strings can span several lines in UNIX shell scripts, so it is perfectly legal to write: NEWLINE=" " # A variable that contains just a line break to get a line break within a shell variable - but the highlighter stops considering a string at the end of the line, so the comment seems to be within a string... It would be great if the syntax highlighter could (be told to) look for a closing single or double quote until the end of the file, like the shell does, otherwise it does not help with strings you forgot to close. :-| All that said, I totally love PSpad (Version 4.7.5 (2450)) and use it every day, very often to edit shell-scripts or awk-scripts on a remote UNIX machine via the ftp feature - great feature! (Once in a while I need the Vim editor to find a "runaway string" because it has correct syntax highlighting for shell scripts, but I prefer PSpad very much!) :-) :-) :-) By the way - I created a syntax highlighter for awk. It has the same problem with strings spanning more than one line. Is anybody interested anyway? Greetings from Germany Dirk -- <http://forum.pspad.com/read.php?2,61817,61817> PSPad freeware editor http://www.pspad.com
