From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-1.1 required=5.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,FREEMAIL_FROM,MAILING_LIST_MULTI,RCVD_IN_DNSWL_NONE autolearn=ham autolearn_force=no version=3.4.2 Received: from primenet.com.au (ns1.primenet.com.au [203.24.36.2]) by inbox.vuxu.org (OpenSMTPD) with ESMTP id 2813322d for ; Fri, 29 Nov 2019 15:26:32 +0000 (UTC) Received: (qmail 4185 invoked by alias); 29 Nov 2019 15:26:24 -0000 Mailing-List: contact zsh-workers-help@zsh.org; run by ezmlm Precedence: bulk X-No-Archive: yes List-Id: Zsh Workers List List-Post: List-Help: List-Unsubscribe: X-Seq: 44951 Received: (qmail 14160 invoked by uid 1010); 29 Nov 2019 15:26:24 -0000 X-Qmail-Scanner-Diagnostics: from mail-io1-f66.google.com by f.primenet.com.au (envelope-from , uid 7791) with qmail-scanner-2.11 (clamdscan: 0.102.0/25642. spamassassin: 3.4.2. Clear:RC:0(209.85.166.66):SA:0(-2.0/5.0):. Processed in 4.628806 secs); 29 Nov 2019 15:26:24 -0000 X-Envelope-From: mikachu@gmail.com X-Qmail-Scanner-Mime-Attachments: | X-Qmail-Scanner-Zip-Files: | Received-SPF: pass (ns1.primenet.com.au: SPF record at _netblocks.google.com designates 209.85.166.66 as permitted sender) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=nbaYpOWdz3HxHJ34Ljg0+NyWLcuBhrFJIxz5cYDFCsk=; b=rVN0I09L48HX2j7IJAL4FJSGypJONPxYQXA0HaDfkRw4W5K1bT1ehkkxWQ+9gtnKOL 3Dt3pxald4KeWh5rtHK2AzCvjMON3YaF+LBI5HRwR+GhzLLUDmfYGdkr20u0+HCsGopH T9Tvz546TCXG0sxPBZi/JwQ/5hD8e32AweKSyibaVSx7CHkKpcpCu6PJ9V1Etnlwo1Et FZLcy3EB6Y5pH5109ciOtOry6Y6W225OvpA8l+dfkF74QVa7pkCFX8kqxrXLugsRB0sa iALLo38NqVM/2SmNpUEomGAN2m2GpT5EnMHjRdE3Frlfysa9zR0ifgYfL/Xt2IyKqaLo GasA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=nbaYpOWdz3HxHJ34Ljg0+NyWLcuBhrFJIxz5cYDFCsk=; b=DICu4Fy/WzSEpDSgPotc1qwg6E4lXlvl0HqI/sSiLwNpnQ4S/eGlHHP3k8ccg0rWhh 9i0vkeIbglwxYZ5dSlidKtnAzMNQKh1M/Z7MNOfhn1LLWpyp1YCWDztYrcHXGjyel8Mf NpPe6tkuiwnRXB37fsFxwjTfYzIEs1o8VcjpIsgSZ93dd5tW4QRDVW6Q2RPMQJtZLVdp ikMZXnihK5BgP1DJ7bSizLCfJoxZh2JY36M4UMmKNy2tHKjTa8K53p/TPRz7Jmtyl5h6 jTeS6SBcfyM9mpqEuhhINdXQbSGKeiTkl3UBVzbd/5+vl4Z3OjsdsghRUxqBJA+O4hSS 3r6w== X-Gm-Message-State: APjAAAXPjFfl3AR7Wg2iqNqpt840GTq/Fe24bFr5kPYP8tDicArRt36b YQZq0ueW7VjZb1QODTVNPvlC5oyED2luzeNSiy8= X-Google-Smtp-Source: APXvYqxHbld8rBms7bQNVvJMtG67mOT+ABH+X/Sy8PPk+arB9LI9y/v28OGRaPBmiHiHCWBwyGAaYjXnvrYuT3IEr6g= X-Received: by 2002:a5d:938d:: with SMTP id c13mr41576576iol.159.1575041146145; Fri, 29 Nov 2019 07:25:46 -0800 (PST) MIME-Version: 1.0 In-Reply-To: References: <20191123221443.279556-1-mezin.alexander@gmail.com> <20191123221443.279556-3-mezin.alexander@gmail.com> <20191125043525.lcxm532gi6hb7n53@tarpaulin.shahaf.local2> <9438ca11-d0be-4c67-a5b3-a0b900342302@www.fastmail.com> <5edaa985-4ac9-411c-b4c2-415c49a563e3@www.fastmail.com> <20191128213430.53b5akiq43l7bzbx@tarpaulin.shahaf.local2> From: Mikael Magnusson Date: Fri, 29 Nov 2019 16:25:44 +0100 Message-ID: Subject: Re: [PATCH 2/3] vcs_info/cvs: set vcs_comm[basedir] in VCS_INFO_detect_cvs To: Aleksandr Mezin Cc: Daniel Shahaf , zsh-workers@zsh.org Content-Type: text/plain; charset="UTF-8" On 11/29/19, Aleksandr Mezin wrote: > Then I don't see a sane way to choose which VCS to show, other than > how it's already done (first one detected from 'enabled'). For > example, a hg work tree in cwd, and GIT_WORK_TREE is set to something > else (maybe parent directory, maybe ../other-dir). Which one (hg or > git) to choose? Why? > > I guess I'll have to live with my own fork of vcs_info, because any > changes there will break it for someone else. If you use zstyle -e to change the enable (or disable) style of vcs_info, you should be able to decide in the way you want. (Arguably it should use the order of the systems listed in the enable style to decide which to prioritise). Or you can include one system in enable for a more specific style only, eg zstyle :vcs_info:hgonly:* enable hg, and then call "vcs_info hgonly", etc. -- Mikael Magnusson