On 6/6/16 12:50 AM, Dan Douglas wrote:
> On Sun, Jun 5, 2016 at 8:48 PM, Chet Ramey wrote:
>> "Traced functions inherit the DEBUG and RETURN traps from the calling
>> shell."
>
> Why did RETURN originally get sucked into set -T? Was it supposed to
> be primarily for debugging?
Yes. The R
On Sun, Jun 5, 2016 at 8:48 PM, Chet Ramey wrote:
> "Traced functions inherit the DEBUG and RETURN traps from the calling
> shell."
Why did RETURN originally get sucked into set -T? Was it supposed to
be primarily for debugging? Some functions actually use it for
internal purposes and enabl
On 6/2/16 9:20 AM, Paulo César Pereira de Andrade wrote:
> Hi,
>
> This is a "RFC" to update documentation to better match behavior,
> or, to get some information about shell tracing.
>
> Bellow I am quoting a request from an user:
>
> ---8<---
> The bash shell offers the xtrace (set -x),
Not sure exactly how zsh does it but I know not having the option for
both global and local tracing can be annoying.
The two big ways of handling xtrace I mostly see are either bash's
global `set -x` or ksh93's per-function tracing, and it can be
annoying to be missing either one. There are tricks
