From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 27337 invoked by alias); 2 Jan 2017 15:41:52 -0000 Mailing-List: contact zsh-users-help@zsh.org; run by ezmlm Precedence: bulk X-No-Archive: yes List-Id: Zsh Users List List-Post: List-Help: X-Seq: 22320 Received: (qmail 28195 invoked from network); 2 Jan 2017 15:41:52 -0000 X-Qmail-Scanner-Diagnostics: from out1-smtp.messagingengine.com by f.primenet.com.au (envelope-from , uid 7791) with qmail-scanner-2.11 (clamdscan: 0.99.2/21882. spamassassin: 3.4.1. Clear:RC:0(66.111.4.25):SA:0(-0.7/5.0):. Processed in 1.25038 secs); 02 Jan 2017 15:41:52 -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.7 required=5.0 tests=RCVD_IN_DNSWL_LOW, RCVD_IN_MSPIKE_H3,RCVD_IN_MSPIKE_WL,T_DKIM_INVALID autolearn=unavailable autolearn_force=no version=3.4.1 X-Envelope-From: d.s@daniel.shahaf.name X-Qmail-Scanner-Mime-Attachments: | X-Qmail-Scanner-Zip-Files: | Received-SPF: none (ns1.primenet.com.au: domain at daniel.shahaf.name does not designate permitted sender hosts) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= daniel.shahaf.name; h=cc:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc:x-sasl-enc; s=mesmtp; bh=2ERi2wKBtzZpfiO Q0U5Q0ZyFPmc=; b=bv6PK1eY8SMysCADTjGGxcsDCmKCerQ1Z8FHZg96wcwAwfb HR1YOe1ZH3UyetHvMRvzjuNdEhJXQbQO9M76QVectJpsYfHvdOCdzqlZNg40FuSz BMi7ddgnR8Tb2LuqrsIFt9T4divB39iROClHal7/jM/5Y+ApVXIkjKcmQnUw= DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc:x-sasl-enc; s=smtpout; bh=2ERi2wKBtzZpfi OQ0U5Q0ZyFPmc=; b=aNFJbao+7/5F6M6ajM1+GIUb+VXY1e4kLmvC1bgI7k4gCg 6LYe0AYcrJOXJUf2KcI4h6+6cOWEqUpad37Z7MXg2g5xDH7xWKDc3JB72knX+mx+ GZpZTumF5BhoNlUutVLwhmKzflptlCISANYJ8MZrLiO+0K1LYJi2cyj2F1ck4= X-ME-Sender: X-Sasl-enc: QqtHGOjmDK7sTwyaXcVW/4ukD6axybzqP0+Tdn24lJDu 1483371699 Date: Mon, 2 Jan 2017 15:38:30 +0000 From: Daniel Shahaf To: Timothee Cour Cc: zsh-users@zsh.org Subject: Re: using gitlab (or other) issue tracker instead of mailing list? Message-ID: <20170102153830.GA4752@fujitsu.shahaf.local2> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.23 (2014-03-12) Timothee Cour wrote on Sat, Dec 31, 2016 at 17:10:43 -0800: > Spawned off from a separate discussion: > > regression: zsh completion stopped working after upgrading zsh 5.2=>5.3 > > What are your requirements for tracking zsh issues, and could this be > accomplished by a standard issue tracker (eg github/gitlab/bitbucket) > instead of this mailing list ? Thanks for starting this thread. For what it's worth, I do support having some list of bugs: we do from time to time run into bugs, but those that we don't patch immediately are only recorded in the list archives. Bug trackers are generally open to the public and so serve some user support role as well. However, as far as I know, the existing support channels work well, and only a "repository of known, acknowledged, unfixed bugs" functionality is missing. As Eric points out, we could simply start using Etc/BUGS to fill that functionality. Let's adopt the convention that every entry be tagged with an X-Seq number for ease of reference: diff --git a/Etc/BUGS b/Etc/BUGS index 9991ad9..96958f9 100644 --- a/Etc/BUGS +++ b/Etc/BUGS @@ -12,6 +12,13 @@ the nonomatch and nullglob options. ------------------------------------------------------------------------ It is currently impossible to time builtins. ------------------------------------------------------------------------ -The comp* completion-related builtins (compadd, compset, etc) are run with -$_comp_options in effect, rather than the user's options. +40106: The comp* completion-related builtins (compadd, compset, etc) are +run with $_comp_options in effect, rather than the user's options. +------------------------------------------------------------------------ +40240: vcs_info: percent escapes in payloads are interpreted + +Example: hg branch names and quilt patch subjects that contain the literal +string '%F{blue}', cause $vcs_info_msg_N_ to be rendered in blue. + +40240 has a patch, but 40241 explains why that patch is incomplete. ------------------------------------------------------------------------ ... and to be clear, the venue for support questions and bug reporting will [under this proposal] continue to be the zsh-users@ mailing list. Cheers, Daniel