Section title with runin and KOMA class?Incompatibilities between KOMA-Script and titlesecFormatting Section...
If the Captain's screens are out, does he switch seats with the co-pilot?
Why is this plane circling around the Lucknow airport every day?
What is the likely impact of grounding an entire aircraft series?
Virginia employer terminated employee and wants signing bonus returned
Replacing Windows 7 security updates with anti-virus?
Is having access to past exams cheating and, if yes, could it be proven just by a good grade?
What are some noteworthy "mic-drop" moments in math?
What to do when during a meeting client people start to fight (even physically) with each others?
Finding algorithms of QGIS commands?
Am I not good enough for you?
Are the terms "stab" and "staccato" synonyms?
Single word request: Harming the benefactor
Is "history" a male-biased word ("his+story")?
Are babies of evil humanoid species inherently evil?
Does "variables should live in the smallest scope as possible" include the case "variables should not exist if possible"?
Space in array system equations
"One can do his homework in the library"
Why would one plane in this picture not have gear down yet?
How do I deal with a powergamer in a game full of beginners in a school club?
Unreachable code, but reachable with exception
Built-In Shelves/Bookcases - IKEA vs Built
Does splitting a potentially monolithic application into several smaller ones help prevent bugs?
Best approach to update all entries in a list that is paginated?
Is it possible to have an Abelian group under two different binary operations but the binary operations are not distributive?
Section title with runin and KOMA class?
Incompatibilities between KOMA-Script and titlesecFormatting Section in KOMA-ScriptAdjusting spacing around section/subsection titles with koma-scriptSpacing after KOMA section in multicol environmentset font weight in titles in a scrartclCollapsing section ranges in titlesec page headersRedeclaresectioncommand does not work for section - Koma Script Report - LyxUsing KOMA-script article with org-modeKOMA-Script thanks command and biblatex-chicagoProblems with fancy style and KOMA-ScriptHeader with Section short title and Chapter short title using KOMA-script
I would like to have section titles with runin so that there is no newline after the section title. This can be done with
documentclass{article}
usepackage{titlesec}
title{section}[runin]{large}{thesection}{1em}{}[]
begin{document}
section{First section}
This text follows on the same line as "First section"
end{document}
However, I am using the KOMA scrartcl
class and use of the titlesec
package is discouraged (see Incompatibilities between KOMA-Script and titlesec).
I have searched through the KOMA-Script documentation, but cannot find anything like the runin
option in titlesec
. How can I achieve this functionality while using a KOMA-Script class?
koma-script titlesec
add a comment |
I would like to have section titles with runin so that there is no newline after the section title. This can be done with
documentclass{article}
usepackage{titlesec}
title{section}[runin]{large}{thesection}{1em}{}[]
begin{document}
section{First section}
This text follows on the same line as "First section"
end{document}
However, I am using the KOMA scrartcl
class and use of the titlesec
package is discouraged (see Incompatibilities between KOMA-Script and titlesec).
I have searched through the KOMA-Script documentation, but cannot find anything like the runin
option in titlesec
. How can I achieve this functionality while using a KOMA-Script class?
koma-script titlesec
add a comment |
I would like to have section titles with runin so that there is no newline after the section title. This can be done with
documentclass{article}
usepackage{titlesec}
title{section}[runin]{large}{thesection}{1em}{}[]
begin{document}
section{First section}
This text follows on the same line as "First section"
end{document}
However, I am using the KOMA scrartcl
class and use of the titlesec
package is discouraged (see Incompatibilities between KOMA-Script and titlesec).
I have searched through the KOMA-Script documentation, but cannot find anything like the runin
option in titlesec
. How can I achieve this functionality while using a KOMA-Script class?
koma-script titlesec
I would like to have section titles with runin so that there is no newline after the section title. This can be done with
documentclass{article}
usepackage{titlesec}
title{section}[runin]{large}{thesection}{1em}{}[]
begin{document}
section{First section}
This text follows on the same line as "First section"
end{document}
However, I am using the KOMA scrartcl
class and use of the titlesec
package is discouraged (see Incompatibilities between KOMA-Script and titlesec).
I have searched through the KOMA-Script documentation, but cannot find anything like the runin
option in titlesec
. How can I achieve this functionality while using a KOMA-Script class?
koma-script titlesec
koma-script titlesec
edited Apr 13 '17 at 12:35
Community♦
1
1
asked Aug 31 '14 at 20:18
EP_GuyEP_Guy
385
385
add a comment |
add a comment |
3 Answers
3
active
oldest
votes
1 Older version of KOMAScript
You have to redefine the definition of section
, subsection
etc. You use a negativ values to set runin heading, like in the standard article-class. I have copied the definition of headings from scrartcl
sometimes in the past. Be aware that this solution may break if scrartcl
is changed.
If you take a look at page 351 in the English manual for Komascript, you will see that there are several commands for changing the space above and below chapter
and part
. Hopefully, we will see a similar command for section
and her sisters.
Here, I have redefined both section and subsection to be runin-header.
documentclass{scrartcl}
makeatletter
renewcommandsection{@startsection{section}{1}{z@}%
{-1.5ex}%
{-1em}%{2.3ex @plus.2ex}% < - negative value here negative value here,
% the values behind % are the original.
% no use for rubber values, use a fix value to set the
% distance to between heading and the text
{ifnum scr@compatibility>@nameuse{scr@v@2.96}relax
setlength{parfillskip}{z@ plus 1fil}fi
raggedsectionsectfontnobreaksize@section}%
}
renewcommandsubsection{@startsection{subsection}{1}{z@}%
{-1.5ex @plus -1ex @minus -.2ex}%
{-1em}%{2.3ex @plus.2ex}% <- negative value here, the values behind % are the original
{ifnum scr@compatibility>@nameuse{scr@v@2.96}relax
setlength{parfillskip}{z@ plus 1fil}fi
raggedsectionnormalfontsectfontnobreaksize@section}%
}
makeatother
begin{document}
section{First section}
This text follows on the same line as "First section"
end{document}
You use the ordinary addtokomafont
etc. to change the font, colour etc. ANd of course, you have to fiddle around with the figures to get the space above you prefer.
2. Never versions of KOMAScript
I refer to Johannes_B’s answer below.
For the sake of completeness, I will bring your attention to page 363 ff. in the English KOMAScript manual as of 2015-10-03. The author has (from version 3.16?) added the possibility to interface to section{}
and her sisters by the four commands:
DeclareSectionCommand[attributes]{name}
DeclareNewSectionCommand[attributes]{name}
RedeclareSectionCommand[attributes]{name}
ProvideSectionCommand[attributes]{name}
You may use this commands to define totally new sectioning commands, but also to redefine the existing ones, including the possibility to easily define the section{}
-command to be a run-in heading.
RedeclareSectionCommand[%
afterskip=-10pt plus -1sp minus 1sp% using rubber is optional
]{section}
Just use a negative value as the first afterskip
value ( I have used -10pt here).
It's unfortunate the KOMA classes don't support this directly. However, your answer seems to be the best option for now.
– EP_Guy
Sep 1 '14 at 17:49
@EP_Guy If you compare to the standard LaTeX classes, it is easy to change many of KOMAscript's pre set parameters. And you a guaranteed a consistent and workable result. To protect the users from the most horrible results, some parameters are not easily changed.
– Sveinung
Sep 1 '14 at 18:09
add a comment |
The author of KOMA-script added an easy to use interface to redeclare sectioning commands (chapters and parts as well). In my opinion, it is much simpler than using titlesec
;-)
Of course, you need a fairly recent KOMA-bundle.
documentclass{scrartcl}
RedeclareSectionCommand[afterskip=-1em,%negative value -> runin
font=largenormalfont%match the font of your example
]{section}
begin{document}
section{First section}
This text follows on the same line as "First section"
end{document}
Level 10 nonsense, a headline you can't distinguish from text. But however, +1 for Johannes_B for a good answer.
– Keks Dose
Feb 10 '15 at 15:27
add a comment |
As from v3.26
, one may also use the switch runin
.
RedeclareSectionCommand[runin=on]{section}
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
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2ftex.stackexchange.com%2fquestions%2f198830%2fsection-title-with-runin-and-koma-class%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
3 Answers
3
active
oldest
votes
3 Answers
3
active
oldest
votes
active
oldest
votes
active
oldest
votes
1 Older version of KOMAScript
You have to redefine the definition of section
, subsection
etc. You use a negativ values to set runin heading, like in the standard article-class. I have copied the definition of headings from scrartcl
sometimes in the past. Be aware that this solution may break if scrartcl
is changed.
If you take a look at page 351 in the English manual for Komascript, you will see that there are several commands for changing the space above and below chapter
and part
. Hopefully, we will see a similar command for section
and her sisters.
Here, I have redefined both section and subsection to be runin-header.
documentclass{scrartcl}
makeatletter
renewcommandsection{@startsection{section}{1}{z@}%
{-1.5ex}%
{-1em}%{2.3ex @plus.2ex}% < - negative value here negative value here,
% the values behind % are the original.
% no use for rubber values, use a fix value to set the
% distance to between heading and the text
{ifnum scr@compatibility>@nameuse{scr@v@2.96}relax
setlength{parfillskip}{z@ plus 1fil}fi
raggedsectionsectfontnobreaksize@section}%
}
renewcommandsubsection{@startsection{subsection}{1}{z@}%
{-1.5ex @plus -1ex @minus -.2ex}%
{-1em}%{2.3ex @plus.2ex}% <- negative value here, the values behind % are the original
{ifnum scr@compatibility>@nameuse{scr@v@2.96}relax
setlength{parfillskip}{z@ plus 1fil}fi
raggedsectionnormalfontsectfontnobreaksize@section}%
}
makeatother
begin{document}
section{First section}
This text follows on the same line as "First section"
end{document}
You use the ordinary addtokomafont
etc. to change the font, colour etc. ANd of course, you have to fiddle around with the figures to get the space above you prefer.
2. Never versions of KOMAScript
I refer to Johannes_B’s answer below.
For the sake of completeness, I will bring your attention to page 363 ff. in the English KOMAScript manual as of 2015-10-03. The author has (from version 3.16?) added the possibility to interface to section{}
and her sisters by the four commands:
DeclareSectionCommand[attributes]{name}
DeclareNewSectionCommand[attributes]{name}
RedeclareSectionCommand[attributes]{name}
ProvideSectionCommand[attributes]{name}
You may use this commands to define totally new sectioning commands, but also to redefine the existing ones, including the possibility to easily define the section{}
-command to be a run-in heading.
RedeclareSectionCommand[%
afterskip=-10pt plus -1sp minus 1sp% using rubber is optional
]{section}
Just use a negative value as the first afterskip
value ( I have used -10pt here).
It's unfortunate the KOMA classes don't support this directly. However, your answer seems to be the best option for now.
– EP_Guy
Sep 1 '14 at 17:49
@EP_Guy If you compare to the standard LaTeX classes, it is easy to change many of KOMAscript's pre set parameters. And you a guaranteed a consistent and workable result. To protect the users from the most horrible results, some parameters are not easily changed.
– Sveinung
Sep 1 '14 at 18:09
add a comment |
1 Older version of KOMAScript
You have to redefine the definition of section
, subsection
etc. You use a negativ values to set runin heading, like in the standard article-class. I have copied the definition of headings from scrartcl
sometimes in the past. Be aware that this solution may break if scrartcl
is changed.
If you take a look at page 351 in the English manual for Komascript, you will see that there are several commands for changing the space above and below chapter
and part
. Hopefully, we will see a similar command for section
and her sisters.
Here, I have redefined both section and subsection to be runin-header.
documentclass{scrartcl}
makeatletter
renewcommandsection{@startsection{section}{1}{z@}%
{-1.5ex}%
{-1em}%{2.3ex @plus.2ex}% < - negative value here negative value here,
% the values behind % are the original.
% no use for rubber values, use a fix value to set the
% distance to between heading and the text
{ifnum scr@compatibility>@nameuse{scr@v@2.96}relax
setlength{parfillskip}{z@ plus 1fil}fi
raggedsectionsectfontnobreaksize@section}%
}
renewcommandsubsection{@startsection{subsection}{1}{z@}%
{-1.5ex @plus -1ex @minus -.2ex}%
{-1em}%{2.3ex @plus.2ex}% <- negative value here, the values behind % are the original
{ifnum scr@compatibility>@nameuse{scr@v@2.96}relax
setlength{parfillskip}{z@ plus 1fil}fi
raggedsectionnormalfontsectfontnobreaksize@section}%
}
makeatother
begin{document}
section{First section}
This text follows on the same line as "First section"
end{document}
You use the ordinary addtokomafont
etc. to change the font, colour etc. ANd of course, you have to fiddle around with the figures to get the space above you prefer.
2. Never versions of KOMAScript
I refer to Johannes_B’s answer below.
For the sake of completeness, I will bring your attention to page 363 ff. in the English KOMAScript manual as of 2015-10-03. The author has (from version 3.16?) added the possibility to interface to section{}
and her sisters by the four commands:
DeclareSectionCommand[attributes]{name}
DeclareNewSectionCommand[attributes]{name}
RedeclareSectionCommand[attributes]{name}
ProvideSectionCommand[attributes]{name}
You may use this commands to define totally new sectioning commands, but also to redefine the existing ones, including the possibility to easily define the section{}
-command to be a run-in heading.
RedeclareSectionCommand[%
afterskip=-10pt plus -1sp minus 1sp% using rubber is optional
]{section}
Just use a negative value as the first afterskip
value ( I have used -10pt here).
It's unfortunate the KOMA classes don't support this directly. However, your answer seems to be the best option for now.
– EP_Guy
Sep 1 '14 at 17:49
@EP_Guy If you compare to the standard LaTeX classes, it is easy to change many of KOMAscript's pre set parameters. And you a guaranteed a consistent and workable result. To protect the users from the most horrible results, some parameters are not easily changed.
– Sveinung
Sep 1 '14 at 18:09
add a comment |
1 Older version of KOMAScript
You have to redefine the definition of section
, subsection
etc. You use a negativ values to set runin heading, like in the standard article-class. I have copied the definition of headings from scrartcl
sometimes in the past. Be aware that this solution may break if scrartcl
is changed.
If you take a look at page 351 in the English manual for Komascript, you will see that there are several commands for changing the space above and below chapter
and part
. Hopefully, we will see a similar command for section
and her sisters.
Here, I have redefined both section and subsection to be runin-header.
documentclass{scrartcl}
makeatletter
renewcommandsection{@startsection{section}{1}{z@}%
{-1.5ex}%
{-1em}%{2.3ex @plus.2ex}% < - negative value here negative value here,
% the values behind % are the original.
% no use for rubber values, use a fix value to set the
% distance to between heading and the text
{ifnum scr@compatibility>@nameuse{scr@v@2.96}relax
setlength{parfillskip}{z@ plus 1fil}fi
raggedsectionsectfontnobreaksize@section}%
}
renewcommandsubsection{@startsection{subsection}{1}{z@}%
{-1.5ex @plus -1ex @minus -.2ex}%
{-1em}%{2.3ex @plus.2ex}% <- negative value here, the values behind % are the original
{ifnum scr@compatibility>@nameuse{scr@v@2.96}relax
setlength{parfillskip}{z@ plus 1fil}fi
raggedsectionnormalfontsectfontnobreaksize@section}%
}
makeatother
begin{document}
section{First section}
This text follows on the same line as "First section"
end{document}
You use the ordinary addtokomafont
etc. to change the font, colour etc. ANd of course, you have to fiddle around with the figures to get the space above you prefer.
2. Never versions of KOMAScript
I refer to Johannes_B’s answer below.
For the sake of completeness, I will bring your attention to page 363 ff. in the English KOMAScript manual as of 2015-10-03. The author has (from version 3.16?) added the possibility to interface to section{}
and her sisters by the four commands:
DeclareSectionCommand[attributes]{name}
DeclareNewSectionCommand[attributes]{name}
RedeclareSectionCommand[attributes]{name}
ProvideSectionCommand[attributes]{name}
You may use this commands to define totally new sectioning commands, but also to redefine the existing ones, including the possibility to easily define the section{}
-command to be a run-in heading.
RedeclareSectionCommand[%
afterskip=-10pt plus -1sp minus 1sp% using rubber is optional
]{section}
Just use a negative value as the first afterskip
value ( I have used -10pt here).
1 Older version of KOMAScript
You have to redefine the definition of section
, subsection
etc. You use a negativ values to set runin heading, like in the standard article-class. I have copied the definition of headings from scrartcl
sometimes in the past. Be aware that this solution may break if scrartcl
is changed.
If you take a look at page 351 in the English manual for Komascript, you will see that there are several commands for changing the space above and below chapter
and part
. Hopefully, we will see a similar command for section
and her sisters.
Here, I have redefined both section and subsection to be runin-header.
documentclass{scrartcl}
makeatletter
renewcommandsection{@startsection{section}{1}{z@}%
{-1.5ex}%
{-1em}%{2.3ex @plus.2ex}% < - negative value here negative value here,
% the values behind % are the original.
% no use for rubber values, use a fix value to set the
% distance to between heading and the text
{ifnum scr@compatibility>@nameuse{scr@v@2.96}relax
setlength{parfillskip}{z@ plus 1fil}fi
raggedsectionsectfontnobreaksize@section}%
}
renewcommandsubsection{@startsection{subsection}{1}{z@}%
{-1.5ex @plus -1ex @minus -.2ex}%
{-1em}%{2.3ex @plus.2ex}% <- negative value here, the values behind % are the original
{ifnum scr@compatibility>@nameuse{scr@v@2.96}relax
setlength{parfillskip}{z@ plus 1fil}fi
raggedsectionnormalfontsectfontnobreaksize@section}%
}
makeatother
begin{document}
section{First section}
This text follows on the same line as "First section"
end{document}
You use the ordinary addtokomafont
etc. to change the font, colour etc. ANd of course, you have to fiddle around with the figures to get the space above you prefer.
2. Never versions of KOMAScript
I refer to Johannes_B’s answer below.
For the sake of completeness, I will bring your attention to page 363 ff. in the English KOMAScript manual as of 2015-10-03. The author has (from version 3.16?) added the possibility to interface to section{}
and her sisters by the four commands:
DeclareSectionCommand[attributes]{name}
DeclareNewSectionCommand[attributes]{name}
RedeclareSectionCommand[attributes]{name}
ProvideSectionCommand[attributes]{name}
You may use this commands to define totally new sectioning commands, but also to redefine the existing ones, including the possibility to easily define the section{}
-command to be a run-in heading.
RedeclareSectionCommand[%
afterskip=-10pt plus -1sp minus 1sp% using rubber is optional
]{section}
Just use a negative value as the first afterskip
value ( I have used -10pt here).
edited Jan 19 '16 at 18:08
answered Aug 31 '14 at 21:59
SveinungSveinung
11k23256
11k23256
It's unfortunate the KOMA classes don't support this directly. However, your answer seems to be the best option for now.
– EP_Guy
Sep 1 '14 at 17:49
@EP_Guy If you compare to the standard LaTeX classes, it is easy to change many of KOMAscript's pre set parameters. And you a guaranteed a consistent and workable result. To protect the users from the most horrible results, some parameters are not easily changed.
– Sveinung
Sep 1 '14 at 18:09
add a comment |
It's unfortunate the KOMA classes don't support this directly. However, your answer seems to be the best option for now.
– EP_Guy
Sep 1 '14 at 17:49
@EP_Guy If you compare to the standard LaTeX classes, it is easy to change many of KOMAscript's pre set parameters. And you a guaranteed a consistent and workable result. To protect the users from the most horrible results, some parameters are not easily changed.
– Sveinung
Sep 1 '14 at 18:09
It's unfortunate the KOMA classes don't support this directly. However, your answer seems to be the best option for now.
– EP_Guy
Sep 1 '14 at 17:49
It's unfortunate the KOMA classes don't support this directly. However, your answer seems to be the best option for now.
– EP_Guy
Sep 1 '14 at 17:49
@EP_Guy If you compare to the standard LaTeX classes, it is easy to change many of KOMAscript's pre set parameters. And you a guaranteed a consistent and workable result. To protect the users from the most horrible results, some parameters are not easily changed.
– Sveinung
Sep 1 '14 at 18:09
@EP_Guy If you compare to the standard LaTeX classes, it is easy to change many of KOMAscript's pre set parameters. And you a guaranteed a consistent and workable result. To protect the users from the most horrible results, some parameters are not easily changed.
– Sveinung
Sep 1 '14 at 18:09
add a comment |
The author of KOMA-script added an easy to use interface to redeclare sectioning commands (chapters and parts as well). In my opinion, it is much simpler than using titlesec
;-)
Of course, you need a fairly recent KOMA-bundle.
documentclass{scrartcl}
RedeclareSectionCommand[afterskip=-1em,%negative value -> runin
font=largenormalfont%match the font of your example
]{section}
begin{document}
section{First section}
This text follows on the same line as "First section"
end{document}
Level 10 nonsense, a headline you can't distinguish from text. But however, +1 for Johannes_B for a good answer.
– Keks Dose
Feb 10 '15 at 15:27
add a comment |
The author of KOMA-script added an easy to use interface to redeclare sectioning commands (chapters and parts as well). In my opinion, it is much simpler than using titlesec
;-)
Of course, you need a fairly recent KOMA-bundle.
documentclass{scrartcl}
RedeclareSectionCommand[afterskip=-1em,%negative value -> runin
font=largenormalfont%match the font of your example
]{section}
begin{document}
section{First section}
This text follows on the same line as "First section"
end{document}
Level 10 nonsense, a headline you can't distinguish from text. But however, +1 for Johannes_B for a good answer.
– Keks Dose
Feb 10 '15 at 15:27
add a comment |
The author of KOMA-script added an easy to use interface to redeclare sectioning commands (chapters and parts as well). In my opinion, it is much simpler than using titlesec
;-)
Of course, you need a fairly recent KOMA-bundle.
documentclass{scrartcl}
RedeclareSectionCommand[afterskip=-1em,%negative value -> runin
font=largenormalfont%match the font of your example
]{section}
begin{document}
section{First section}
This text follows on the same line as "First section"
end{document}
The author of KOMA-script added an easy to use interface to redeclare sectioning commands (chapters and parts as well). In my opinion, it is much simpler than using titlesec
;-)
Of course, you need a fairly recent KOMA-bundle.
documentclass{scrartcl}
RedeclareSectionCommand[afterskip=-1em,%negative value -> runin
font=largenormalfont%match the font of your example
]{section}
begin{document}
section{First section}
This text follows on the same line as "First section"
end{document}
answered Feb 10 '15 at 14:12
Johannes_BJohannes_B
21k351203
21k351203
Level 10 nonsense, a headline you can't distinguish from text. But however, +1 for Johannes_B for a good answer.
– Keks Dose
Feb 10 '15 at 15:27
add a comment |
Level 10 nonsense, a headline you can't distinguish from text. But however, +1 for Johannes_B for a good answer.
– Keks Dose
Feb 10 '15 at 15:27
Level 10 nonsense, a headline you can't distinguish from text. But however, +1 for Johannes_B for a good answer.
– Keks Dose
Feb 10 '15 at 15:27
Level 10 nonsense, a headline you can't distinguish from text. But however, +1 for Johannes_B for a good answer.
– Keks Dose
Feb 10 '15 at 15:27
add a comment |
As from v3.26
, one may also use the switch runin
.
RedeclareSectionCommand[runin=on]{section}
add a comment |
As from v3.26
, one may also use the switch runin
.
RedeclareSectionCommand[runin=on]{section}
add a comment |
As from v3.26
, one may also use the switch runin
.
RedeclareSectionCommand[runin=on]{section}
As from v3.26
, one may also use the switch runin
.
RedeclareSectionCommand[runin=on]{section}
answered 17 mins ago
natural stupiditynatural stupidity
22518
22518
add a comment |
add a comment |
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.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2ftex.stackexchange.com%2fquestions%2f198830%2fsection-title-with-runin-and-koma-class%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown