|
Carl, A request: Your example of Run $FP - please allow omitting the "Run ". $FP<Enter> can only mean run it. Also I find that I can (in XyWrite) dispense with both cd and ca: subdir1<Enter> and foobar.txt almost always means ca foobar.txt It's surprising how nice it is to be able to drop those two or three letters. Hmmm, maybe XyScript will enable users to customize this sort of thing themselves? --Harry On Mon, 22 Jun 2026 17:52:21 -0400, Carl Distefano wrote: > Reply to note from harrybinswanger <dmarc-noreply@xxxxxxxxxxxxx> Mon, 22 Jun 2026 12:06:39 -0400 > > Harry, > > > You did basically what I did. > > Ha, pun intended? ... What I did -- am doing -- is summed up in "It's all XPL": a unified syntax that works on the command line, in the KBD file, and in scripts. The distinction between commands and functions is abolished -- everything is a command (or "verb"). Commands are chained together with semicolons; in scripts, semicolons and newlines are 99% interchangeable. <VA$nn> variables are now just plain-text `$nn`, and they're accessible directly without first being assigned to a "save/get" or user variable. So if you're editing an XPL script and want to run it, `RUN $FP` on the CMline does it. KBD-file usage is cast in the same mold and much simpler than in XyWrite (the commas are gone): > > ; single character > nn=A > > ; multiple characters a/k/a strings > nn="My name is \"Ada\", what's yours?" > > ; single command > nn=AB > > ; multiple commands > nn=SA;AB > > ; Delete DeFine else single character > nn=IF $DF;DZ;RD;ELSE;RC;EI > > It's coming along nicely. Yesterday I added Auto-Replace. > > -- > Carl Distefano > cld@xxxxxxxxxx > |