Macros dv and pdv eat the subsequent paranthesis argument
The physics package
has the macros dv
and pdv
which are great but I have a small problem with them.
If an argument with parenthesis included right after them they eat the whole argument. If there is a space in between the argument everything works fine but I want to prevent this happening all together. I checked the documentation but couldn't find a solution. So an example would be
documentclass{article}
usepackage{physics}
begin{document}
[dv{x}{t}(y^2-5) qquad dv{x}{t} (y^2-5) qquad dv{x}{t} ]
end{document}
I want the output of the equation on the left to be the same as the middle one.
brackets physics
add a comment |
The physics package
has the macros dv
and pdv
which are great but I have a small problem with them.
If an argument with parenthesis included right after them they eat the whole argument. If there is a space in between the argument everything works fine but I want to prevent this happening all together. I checked the documentation but couldn't find a solution. So an example would be
documentclass{article}
usepackage{physics}
begin{document}
[dv{x}{t}(y^2-5) qquad dv{x}{t} (y^2-5) qquad dv{x}{t} ]
end{document}
I want the output of the equation on the left to be the same as the middle one.
brackets physics
add a comment |
The physics package
has the macros dv
and pdv
which are great but I have a small problem with them.
If an argument with parenthesis included right after them they eat the whole argument. If there is a space in between the argument everything works fine but I want to prevent this happening all together. I checked the documentation but couldn't find a solution. So an example would be
documentclass{article}
usepackage{physics}
begin{document}
[dv{x}{t}(y^2-5) qquad dv{x}{t} (y^2-5) qquad dv{x}{t} ]
end{document}
I want the output of the equation on the left to be the same as the middle one.
brackets physics
The physics package
has the macros dv
and pdv
which are great but I have a small problem with them.
If an argument with parenthesis included right after them they eat the whole argument. If there is a space in between the argument everything works fine but I want to prevent this happening all together. I checked the documentation but couldn't find a solution. So an example would be
documentclass{article}
usepackage{physics}
begin{document}
[dv{x}{t}(y^2-5) qquad dv{x}{t} (y^2-5) qquad dv{x}{t} ]
end{document}
I want the output of the equation on the left to be the same as the middle one.
brackets physics
brackets physics
edited 13 mins ago
Calvin Kent
asked 31 mins ago
Calvin KentCalvin Kent
135
135
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
That's because dv
(which is a shorthand for derivative
) is defined as
DeclareDocumentCommandderivative{ s o m g d() }
{ % Total derivative
% s: star for flatfrac flat derivative
% o: optional n for nth derivative
% m: mandatory (x in df/dx)
% g: optional (f in df/dx)
% d: long-form d/dx(...)
Even if the optional g
-type argument is given (as in your case) the command will scan further for an optional delimited d
-type argument which is delimited by (
and )
(maybe not the best choice in a mathematical context). To circumvent this you don't really have a choice but to insert a space.
At the same time I'd like to note that the physics
package does not really help me writing physics formulae and I'm usually much better off typing the stuff by hand using the amsmath
macros.
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%2f470819%2fmacros-dv-and-pdv-eat-the-subsequent-paranthesis-argument%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
That's because dv
(which is a shorthand for derivative
) is defined as
DeclareDocumentCommandderivative{ s o m g d() }
{ % Total derivative
% s: star for flatfrac flat derivative
% o: optional n for nth derivative
% m: mandatory (x in df/dx)
% g: optional (f in df/dx)
% d: long-form d/dx(...)
Even if the optional g
-type argument is given (as in your case) the command will scan further for an optional delimited d
-type argument which is delimited by (
and )
(maybe not the best choice in a mathematical context). To circumvent this you don't really have a choice but to insert a space.
At the same time I'd like to note that the physics
package does not really help me writing physics formulae and I'm usually much better off typing the stuff by hand using the amsmath
macros.
add a comment |
That's because dv
(which is a shorthand for derivative
) is defined as
DeclareDocumentCommandderivative{ s o m g d() }
{ % Total derivative
% s: star for flatfrac flat derivative
% o: optional n for nth derivative
% m: mandatory (x in df/dx)
% g: optional (f in df/dx)
% d: long-form d/dx(...)
Even if the optional g
-type argument is given (as in your case) the command will scan further for an optional delimited d
-type argument which is delimited by (
and )
(maybe not the best choice in a mathematical context). To circumvent this you don't really have a choice but to insert a space.
At the same time I'd like to note that the physics
package does not really help me writing physics formulae and I'm usually much better off typing the stuff by hand using the amsmath
macros.
add a comment |
That's because dv
(which is a shorthand for derivative
) is defined as
DeclareDocumentCommandderivative{ s o m g d() }
{ % Total derivative
% s: star for flatfrac flat derivative
% o: optional n for nth derivative
% m: mandatory (x in df/dx)
% g: optional (f in df/dx)
% d: long-form d/dx(...)
Even if the optional g
-type argument is given (as in your case) the command will scan further for an optional delimited d
-type argument which is delimited by (
and )
(maybe not the best choice in a mathematical context). To circumvent this you don't really have a choice but to insert a space.
At the same time I'd like to note that the physics
package does not really help me writing physics formulae and I'm usually much better off typing the stuff by hand using the amsmath
macros.
That's because dv
(which is a shorthand for derivative
) is defined as
DeclareDocumentCommandderivative{ s o m g d() }
{ % Total derivative
% s: star for flatfrac flat derivative
% o: optional n for nth derivative
% m: mandatory (x in df/dx)
% g: optional (f in df/dx)
% d: long-form d/dx(...)
Even if the optional g
-type argument is given (as in your case) the command will scan further for an optional delimited d
-type argument which is delimited by (
and )
(maybe not the best choice in a mathematical context). To circumvent this you don't really have a choice but to insert a space.
At the same time I'd like to note that the physics
package does not really help me writing physics formulae and I'm usually much better off typing the stuff by hand using the amsmath
macros.
answered 24 secs ago
Henri MenkeHenri Menke
71.2k8157264
71.2k8157264
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%2f470819%2fmacros-dv-and-pdv-eat-the-subsequent-paranthesis-argument%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