zsh-workers
 help / color / mirror / code / Atom feed
From: Frank Terbeck <ft@bewatermyfriend.org>
To: zsh-workers@zsh.org
Subject: PATCH: vcs_info: Set NO_warn_create_global option
Date: Sun, 21 Feb 2010 15:53:24 +0100	[thread overview]
Message-ID: <1266764004-15068-1-git-send-email-ft@bewatermyfriend.org> (raw)

I wanted to do the following, because I'd like to have
`check-for-changes' set in my own project directories, but not in
others, I just check out (because it can be slow for big repos):

function estyle-cfc() {
    local d
    local -a cfc_dirs
    cfc_dirs=( ${HOME}/src/code/*(/) )

    for d in ${cfc_dirs}; do
        d=${d%/##}
        [[ $PWD == $d(|/*) ]] && return 0
    done
    return 1
}

zstyle -e ':vcs_info:git:*' \
    check-for-changes 'estyle-cfc && reply=( true ) || reply=( false )'

That however, welcomes me with this nice warning:
VCS_INFO_get_data_git:49: array parameter reply created globally in function

In theory the above should work (and it does except for the warning). It
also works in compsys, where I'm using this:

zstyle -e ':completion:*:approximate:*' \
    max-errors 'reply=( $(( ($#PREFIX + $#SUFFIX) / 3 )) )'

What compsys does is, it disables the warn_create_global option while
it's running.

While I like what the option does (prevent me from cluttering the shell
with all sorts of variables if I forget `local'), I still want to be
able to use `-e' with zstyle.

So, there are three options:
 a) Get the big hammer and just disable `warn_create_global' in
    vcs_info.
 b) Use a smaller hammer, and create a wrapper function around zstyle
    for vcs_info, that disables the option locally.
 c) Disable `warn_create_global' in code executed by "zstyle -e". Or
    make `reply' and `REPLY' special in that case. Or whatever makes the
    most sense.

This patch does what "a)" suggests, basically because it works and I was
lazy. I think "c)" would be the cleanest solution, but I don't know if
that's doable and I haven't looked at the involved code yet.

I might implement "b)" at a later date if "c)" is not feasilbe with
reasonable effort.

Regards, Frank
---
 Functions/VCS_Info/vcs_info |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)

diff --git a/Functions/VCS_Info/vcs_info b/Functions/VCS_Info/vcs_info
index 906d984..a9e65e1 100644
--- a/Functions/VCS_Info/vcs_info
+++ b/Functions/VCS_Info/vcs_info
@@ -40,7 +40,7 @@ vcs_info_setsys
 # and now, finally create the real vcs_info function
 vcs_info () {
     emulate -L zsh
-    setopt extendedglob
+    setopt extendedglob NO_warn_create_global
 
     [[ -r . ]] || return 0
 
-- 
1.7.0


             reply	other threads:[~2010-02-21 14:59 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-21 14:53 Frank Terbeck [this message]
2010-02-21 15:09 ` PATCH: Disable WARN_CREATE_GLOBAL in 'zstyle -e' code Frank Terbeck
2010-02-21 15:18   ` Frank Terbeck
2010-02-21 17:25 ` PATCH: vcs_info: Set NO_warn_create_global option Bart Schaefer
2010-02-21 20:06   ` Frank Terbeck
2010-02-21 21:17     ` Bart Schaefer
2010-02-21 21:34       ` Frank Terbeck

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=1266764004-15068-1-git-send-email-ft@bewatermyfriend.org \
    --to=ft@bewatermyfriend.org \
    --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).