From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-0.7 required=5.0 tests=DKIM_INVALID,DKIM_SIGNED, MAILING_LIST_MULTI,RCVD_IN_DNSWL_NONE,URIBL_SBL_A autolearn=ham autolearn_force=no version=3.4.4 Received: (qmail 12397 invoked from network); 16 Apr 2023 16:24:45 -0000 Received: from zapf.ntg.nl (5.39.185.232) by inbox.vuxu.org with ESMTPUTF8; 16 Apr 2023 16:24:45 -0000 Received: from localhost (localhost [127.0.0.1]) by zapf.ntg.nl (Postfix) with ESMTP id D5B0E1C02FF; Sun, 16 Apr 2023 18:24:23 +0200 (CEST) X-Virus-Scanned: Debian amavisd-new at zapf.ntg.nl Received: from zapf.ntg.nl ([127.0.0.1]) by localhost (zapf.ntg.nl [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eEevJpYKytnG; Sun, 16 Apr 2023 18:24:20 +0200 (CEST) Received: from zapf.ntg.nl (localhost [127.0.0.1]) by zapf.ntg.nl (Postfix) with ESMTP id 5F7AB1461; Sun, 16 Apr 2023 18:24:20 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by zapf.ntg.nl (Postfix) with ESMTP id 257EF1461 for ; Sun, 16 Apr 2023 18:24:18 +0200 (CEST) X-Virus-Scanned: Debian amavisd-new at zapf.ntg.nl Received: from zapf.ntg.nl ([127.0.0.1]) by localhost (zapf.ntg.nl [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Kn3FpXQ00g87 for ; Sun, 16 Apr 2023 18:24:17 +0200 (CEST) Received-SPF: Pass (mailfrom) identity=mailfrom; client-ip=67.215.8.22; helo=seout13.web-dns1.com; envelope-from=zlists+context@jdvb.ca; receiver= Received: from seout13.web-dns1.com (seout13.web-dns1.com [67.215.8.22]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by zapf.ntg.nl (Postfix) with ESMTPS id C7CA49B7 for ; Sun, 16 Apr 2023 18:24:16 +0200 (CEST) Received: from mailpro1.whc.ca ([51.79.16.13]) by se3.web-dns1.com with esmtps (TLSv1.3:TLS_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1po5Ai-0004Fc-6m; Sun, 16 Apr 2023 12:24:14 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=jdvb.ca; s=default; h=In-Reply-To:Content-Type:MIME-Version:References:Message-ID: Subject:Cc:To:From:Date:Sender:Reply-To:Content-Transfer-Encoding:Content-ID: Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc :Resent-Message-ID:List-Id:List-Help:List-Unsubscribe:List-Subscribe: List-Post:List-Owner:List-Archive; bh=ugtLaONecpBOwT98kiDmRM7XFgT2sgufX3nzTxbNzjM=; b=Yf6VwzhuOZI8m6qTQp80a7vs8d 8lgeq+EIhKbu0idEJ6S3ukCdUq43gpoBq5Ezz+c6EYDVAJnq2CqufDwYyWn+EUgVXA3by8KcLd8hD RFCU56t76dZxD1QANKfTDOxGC5k/CApCbLoFGyPFPSNfEGA+BcWnYjIi6XXhhLhdCYW0IUwuP9Vty 5rAsiuvziuoP11ssACHFi8uKTyDR6EuWDjRHq6FIG6foZjGwjH6cycDUpojKYH+l2eAzIdnwhJq/A PR64SEHzRQQVzHEDTsTsCU9uqUjAE8EMZM56sD/q4s+oP+mvbLfzIDcJEy9WGMwROYC3KQOxz58yV vTjNMuLw==; Received: from [142.177.159.153] (port=51744 helo=x360) by mailpro1.whc.ca with esmtpsa (TLS1.3) tls TLS_AES_256_GCM_SHA384 (Exim 4.95) (envelope-from ) id 1po5Ae-00Aq6c-NC; Sun, 16 Apr 2023 12:24:11 -0400 Received: by x360 (Postfix, from userid 1000) id 4452E1E0927; Sun, 16 Apr 2023 13:24:08 -0300 (ADT) Date: Sun, 16 Apr 2023 13:24:08 -0300 To: mailing list for ConTeXt users Message-ID: References: MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: X-Microslop: Just say no X-Originating-IP: 51.79.16.13 X-SpamExperts-Domain: out.mailpro1.whc.ca X-SpamExperts-Username: 51.79.16.13 Authentication-Results: web-dns1.com; auth=pass smtp.auth=51.79.16.13@out.mailpro1.whc.ca X-SpamExperts-Outgoing-Class: unsure X-SpamExperts-Outgoing-Evidence: Combined (0.32) X-Recommended-Action: accept X-Filter-ID: Pt3MvcO5N4iKaDQ5O6lkdGlMVN6RH8bjRMzItlySaT9ORw3T7yZZX8MpBaNdOyEfPUtbdvnXkggZ 3YnVId/Y5jcf0yeVQAvfjHznO7+bT5ztfmuPGETD329aYmyGIscRNyZc1sxMQV+MlezyhpoWDQFO yVE8oVAvPecYkEdv8J/kmxK59qrC5d72gYUyctQiIthZ1E08p4dGjiIH+Kib8WXx2azEPCntGfKY yhVHoInNjAO630Xek4v1WZSQqM95DLsOiYBRmCiff0jjge5AEGosc+GhRozOrddAqOmMFOJy8oFz lZDzSFMZMCEJKqX3eLIoiT9b9S5SVizz3DNwuslSybMqs8+cw05SXUYIt2ru9NCFlaHqECDZ0njF fPczgf113mZYUbXVpatdviFoMJkHtDUeNUPQBvuvTgeocAejtRu5bPC8zl5GPOV9RgMxYWA4ryBb 6FrOHzigF4y0YTcZoh+UidCgbs+IOOJ2oKzna6MyGOkqIqWHjqWJFjYk7LkpijicqSalrW2rJb6H PsFUVZKs0eeC26uVFs0oAkh+djWY6GBDt0UpG6K4iuv2o+Bse6gz8O3xVRmqUy3DOY/yXIk618YV Jp5jM2kZcUgHPUbw7CVpNolczSoTuJsRnENsSECCOsy4kitQ2EVON/d1C1PtUzdL2kOYVjIShWBG ukMcUEqpvTahetOmCeuNOBJTgQKvqNpm4+ao68PdgAeYUOp7A73HI6oJg7w/Vod/PDA/oQLSZdAD OeDprKKEzznCpn9MRUzzcEJzOzmIv9M+m4WpRRDP6YzwkAPgQJaftECi/qMvyw4uAb4dsIQ+DzuN uKfKy8BVJTxd+/+9JuNey1usqYhWNGXpA6TRFNmUFFnHeQnQgbqrxs/gJu05dOM0i6i8IGB1nDZZ aZou1o2sETJvhivH157Is5xRQ59SsRwf3rRhvoymIv7bzlshK+VzIi1ULT1qXnF5VPHSv9Xq55AC eiZaQb8ewghGEDNJVUFe6CSZa34XnaGhLIiXQv7eRdcpNBYvaGcus4x0lbpDKG8jcIdTu+Oo+xXh pRgb83lMTunQlqe28yg+FdK/MS+4ayUpOtEhdxekWDmK9g== X-Report-Abuse-To: spam@se1.web-dns1.com Subject: Re: [NTG-context] \setupitemize[indentnext=auto] broken? X-BeenThere: ntg-context@ntg.nl X-Mailman-Version: 2.1.38 Precedence: list List-Id: mailing list for ConTeXt users List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , From: Jim via ntg-context Reply-To: mailing list for ConTeXt users Cc: Jim , Carlos Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: ntg-context-bounces@ntg.nl Sender: "ntg-context" On Sun, Apr 16, 2023 at 08:28 (-0400), Carlos via ntg-context wrote: > On Sat, Apr 15, 2023 at 02:27:56PM -0300, Jim via ntg-context wrote: >> In the wiki page https://wiki.contextgarden.net/Indentation there is the >> following example: >> %------------------------------------------------------------------------ >> \setupindenting[medium,yes] >> \setupitemize[indentnext=auto] >> \startitemize >> \item One >> \stopitemize >> This paragraph should be indented - due to the blank line after \type{\stopitemize}. >> \startitemize >> \item Two >> \stopitemize >> This paragraph should not be indented. >> %------------------------------------------------------------------------ >> Tragically, the paragraph which claims it should be indented is not, in >> both my test and the wiki page itself. >> Is this a documentation bug, a ConTeXt bug, or something else yet? > I don't know. OK, but I wasn't asking you specifically. > Why would it be a documentation bug if it clearly says it should be > indented only after the blank line, unless \indent was omitted on purpose > while trying to make it look as if the blank line would have any effect > after all. Makes no sense. Have you never run into a documentation bug before? Happy you! I see two possibly reasons for a documentation bug here (there might be more): (1) The documentation was incorrect at time of writing. Humans have been known to make mistakes. (2) The semantics of \setupitemize might have changed since the documentation was written, and the change has not yet been reflected in this particular piece of documentation. This would not be the first time that documentation changes lagged behind code changes. The point is, there is a disconnect between the documentation says will happen and what actually happens. I don't know which is wrong, and thus my question. I hope that sooner or later someone who can definitively comment on the disconnect will speak up. > \setupindenting[medium,yes] > \setupitemize[indentnext=auto] > \starttext > \startitemize > \item One > \stopitemize\indent%blank line > This paragraph should be indented - due to the blank line after \type{\stopitemize}. > \startitemize > \item Two > \stopitemize > \noindent{\dorecurse{10}{\indent This paragraph should not be indented.}} > \stoptext ___________________________________________________________________________________ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context webpage : https://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : https://contextgarden.net ___________________________________________________________________________________