Re: Interesting handling of command line arguments
>>>> "Chris" == Chris Palmer
<chris(a)nodewarrior.org> writes:
Chris> Valdis.Kletnieks(a)vt.edu writes:
> Just because it already implements counterintuitive behavior is
> no reason to keep doing so.
Yeah, right. Tell that to Mike Sperber (wearing his EFS hat, not his
KKCC hat), who is hosed by every Red Hat release.
On balance I think in this case it's reasonable to change. But that's
only because it seems awfully implausible that there are scripts out
there that depend on files (or lisp functions! -f -func) whose names
begin with `-' being created (invoked) rather than bitched about.
> should 'xemacs --hepl' invoke usage() or should it open
the
> file as specified?)
Chris> It should definitely show the command line usage help.
Uh-uh. Unless -batch was given (and maybe -eval or -funcall, ie an
attempt to perform a possibly destructive operation), I see no good
reason for not invoking the editor, and displaying a warning. Maybe
it should push the offending argument on the find file history, just
for kicks.
--
Institute of Policy and Planning Sciences http://turnbull.sk.tsukuba.ac.jp
University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN
Ask not how you can "do" free software business;
ask what your business can "do for" free software.