Is there an advantage in converting user provided hfuzz values to sp?
I was looking through the fancyvrb
code. At a point it defines a key hfuzz
as follows:
define@key{FV}{hfuzz}{%
@tempdima=#1relax
edeffv_hfuzz{number@tempdima sp}}}
fvset{hfuzz=2pt}
What is the reason to convert it to sp?
tex-core
add a comment |
I was looking through the fancyvrb
code. At a point it defines a key hfuzz
as follows:
define@key{FV}{hfuzz}{%
@tempdima=#1relax
edeffv_hfuzz{number@tempdima sp}}}
fvset{hfuzz=2pt}
What is the reason to convert it to sp?
tex-core
add a comment |
I was looking through the fancyvrb
code. At a point it defines a key hfuzz
as follows:
define@key{FV}{hfuzz}{%
@tempdima=#1relax
edeffv_hfuzz{number@tempdima sp}}}
fvset{hfuzz=2pt}
What is the reason to convert it to sp?
tex-core
I was looking through the fancyvrb
code. At a point it defines a key hfuzz
as follows:
define@key{FV}{hfuzz}{%
@tempdima=#1relax
edeffv_hfuzz{number@tempdima sp}}}
fvset{hfuzz=2pt}
What is the reason to convert it to sp?
tex-core
tex-core
asked 54 mins ago
Yiannis Lazarides
91.9k20232511
91.9k20232511
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
Suppose you do
fvset{1em}
in the preamble.
If the code just did deffv_hfuzz{#1}
the value of em
current at point of usage would be used (maybe influenced by some footnotesize
or similar declaration).
The code in fancyvrb.sty
, instead, freezes the value at point of definition.
You also get an error in case of an input such as fvset{hfuzz=2}
.
On the other hand,
edeffv_hfuzz{the@tempdima}
would be as good.
Thanks and Merry Christmas, so no advantage in converting tosp
units?
– Yiannis Lazarides
33 mins ago
@YiannisLazarides I see none at all: the conversion frompt
tosp
is completely predictable. Maybe the author likes integers better than floating point numbers.
– egreg
31 mins ago
Thought so too! Thanks for confirming it.
– Yiannis Lazarides
30 mins ago
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%2f467315%2fis-there-an-advantage-in-converting-user-provided-hfuzz-values-to-sp%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
Suppose you do
fvset{1em}
in the preamble.
If the code just did deffv_hfuzz{#1}
the value of em
current at point of usage would be used (maybe influenced by some footnotesize
or similar declaration).
The code in fancyvrb.sty
, instead, freezes the value at point of definition.
You also get an error in case of an input such as fvset{hfuzz=2}
.
On the other hand,
edeffv_hfuzz{the@tempdima}
would be as good.
Thanks and Merry Christmas, so no advantage in converting tosp
units?
– Yiannis Lazarides
33 mins ago
@YiannisLazarides I see none at all: the conversion frompt
tosp
is completely predictable. Maybe the author likes integers better than floating point numbers.
– egreg
31 mins ago
Thought so too! Thanks for confirming it.
– Yiannis Lazarides
30 mins ago
add a comment |
Suppose you do
fvset{1em}
in the preamble.
If the code just did deffv_hfuzz{#1}
the value of em
current at point of usage would be used (maybe influenced by some footnotesize
or similar declaration).
The code in fancyvrb.sty
, instead, freezes the value at point of definition.
You also get an error in case of an input such as fvset{hfuzz=2}
.
On the other hand,
edeffv_hfuzz{the@tempdima}
would be as good.
Thanks and Merry Christmas, so no advantage in converting tosp
units?
– Yiannis Lazarides
33 mins ago
@YiannisLazarides I see none at all: the conversion frompt
tosp
is completely predictable. Maybe the author likes integers better than floating point numbers.
– egreg
31 mins ago
Thought so too! Thanks for confirming it.
– Yiannis Lazarides
30 mins ago
add a comment |
Suppose you do
fvset{1em}
in the preamble.
If the code just did deffv_hfuzz{#1}
the value of em
current at point of usage would be used (maybe influenced by some footnotesize
or similar declaration).
The code in fancyvrb.sty
, instead, freezes the value at point of definition.
You also get an error in case of an input such as fvset{hfuzz=2}
.
On the other hand,
edeffv_hfuzz{the@tempdima}
would be as good.
Suppose you do
fvset{1em}
in the preamble.
If the code just did deffv_hfuzz{#1}
the value of em
current at point of usage would be used (maybe influenced by some footnotesize
or similar declaration).
The code in fancyvrb.sty
, instead, freezes the value at point of definition.
You also get an error in case of an input such as fvset{hfuzz=2}
.
On the other hand,
edeffv_hfuzz{the@tempdima}
would be as good.
answered 42 mins ago
egreg
707k8618793160
707k8618793160
Thanks and Merry Christmas, so no advantage in converting tosp
units?
– Yiannis Lazarides
33 mins ago
@YiannisLazarides I see none at all: the conversion frompt
tosp
is completely predictable. Maybe the author likes integers better than floating point numbers.
– egreg
31 mins ago
Thought so too! Thanks for confirming it.
– Yiannis Lazarides
30 mins ago
add a comment |
Thanks and Merry Christmas, so no advantage in converting tosp
units?
– Yiannis Lazarides
33 mins ago
@YiannisLazarides I see none at all: the conversion frompt
tosp
is completely predictable. Maybe the author likes integers better than floating point numbers.
– egreg
31 mins ago
Thought so too! Thanks for confirming it.
– Yiannis Lazarides
30 mins ago
Thanks and Merry Christmas, so no advantage in converting to
sp
units?– Yiannis Lazarides
33 mins ago
Thanks and Merry Christmas, so no advantage in converting to
sp
units?– Yiannis Lazarides
33 mins ago
@YiannisLazarides I see none at all: the conversion from
pt
to sp
is completely predictable. Maybe the author likes integers better than floating point numbers.– egreg
31 mins ago
@YiannisLazarides I see none at all: the conversion from
pt
to sp
is completely predictable. Maybe the author likes integers better than floating point numbers.– egreg
31 mins ago
Thought so too! Thanks for confirming it.
– Yiannis Lazarides
30 mins ago
Thought so too! Thanks for confirming it.
– Yiannis Lazarides
30 mins ago
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%2f467315%2fis-there-an-advantage-in-converting-user-provided-hfuzz-values-to-sp%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