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 932 invoked from network); 18 Apr 2023 13:48:53 -0000 Received: from zapf.ntg.nl (5.39.185.232) by inbox.vuxu.org with ESMTPUTF8; 18 Apr 2023 13:48:53 -0000 Received: from localhost (localhost [127.0.0.1]) by zapf.ntg.nl (Postfix) with ESMTP id 35E55EB; Tue, 18 Apr 2023 15:48:34 +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 8y99sMIEmic9; Tue, 18 Apr 2023 15:48:32 +0200 (CEST) Received: from zapf.ntg.nl (localhost [127.0.0.1]) by zapf.ntg.nl (Postfix) with ESMTP id 1CF66618; Tue, 18 Apr 2023 15:48:32 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by zapf.ntg.nl (Postfix) with ESMTP id 0F94E618 for ; Tue, 18 Apr 2023 15:48:30 +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 oD2gG4kyYXjO for ; Tue, 18 Apr 2023 15:48:29 +0200 (CEST) Received-SPF: Softfail (mailfrom) identity=mailfrom; client-ip=132.206.73.2; helo=orford.cim.mcgill.ca; envelope-from=adityam@umich.edu; receiver= Received: from orford.cim.mcgill.ca (smtp.cim.mcgill.ca [132.206.73.2]) (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 CDC73EB for ; Tue, 18 Apr 2023 15:48:27 +0200 (CEST) Received: from adi-thinkpad (unknown [108.175.235.192]) (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) (Authenticated sender: adityam) by orford.cim.mcgill.ca (Postfix) with ESMTPSA id 5394D9BC9F for ; Tue, 18 Apr 2023 09:48:26 -0400 (EDT) Date: Tue, 18 Apr 2023 09:48:22 -0400 (EDT) To: Hans Hagen via ntg-context In-Reply-To: <18432049-ceec-d0f7-0d32-0522bbf618b3@freedom.nl> Message-ID: References: <58819sro-924s-s86n-44o2-2on15s558sq4@hzvpu.rqh> <18432049-ceec-d0f7-0d32-0522bbf618b3@freedom.nl> MIME-Version: 1.0 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: Aditya Mahajan via ntg-context Reply-To: mailing list for ConTeXt users Cc: Aditya Mahajan Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: ntg-context-bounces@ntg.nl Sender: "ntg-context" On Mon, 17 Apr 2023, Hans Hagen via ntg-context wrote: > On 4/17/2023 7:06 AM, Aditya Mahajan via ntg-context wrote: > > On Sun, 16 Apr 2023, Aditya Mahajan via ntg-context wrote: > > > >> On Sat, 15 Apr 2023, Jim via ntg-context wrote: > >> > >>> %------------------------------------------------------------------------ > >>> > >>> \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. > >>> > >>> %------------------------------------------------------------------------ > >> Works in mkiv but appears to be a bug in lmtx. I haven't debugged what is > >> going wrong. > > > > `indentnext=auto` doesn't appear to work for any environment. > can you test with this patch This works on with the 3-4 test examples that I had but ... > \permanent\protected\protected\def\spac_indentation_check_next_indentation ^^^^^^^^^^^^^^^^^^^^^ Is that a typo (double \protected)? I tested with a single \protected and that also works. Aditya ___________________________________________________________________________________ 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 ___________________________________________________________________________________