From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <zsh-users-return-22375-mason-zsh=primenet.com.au@zsh.org>
Received: (qmail 13142 invoked by alias); 14 Jan 2017 16:58:56 -0000
Mailing-List: contact zsh-users-help@zsh.org; run by ezmlm
Precedence: bulk
X-No-Archive: yes
List-Id: Zsh Users List <zsh-users.zsh.org>
List-Post: <mailto:zsh-users@zsh.org>
List-Help: <mailto:zsh-users-help@zsh.org>
X-Seq: 22375
Received: (qmail 8004 invoked from network); 14 Jan 2017 16:58:56 -0000
X-Qmail-Scanner-Diagnostics: from mercury.zanshin.com by f.primenet.com.au (envelope-from <schaefer@brasslantern.com>, uid 7791) with qmail-scanner-2.11 
 (clamdscan: 0.99.2/21882. spamassassin: 3.4.1.  
 Clear:RC:0(64.84.47.142):SA:0(-0.0/5.0):. 
 Processed in 1.571585 secs); 14 Jan 2017 16:58:56 -0000
X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on f.primenet.com.au
X-Spam-Level: 
X-Spam-Status: No, score=-0.0 required=5.0 tests=SPF_PASS
	autolearn=unavailable autolearn_force=no version=3.4.1
X-Envelope-From: schaefer@brasslantern.com
X-Qmail-Scanner-Mime-Attachments: |
X-Qmail-Scanner-Zip-Files: |
Received-SPF: pass (ns1.primenet.com.au: SPF record at ipost.com designates 64.84.47.142 as permitted sender)
Date: Sat, 14 Jan 2017 08:58:15 -0800 (PST)
From: Bart Schaefer <schaefer@brasslantern.com>
Reply-To: Bart Schaefer <schaefer@brasslantern.com>
To: Timothee Cour <timothee.cour2@gmail.com>
cc: Zsh Users <zsh-users@zsh.org>
Subject: Re: option to show file:line everytime echo is called?
In-Reply-To: <CAM4j=kPc6XtoZesc+ysGOfa64LsuBL6BbKdTK3mjU=4vOpcjQQ@mail.gmail.com>
Message-ID: <alpine.LRH.2.00.1701140854160.4560@toltec.zanshin.com>
References: <CGME20170110091259epcas5p14d052ee1dc7ebb5c4dd74e4aa02a8d18@epcas5p1.samsung.com> <CANri+EzTiiKkfeDODR8PyBc=khLFONk738sFp7Vpo4uzwKMoXw@mail.gmail.com> <20170110093042.41111f8a@pwslap01u.europe.root.pri>
 <CANri+EwT3h8MkpeKSd-9_QLp9S=TEibmSgjS3r9mv0jY46dQAw__39244.7733007886$1484262699$gmane$org@mail.gmail.com> <20170113035730.GA1812@fujitsu.shahaf.local2> <alpine.LRH.2.00.1701122304500.4560@toltec.zanshin.com> <alpine.LRH.2.00.1701130005240.4560@toltec.zanshin.com>
 <CAM4j=kPc6XtoZesc+ysGOfa64LsuBL6BbKdTK3mjU=4vOpcjQQ@mail.gmail.com>
User-Agent: Alpine 2.00 (LRH 1167 2008-08-23)
X-Face: "f/X=UCVgd*^c>+x(gMq0at?e:woX+;'snkkRzc3SX<0AZ (/PS4.M2hzGS9X:Qj]at_H/%a9K}:-eS<"v_7vX84PG9Bf Zpb`wI!I4geY=or+nWq`3CX`oq&TJR;g^ps|7(MH?jh;bs %vHJfCh5>a*6Re5m|Bidja\\o]>n\A)ib1:yX*T`zR(*h~ %tOw<~!D9{e6h!8M2:d8G2@K>y^1I_Vdy\d\MYe]z7c
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

On Fri, 13 Jan 2017, Timothee Cour wrote:

> turns out Anthony Heading's solution works great (thanks!): alias
> echo2='echo ${(%):-%x:%I}'
>
> any downside compared to Daniel Shahaf's solution i haven't seen yet?

Use of $funcfiletrace (like in my follow-up to Daniel) will show you
not just the file:line where the echo was called, but also the file:line
where the caller of echo was called, and so on all the way up to the
top-level execution loop e.g. the interactive command line.