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 14742 invoked from network); 16 Apr 2023 17:26:20 -0000 Received: from zapf.ntg.nl (5.39.185.232) by inbox.vuxu.org with ESMTPUTF8; 16 Apr 2023 17:26:20 -0000 Received: from localhost (localhost [127.0.0.1]) by zapf.ntg.nl (Postfix) with ESMTP id D546A1C03A2; Sun, 16 Apr 2023 19:23:45 +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 o0hmWKWrtYyn; Sun, 16 Apr 2023 19:23:43 +0200 (CEST) Received: from zapf.ntg.nl (localhost [127.0.0.1]) by zapf.ntg.nl (Postfix) with ESMTP id 6AEF21C02FC; Sun, 16 Apr 2023 19:23:43 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by zapf.ntg.nl (Postfix) with ESMTP id 563CF1C14D4 for ; Sun, 16 Apr 2023 19:23:41 +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 Y9XTn9I98SDp for ; Sun, 16 Apr 2023 19:23:40 +0200 (CEST) Received-SPF: Pass (mailfrom) identity=mailfrom; client-ip=67.215.8.18; helo=se2.web-dns1.com; envelope-from=zlists+context@jdvb.ca; receiver= Received: from se2.web-dns1.com (se2.web-dns1.com [67.215.8.18]) (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 23C47115 for ; Sun, 16 Apr 2023 19:23:39 +0200 (CEST) Received: from mailpro1.whc.ca ([51.79.16.13]) by se1.web-dns1.com with esmtps (TLSv1.3:TLS_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1po666-00044o-Op for ntg-context@ntg.nl; Sun, 16 Apr 2023 13:23:38 -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:To:From:Date:Sender:Reply-To:Cc: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=fWF26eAu0qWLKjntpcYVyqNoFu9X7KPvqd8flQLH/iA=; b=PXy02ogtaCG6uy1B7YMpGhEKCp f/lMX/KyHjZzAdF6idIZ4fUIf2tWGW0BQ3nNPzoCfIyybtT0kEJxSTyRwxF8gEE3hR0a33AXFutQB v/hMdqJy3ynxAT74Jnr4rvr6CmWW2nzprFj45RnAc+UCysZfgDhkb8x4jjdopjKsVhAR796mqMWy0 0kfDW08HkD3Osr34Yma2LkgzOvliKkMWRS6C9HETIItYOMvglyc2qgwSyQyCeRGm5FO9Moacd1qB8 YbioP537d6eWmPvPObmdLw5tAZMAKF7auFrzK2wNZD0wramXdbAOtX+LLVr4sbNCSdjGhTr2TusPI H2SBrpKA==; Received: from [142.177.159.153] (port=58360 helo=x360) by mailpro1.whc.ca with esmtpsa (TLS1.3) tls TLS_AES_256_GCM_SHA384 (Exim 4.95) (envelope-from ) id 1po665-00B4Dg-Du for ntg-context@ntg.nl; Sun, 16 Apr 2023 13:23:29 -0400 Received: by x360 (Postfix, from userid 1000) id 0373E1E0927; Sun, 16 Apr 2023 14:23:29 -0300 (ADT) Date: Sun, 16 Apr 2023 14:23:28 -0300 To: mailing list for ConTeXt users Message-ID: References: <58819sro-924s-s86n-44o2-2on15s558sq4@hzvpu.rqh> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <58819sro-924s-s86n-44o2-2on15s558sq4@hzvpu.rqh> 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: ham X-SpamExperts-Outgoing-Evidence: Combined (0.28) X-Recommended-Action: accept X-Filter-ID: Pt3MvcO5N4iKaDQ5O6lkdGlMVN6RH8bjRMzItlySaT9gPrOmhM5zKaPbEfPaI/8APUtbdvnXkggZ 3YnVId/Y5jcf0yeVQAvfjHznO7+bT5x+OkQ6e4TPVgvpcS1fNw4ZIpdOJ9Sgfu6rKL8kf6cp2f/O dylwSmmqX1x5Blkdv/vilbHtbFYVmmyNP/jzd7CCzPgfBgZM0FjuQW6Y55dUifPx2oH3KEE2SmzU yTVOi831ySm8nW3P8R2RmEa7QwTRNI+Mp5iAKuFzLuv07zCdk07dkvTsh8os0vjb4olpFiZo7WR4 Omwj0a5PnE6t4RB3zO11BRKqT8B4uLrn7iz8uvLBMzbIQcSG8L0jOzL80Q1MxDcqDeEvahfPkDkT lH91LgaQnmF8H6pa6B8MTK1ligAJ9G0GMvMSOAhk0taEj8zIfd9jilKJ6DuubUWmwQ3j9WVr3gC4 GEqSrWRyxMDuUa6qvRqKQ68kD4O7N4Xhv7KbcCEbjbqaWJiQIcFmk6Cipzi4JDWEiJuf4ysgNjLZ YBSQmkcr/+WWHnohyAuskHzZarYidkZBdHCCngOK96nKw3qNhf+deQvJCdEKHScH65hRrOZZqMOo Ds1PwmznbNIBIkUL/j1Y48GvmeURQjjE2gnHTTePLKNOGxtNqX0yvUSEGEQh6rROzTDrGKyiy4uB +5C5rwEXEcmVmMI1+0AqMVCdBIz+JCn83rTtkUWIdCrJMJqLQ8QKPxsoSCxG7xgs6Os7DAYjeQq7 TkmcOW/uOaPQG9ZYBdOUNZUlb9fAsbLVFcLo2eSwzZQo8J+LvNg9ErYG3wF2yynw/Tn0o99AjXf4 xCL8iat61P4/YzYUyVz1pRXWhjh9fdbl44I0Df1prNsWJM98VBjETtrsB33uxw0TdiKzKzTokTXv Ud91kwTLb0Ae2tJnW9h23ZvT+c4pPIYZ8jmsTzUI+DlGF95mC6gzAu46dEsRzJ3+a1bn3pn3qNJh gDW8pMjF4V6zFxd+vwaYt0T28J35bZnWIbDObUK5la/oRXAFcTFMR6oSISjY4IH8/oC+RjBWlIqC Uy8= 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 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 12:35 (-0400), Aditya Mahajan via ntg-context wrote: > On Sat, 15 Apr 2023, 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? > Works in mkiv but appears to be a bug in lmtx. I haven't debugged what is > going wrong. > Aditya (who wrote bulk of that wiki page) Thanks very much for getting back. And for your wiki contributions. Jim ___________________________________________________________________________________ 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 ___________________________________________________________________________________