Reduce spacing after glossary title
1
I would like to reduce the spacing after the Acronyms title to match spacing of a regular section, but don't know how.
I tried to reduce it manually using renewcommand{glossarypreamble}{vspace*{-baselineskip}}, which works, but is a really bad way of doing it.
MWE:
documentclass[a4paper, 12pt]{article}
usepackage[acronym]{glossaries}
setglossarystyle{alttree}
makeglossaries
newacronym{frc}{FRC}{First Robotics Competition}
newacronym{ftc}{FTC}{First Technical Challenge}
newacronym{fll}{FLL}{First Lego League}
glsaddall
glsfindwidesttoplevelname
begin{document}
section{Sample Text}
gls{frc}, gls{ftc}, gls{fll}
printglossary[type=acronymtype]
end{document}
spacing titles glossaries
asked Feb 23 at 11:53
Tomáš SlámaTomáš Sláma
375
add a comment |
1
I would like to reduce the spacing after the Acronyms title to match spacing of a regular section, but don't know how.
I tried to reduce it manually using renewcommand{glossarypreamble}{vspace*{-baselineskip}}, which works, but is a really bad way of doing it.
MWE:
documentclass[a4paper, 12pt]{article}
usepackage[acronym]{glossaries}
setglossarystyle{alttree}
makeglossaries
newacronym{frc}{FRC}{First Robotics Competition}
newacronym{ftc}{FTC}{First Technical Challenge}
newacronym{fll}{FLL}{First Lego League}
glsaddall
glsfindwidesttoplevelname
begin{document}
section{Sample Text}
gls{frc}, gls{ftc}, gls{fll}
printglossary[type=acronymtype]
end{document}
spacing titles glossaries
asked Feb 23 at 11:53
Tomáš SlámaTomáš Sláma
375
Can you explain why you think thatrenewcommand{glossarypreamble}{vspace*{-baselineskip}}is a bad way to reduce vertical space?
– Hafid Boukhoulda
Feb 23 at 12:11
Because the resulting spacing isn't exactly equal to the spacing of a regular section.
– Tomáš Sláma
Feb 23 at 12:16
add a comment |
1
1
1
I would like to reduce the spacing after the Acronyms title to match spacing of a regular section, but don't know how.
I tried to reduce it manually using renewcommand{glossarypreamble}{vspace*{-baselineskip}}, which works, but is a really bad way of doing it.
MWE:
documentclass[a4paper, 12pt]{article}
usepackage[acronym]{glossaries}
setglossarystyle{alttree}
makeglossaries
newacronym{frc}{FRC}{First Robotics Competition}
newacronym{ftc}{FTC}{First Technical Challenge}
newacronym{fll}{FLL}{First Lego League}
glsaddall
glsfindwidesttoplevelname
begin{document}
section{Sample Text}
gls{frc}, gls{ftc}, gls{fll}
printglossary[type=acronymtype]
end{document}
spacing titles glossaries
asked Feb 23 at 11:53
Tomáš SlámaTomáš Sláma
375
I would like to reduce the spacing after the Acronyms title to match spacing of a regular section, but don't know how.
I tried to reduce it manually using renewcommand{glossarypreamble}{vspace*{-baselineskip}}, which works, but is a really bad way of doing it.
MWE:
documentclass[a4paper, 12pt]{article}
usepackage[acronym]{glossaries}
setglossarystyle{alttree}
makeglossaries
newacronym{frc}{FRC}{First Robotics Competition}
newacronym{ftc}{FTC}{First Technical Challenge}
newacronym{fll}{FLL}{First Lego League}
glsaddall
glsfindwidesttoplevelname
begin{document}
section{Sample Text}
gls{frc}, gls{ftc}, gls{fll}
printglossary[type=acronymtype]
end{document}
spacing titles glossaries
spacing titles glossaries
asked Feb 23 at 11:53
Tomáš SlámaTomáš Sláma
375
asked Feb 23 at 11:53
Tomáš SlámaTomáš Sláma
375
asked Feb 23 at 11:53
Tomáš SlámaTomáš Sláma
375
asked Feb 23 at 11:53
Tomáš SlámaTomáš Sláma
375
asked Feb 23 at 11:53
Tomáš SlámaTomáš Sláma
375
375
Can you explain why you think thatrenewcommand{glossarypreamble}{vspace*{-baselineskip}}is a bad way to reduce vertical space?
– Hafid Boukhoulda
Feb 23 at 12:11
Because the resulting spacing isn't exactly equal to the spacing of a regular section.
– Tomáš Sláma
Feb 23 at 12:16
add a comment |
Can you explain why you think thatrenewcommand{glossarypreamble}{vspace*{-baselineskip}}is a bad way to reduce vertical space?
– Hafid Boukhoulda
Feb 23 at 12:11
Because the resulting spacing isn't exactly equal to the spacing of a regular section.
– Tomáš Sláma
Feb 23 at 12:16
Can you explain why you think that
renewcommand{glossarypreamble}{vspace*{-baselineskip}} is a bad way to reduce vertical space?– Hafid Boukhoulda
Feb 23 at 12:11
Can you explain why you think that
renewcommand{glossarypreamble}{vspace*{-baselineskip}} is a bad way to reduce vertical space?– Hafid Boukhoulda
Feb 23 at 12:11
Because the resulting spacing isn't exactly equal to the spacing of a regular section.
– Tomáš Sláma
Feb 23 at 12:16
Because the resulting spacing isn't exactly equal to the spacing of a regular section.
– Tomáš Sláma
Feb 23 at 12:16
add a comment |
2 Answers
2
active
oldest
votes
1
For some reason, glossaries does mbox{}par at the start of a glossary, so adding an empty line.
documentclass[a4paper, 12pt]{article}
usepackage[acronym]{glossaries}
setglossarystyle{alttree}
setglossarypreamble[acronym]{vspace*{-baselineskip}}
makeglossaries
newacronym{frc}{FRC}{First Robotics Competition}
newacronym{ftc}{FTC}{First Technical Challenge}
newacronym{fll}{FLL}{First Lego League}
glsaddall
glsfindwidesttoplevelname
begin{document}
section{Sample Text}
gls{frc}, gls{ftc}, gls{fll}
printglossary[type=acronymtype]
section*{Acronyms}
textbf{FLL} First Lego League. 1
end{document}
answered Feb 23 at 12:39
egregegreg
723k8819173221
This does fix the MWE, but it seems that when you add spacing between each of the acronyms, it is also added to the top and that's why it isn't working in my full document.
– Tomáš Sláma
Feb 23 at 12:54
@TomášSláma I don't know how you add spacing between acronyms.
– egreg
Feb 23 at 13:51
The spacing was likely due to me changing parskip length. I managed to fix the issue by doingrenewcommand{glossarypreamble}{vspace*{-baselineskip}vspace*{-parskip}}.
– Tomáš Sláma
Feb 23 at 14:08
add a comment |
0
The additional space is caused by setglossarystyle{alttree}. Use setglossarystyle{tree}.
documentclass[a4paper, 12pt]{article}
usepackage[acronym]{glossaries}
setglossarystyle{tree}
makeglossaries
newacronym{frc}{FRC}{First Robotics Competition}
newacronym{ftc}{FTC}{First Technical Challenge}
newacronym{fll}{FLL}{First Lego League}
glsaddall
glsfindwidesttoplevelname
begin{document}
section{Sample Text}
gls{frc}, gls{ftc}, gls{fll}
printglossary[type=acronymtype]
end{document}
answered Feb 23 at 12:57
Hafid BoukhouldaHafid Boukhoulda
4,3721624
Using the tree glossary style would make the long acronym names misaligned, which is something I don't want.
– Tomáš Sláma
Feb 23 at 12:59
@TomášSláma I see!
– Hafid Boukhoulda
Feb 23 at 13:14
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');
});
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%2f476314%2freduce-spacing-after-glossary-title%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
1
For some reason, glossaries does mbox{}par at the start of a glossary, so adding an empty line.
documentclass[a4paper, 12pt]{article}
usepackage[acronym]{glossaries}
setglossarystyle{alttree}
setglossarypreamble[acronym]{vspace*{-baselineskip}}
makeglossaries
newacronym{frc}{FRC}{First Robotics Competition}
newacronym{ftc}{FTC}{First Technical Challenge}
newacronym{fll}{FLL}{First Lego League}
glsaddall
glsfindwidesttoplevelname
begin{document}
section{Sample Text}
gls{frc}, gls{ftc}, gls{fll}
printglossary[type=acronymtype]
section*{Acronyms}
textbf{FLL} First Lego League. 1
end{document}
answered Feb 23 at 12:39
egregegreg
723k8819173221
This does fix the MWE, but it seems that when you add spacing between each of the acronyms, it is also added to the top and that's why it isn't working in my full document.
– Tomáš Sláma
Feb 23 at 12:54
@TomášSláma I don't know how you add spacing between acronyms.
– egreg
Feb 23 at 13:51
The spacing was likely due to me changing parskip length. I managed to fix the issue by doingrenewcommand{glossarypreamble}{vspace*{-baselineskip}vspace*{-parskip}}.
– Tomáš Sláma
Feb 23 at 14:08
add a comment |
1
For some reason, glossaries does mbox{}par at the start of a glossary, so adding an empty line.
documentclass[a4paper, 12pt]{article}
usepackage[acronym]{glossaries}
setglossarystyle{alttree}
setglossarypreamble[acronym]{vspace*{-baselineskip}}
makeglossaries
newacronym{frc}{FRC}{First Robotics Competition}
newacronym{ftc}{FTC}{First Technical Challenge}
newacronym{fll}{FLL}{First Lego League}
glsaddall
glsfindwidesttoplevelname
begin{document}
section{Sample Text}
gls{frc}, gls{ftc}, gls{fll}
printglossary[type=acronymtype]
section*{Acronyms}
textbf{FLL} First Lego League. 1
end{document}
answered Feb 23 at 12:39
egregegreg
723k8819173221
This does fix the MWE, but it seems that when you add spacing between each of the acronyms, it is also added to the top and that's why it isn't working in my full document.
– Tomáš Sláma
Feb 23 at 12:54
@TomášSláma I don't know how you add spacing between acronyms.
– egreg
Feb 23 at 13:51
The spacing was likely due to me changing parskip length. I managed to fix the issue by doingrenewcommand{glossarypreamble}{vspace*{-baselineskip}vspace*{-parskip}}.
– Tomáš Sláma
Feb 23 at 14:08
add a comment |
1
1
1
For some reason, glossaries does mbox{}par at the start of a glossary, so adding an empty line.
documentclass[a4paper, 12pt]{article}
usepackage[acronym]{glossaries}
setglossarystyle{alttree}
setglossarypreamble[acronym]{vspace*{-baselineskip}}
makeglossaries
newacronym{frc}{FRC}{First Robotics Competition}
newacronym{ftc}{FTC}{First Technical Challenge}
newacronym{fll}{FLL}{First Lego League}
glsaddall
glsfindwidesttoplevelname
begin{document}
section{Sample Text}
gls{frc}, gls{ftc}, gls{fll}
printglossary[type=acronymtype]
section*{Acronyms}
textbf{FLL} First Lego League. 1
end{document}
answered Feb 23 at 12:39
egregegreg
723k8819173221
For some reason, glossaries does mbox{}par at the start of a glossary, so adding an empty line.
documentclass[a4paper, 12pt]{article}
usepackage[acronym]{glossaries}
setglossarystyle{alttree}
setglossarypreamble[acronym]{vspace*{-baselineskip}}
makeglossaries
newacronym{frc}{FRC}{First Robotics Competition}
newacronym{ftc}{FTC}{First Technical Challenge}
newacronym{fll}{FLL}{First Lego League}
glsaddall
glsfindwidesttoplevelname
begin{document}
section{Sample Text}
gls{frc}, gls{ftc}, gls{fll}
printglossary[type=acronymtype]
section*{Acronyms}
textbf{FLL} First Lego League. 1
end{document}
answered Feb 23 at 12:39
egregegreg
723k8819173221
answered Feb 23 at 12:39
egregegreg
723k8819173221
answered Feb 23 at 12:39
egregegreg
723k8819173221
answered Feb 23 at 12:39
egregegreg
723k8819173221
723k8819173221
This does fix the MWE, but it seems that when you add spacing between each of the acronyms, it is also added to the top and that's why it isn't working in my full document.
– Tomáš Sláma
Feb 23 at 12:54
@TomášSláma I don't know how you add spacing between acronyms.
– egreg
Feb 23 at 13:51
The spacing was likely due to me changing parskip length. I managed to fix the issue by doingrenewcommand{glossarypreamble}{vspace*{-baselineskip}vspace*{-parskip}}.
– Tomáš Sláma
Feb 23 at 14:08
add a comment |
This does fix the MWE, but it seems that when you add spacing between each of the acronyms, it is also added to the top and that's why it isn't working in my full document.
– Tomáš Sláma
Feb 23 at 12:54
@TomášSláma I don't know how you add spacing between acronyms.
– egreg
Feb 23 at 13:51
The spacing was likely due to me changing parskip length. I managed to fix the issue by doingrenewcommand{glossarypreamble}{vspace*{-baselineskip}vspace*{-parskip}}.
– Tomáš Sláma
Feb 23 at 14:08
This does fix the MWE, but it seems that when you add spacing between each of the acronyms, it is also added to the top and that's why it isn't working in my full document.
– Tomáš Sláma
Feb 23 at 12:54
This does fix the MWE, but it seems that when you add spacing between each of the acronyms, it is also added to the top and that's why it isn't working in my full document.
– Tomáš Sláma
Feb 23 at 12:54
@TomášSláma I don't know how you add spacing between acronyms.
– egreg
Feb 23 at 13:51
@TomášSláma I don't know how you add spacing between acronyms.
– egreg
Feb 23 at 13:51
The spacing was likely due to me changing parskip length. I managed to fix the issue by doing
renewcommand{glossarypreamble}{vspace*{-baselineskip}vspace*{-parskip}}.– Tomáš Sláma
Feb 23 at 14:08
The spacing was likely due to me changing parskip length. I managed to fix the issue by doing
renewcommand{glossarypreamble}{vspace*{-baselineskip}vspace*{-parskip}}.– Tomáš Sláma
Feb 23 at 14:08
add a comment |
0
The additional space is caused by setglossarystyle{alttree}. Use setglossarystyle{tree}.
documentclass[a4paper, 12pt]{article}
usepackage[acronym]{glossaries}
setglossarystyle{tree}
makeglossaries
newacronym{frc}{FRC}{First Robotics Competition}
newacronym{ftc}{FTC}{First Technical Challenge}
newacronym{fll}{FLL}{First Lego League}
glsaddall
glsfindwidesttoplevelname
begin{document}
section{Sample Text}
gls{frc}, gls{ftc}, gls{fll}
printglossary[type=acronymtype]
end{document}
answered Feb 23 at 12:57
Hafid BoukhouldaHafid Boukhoulda
4,3721624
Using the tree glossary style would make the long acronym names misaligned, which is something I don't want.
– Tomáš Sláma
Feb 23 at 12:59
@TomášSláma I see!
– Hafid Boukhoulda
Feb 23 at 13:14
add a comment |
0
The additional space is caused by setglossarystyle{alttree}. Use setglossarystyle{tree}.
documentclass[a4paper, 12pt]{article}
usepackage[acronym]{glossaries}
setglossarystyle{tree}
makeglossaries
newacronym{frc}{FRC}{First Robotics Competition}
newacronym{ftc}{FTC}{First Technical Challenge}
newacronym{fll}{FLL}{First Lego League}
glsaddall
glsfindwidesttoplevelname
begin{document}
section{Sample Text}
gls{frc}, gls{ftc}, gls{fll}
printglossary[type=acronymtype]
end{document}
answered Feb 23 at 12:57
Hafid BoukhouldaHafid Boukhoulda
4,3721624
Using the tree glossary style would make the long acronym names misaligned, which is something I don't want.
– Tomáš Sláma
Feb 23 at 12:59
@TomášSláma I see!
– Hafid Boukhoulda
Feb 23 at 13:14
add a comment |
0
0
0
The additional space is caused by setglossarystyle{alttree}. Use setglossarystyle{tree}.
documentclass[a4paper, 12pt]{article}
usepackage[acronym]{glossaries}
setglossarystyle{tree}
makeglossaries
newacronym{frc}{FRC}{First Robotics Competition}
newacronym{ftc}{FTC}{First Technical Challenge}
newacronym{fll}{FLL}{First Lego League}
glsaddall
glsfindwidesttoplevelname
begin{document}
section{Sample Text}
gls{frc}, gls{ftc}, gls{fll}
printglossary[type=acronymtype]
end{document}
answered Feb 23 at 12:57
Hafid BoukhouldaHafid Boukhoulda
4,3721624
The additional space is caused by setglossarystyle{alttree}. Use setglossarystyle{tree}.
documentclass[a4paper, 12pt]{article}
usepackage[acronym]{glossaries}
setglossarystyle{tree}
makeglossaries
newacronym{frc}{FRC}{First Robotics Competition}
newacronym{ftc}{FTC}{First Technical Challenge}
newacronym{fll}{FLL}{First Lego League}
glsaddall
glsfindwidesttoplevelname
begin{document}
section{Sample Text}
gls{frc}, gls{ftc}, gls{fll}
printglossary[type=acronymtype]
end{document}
answered Feb 23 at 12:57
Hafid BoukhouldaHafid Boukhoulda
4,3721624
answered Feb 23 at 12:57
Hafid BoukhouldaHafid Boukhoulda
4,3721624
answered Feb 23 at 12:57
Hafid BoukhouldaHafid Boukhoulda
4,3721624
answered Feb 23 at 12:57
Hafid BoukhouldaHafid Boukhoulda
4,3721624
4,3721624
Using the tree glossary style would make the long acronym names misaligned, which is something I don't want.
– Tomáš Sláma
Feb 23 at 12:59
@TomášSláma I see!
– Hafid Boukhoulda
Feb 23 at 13:14
add a comment |
Using the tree glossary style would make the long acronym names misaligned, which is something I don't want.
– Tomáš Sláma
Feb 23 at 12:59
@TomášSláma I see!
– Hafid Boukhoulda
Feb 23 at 13:14
Using the tree glossary style would make the long acronym names misaligned, which is something I don't want.
– Tomáš Sláma
Feb 23 at 12:59
Using the tree glossary style would make the long acronym names misaligned, which is something I don't want.
– Tomáš Sláma
Feb 23 at 12:59
@TomášSláma I see!
– Hafid Boukhoulda
Feb 23 at 13:14
@TomášSláma I see!
– Hafid Boukhoulda
Feb 23 at 13:14
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');
});
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%2f476314%2freduce-spacing-after-glossary-title%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
Can you explain why you think that
renewcommand{glossarypreamble}{vspace*{-baselineskip}}is a bad way to reduce vertical space?– Hafid Boukhoulda
Feb 23 at 12:11
Because the resulting spacing isn't exactly equal to the spacing of a regular section.
– Tomáš Sláma
Feb 23 at 12:16