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.9 required=5.0 tests=MAILING_LIST_MULTI, RCVD_IN_DNSWL_NONE,URIBL_SBL_A autolearn=ham autolearn_force=no version=3.4.4 Received: (qmail 17626 invoked from network); 19 Apr 2023 12:24:10 -0000 Received: from zapf.ntg.nl (5.39.185.232) by inbox.vuxu.org with ESMTPUTF8; 19 Apr 2023 12:24:10 -0000 Received: from localhost (localhost [127.0.0.1]) by zapf.ntg.nl (Postfix) with ESMTP id 4F24F4B33; Wed, 19 Apr 2023 14:24:00 +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 ZpCzJXBojfWM; Wed, 19 Apr 2023 14:23:55 +0200 (CEST) Received: from zapf.ntg.nl (localhost [127.0.0.1]) by zapf.ntg.nl (Postfix) with ESMTP id 7A52442BD; Wed, 19 Apr 2023 14:23:55 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by zapf.ntg.nl (Postfix) with ESMTP id 5F2CD3CBE for ; Wed, 19 Apr 2023 14:23:54 +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 7qxZWFEmtZKw for ; Wed, 19 Apr 2023 14:23:49 +0200 (CEST) Received-SPF: Pass (mailfrom) identity=mailfrom; client-ip=116.202.254.214; helo=ciao.gmane.io; envelope-from=gctc-ntg-context-518@m.gmane-mx.org; receiver= Received: from ciao.gmane.io (ciao.gmane.io [116.202.254.214]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by zapf.ntg.nl (Postfix) with ESMTPS id 450254332 for ; Wed, 19 Apr 2023 14:23:49 +0200 (CEST) Received: from list by ciao.gmane.io with local (Exim 4.92) (envelope-from ) id 1pp6qi-000AGb-F8 for ntg-context@ntg.nl; Wed, 19 Apr 2023 14:23:48 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: ntg-context@ntg.nl Date: Wed, 19 Apr 2023 08:23:39 -0400 Message-ID: References: Mime-Version: 1.0 Content-Disposition: inline In-Reply-To: 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: Carlos via ntg-context Reply-To: mailing list for ConTeXt users Cc: 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 01:24:08PM -0300, Jim via ntg-context wrote: > 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. Thnt's more than obvious, asshole. Or passive-aggressive asshole. You're posting it on the mailing list for the users, devs, and end-users alike to test it out as required and comment or say whatever they want. > > > 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. > Neither one. > 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. I agree. :) > > > \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 > ___________________________________________________________________________________ > -- To err is human -- to blame it on a computer is even more so. ___________________________________________________________________________________ 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 ___________________________________________________________________________________