Custom Query (44 matches)
Results (7 - 9 of 44)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #10 | fixed | @eawrite and @earead should trim blanks from EA name | ||
| Description |
Like many people, I do not use spaces consistently. Using @eawrite, it is all too easy to create the wrong EA by putting a space after the comma--
won't work, because there is no ".SUBJECT" EA; the EA is " .SUBJECT" (why did IBM allow leading and trailing spaces in an EA name anyway?) |
|||
| #11 | fixed | @words[] does not know the word "0" | ||
| Description |
@words[a] returns 1 @words[] returns 1 Claiming there is one word in an empty string is contrary to common sense, useless, and makes for unnecessary complications in loops. This has been around for years in 4DOS and 4OS2, but I still think its wrong. |
|||
| #14 | fixed | CDWithoutBackslash=2 breaks some scripts | ||
| Description |
I have tried running fm2dump.cmd and keep getting the following error message: G:\FM2.TEST\FM2DUMP.CMD [34] Unknown command "orlevel" Directory U:\Dump does not exist - check set D= statement on line 26 Line 34: if not errorlevel 1 goto DirOK This is caused by CDWithoutBackslash=2. If I don't set it (default is 1 check for executable first) fm2dump works. If I type fm2dump.cmd (adding the extension) with it set to 2 it works. It's obvious that something is gobbling up some of the characters that should be part of the next statement. You can make the error message disappear by adding a few blanks lines before the if statement. I am attaching fm2dump.cmd as a test case |
|||
