How to troubleshoot unwanted white spaces smartly?
Why is there a white space on the left side?
documentclass{standalone}
usepackage{asymptote}
begin{document}
noindent
begin{asy}
size(10cm,10cm);
draw((0,0)--(100,100));
draw((0,100)--(100,0));
dot((50,50));
end{asy}
end{document}
asymptote
add a comment |
Why is there a white space on the left side?
documentclass{standalone}
usepackage{asymptote}
begin{document}
noindent
begin{asy}
size(10cm,10cm);
draw((0,0)--(100,100));
draw((0,100)--(100,0));
dot((50,50));
end{asy}
end{document}
asymptote
@chishimotoji: You must contact the package author to remove the white spaces.
– God Must Be Crazy
Dec 17 '18 at 8:35
@ArtificialStupidity I filed a bug report to one of the maintainers.
– egreg
Dec 17 '18 at 8:37
@egreg: Thank you very much!
– God Must Be Crazy
Dec 17 '18 at 8:38
add a comment |
Why is there a white space on the left side?
documentclass{standalone}
usepackage{asymptote}
begin{document}
noindent
begin{asy}
size(10cm,10cm);
draw((0,0)--(100,100));
draw((0,100)--(100,0));
dot((50,50));
end{asy}
end{document}
asymptote
Why is there a white space on the left side?
documentclass{standalone}
usepackage{asymptote}
begin{document}
noindent
begin{asy}
size(10cm,10cm);
draw((0,0)--(100,100));
draw((0,100)--(100,0));
dot((50,50));
end{asy}
end{document}
asymptote
asymptote
edited Dec 17 '18 at 9:06
God Must Be Crazy
asked Dec 17 '18 at 8:08
God Must Be CrazyGod Must Be Crazy
6,00511039
6,00511039
@chishimotoji: You must contact the package author to remove the white spaces.
– God Must Be Crazy
Dec 17 '18 at 8:35
@ArtificialStupidity I filed a bug report to one of the maintainers.
– egreg
Dec 17 '18 at 8:37
@egreg: Thank you very much!
– God Must Be Crazy
Dec 17 '18 at 8:38
add a comment |
@chishimotoji: You must contact the package author to remove the white spaces.
– God Must Be Crazy
Dec 17 '18 at 8:35
@ArtificialStupidity I filed a bug report to one of the maintainers.
– egreg
Dec 17 '18 at 8:37
@egreg: Thank you very much!
– God Must Be Crazy
Dec 17 '18 at 8:38
@chishimotoji: You must contact the package author to remove the white spaces.
– God Must Be Crazy
Dec 17 '18 at 8:35
@chishimotoji: You must contact the package author to remove the white spaces.
– God Must Be Crazy
Dec 17 '18 at 8:35
@ArtificialStupidity I filed a bug report to one of the maintainers.
– egreg
Dec 17 '18 at 8:37
@ArtificialStupidity I filed a bug report to one of the maintainers.
– egreg
Dec 17 '18 at 8:37
@egreg: Thank you very much!
– God Must Be Crazy
Dec 17 '18 at 8:38
@egreg: Thank you very much!
– God Must Be Crazy
Dec 17 '18 at 8:38
add a comment |
1 Answer
1
active
oldest
votes
Three unprotected end-of-lines in asymptote.sty
(marked with %<---
).
documentclass{standalone}
usepackage{asymptote}
makeatletter
defasy@init{%<---
defASYlatexdir{}%<---
ifxasylatexdiremptyelse
defASYlatexdir{asylatexdir/}%
fi
ifxasydiremptyelse
defASYasydir{asydir/}%
fi
defASYprefix{ASYlatexdirASYasydir}%
}
renewcommandasy[1]{%
stepcounter{asy}%
setkeys{ASYkeys}{#1}%
ifASYattach
ASYinlinefalse
fi
asy@init
immediatewriteAsyPreStream{%
noexpandInputIfFileExists{%
ASYprefixnoexpandjobname-thec@asy.pre}{}{}%
}%<---
asy@write@graphic@header
letThisAsymptoteWriteAsyLine
ProcessAsymptote{asy}%
}
makeatother
begin{document}
begin{asy}
size(10cm,10cm);
draw((0,0)--(100,100));
draw((0,100)--(100,0));
dot((50,50));
end{asy}
end{document}
Note that noindent
is not necessary.
How to find them? I removed noindent
that does nothing with standalone
, replacing it with
tracingcommands=1 tracingmacros=1
I compiled with pdflatex
, ran asy
and compiled again. The .log
file is the searched for {blank space}
:
asy@init -> def ASYlatexdir {} ifx asylatexdir empty else def ASYlatex
dir {asylatexdir /}fi ifx asydir empty else def ASYasydir {asydir /}f
i def ASYprefix {ASYlatexdir ASYasydir }
{blank space }
{def}
{blank space }
{def}
{immediate}
ASYprefix ->ASYlatexdir ASYasydir
ASYlatexdir ->
ASYasydir ->
{blank space }
asy@write@graphic@header ->immediate openout AsyStream =ASYasydir jobname
It is apparent that asy@init
is responsible and indeed its definition is
defasy@init{
defASYlatexdir{}
ifxasylatexdiremptyelse
defASYlatexdir{asylatexdir/}%
fi
ifxasydiremptyelse
defASYasydir{asydir/}%
fi
defASYprefix{ASYlatexdirASYasydir}%
}
showing two missing %
protections.
Redefine the command and retry. Darn! There's still a blank space!
ASYasydir ->
{blank space }
asy@write@graphic@header ->immediate openout AsyStream =ASYasydir jobname
Look for asy@write@graphic@header
in asymptote.sty
: we find it in the definition of asy
:
newcommandasy[1]{%
stepcounter{asy}%
setkeys{ASYkeys}{#1}%
ifASYattach
ASYinlinefalse
fi
asy@init
immediatewriteAsyPreStream{%
noexpandInputIfFileExists{%
ASYprefixnoexpandjobname-thec@asy.pre}{}{}%
}
asy@write@graphic@header
letThisAsymptoteWriteAsyLine
ProcessAsymptote{asy}%
}
Fix it and check again. Hurray! No spaces!
(+1) This nice fix should go intoasymptote.sty
soon! Thanks @egreg.
– AboAmmar
Dec 17 '18 at 14:40
I believe this really shows how horrible LaTeX programming is... How can anybody conceive a language in which comments influence the execution?!
– Federico
Dec 17 '18 at 17:05
@Federico It's one of the reasons whyexpl3
was born. On the other hand, TeX is a typesetting program, so spaces cannot generally be ignored.
– egreg
Dec 17 '18 at 18:17
@egreg Good to know aboutexpl3
; I'll have a look. "TeX is a typesetting program, so spaces cannot generally be ignored": that is just a severely bad separation of concerns in the TeX system, where there is no distinction between "typing mode" and "programming mode".
– Federico
Dec 17 '18 at 18:22
@egreg Many thanks I sent a mail to the authors, it is fixed.
– O.G.
Dec 29 '18 at 19:40
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%2f466170%2fhow-to-troubleshoot-unwanted-white-spaces-smartly%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
Three unprotected end-of-lines in asymptote.sty
(marked with %<---
).
documentclass{standalone}
usepackage{asymptote}
makeatletter
defasy@init{%<---
defASYlatexdir{}%<---
ifxasylatexdiremptyelse
defASYlatexdir{asylatexdir/}%
fi
ifxasydiremptyelse
defASYasydir{asydir/}%
fi
defASYprefix{ASYlatexdirASYasydir}%
}
renewcommandasy[1]{%
stepcounter{asy}%
setkeys{ASYkeys}{#1}%
ifASYattach
ASYinlinefalse
fi
asy@init
immediatewriteAsyPreStream{%
noexpandInputIfFileExists{%
ASYprefixnoexpandjobname-thec@asy.pre}{}{}%
}%<---
asy@write@graphic@header
letThisAsymptoteWriteAsyLine
ProcessAsymptote{asy}%
}
makeatother
begin{document}
begin{asy}
size(10cm,10cm);
draw((0,0)--(100,100));
draw((0,100)--(100,0));
dot((50,50));
end{asy}
end{document}
Note that noindent
is not necessary.
How to find them? I removed noindent
that does nothing with standalone
, replacing it with
tracingcommands=1 tracingmacros=1
I compiled with pdflatex
, ran asy
and compiled again. The .log
file is the searched for {blank space}
:
asy@init -> def ASYlatexdir {} ifx asylatexdir empty else def ASYlatex
dir {asylatexdir /}fi ifx asydir empty else def ASYasydir {asydir /}f
i def ASYprefix {ASYlatexdir ASYasydir }
{blank space }
{def}
{blank space }
{def}
{immediate}
ASYprefix ->ASYlatexdir ASYasydir
ASYlatexdir ->
ASYasydir ->
{blank space }
asy@write@graphic@header ->immediate openout AsyStream =ASYasydir jobname
It is apparent that asy@init
is responsible and indeed its definition is
defasy@init{
defASYlatexdir{}
ifxasylatexdiremptyelse
defASYlatexdir{asylatexdir/}%
fi
ifxasydiremptyelse
defASYasydir{asydir/}%
fi
defASYprefix{ASYlatexdirASYasydir}%
}
showing two missing %
protections.
Redefine the command and retry. Darn! There's still a blank space!
ASYasydir ->
{blank space }
asy@write@graphic@header ->immediate openout AsyStream =ASYasydir jobname
Look for asy@write@graphic@header
in asymptote.sty
: we find it in the definition of asy
:
newcommandasy[1]{%
stepcounter{asy}%
setkeys{ASYkeys}{#1}%
ifASYattach
ASYinlinefalse
fi
asy@init
immediatewriteAsyPreStream{%
noexpandInputIfFileExists{%
ASYprefixnoexpandjobname-thec@asy.pre}{}{}%
}
asy@write@graphic@header
letThisAsymptoteWriteAsyLine
ProcessAsymptote{asy}%
}
Fix it and check again. Hurray! No spaces!
(+1) This nice fix should go intoasymptote.sty
soon! Thanks @egreg.
– AboAmmar
Dec 17 '18 at 14:40
I believe this really shows how horrible LaTeX programming is... How can anybody conceive a language in which comments influence the execution?!
– Federico
Dec 17 '18 at 17:05
@Federico It's one of the reasons whyexpl3
was born. On the other hand, TeX is a typesetting program, so spaces cannot generally be ignored.
– egreg
Dec 17 '18 at 18:17
@egreg Good to know aboutexpl3
; I'll have a look. "TeX is a typesetting program, so spaces cannot generally be ignored": that is just a severely bad separation of concerns in the TeX system, where there is no distinction between "typing mode" and "programming mode".
– Federico
Dec 17 '18 at 18:22
@egreg Many thanks I sent a mail to the authors, it is fixed.
– O.G.
Dec 29 '18 at 19:40
add a comment |
Three unprotected end-of-lines in asymptote.sty
(marked with %<---
).
documentclass{standalone}
usepackage{asymptote}
makeatletter
defasy@init{%<---
defASYlatexdir{}%<---
ifxasylatexdiremptyelse
defASYlatexdir{asylatexdir/}%
fi
ifxasydiremptyelse
defASYasydir{asydir/}%
fi
defASYprefix{ASYlatexdirASYasydir}%
}
renewcommandasy[1]{%
stepcounter{asy}%
setkeys{ASYkeys}{#1}%
ifASYattach
ASYinlinefalse
fi
asy@init
immediatewriteAsyPreStream{%
noexpandInputIfFileExists{%
ASYprefixnoexpandjobname-thec@asy.pre}{}{}%
}%<---
asy@write@graphic@header
letThisAsymptoteWriteAsyLine
ProcessAsymptote{asy}%
}
makeatother
begin{document}
begin{asy}
size(10cm,10cm);
draw((0,0)--(100,100));
draw((0,100)--(100,0));
dot((50,50));
end{asy}
end{document}
Note that noindent
is not necessary.
How to find them? I removed noindent
that does nothing with standalone
, replacing it with
tracingcommands=1 tracingmacros=1
I compiled with pdflatex
, ran asy
and compiled again. The .log
file is the searched for {blank space}
:
asy@init -> def ASYlatexdir {} ifx asylatexdir empty else def ASYlatex
dir {asylatexdir /}fi ifx asydir empty else def ASYasydir {asydir /}f
i def ASYprefix {ASYlatexdir ASYasydir }
{blank space }
{def}
{blank space }
{def}
{immediate}
ASYprefix ->ASYlatexdir ASYasydir
ASYlatexdir ->
ASYasydir ->
{blank space }
asy@write@graphic@header ->immediate openout AsyStream =ASYasydir jobname
It is apparent that asy@init
is responsible and indeed its definition is
defasy@init{
defASYlatexdir{}
ifxasylatexdiremptyelse
defASYlatexdir{asylatexdir/}%
fi
ifxasydiremptyelse
defASYasydir{asydir/}%
fi
defASYprefix{ASYlatexdirASYasydir}%
}
showing two missing %
protections.
Redefine the command and retry. Darn! There's still a blank space!
ASYasydir ->
{blank space }
asy@write@graphic@header ->immediate openout AsyStream =ASYasydir jobname
Look for asy@write@graphic@header
in asymptote.sty
: we find it in the definition of asy
:
newcommandasy[1]{%
stepcounter{asy}%
setkeys{ASYkeys}{#1}%
ifASYattach
ASYinlinefalse
fi
asy@init
immediatewriteAsyPreStream{%
noexpandInputIfFileExists{%
ASYprefixnoexpandjobname-thec@asy.pre}{}{}%
}
asy@write@graphic@header
letThisAsymptoteWriteAsyLine
ProcessAsymptote{asy}%
}
Fix it and check again. Hurray! No spaces!
(+1) This nice fix should go intoasymptote.sty
soon! Thanks @egreg.
– AboAmmar
Dec 17 '18 at 14:40
I believe this really shows how horrible LaTeX programming is... How can anybody conceive a language in which comments influence the execution?!
– Federico
Dec 17 '18 at 17:05
@Federico It's one of the reasons whyexpl3
was born. On the other hand, TeX is a typesetting program, so spaces cannot generally be ignored.
– egreg
Dec 17 '18 at 18:17
@egreg Good to know aboutexpl3
; I'll have a look. "TeX is a typesetting program, so spaces cannot generally be ignored": that is just a severely bad separation of concerns in the TeX system, where there is no distinction between "typing mode" and "programming mode".
– Federico
Dec 17 '18 at 18:22
@egreg Many thanks I sent a mail to the authors, it is fixed.
– O.G.
Dec 29 '18 at 19:40
add a comment |
Three unprotected end-of-lines in asymptote.sty
(marked with %<---
).
documentclass{standalone}
usepackage{asymptote}
makeatletter
defasy@init{%<---
defASYlatexdir{}%<---
ifxasylatexdiremptyelse
defASYlatexdir{asylatexdir/}%
fi
ifxasydiremptyelse
defASYasydir{asydir/}%
fi
defASYprefix{ASYlatexdirASYasydir}%
}
renewcommandasy[1]{%
stepcounter{asy}%
setkeys{ASYkeys}{#1}%
ifASYattach
ASYinlinefalse
fi
asy@init
immediatewriteAsyPreStream{%
noexpandInputIfFileExists{%
ASYprefixnoexpandjobname-thec@asy.pre}{}{}%
}%<---
asy@write@graphic@header
letThisAsymptoteWriteAsyLine
ProcessAsymptote{asy}%
}
makeatother
begin{document}
begin{asy}
size(10cm,10cm);
draw((0,0)--(100,100));
draw((0,100)--(100,0));
dot((50,50));
end{asy}
end{document}
Note that noindent
is not necessary.
How to find them? I removed noindent
that does nothing with standalone
, replacing it with
tracingcommands=1 tracingmacros=1
I compiled with pdflatex
, ran asy
and compiled again. The .log
file is the searched for {blank space}
:
asy@init -> def ASYlatexdir {} ifx asylatexdir empty else def ASYlatex
dir {asylatexdir /}fi ifx asydir empty else def ASYasydir {asydir /}f
i def ASYprefix {ASYlatexdir ASYasydir }
{blank space }
{def}
{blank space }
{def}
{immediate}
ASYprefix ->ASYlatexdir ASYasydir
ASYlatexdir ->
ASYasydir ->
{blank space }
asy@write@graphic@header ->immediate openout AsyStream =ASYasydir jobname
It is apparent that asy@init
is responsible and indeed its definition is
defasy@init{
defASYlatexdir{}
ifxasylatexdiremptyelse
defASYlatexdir{asylatexdir/}%
fi
ifxasydiremptyelse
defASYasydir{asydir/}%
fi
defASYprefix{ASYlatexdirASYasydir}%
}
showing two missing %
protections.
Redefine the command and retry. Darn! There's still a blank space!
ASYasydir ->
{blank space }
asy@write@graphic@header ->immediate openout AsyStream =ASYasydir jobname
Look for asy@write@graphic@header
in asymptote.sty
: we find it in the definition of asy
:
newcommandasy[1]{%
stepcounter{asy}%
setkeys{ASYkeys}{#1}%
ifASYattach
ASYinlinefalse
fi
asy@init
immediatewriteAsyPreStream{%
noexpandInputIfFileExists{%
ASYprefixnoexpandjobname-thec@asy.pre}{}{}%
}
asy@write@graphic@header
letThisAsymptoteWriteAsyLine
ProcessAsymptote{asy}%
}
Fix it and check again. Hurray! No spaces!
Three unprotected end-of-lines in asymptote.sty
(marked with %<---
).
documentclass{standalone}
usepackage{asymptote}
makeatletter
defasy@init{%<---
defASYlatexdir{}%<---
ifxasylatexdiremptyelse
defASYlatexdir{asylatexdir/}%
fi
ifxasydiremptyelse
defASYasydir{asydir/}%
fi
defASYprefix{ASYlatexdirASYasydir}%
}
renewcommandasy[1]{%
stepcounter{asy}%
setkeys{ASYkeys}{#1}%
ifASYattach
ASYinlinefalse
fi
asy@init
immediatewriteAsyPreStream{%
noexpandInputIfFileExists{%
ASYprefixnoexpandjobname-thec@asy.pre}{}{}%
}%<---
asy@write@graphic@header
letThisAsymptoteWriteAsyLine
ProcessAsymptote{asy}%
}
makeatother
begin{document}
begin{asy}
size(10cm,10cm);
draw((0,0)--(100,100));
draw((0,100)--(100,0));
dot((50,50));
end{asy}
end{document}
Note that noindent
is not necessary.
How to find them? I removed noindent
that does nothing with standalone
, replacing it with
tracingcommands=1 tracingmacros=1
I compiled with pdflatex
, ran asy
and compiled again. The .log
file is the searched for {blank space}
:
asy@init -> def ASYlatexdir {} ifx asylatexdir empty else def ASYlatex
dir {asylatexdir /}fi ifx asydir empty else def ASYasydir {asydir /}f
i def ASYprefix {ASYlatexdir ASYasydir }
{blank space }
{def}
{blank space }
{def}
{immediate}
ASYprefix ->ASYlatexdir ASYasydir
ASYlatexdir ->
ASYasydir ->
{blank space }
asy@write@graphic@header ->immediate openout AsyStream =ASYasydir jobname
It is apparent that asy@init
is responsible and indeed its definition is
defasy@init{
defASYlatexdir{}
ifxasylatexdiremptyelse
defASYlatexdir{asylatexdir/}%
fi
ifxasydiremptyelse
defASYasydir{asydir/}%
fi
defASYprefix{ASYlatexdirASYasydir}%
}
showing two missing %
protections.
Redefine the command and retry. Darn! There's still a blank space!
ASYasydir ->
{blank space }
asy@write@graphic@header ->immediate openout AsyStream =ASYasydir jobname
Look for asy@write@graphic@header
in asymptote.sty
: we find it in the definition of asy
:
newcommandasy[1]{%
stepcounter{asy}%
setkeys{ASYkeys}{#1}%
ifASYattach
ASYinlinefalse
fi
asy@init
immediatewriteAsyPreStream{%
noexpandInputIfFileExists{%
ASYprefixnoexpandjobname-thec@asy.pre}{}{}%
}
asy@write@graphic@header
letThisAsymptoteWriteAsyLine
ProcessAsymptote{asy}%
}
Fix it and check again. Hurray! No spaces!
edited Dec 17 '18 at 8:48
answered Dec 17 '18 at 8:31
egregegreg
711k8618913174
711k8618913174
(+1) This nice fix should go intoasymptote.sty
soon! Thanks @egreg.
– AboAmmar
Dec 17 '18 at 14:40
I believe this really shows how horrible LaTeX programming is... How can anybody conceive a language in which comments influence the execution?!
– Federico
Dec 17 '18 at 17:05
@Federico It's one of the reasons whyexpl3
was born. On the other hand, TeX is a typesetting program, so spaces cannot generally be ignored.
– egreg
Dec 17 '18 at 18:17
@egreg Good to know aboutexpl3
; I'll have a look. "TeX is a typesetting program, so spaces cannot generally be ignored": that is just a severely bad separation of concerns in the TeX system, where there is no distinction between "typing mode" and "programming mode".
– Federico
Dec 17 '18 at 18:22
@egreg Many thanks I sent a mail to the authors, it is fixed.
– O.G.
Dec 29 '18 at 19:40
add a comment |
(+1) This nice fix should go intoasymptote.sty
soon! Thanks @egreg.
– AboAmmar
Dec 17 '18 at 14:40
I believe this really shows how horrible LaTeX programming is... How can anybody conceive a language in which comments influence the execution?!
– Federico
Dec 17 '18 at 17:05
@Federico It's one of the reasons whyexpl3
was born. On the other hand, TeX is a typesetting program, so spaces cannot generally be ignored.
– egreg
Dec 17 '18 at 18:17
@egreg Good to know aboutexpl3
; I'll have a look. "TeX is a typesetting program, so spaces cannot generally be ignored": that is just a severely bad separation of concerns in the TeX system, where there is no distinction between "typing mode" and "programming mode".
– Federico
Dec 17 '18 at 18:22
@egreg Many thanks I sent a mail to the authors, it is fixed.
– O.G.
Dec 29 '18 at 19:40
(+1) This nice fix should go into
asymptote.sty
soon! Thanks @egreg.– AboAmmar
Dec 17 '18 at 14:40
(+1) This nice fix should go into
asymptote.sty
soon! Thanks @egreg.– AboAmmar
Dec 17 '18 at 14:40
I believe this really shows how horrible LaTeX programming is... How can anybody conceive a language in which comments influence the execution?!
– Federico
Dec 17 '18 at 17:05
I believe this really shows how horrible LaTeX programming is... How can anybody conceive a language in which comments influence the execution?!
– Federico
Dec 17 '18 at 17:05
@Federico It's one of the reasons why
expl3
was born. On the other hand, TeX is a typesetting program, so spaces cannot generally be ignored.– egreg
Dec 17 '18 at 18:17
@Federico It's one of the reasons why
expl3
was born. On the other hand, TeX is a typesetting program, so spaces cannot generally be ignored.– egreg
Dec 17 '18 at 18:17
@egreg Good to know about
expl3
; I'll have a look. "TeX is a typesetting program, so spaces cannot generally be ignored": that is just a severely bad separation of concerns in the TeX system, where there is no distinction between "typing mode" and "programming mode".– Federico
Dec 17 '18 at 18:22
@egreg Good to know about
expl3
; I'll have a look. "TeX is a typesetting program, so spaces cannot generally be ignored": that is just a severely bad separation of concerns in the TeX system, where there is no distinction between "typing mode" and "programming mode".– Federico
Dec 17 '18 at 18:22
@egreg Many thanks I sent a mail to the authors, it is fixed.
– O.G.
Dec 29 '18 at 19:40
@egreg Many thanks I sent a mail to the authors, it is fixed.
– O.G.
Dec 29 '18 at 19:40
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.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- 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%2f466170%2fhow-to-troubleshoot-unwanted-white-spaces-smartly%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
@chishimotoji: You must contact the package author to remove the white spaces.
– God Must Be Crazy
Dec 17 '18 at 8:35
@ArtificialStupidity I filed a bug report to one of the maintainers.
– egreg
Dec 17 '18 at 8:37
@egreg: Thank you very much!
– God Must Be Crazy
Dec 17 '18 at 8:38