Re: running libtool from emacs gud mode

[Justin Randall]

----- Original Message ----- 
From: "Simon Josefsson" <address@hidden>
To: "Justin Randall" <address@hidden>
Cc: <address@hidden>
Sent: Tuesday, August 26, 2003 7:23 PM
Subject: Re: running libtool from emacs gud mode
...

> This has been fixed in gud in Emacs HEAD.
>
>

That's excellent news. For those of us who aren't ready to upgrade (I use
emacs on a gentoo linux distribution, nothing unmasked) that diff should
work.

I don't know if this is the case, but it would seem that unhandled
parameters to libtool may be a more general problem anyway. libtool behaves
as if it should seamlessly front-end any uninstalled program that needs to
be run, but bails out if parameter lists are not ordered to its liking.

One would expect a command line like
<target> <options>
to always be invoked alternately as
libtool <target> <options>

but clearly this didn't work with emacs-21.3.

Could libtool handle situations where the frontend is improperly mangled:
libtool <options> <target>
such that it would better handle bad behavior?
libtool <libtool-specific-options> <target> <other unknown options>
<properly appended options>
to reduce the likelihood of errors we see with emacs-21.3?

At the very least, it couldn't make things worse, could it?