Indentation after a title using `alternative=text`

I am using ConTeXt 2018.04.04 from TeXLive 2018.
When I use the alternative=text option in setuphead, the second paragraph after the title is not indented.
I cannot find in the manual how to get it indented.

Here is a minimal example:

setupindenting[yes,big]

setuphead[section][alternative=text]

starttext

section{Introduction}

input knuth

stoptext

When I add the following option, it does not change anything:

setuphead[section][alternative=text,indentnext=yes]

In the example, I want the paragraph beginning with

The separation of any...

to be indented, but it isn't.

enter image description here

edited Feb 27 at 10:18

Bernard

172k776204

asked Feb 27 at 9:24

Jan. N.

182

Welcome to TeX.SE!

– Kurt
Feb 27 at 9:25

add a comment |

Here is a minimal example:

setupindenting[yes,big]

setuphead[section][alternative=text]

starttext

section{Introduction}

input knuth

stoptext

When I add the following option, it does not change anything:

setuphead[section][alternative=text,indentnext=yes]

In the example, I want the paragraph beginning with

The separation of any...

to be indented, but it isn't.

enter image description here

edited Feb 27 at 10:18

Bernard

172k776204

asked Feb 27 at 9:24

Jan. N.

182

Welcome to TeX.SE!

– Kurt
Feb 27 at 9:25

add a comment |

Here is a minimal example:

setupindenting[yes,big]

setuphead[section][alternative=text]

starttext

section{Introduction}

input knuth

stoptext

When I add the following option, it does not change anything:

setuphead[section][alternative=text,indentnext=yes]

In the example, I want the paragraph beginning with

The separation of any...

to be indented, but it isn't.

enter image description here

edited Feb 27 at 10:18

Bernard

172k776204

asked Feb 27 at 9:24

Jan. N.

182

Here is a minimal example:

setupindenting[yes,big]

setuphead[section][alternative=text]

starttext

section{Introduction}

input knuth

stoptext

When I add the following option, it does not change anything:

setuphead[section][alternative=text,indentnext=yes]

In the example, I want the paragraph beginning with

The separation of any...

to be indented, but it isn't.

enter image description here

indentation context

edited Feb 27 at 10:18

Bernard

172k776204

asked Feb 27 at 9:24

Jan. N.

182

edited Feb 27 at 10:18

Bernard

172k776204

asked Feb 27 at 9:24

Jan. N.

182

edited Feb 27 at 10:18

Bernard

172k776204

edited Feb 27 at 10:18

Bernard

172k776204

edited Feb 27 at 10:18

Bernard

172k776204

asked Feb 27 at 9:24

Jan. N.

182

asked Feb 27 at 9:24

Jan. N.

182

asked Feb 27 at 9:24

Jan. N.

182

Welcome to TeX.SE!

– Kurt
Feb 27 at 9:25

add a comment |

Welcome to TeX.SE!

– Kurt
Feb 27 at 9:25

Welcome to TeX.SE!

– Kurt
Feb 27 at 9:25

add a comment |

1 Answer
1

active

oldest

votes

The problem also appears in the latest beta. Apparently the problem was introduced when fixing another bug, because commenting the line

noindentation % recently added, was a bug

in strc_rendering_stop_placement fixes the problem. This has been reported on the mailing list: https://mailman.ntg.nl/pipermail/ntg-context/2019/094251.html

unprotect



defstrc_rendering_stop_placement

  {n_strc_rendering_hang_lineszerocount

   ifconditionalheadisdisplay

     strc_rendering_initialize_line_hang

     % kind of special, we want to snap heads also according to local specs local

     setboxb_strc_rendering_headhbox

       {hskipdimexprd_strc_rendering_local_leftoffset+headparameterc!marginrelax

        boxb_strc_rendering_head

        getheadsyncs % a latelua why not in the box

        }%

     ifgridsnapping

       applygridmethod

         {headparameterc!grid}%

         {ifconditionalheadisdisplay

            strc_rendering_initialize_style_and_color_displayc!textstylec!textcolor

          fi}%

         {boxb_strc_rendering_head}

     else

       boxb_strc_rendering_head

     fi

     flushnotes % new, not really needed

     endgraf

     ifvmode

       ifnumn_strc_rendering_hang_lines>zerocount

         dorecursen_strc_rendering_hang_lines{nointerlineskipdosomebreaknobreakstrutendgraf}% to be checked

       fi

       nointerlineskip

       dosomebreaknobreak

     fi

%      getheadsyncs % a latelua why not in the box

   else

     % somehow this goes ok even when we push in the margin probably because we gobble pars

     % in the process of collecting index entries etc

     strut

     flushnotes % new, here since we're in par mode

     unhboxb_strc_rendering_head

     getheadsyncs % a latelua

     ifconditionalheadissomewhere

       strc_sectioning_stay_on_this_line % test case: alternative=margintext and startparagraph ..

     else

      %hskipheadnumberdistances!plusheadnumberdistances!minus.25dimexprheadnumberdistancerelax

       hskipheadtextdistancerelax

       strc_sectioning_inject_continuous_signal

     fi

   fi

   ifconditionalheadisdisplay

     ifvmode

       ifgridsnapping % important, font related depth, see comment

         prevdepthstrutdp

       else

         prevdepthd_strc_rendering_local_depth

       fi

     fi

   fi

   synctexpopline

   egroup

   egroup

   ifconditionalheadisdisplay

     useindentnextparameterheadparameter

   else

     ignoreparskip

     % noindentation % recently added, was a bug

   fi}



protect



setupindenting[yes,big]

setuphead[section][alternative=text,indentnext=yes]

starttext

section{Introduction}

input knuth

stoptext

enter image description here

edited Feb 27 at 20:51

answered Feb 27 at 10:25

Henri Menke

76.1k8167281

This kind of redefinition looks like a use case for some xpatch or etoolbox type of patching functionality, is anything like that available or planned for ConTeXt?

– Marijn
Feb 27 at 14:49

1

@Marijn No, there is no such thing for ConTeXt, because in contrast to most LaTeX packages, ConTeXt is actually actively being developed which means that bugs are fixed as soon as they are reported, making all the weird patching business superfluous.

– Henri Menke
Feb 27 at 20:45

Case in point: mailman.ntg.nl/pipermail/dev-context/2019/003551.html

– Aditya
Feb 28 at 11:56

add a comment |

Your Answer

StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "85"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});

}
});

draft saved

draft discarded

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2ftex.stackexchange.com%2fquestions%2f476901%2findentation-after-a-title-using-alternative-text%23new-answer', 'question_page');
}
);

Post as a guest

Name

Required, but never shown

1 Answer
1

active

oldest

votes

1 Answer
1

active

oldest

votes

The problem also appears in the latest beta. Apparently the problem was introduced when fixing another bug, because commenting the line

noindentation % recently added, was a bug

in strc_rendering_stop_placement fixes the problem. This has been reported on the mailing list: https://mailman.ntg.nl/pipermail/ntg-context/2019/094251.html

unprotect



defstrc_rendering_stop_placement

  {n_strc_rendering_hang_lineszerocount

   ifconditionalheadisdisplay

     strc_rendering_initialize_line_hang

     % kind of special, we want to snap heads also according to local specs local

     setboxb_strc_rendering_headhbox

       {hskipdimexprd_strc_rendering_local_leftoffset+headparameterc!marginrelax

        boxb_strc_rendering_head

        getheadsyncs % a latelua why not in the box

        }%

     ifgridsnapping

       applygridmethod

         {headparameterc!grid}%

         {ifconditionalheadisdisplay

            strc_rendering_initialize_style_and_color_displayc!textstylec!textcolor

          fi}%

         {boxb_strc_rendering_head}

     else

       boxb_strc_rendering_head

     fi

     flushnotes % new, not really needed

     endgraf

     ifvmode

       ifnumn_strc_rendering_hang_lines>zerocount

         dorecursen_strc_rendering_hang_lines{nointerlineskipdosomebreaknobreakstrutendgraf}% to be checked

       fi

       nointerlineskip

       dosomebreaknobreak

     fi

%      getheadsyncs % a latelua why not in the box

   else

     % somehow this goes ok even when we push in the margin probably because we gobble pars

     % in the process of collecting index entries etc

     strut

     flushnotes % new, here since we're in par mode

     unhboxb_strc_rendering_head

     getheadsyncs % a latelua

     ifconditionalheadissomewhere

       strc_sectioning_stay_on_this_line % test case: alternative=margintext and startparagraph ..

     else

      %hskipheadnumberdistances!plusheadnumberdistances!minus.25dimexprheadnumberdistancerelax

       hskipheadtextdistancerelax

       strc_sectioning_inject_continuous_signal

     fi

   fi

   ifconditionalheadisdisplay

     ifvmode

       ifgridsnapping % important, font related depth, see comment

         prevdepthstrutdp

       else

         prevdepthd_strc_rendering_local_depth

       fi

     fi

   fi

   synctexpopline

   egroup

   egroup

   ifconditionalheadisdisplay

     useindentnextparameterheadparameter

   else

     ignoreparskip

     % noindentation % recently added, was a bug

   fi}



protect



setupindenting[yes,big]

setuphead[section][alternative=text,indentnext=yes]

starttext

section{Introduction}

input knuth

stoptext

enter image description here

edited Feb 27 at 20:51

answered Feb 27 at 10:25

Henri Menke

76.1k8167281

This kind of redefinition looks like a use case for some xpatch or etoolbox type of patching functionality, is anything like that available or planned for ConTeXt?

– Marijn
Feb 27 at 14:49

1

@Marijn No, there is no such thing for ConTeXt, because in contrast to most LaTeX packages, ConTeXt is actually actively being developed which means that bugs are fixed as soon as they are reported, making all the weird patching business superfluous.

– Henri Menke
Feb 27 at 20:45

Case in point: mailman.ntg.nl/pipermail/dev-context/2019/003551.html

– Aditya
Feb 28 at 11:56

add a comment |

The problem also appears in the latest beta. Apparently the problem was introduced when fixing another bug, because commenting the line

noindentation % recently added, was a bug

in strc_rendering_stop_placement fixes the problem. This has been reported on the mailing list: https://mailman.ntg.nl/pipermail/ntg-context/2019/094251.html

unprotect



defstrc_rendering_stop_placement

  {n_strc_rendering_hang_lineszerocount

   ifconditionalheadisdisplay

     strc_rendering_initialize_line_hang

     % kind of special, we want to snap heads also according to local specs local

     setboxb_strc_rendering_headhbox

       {hskipdimexprd_strc_rendering_local_leftoffset+headparameterc!marginrelax

        boxb_strc_rendering_head

        getheadsyncs % a latelua why not in the box

        }%

     ifgridsnapping

       applygridmethod

         {headparameterc!grid}%

         {ifconditionalheadisdisplay

            strc_rendering_initialize_style_and_color_displayc!textstylec!textcolor

          fi}%

         {boxb_strc_rendering_head}

     else

       boxb_strc_rendering_head

     fi

     flushnotes % new, not really needed

     endgraf

     ifvmode

       ifnumn_strc_rendering_hang_lines>zerocount

         dorecursen_strc_rendering_hang_lines{nointerlineskipdosomebreaknobreakstrutendgraf}% to be checked

       fi

       nointerlineskip

       dosomebreaknobreak

     fi

%      getheadsyncs % a latelua why not in the box

   else

     % somehow this goes ok even when we push in the margin probably because we gobble pars

     % in the process of collecting index entries etc

     strut

     flushnotes % new, here since we're in par mode

     unhboxb_strc_rendering_head

     getheadsyncs % a latelua

     ifconditionalheadissomewhere

       strc_sectioning_stay_on_this_line % test case: alternative=margintext and startparagraph ..

     else

      %hskipheadnumberdistances!plusheadnumberdistances!minus.25dimexprheadnumberdistancerelax

       hskipheadtextdistancerelax

       strc_sectioning_inject_continuous_signal

     fi

   fi

   ifconditionalheadisdisplay

     ifvmode

       ifgridsnapping % important, font related depth, see comment

         prevdepthstrutdp

       else

         prevdepthd_strc_rendering_local_depth

       fi

     fi

   fi

   synctexpopline

   egroup

   egroup

   ifconditionalheadisdisplay

     useindentnextparameterheadparameter

   else

     ignoreparskip

     % noindentation % recently added, was a bug

   fi}



protect



setupindenting[yes,big]

setuphead[section][alternative=text,indentnext=yes]

starttext

section{Introduction}

input knuth

stoptext

enter image description here

edited Feb 27 at 20:51

answered Feb 27 at 10:25

Henri Menke

76.1k8167281

This kind of redefinition looks like a use case for some xpatch or etoolbox type of patching functionality, is anything like that available or planned for ConTeXt?

– Marijn
Feb 27 at 14:49

1

@Marijn No, there is no such thing for ConTeXt, because in contrast to most LaTeX packages, ConTeXt is actually actively being developed which means that bugs are fixed as soon as they are reported, making all the weird patching business superfluous.

– Henri Menke
Feb 27 at 20:45

Case in point: mailman.ntg.nl/pipermail/dev-context/2019/003551.html

– Aditya
Feb 28 at 11:56

add a comment |

The problem also appears in the latest beta. Apparently the problem was introduced when fixing another bug, because commenting the line

noindentation % recently added, was a bug

in strc_rendering_stop_placement fixes the problem. This has been reported on the mailing list: https://mailman.ntg.nl/pipermail/ntg-context/2019/094251.html

unprotect



defstrc_rendering_stop_placement

  {n_strc_rendering_hang_lineszerocount

   ifconditionalheadisdisplay

     strc_rendering_initialize_line_hang

     % kind of special, we want to snap heads also according to local specs local

     setboxb_strc_rendering_headhbox

       {hskipdimexprd_strc_rendering_local_leftoffset+headparameterc!marginrelax

        boxb_strc_rendering_head

        getheadsyncs % a latelua why not in the box

        }%

     ifgridsnapping

       applygridmethod

         {headparameterc!grid}%

         {ifconditionalheadisdisplay

            strc_rendering_initialize_style_and_color_displayc!textstylec!textcolor

          fi}%

         {boxb_strc_rendering_head}

     else

       boxb_strc_rendering_head

     fi

     flushnotes % new, not really needed

     endgraf

     ifvmode

       ifnumn_strc_rendering_hang_lines>zerocount

         dorecursen_strc_rendering_hang_lines{nointerlineskipdosomebreaknobreakstrutendgraf}% to be checked

       fi

       nointerlineskip

       dosomebreaknobreak

     fi

%      getheadsyncs % a latelua why not in the box

   else

     % somehow this goes ok even when we push in the margin probably because we gobble pars

     % in the process of collecting index entries etc

     strut

     flushnotes % new, here since we're in par mode

     unhboxb_strc_rendering_head

     getheadsyncs % a latelua

     ifconditionalheadissomewhere

       strc_sectioning_stay_on_this_line % test case: alternative=margintext and startparagraph ..

     else

      %hskipheadnumberdistances!plusheadnumberdistances!minus.25dimexprheadnumberdistancerelax

       hskipheadtextdistancerelax

       strc_sectioning_inject_continuous_signal

     fi

   fi

   ifconditionalheadisdisplay

     ifvmode

       ifgridsnapping % important, font related depth, see comment

         prevdepthstrutdp

       else

         prevdepthd_strc_rendering_local_depth

       fi

     fi

   fi

   synctexpopline

   egroup

   egroup

   ifconditionalheadisdisplay

     useindentnextparameterheadparameter

   else

     ignoreparskip

     % noindentation % recently added, was a bug

   fi}



protect



setupindenting[yes,big]

setuphead[section][alternative=text,indentnext=yes]

starttext

section{Introduction}

input knuth

stoptext

enter image description here

edited Feb 27 at 20:51

answered Feb 27 at 10:25

Henri Menke

76.1k8167281

The problem also appears in the latest beta. Apparently the problem was introduced when fixing another bug, because commenting the line

noindentation % recently added, was a bug

in strc_rendering_stop_placement fixes the problem. This has been reported on the mailing list: https://mailman.ntg.nl/pipermail/ntg-context/2019/094251.html

unprotect



defstrc_rendering_stop_placement

  {n_strc_rendering_hang_lineszerocount

   ifconditionalheadisdisplay

     strc_rendering_initialize_line_hang

     % kind of special, we want to snap heads also according to local specs local

     setboxb_strc_rendering_headhbox

       {hskipdimexprd_strc_rendering_local_leftoffset+headparameterc!marginrelax

        boxb_strc_rendering_head

        getheadsyncs % a latelua why not in the box

        }%

     ifgridsnapping

       applygridmethod

         {headparameterc!grid}%

         {ifconditionalheadisdisplay

            strc_rendering_initialize_style_and_color_displayc!textstylec!textcolor

          fi}%

         {boxb_strc_rendering_head}

     else

       boxb_strc_rendering_head

     fi

     flushnotes % new, not really needed

     endgraf

     ifvmode

       ifnumn_strc_rendering_hang_lines>zerocount

         dorecursen_strc_rendering_hang_lines{nointerlineskipdosomebreaknobreakstrutendgraf}% to be checked

       fi

       nointerlineskip

       dosomebreaknobreak

     fi

%      getheadsyncs % a latelua why not in the box

   else

     % somehow this goes ok even when we push in the margin probably because we gobble pars

     % in the process of collecting index entries etc

     strut

     flushnotes % new, here since we're in par mode

     unhboxb_strc_rendering_head

     getheadsyncs % a latelua

     ifconditionalheadissomewhere

       strc_sectioning_stay_on_this_line % test case: alternative=margintext and startparagraph ..

     else

      %hskipheadnumberdistances!plusheadnumberdistances!minus.25dimexprheadnumberdistancerelax

       hskipheadtextdistancerelax

       strc_sectioning_inject_continuous_signal

     fi

   fi

   ifconditionalheadisdisplay

     ifvmode

       ifgridsnapping % important, font related depth, see comment

         prevdepthstrutdp

       else

         prevdepthd_strc_rendering_local_depth

       fi

     fi

   fi

   synctexpopline

   egroup

   egroup

   ifconditionalheadisdisplay

     useindentnextparameterheadparameter

   else

     ignoreparskip

     % noindentation % recently added, was a bug

   fi}



protect



setupindenting[yes,big]

setuphead[section][alternative=text,indentnext=yes]

starttext

section{Introduction}

input knuth

stoptext

enter image description here

edited Feb 27 at 20:51

answered Feb 27 at 10:25

Henri Menke

76.1k8167281

edited Feb 27 at 20:51

answered Feb 27 at 10:25

Henri Menke

76.1k8167281

answered Feb 27 at 10:25

Henri Menke

76.1k8167281

answered Feb 27 at 10:25

Henri Menke

76.1k8167281

This kind of redefinition looks like a use case for some xpatch or etoolbox type of patching functionality, is anything like that available or planned for ConTeXt?

– Marijn
Feb 27 at 14:49

1

@Marijn No, there is no such thing for ConTeXt, because in contrast to most LaTeX packages, ConTeXt is actually actively being developed which means that bugs are fixed as soon as they are reported, making all the weird patching business superfluous.

– Henri Menke
Feb 27 at 20:45

Case in point: mailman.ntg.nl/pipermail/dev-context/2019/003551.html

– Aditya
Feb 28 at 11:56

add a comment |

This kind of redefinition looks like a use case for some xpatch or etoolbox type of patching functionality, is anything like that available or planned for ConTeXt?

– Marijn
Feb 27 at 14:49

1

@Marijn No, there is no such thing for ConTeXt, because in contrast to most LaTeX packages, ConTeXt is actually actively being developed which means that bugs are fixed as soon as they are reported, making all the weird patching business superfluous.

– Henri Menke
Feb 27 at 20:45

Case in point: mailman.ntg.nl/pipermail/dev-context/2019/003551.html

– Aditya
Feb 28 at 11:56

This kind of redefinition looks like a use case for some xpatch or etoolbox type of patching functionality, is anything like that available or planned for ConTeXt?

– Marijn
Feb 27 at 14:49

@Marijn No, there is no such thing for ConTeXt, because in contrast to most LaTeX packages, ConTeXt is actually actively being developed which means that bugs are fixed as soon as they are reported, making all the weird patching business superfluous.

– Henri Menke
Feb 27 at 20:45

Case in point: mailman.ntg.nl/pipermail/dev-context/2019/003551.html

– Aditya
Feb 28 at 11:56

add a comment |

draft saved

draft discarded

Thanks for contributing an answer to TeX - LaTeX Stack Exchange!

Please be sure to answer the question. Provide details and share your research!

But avoid …

Asking for help, clarification, or responding to other answers.

Making statements based on opinion; back them up with references or personal experience.

To learn more, see our tips on writing great answers.

draft saved

draft discarded

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

Post as a guest

Name

Required, but never shown

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

Name

Required, but never shown

Name

Required, but never shown

This page is only for reference, If you need detailed information, please check here

搜尋此網誌

Cfrgtkky