bug-bash
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: fc echoing DEBUG trap


From: Chet Ramey
Subject: Re: fc echoing DEBUG trap
Date: Tue, 24 Sep 2013 15:55:55 -0400
User-agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:24.0) Gecko/20100101 Thunderbird/24.0

On 9/24/13 11:45 AM, Carlos Pita wrote:
> I see that, Chet. But it's not necessarily supposed to be echoed,
> that's what I'm saying. It's counterintuitive that fc prints the
> output. In fact, the output could very confusing.

OK.  Here's how fc has worked historically: it internally turns on the
-v option after running the editor and evaluates the contents of the
resultant file.  This is so you can see what happens to the edited
commands.  (It's an open question whether or not this should be -x
instead, but it never has been.)  The -v option doesn't discriminate
between commands read from the input stream and commands executed by a
trap.  I assert that it's not counterintuitive -- it's the same thing
that happens when you run the same commands from a prompt.

Chet

-- 
``The lyf so short, the craft so long to lerne.'' - Chaucer
                 ``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, ITS, CWRU    address@hidden    http://cnswww.cns.cwru.edu/~chet/



reply via email to

[Prev in Thread] Current Thread [Next in Thread]