[Info-vax] VMS Features I Wish Linux Had
Johnny Billquist
bqt at softjar.se
Tue Jun 14 05:22:24 EDT 2016
On 2016-06-13 21:36, VAXman- at SendSpamHere.ORG wrote:
> In article <njmdvo$vo0$1 at Iltempo.Update.UU.SE>, Johnny Billquist <bqt at softjar.se> writes:
>> On 2016-06-13 14:59, Bob Koehler wrote:
>>> In article <njeel9$fq3$1 at dont-email.me>, "John E. Malmberg" <wb8tyw at qsl.net_work> writes:
>>>>
>>>> One issue with the VMS terminal line editing is because it is handled in
>>>> the driver, it does not have access to the filesystem to allow it to do
>>>> filename completion.
>>>
>>> Which belongs in the CLI, not the terminal driver. The CLI should be
>>> doing it's own command line editing,instead of leaning on the limited
>>> editing in the driver.
>>
>> I don't agree. I want command line editing, no matter if I'm at the CLI,
>> or in some user application. And I do not consider it to be a good
>> system design that every program should include their own version of
>> commmand line editing.
>
> In VMS, what do you think processes command lines? Assuming you're using
> the VMS CLI callback in yor program(s). If it's just stupid unix-line -X
> switches, etc., then you're on your own.
Uh... What if I do a read in my program...? How would CLI editing come
into play there? Are you suggesting that all terminal I/O should be done
by callbacks to the CLI instead of issuing a QIO?
Johnny
More information about the Info-vax
mailing list