Re: traceon behavior in head [was: another core dump to be fixed before 1.4.5]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi Eric,

Nice work!  Do you ever sleep? ;-)

On 18 Sep 2006, at 06:39, Eric Blake wrote:
> A couple of followon patches I would like to make, based on things I
> noticed in this patch.  First, the name --error-output is  
> misleading - it
> redirects trace and debug output, but does not touch error messages or
> errprint.  A better name might be --debug-output (matching the already
> existing short option -o), or --debugfile (to match the builtin  
> that it
> mirrors, although that name no longer contains an o for the short  
> option
> mnemonic).  Any preferences on the name?

One of the big things I wanted to push for with 2.0 was consistency  
between
the options and builtins, particularly where something was possible  
with one
but not the other.  In respect of that mantra, --debugfile is the  
right option.
Since we don't want to break backwards compatibility so gratuitously,  
lets
continue to support -o and --error-output too, but perhaps give a  
deprecation
warning for the next several releases.

> Second, since POSIX allows dumpdef to display output in an unspecified
> format, would it be worth adding a debug flag to debugmode that  
> enhances
> the dumped output to show the entire stack of pushdef'd definitions,
> rather than just the topmost?

Ooo!  Sexy... yes that would be fantastic :-D

Cheers,
	Gary.
- --
Gary V. Vaughan      ())_.  gary@ 
{lilith.warpmail.net,gnu.org},[email protected]
Research Scientist   ( '/   http://blog.azazil.net
GNU Hacker           / )=   http://www.gnu.org/software/{libtool,m4}
Technical Author   `(_~)_   http://sources.redhat.com/autobook




-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)

iD8DBQFFDzigFRMICSmD1gYRAuzLAKDGxZzEc/DRChaTqeStmXm8qNWoOQCgiAq6
yAVXg9xz2hgyjWo46O+fxCM=
=YOET
-----END PGP SIGNATURE-----