From: Peter Stephenson <p.stephenson@samsung.com>
To: Zsh Hackers' List <zsh-workers@zsh.org>
Subject: Re: PATCH: evaluation depth in prompts
Date: Tue, 02 Sep 2014 09:38:19 +0100 [thread overview]
Message-ID: <20140902093819.0ba101cd@pwslap01u.europe.root.pri> (raw)
In-Reply-To: <140901140202.ZM14612@torch.brasslantern.com>
On Mon, 01 Sep 2014 14:02:02 -0700
Bart Schaefer <schaefer@brasslantern.com> wrote:
> On Aug 29, 5:16pm, Peter Stephenson wrote:
> }
> } In case anyone's still following, here's the original script updated.
> } This now gives reliable tracing of who's calling whom
>
> Here's a related idea/suggestion which adds indentation to the output
> of _complete_debug. There's no convenient way to produce ${(%):-%e}
> spaces for arbitrary depths without turning on promptsubst, so this
> generates a bunch of %N(e. .) expressions and glues them together.
> If completion goes more than 20 function calls deep there's probably
> something wrong anyway.
Seems reasonable --- it doesn't remove any of the existing information.
A visual cue for calls should make it a lot clearer.
> I couldn't decide whether to put the indentation after the leading "+"
> or before it. This has it before.
That makes it easier to strip the spaces if you happen to prefer it
like that.
pws
next prev parent reply other threads:[~2014-09-02 8:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-26 16:40 Function for examining structure of calls in debug output Peter Stephenson
2014-08-26 17:10 ` PATCH: evaluation depth in prompts Peter Stephenson
2014-08-29 16:16 ` Peter Stephenson
2014-09-01 21:02 ` Bart Schaefer
2014-09-02 8:38 ` Peter Stephenson [this message]
2014-09-02 23:53 ` Oliver Kiddle
2014-09-03 1:38 ` Bart Schaefer
2014-08-30 20:35 ` Bart Schaefer
2014-08-30 19:38 ` Function for examining structure of calls in debug output Bart Schaefer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20140902093819.0ba101cd@pwslap01u.europe.root.pri \
--to=p.stephenson@samsung.com \
--cc=zsh-workers@zsh.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).