From: Frank Terbeck <ft@bewatermyfriend.org>
To: Peter Stephenson <p.w.stephenson@ntlworld.com>
Cc: zsh-workers@zsh.org, zsh@benizi.com, schaefer@brasslantern.com,
richih.mailinglist@gmail.com
Subject: Re: PATCH: Add `sourcetrace' option
Date: Sun, 24 Jan 2010 23:27:33 +0100 [thread overview]
Message-ID: <87fx5vw33e.fsf@ft.bewatermyfriend.org> (raw)
In-Reply-To: <20100124211240.3d84f802@pws-pc> (Peter Stephenson's message of "Sun, 24 Jan 2010 21:12:40 +0000")
Peter Stephenson writes:
> Frank Terbeck <ft@bewatermyfriend.org> wrote:
>> Here's an updated patch. Thanks to everyone who reviewed the previous
>> attempts.
>
> I'm just toying with this variant... the difference is this moves the
> output down until after the script name etc. is set up, and uses PS4
> (like the xtrace option), so the output is more configurable. For
> example, I get:
>
> +/etc/zshenv:1> <sourcetrace>
> +/home/pws/.zshenv:1> <sourcetrace>
> +/home/pws/.profile:1> <sourcetrace>
> +/home/pws/.zshrc:1> <sourcetrace>
> /home/pws/.aliasrc:1:> <sourcetrace>
> /home/pws/.compinstall:1:> <sourcetrace>
> /home/pws/.zcompdump_4.3.10-dev-1_pws:1:> <sourcetrace>
>
> (the change in the middle is because I tweak PS4 to remove the "+" in
> .zshrc, for no good reason I can now think of, as well as adding %_, and
> there's only one global file because .zshenv sets NO_GLOBAL_RCS.)
>
> I'm not particularly set on this but it seems more powerful without
> losing anything obvious. The documentation would need tweaking.
Certainly preferable. Would the documentation really need updating? The
entry for `XTRACE' doesn't mention $PS4 either. And the overall
behaviour doesn't differ from my initial approach, does it?
Regards, Frank
--
In protocol design, perfection has been reached not when there is
nothing left to add, but when there is nothing left to take away.
-- RFC 1925
next prev parent reply other threads:[~2010-01-24 22:32 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4B582F3C.2010709@mycircuit.org>
[not found] ` <100121080540.ZM21444@torch.brasslantern.com>
[not found] ` <4B58AB3A.7050300@mycircuit.org>
2010-01-23 10:18 ` Frank Terbeck
2010-01-23 15:46 ` Baptiste Daroussin
2010-01-23 20:16 ` Richard Hartmann
2010-01-23 21:53 ` PATCH: " Frank Terbeck
2010-01-23 22:07 ` Benjamin R. Haskell
2010-01-23 22:23 ` Frank Terbeck
2010-01-23 23:46 ` Bart Schaefer
2010-01-24 0:10 ` Frank Terbeck
2010-01-24 0:18 ` Frank Terbeck
2010-01-24 21:12 ` Peter Stephenson
2010-01-24 22:27 ` Frank Terbeck [this message]
2010-01-23 22:14 ` PATCH: " Frank Terbeck
2010-01-23 23:44 ` Bart Schaefer
2010-01-24 0:05 ` Frank Terbeck
2010-01-24 9:21 ` Peter
[not found] ` <m3fx5y2le2.fsf@klanderman.net>
[not found] ` <87hbqdu9xs.fsf@ft.bewatermyfriend.org>
[not found] ` <4B5A26BA.5080307@mycircuit.org>
[not found] ` <87fx5x6918.fsf@ft.bewatermyfriend.org>
[not found] ` <4B5ABB0D.9010504@mycircuit.org>
[not found] ` <14989d6e1001230228k22e32200s10db146bd8596dc2@mail.gmail.com>
2010-01-23 12:03 ` what is the effect of a percentage sign (%) as last character on the command line Peter
[not found] ` <2d3b879b1001211336m5b78982au96f267ea472af43d@mail.gmail.com>
[not found] ` <4B58D35D.1050208@mycircuit.org>
[not found] ` <100121182713.ZM21821@torch.brasslantern.com>
[not found] ` <4B597061.10701@mycircuit.org>
[not found] ` <100123155239.ZM27228@torch.brasslantern.com>
2010-01-24 9:51 ` Peter
2010-01-24 10:58 ` Frank Terbeck
2010-01-24 14:50 ` Peter
2010-01-26 7:52 ` Peter
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=87fx5vw33e.fsf@ft.bewatermyfriend.org \
--to=ft@bewatermyfriend.org \
--cc=p.w.stephenson@ntlworld.com \
--cc=richih.mailinglist@gmail.com \
--cc=schaefer@brasslantern.com \
--cc=zsh-workers@zsh.org \
--cc=zsh@benizi.com \
/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).