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.0 required=5.0 tests=DKIM_ADSP_CUSTOM_MED, 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 3827800a for ; Sun, 29 Dec 2019 03:15:03 +0000 (UTC) Received: (qmail 29182 invoked by alias); 29 Dec 2019 03:14:57 -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: 45155 Received: (qmail 24690 invoked by uid 1010); 29 Dec 2019 03:14:56 -0000 X-Qmail-Scanner-Diagnostics: from mail-ua1-f50.google.com by f.primenet.com.au (envelope-from , uid 7791) with qmail-scanner-2.11 (clamdscan: 0.102.1/25670. spamassassin: 3.4.2. Clear:RC:0(209.85.222.50):SA:0(-2.0/5.0):. Processed in 2.315637 secs); 29 Dec 2019 03:14:56 -0000 X-Envelope-From: sgniazdowski@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.222.50 as permitted sender) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=mJYftxQZfniB5GxXwS1RkPI9h/FjWnT4WSzvZ5rRwyE=; b=O2LTphDOORoIeiDoO1D8xXpr1371yVDlIrFG7g8c83N9JmqPPR2me4I4jvMkdXzvWj VVASkl7yyRyUJWCZMSjwS6sxXOv2tNBeRYaPoVUTBVszkl1tdtTY/ttwd1P2vB4Fs9CJ MpXOdwQoT8JpOmJDORD+nYpQg9u1uhNXFph2p5YnFU4XhXb8ap/vu4JlOv+xbdheKVgi +lW56HyyCoEUf3RB+nYpoP1HIqxdTPum7LNzUWEjceqhgo2bk3dehtLPwPqb16BlRQ/i gT5mtqf1zuzCRu9iEXwDBDpN9zxdnFSro0R372coEao6tKiW5P+F9WEVU/ne+si2I9VH 06FA== X-Gm-Message-State: APjAAAXk9fBFrm1t8yxOZg0Rtp7qpmdpwrfJCCQD9mMlNixHIFd5j272 YvgF+lvD/rnclyOsEjmPmlkxt4mrLdyETsit46P7nw== X-Google-Smtp-Source: APXvYqziBtD/a5EM6gZ+DW51jBY7LUNt6cOxXjhiMCOt8l7nhkHvI64Ex39BfRbXsDNdTDRo+8mHX7fm+Trlu8o6DtA= X-Received: by 2002:ab0:7852:: with SMTP id y18mr26459363uaq.28.1577589261156; Sat, 28 Dec 2019 19:14:21 -0800 (PST) MIME-Version: 1.0 References: <1a130b2e-5824-4b7a-8510-2b1d0b3fdac5@www.fastmail.com> <20191227052923.yal2nnmxdxfgvfkr@tarpaulin.shahaf.local2> <20191228210017.2cdgwgpqrssrfhgp@tarpaulin.shahaf.local2> <20191229020534.oqh5ri3nqealx4hj@tarpaulin.shahaf.local2> In-Reply-To: <20191229020534.oqh5ri3nqealx4hj@tarpaulin.shahaf.local2> From: Sebastian Gniazdowski Date: Sun, 29 Dec 2019 04:14:11 +0100 Message-ID: Subject: Re: [Bug] S-flag imposes non-greedy match where it shouldn't To: Daniel Shahaf Cc: Zsh hackers list Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Sun, 29 Dec 2019 at 03:06, Daniel Shahaf wrote: > > Sebastian Gniazdowski wrote on Sun, Dec 29, 2019 at 01:56:12 +0100: > > I think that the style of the docs has a value. At first one can get li= ttle > > angry "why the example just doesn't confirm what I already suspect", > > however, after untangling it one most probably will feel satisfaction a= nd > > gratefulness. It's a way to share advanced, expert knowledge. > > There should be no untangling. Documentation is about conveying knowledg= e, not > about presenting riddles. I'm just noticing that the riddle-style is a way to convey peculiar things about the described features and it does work, although it requires involving more resources during reading. Otherwise, there must be basically a long paragraph of text that openly - although with difficulty of stating the subtleties clearly =E2=80=93 describes the things= . I can opt for the riddle style because it has its advantages =E2=80=93 readin= g such long delicate text requires resources too and is open for misreading, while the riddle condensates the knowledge in a form that's not open for that. > > As I said I see much value in the current style of the docs and I've > > learned much from it, so I don't think it should be changed. > > Well, I'm sorry, but I expect consensus will not side with you on this. > > Do you intend to send another revision of the (S) docs patch upthread? Rather not, I've couldn't replace the example with anything simpler and the patch that would describe the issue with (S) would be either superficial (for a short version) or too long and convoluted. --=20 Sebastian Gniazdowski News: https://twitter.com/ZdharmaI IRC: https://kiwiirc.com/client/chat.freenode.net:+6697/#zplugin Blog: http://zdharma.org