Martin Buchholz writes:
>>>>> "Kyle" == Kyle Jones
<kyle_jones(a)wonderworks.com> writes:
Kyle> Hrvoje Niksic writes:
>> Kyle Jones <kyle_jones(a)wonderworks.com> writes:
>> > How is this hurting dunnet?
>>
>> `xemacs -batch -l dunnet' displays ugly newlines after all the
>> prompts. Ugly, ugly, ugly. Cf. with FSFmacs, which handles it
>> correctly.
Kyle> I think this misses the point of batch mode. From time
Kyle> immemorial 'batch' has implied 'non-interactive'. So there
Kyle> should be no interactivity, and therefore no prompts.
I think this is an arbitrary restriction.
Yes. My point is that the behavior we're seeing is unsurprising
because -batch isn't intended to do what "xemacs -batch -l dunnet"
is trying to do. It can be changed, certainly, but it makes more
sense to run dunnet without -batch. Here we have an editor with
powerful interactive input features and then someone wants to use
it like 'ed'? And we should encourage this?
Perhaps -stream would be a better name for a option that
allows a program to generally avoid contact with the icky
user, but still be able to if necessary. Like `perl', for
example.
Yes.
Emacs is a Lisp interpreter first, an editor second.
You've got to be kidding.