would you object to putting line number information in more messages?

[Dan Jacobson]

Would you object to putting line number information in more messages?
$ cat -n /tmp/a
     1  
     2  
     3  
     4  : ${@?}
     5  
$ bash /tmp/a
/tmp/a: @: parameter null or not set

In a billion line shell script, it might help to know which line
number things failed on... Indeed, my memories of debugging bash
scripts are not only can I not jump to say, syntax errors, with emacs'
next-error, I often have no idea ... wait:

$ cat -n /tmp/b
     1  bla
     2  ;
$ bash /tmp/b
b: bla: command not found
b: line 2: syntax error near unexpected token `;'
b: line 2: `;'

OK, so: why not be more forthcoming about which line had the "command
not found"?... tell you what, I'll trade you one of the two [!] lines
of information about my syntax error you just gave me, in exchange for
you just adding line number information about where my command was not
found.  And, if you make sure the result is parsable by emacs'
next-error, I might even throw in my latest baseball cards :-)

$ echo $BASH_VERSION
2.05.0(1)-release
-- 
http://www.geocities.com/jidanni/ Taiwan(04)25854780