Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: PATCH: functrace [was Re: funcstack and backtraces]
- X-seq: zsh-workers 22738
- From: Bart Schaefer <schaefer@xxxxxxxxxxxxxxxx>
- To: zsh-workers@xxxxxxxxxx
- Subject: Re: PATCH: functrace [was Re: funcstack and backtraces]
- Date: Mon, 18 Sep 2006 08:16:33 -0700
- In-reply-to: <20060918110758.GA23984@xxxxxxxxxxx>
- Mailing-list: contact zsh-workers-help@xxxxxxxxxx; run by ezmlm
- References: <20060901191034.GA31335@xxxxxxxxxxx> <060904142643.ZM9472@xxxxxxxxxxxxxxxxxxxxxx> <20060917191418.GA22898@xxxxxxxxxxx> <060917153954.ZM32752@xxxxxxxxxxxxxxxxxxxxxx> <20060918033708.GA6522@xxxxxxxxxxx> <060917225733.ZM1116@xxxxxxxxxxxxxxxxxxxxxx> <20060918110758.GA23984@xxxxxxxxxxx>
On Sep 18, 7:07am, Clint Adams wrote:
}
} > TRAPDEBUG prompt_bart_precmd precmd
} > prompt_bart_precmd:1 Src/zsh:2 Src/zsh:9
}
} So Src/zsh:9 calls precmd, Src/zsh:2 (precmd?) calls prompt_bart_precmd,
} and prompt_bart_precmd:1 unwittingly calls TRAPDEBUG.
OK, so I was misreading it. Just up too late, I guess. Thanks.
} Maybe grabbing the name of the previous function from the funcstack
} would be more useful.
Particularly in combination with my "functions"-output newline-placement
suggestion from zsh-users/10591, so that you could actually match the
line number to a line in a function without having to re-read the source
file.
Messages sorted by:
Reverse Date,
Date,
Thread,
Author