Zsh Mailing List Archive
Messages sorted by:
Re: what is the effect of a percentage sign (%) as last character on the command line
- X-seq: zsh-users 14738
- From: Christian Walther <cptsalek@xxxxxxxxx>
- To: Peter <vmail@xxxxxxxxxxxxx>
- Subject: Re: what is the effect of a percentage sign (%) as last character on the command line
- Date: Sat, 23 Jan 2010 11:28:08 +0100
- Cc: Frank Terbeck <ft@xxxxxxxxxxxxxxxxxxx>, zsh-users@xxxxxxx
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=UyABbWjH/8MEuywUxfnedCLqO39sSanLV3TQCxe2cKY=; b=fDjDqNOk8OhiFBMeQ/xfCFIFHVpV3eVz7qLACvdfQ9In6nzStZjnDhv46MWM9rM+GJ ouWdN/Zuvc3jscG88P/oszQ2rPWpokvhB4fnGofAcYoFXxgSgGNg4H/xIy+IoKsRejCI g2RSETiwibobBYnDJ6QJ02He7eHtNEvTMTCaw=
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=S6UAwTsPyVRqpMW7Z3ovE/F6dv3vOaEGpCuVWjEVaGSHR+Wcq9+CbsCBm6fhcf+6rf vgpkFh9S9jMYtaqqbzx35stjOmHWHeYwjzNnQggE5md8LT5qxxvP9C9MzEbH8TnzYm3y uTCQth9vpu1qlPjnITmYXdFLe7Uvk2bNPUHdI=
- In-reply-to: <4B5ABB0D.9010504@xxxxxxxxxxxxx>
- List-help: <mailto:email@example.com>
- List-id: Zsh Users List <zsh-users.zsh.org>
- List-post: <mailto:firstname.lastname@example.org>
- Mailing-list: contact zsh-users-help@xxxxxxx; run by ezmlm
- References: <4B582F3C.2010709@xxxxxxxxxxxxx> <100121080540.ZM21444@xxxxxxxxxxxxxxxxxxxxxx> <4B58AB3A.7050300@xxxxxxxxxxxxx> <m3fx5y2le2.fsf@xxxxxxxxxxxxxx> <87hbqdu9xs.fsf@xxxxxxxxxxxxxxxxxxxxxx> <4B5A26BA.5080307@xxxxxxxxxxxxx> <87fx5x6918.fsf@xxxxxxxxxxxxxxxxxxxxxx> <4B5ABB0D.9010504@xxxxxxxxxxxxx>
On 23 January 2010 10:02, Peter <vmail@xxxxxxxxxxxxx> wrote:
> Great, thanks a lot for your help.
> I would still like to make a request for a command line switch allowing to
> simply list the config files that were _actually_ read ( you have this thing
> in Python ( modules ), Perl ( modules ), Haskell ( configuration files ) ,
> etc and I think for a product with complex configuration possibilities this
> is really a help for debugging ).
> All that said, of course the problem I had was entirely my fault.
If you need to debug your configuration it is pretty save to just send
the name of the current file to stdout, e.g. by adding a echo to the
beginning of each file. You can even do this conditionally, for
example by adding
to /etc/zshenv if you're root on this machine, or to ~/.zshenv.
And then you add something like
[[ -n $CONFIGDEBUG ]] && echo "Reading: <filename>"
to each file. This way, you see what's happening and it's still easy
to disable the output.
I'm using this method to debug my startup files sometimes, because I
wrote several functions to make it easier to work with several Solaris
commands and products.
Messages sorted by: