From: Hans Hagen via ntg-context <ntg-context@ntg.nl>
To: ntg-context@ntg.nl
Cc: Hans Hagen <j.hagen@freedom.nl>
Subject: Re: [NTG-context] \setupitemize[indentnext=auto] broken?
Date: Tue, 18 Apr 2023 16:56:58 +0200 [thread overview]
Message-ID: <bbfc541b-ba77-b8ab-53f2-1bd8daa9c3e5@freedom.nl> (raw)
In-Reply-To: <r8p5qr32-865q-qrp9-961r-5422s1s8s719@hzvpu.rqh>
On 4/18/2023 3:48 PM, Aditya Mahajan via ntg-context wrote:
> 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.
it's a typo .. maybe i should add (for completeness)
\protected\unprotected\protected
(\permanent only kicks in when you are on overload protection mode,
which I'm always in here)
Hans
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
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
___________________________________________________________________________________
prev parent reply other threads:[~2023-04-18 14:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-15 17:27 Jim via ntg-context
2023-04-15 17:49 ` [NTG-context] https://wiki.contextgarden.net/Enumerations problem Jim via ntg-context
2023-04-16 12:28 ` [NTG-context] \setupitemize[indentnext=auto] broken? Carlos via ntg-context
2023-04-16 16:24 ` Jim via ntg-context
2023-04-19 12:23 ` Carlos via ntg-context
2023-04-16 16:35 ` Aditya Mahajan via ntg-context
2023-04-16 17:23 ` Jim via ntg-context
2023-04-17 5:06 ` Aditya Mahajan via ntg-context
2023-04-17 17:04 ` Hans Hagen via ntg-context
2023-04-18 13:48 ` Aditya Mahajan via ntg-context
2023-04-18 14:56 ` Hans Hagen via ntg-context [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bbfc541b-ba77-b8ab-53f2-1bd8daa9c3e5@freedom.nl \
--to=ntg-context@ntg.nl \
--cc=j.hagen@freedom.nl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).