How can I define a command that uses round parentheses around its arguments?

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP











up vote
11
down vote

favorite
2












I defined a command for probability distributions, for example:



usepackageamsmath
usepackagexstring

DeclarePairedDelimiterXRoundBrackets[1]()#1
newcommandp[1]RoundBracketsStrSubstitute[0]#1mid


This can be used as px. However, I would like to use it as p(x|y). Is there some TeX magic to make that possible?






macros parentheses







share|improve this question





















  • Please state your question clearly and give a minimal working example!
    – Kuttens
    Aug 19 at 15:07














up vote
11
down vote

favorite
2












I defined a command for probability distributions, for example:



usepackageamsmath
usepackagexstring

DeclarePairedDelimiterXRoundBrackets[1]()#1
newcommandp[1]RoundBracketsStrSubstitute[0]#1mid


This can be used as px. However, I would like to use it as p(x|y). Is there some TeX magic to make that possible?






macros parentheses







share|improve this question





















  • Please state your question clearly and give a minimal working example!
    – Kuttens
    Aug 19 at 15:07












up vote
11
down vote

favorite
2









up vote
11
down vote

favorite
2






2





I defined a command for probability distributions, for example:



usepackageamsmath
usepackagexstring

DeclarePairedDelimiterXRoundBrackets[1]()#1
newcommandp[1]RoundBracketsStrSubstitute[0]#1mid


This can be used as px. However, I would like to use it as p(x|y). Is there some TeX magic to make that possible?






macros parentheses







share|improve this question













I defined a command for probability distributions, for example:



usepackageamsmath
usepackagexstring

DeclarePairedDelimiterXRoundBrackets[1]()#1
newcommandp[1]RoundBracketsStrSubstitute[0]#1mid


This can be used as px. However, I would like to use it as p(x|y). Is there some TeX magic to make that possible?






macros parentheses




macros parentheses






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Aug 19 at 15:03









danijar

257212




257212











  • Please state your question clearly and give a minimal working example!
    – Kuttens
    Aug 19 at 15:07
















  • Please state your question clearly and give a minimal working example!
    – Kuttens
    Aug 19 at 15:07















Please state your question clearly and give a minimal working example!
– Kuttens
Aug 19 at 15:07




Please state your question clearly and give a minimal working example!
– Kuttens
Aug 19 at 15:07










3 Answers
3






active

oldest

votes

















up vote
15
down vote



accepted










xparse makes defining a macro with a different kind of mandatory argument delimiter requirement fairly easy. Below, r() does just that.



enter image description here



documentclassarticle

usepackagemathtools,xparse,etoolbox

DeclarePairedDelimiterXRoundBrackets[1]()#1

NewDocumentCommandpr r() %
 defprArg#1% Capture argument in macro
 patchcmdprArgmid% Replace 

begindocument

$pr(a|b)$

enddocument


etoolbox is used to replace | with mid.






share|improve this answer




















  • Great, thank you! This also works with mathematical symbols inside the probability distribution that I had problems with earlier. Is there any reason why defining my probability distributions like this would be discouraged?
    – danijar
    Aug 19 at 16:11











  • How would I modify this to pass the symbol in front of the parentheses (p, q , p_theta, etc) into the command? I know I can just write it before the command but it would be easier to see that it belongs together if it were an argument.
    – danijar
    Aug 19 at 16:22






  • 3




    @danijar: Look at this example.
    – Werner
    Aug 19 at 16:29

















up vote
11
down vote













This also supports the usual options for DeclarePairedDelimiter:



documentclassarticle
usepackageamsmath
usepackagexparse
usepackagemleftright

ExplSyntaxOn

NewDocumentCommandpsOr()
 
 IfBooleanTF#1
 
 mleft(
 danijar_middlevert:
 #3
 mright)
 
 
 group_begin:
 danijar_sizedvert:n #2
 mathopen#2(
 #3
 mathclose#2)
 group_end:
 
 

cs_new_protected:Nn danijar_middlevert:
 __danijar_middle:
 mathcode`
cs_new_protected:Nn __danijar_middle:
 
 ;middlevert;
 

cs_new_protected:Nn danijar_sizedvert:n
 __danijar_mid:
 mathcode`
cs_new_protected:Nn __danijar_mid:
 
 mathrell__danijar_size_tlvert
 

ExplSyntaxOff

begindocument

$p(x) neq p(x|y)$
qquad
$p[big](x) neq p[big](x|y)$
qquad
$p[Big](x) neq p[Big](x|y)$
qquad
$p*(dfracab)neq p*(dfracab|y)$

enddocument


enter image description here



The idea is to locally make | math active, with an appropriate definition, which is ;middlevert; when automatic sizing is declared, or mathrel<size>vert when a manual size is selected.



If you want to add the “P” for “probability”:



documentclassarticle
usepackageamsmath
usepackagexparse
usepackagemleftright

ExplSyntaxOn

NewDocumentCommandpsOr()
 
 operatornameP
 IfBooleanTF#1
 
 mleft(
 danijar_middlevert:
 #3
 mright)
 
 
 group_begin:
 danijar_sizedvert:n #2
 mathopen#2(
 #3
 mathclose#2)
 group_end:
 
 

cs_new_protected:Nn danijar_middlevert:
 __danijar_middle:
 mathcode`
cs_new_protected:Nn __danijar_middle:
 
 ;middlevert;
 

cs_new_protected:Nn danijar_sizedvert:n
 __danijar_mid:
 mathcode`
cs_new_protected:Nn __danijar_mid:
 
 mathrell__danijar_size_tlvert
 

ExplSyntaxOff

begindocument

$p(x) neq p(x|y)$

$p[big](x) neq p[big](x|y)$

$p[Big](x) neq p[Big](x|y)$

$p*(dfracab)neq p*(dfracab|y)$

enddocument


enter image description here






share|improve this answer






















  • Wow, that's amazing. It's a bit more than what I need right now, but if I need symbols of vastly different height inside the parentheses I can go back here and replace the macro with this one.
    – danijar
    Aug 19 at 16:24

















up vote
9
down vote













Probably @Werner's answer is the way to go (robust and easily modified), but in this case, plain TeX also seems to work: 



documentclassarticle

defpr(#1|#2)(#1 mid #2)

begindocument

$pr(a|b)$
$pr(a_r|b^2)$

enddocument


resulting output






share|improve this answer
















  • 2




    This makes the use of | also mandatory (for conditional probability), which might not be the case in general. You'll have to update the definition of pr to accommodate for that conditional use.
    – Werner
    Aug 19 at 15:40










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',
convertImagesToLinks: false,
noModals: false,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);



);













 

draft saved


draft discarded


















StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2ftex.stackexchange.com%2fquestions%2f446677%2fhow-can-i-define-a-command-that-uses-round-parentheses-around-its-arguments%23new-answer', 'question_page');

);

Post as a guest

















3 Answers
3






active

oldest

votes








3 Answers
3






active

oldest

votes









active

oldest

votes






active

oldest

votes








up vote
15
down vote



accepted










xparse makes defining a macro with a different kind of mandatory argument delimiter requirement fairly easy. Below, r() does just that.



enter image description here



documentclassarticle

usepackagemathtools,xparse,etoolbox

DeclarePairedDelimiterXRoundBrackets[1]()#1

NewDocumentCommandpr r() %
 defprArg#1% Capture argument in macro
 patchcmdprArgmid% Replace 

begindocument

$pr(a|b)$

enddocument


etoolbox is used to replace | with mid.






share|improve this answer




















  • Great, thank you! This also works with mathematical symbols inside the probability distribution that I had problems with earlier. Is there any reason why defining my probability distributions like this would be discouraged?
    – danijar
    Aug 19 at 16:11











  • How would I modify this to pass the symbol in front of the parentheses (p, q , p_theta, etc) into the command? I know I can just write it before the command but it would be easier to see that it belongs together if it were an argument.
    – danijar
    Aug 19 at 16:22






  • 3




    @danijar: Look at this example.
    – Werner
    Aug 19 at 16:29














up vote
15
down vote



accepted










xparse makes defining a macro with a different kind of mandatory argument delimiter requirement fairly easy. Below, r() does just that.



enter image description here



documentclassarticle

usepackagemathtools,xparse,etoolbox

DeclarePairedDelimiterXRoundBrackets[1]()#1

NewDocumentCommandpr r() %
 defprArg#1% Capture argument in macro
 patchcmdprArgmid% Replace 

begindocument

$pr(a|b)$

enddocument


etoolbox is used to replace | with mid.






share|improve this answer




















  • Great, thank you! This also works with mathematical symbols inside the probability distribution that I had problems with earlier. Is there any reason why defining my probability distributions like this would be discouraged?
    – danijar
    Aug 19 at 16:11











  • How would I modify this to pass the symbol in front of the parentheses (p, q , p_theta, etc) into the command? I know I can just write it before the command but it would be easier to see that it belongs together if it were an argument.
    – danijar
    Aug 19 at 16:22






  • 3




    @danijar: Look at this example.
    – Werner
    Aug 19 at 16:29












up vote
15
down vote



accepted







up vote
15
down vote



accepted






xparse makes defining a macro with a different kind of mandatory argument delimiter requirement fairly easy. Below, r() does just that.



enter image description here



documentclassarticle

usepackagemathtools,xparse,etoolbox

DeclarePairedDelimiterXRoundBrackets[1]()#1

NewDocumentCommandpr r() %
 defprArg#1% Capture argument in macro
 patchcmdprArgmid% Replace 

begindocument

$pr(a|b)$

enddocument


etoolbox is used to replace | with mid.






share|improve this answer












xparse makes defining a macro with a different kind of mandatory argument delimiter requirement fairly easy. Below, r() does just that.



enter image description here



documentclassarticle

usepackagemathtools,xparse,etoolbox

DeclarePairedDelimiterXRoundBrackets[1]()#1

NewDocumentCommandpr r() %
 defprArg#1% Capture argument in macro
 patchcmdprArgmid% Replace 

begindocument

$pr(a|b)$

enddocument


etoolbox is used to replace | with mid.







share|improve this answer












share|improve this answer



share|improve this answer










answered Aug 19 at 15:16









Werner

421k589171588




421k589171588











  • Great, thank you! This also works with mathematical symbols inside the probability distribution that I had problems with earlier. Is there any reason why defining my probability distributions like this would be discouraged?
    – danijar
    Aug 19 at 16:11











  • How would I modify this to pass the symbol in front of the parentheses (p, q , p_theta, etc) into the command? I know I can just write it before the command but it would be easier to see that it belongs together if it were an argument.
    – danijar
    Aug 19 at 16:22






  • 3




    @danijar: Look at this example.
    – Werner
    Aug 19 at 16:29
















  • Great, thank you! This also works with mathematical symbols inside the probability distribution that I had problems with earlier. Is there any reason why defining my probability distributions like this would be discouraged?
    – danijar
    Aug 19 at 16:11











  • How would I modify this to pass the symbol in front of the parentheses (p, q , p_theta, etc) into the command? I know I can just write it before the command but it would be easier to see that it belongs together if it were an argument.
    – danijar
    Aug 19 at 16:22






  • 3




    @danijar: Look at this example.
    – Werner
    Aug 19 at 16:29















Great, thank you! This also works with mathematical symbols inside the probability distribution that I had problems with earlier. Is there any reason why defining my probability distributions like this would be discouraged?
– danijar
Aug 19 at 16:11





Great, thank you! This also works with mathematical symbols inside the probability distribution that I had problems with earlier. Is there any reason why defining my probability distributions like this would be discouraged?
– danijar
Aug 19 at 16:11













How would I modify this to pass the symbol in front of the parentheses (p, q , p_theta, etc) into the command? I know I can just write it before the command but it would be easier to see that it belongs together if it were an argument.
– danijar
Aug 19 at 16:22




How would I modify this to pass the symbol in front of the parentheses (p, q , p_theta, etc) into the command? I know I can just write it before the command but it would be easier to see that it belongs together if it were an argument.
– danijar
Aug 19 at 16:22




3




3




@danijar: Look at this example.
– Werner
Aug 19 at 16:29




@danijar: Look at this example.
– Werner
Aug 19 at 16:29










up vote
11
down vote













This also supports the usual options for DeclarePairedDelimiter:



documentclassarticle
usepackageamsmath
usepackagexparse
usepackagemleftright

ExplSyntaxOn

NewDocumentCommandpsOr()
 
 IfBooleanTF#1
 
 mleft(
 danijar_middlevert:
 #3
 mright)
 
 
 group_begin:
 danijar_sizedvert:n #2
 mathopen#2(
 #3
 mathclose#2)
 group_end:
 
 

cs_new_protected:Nn danijar_middlevert:
 __danijar_middle:
 mathcode`
cs_new_protected:Nn __danijar_middle:
 
 ;middlevert;
 

cs_new_protected:Nn danijar_sizedvert:n
 __danijar_mid:
 mathcode`
cs_new_protected:Nn __danijar_mid:
 
 mathrell__danijar_size_tlvert
 

ExplSyntaxOff

begindocument

$p(x) neq p(x|y)$
qquad
$p[big](x) neq p[big](x|y)$
qquad
$p[Big](x) neq p[Big](x|y)$
qquad
$p*(dfracab)neq p*(dfracab|y)$

enddocument


enter image description here



The idea is to locally make | math active, with an appropriate definition, which is ;middlevert; when automatic sizing is declared, or mathrel<size>vert when a manual size is selected.



If you want to add the “P” for “probability”:



documentclassarticle
usepackageamsmath
usepackagexparse
usepackagemleftright

ExplSyntaxOn

NewDocumentCommandpsOr()
 
 operatornameP
 IfBooleanTF#1
 
 mleft(
 danijar_middlevert:
 #3
 mright)
 
 
 group_begin:
 danijar_sizedvert:n #2
 mathopen#2(
 #3
 mathclose#2)
 group_end:
 
 

cs_new_protected:Nn danijar_middlevert:
 __danijar_middle:
 mathcode`
cs_new_protected:Nn __danijar_middle:
 
 ;middlevert;
 

cs_new_protected:Nn danijar_sizedvert:n
 __danijar_mid:
 mathcode`
cs_new_protected:Nn __danijar_mid:
 
 mathrell__danijar_size_tlvert
 

ExplSyntaxOff

begindocument

$p(x) neq p(x|y)$

$p[big](x) neq p[big](x|y)$

$p[Big](x) neq p[Big](x|y)$

$p*(dfracab)neq p*(dfracab|y)$

enddocument


enter image description here






share|improve this answer






















  • Wow, that's amazing. It's a bit more than what I need right now, but if I need symbols of vastly different height inside the parentheses I can go back here and replace the macro with this one.
    – danijar
    Aug 19 at 16:24














up vote
11
down vote













This also supports the usual options for DeclarePairedDelimiter:



documentclassarticle
usepackageamsmath
usepackagexparse
usepackagemleftright

ExplSyntaxOn

NewDocumentCommandpsOr()
 
 IfBooleanTF#1
 
 mleft(
 danijar_middlevert:
 #3
 mright)
 
 
 group_begin:
 danijar_sizedvert:n #2
 mathopen#2(
 #3
 mathclose#2)
 group_end:
 
 

cs_new_protected:Nn danijar_middlevert:
 __danijar_middle:
 mathcode`
cs_new_protected:Nn __danijar_middle:
 
 ;middlevert;
 

cs_new_protected:Nn danijar_sizedvert:n
 __danijar_mid:
 mathcode`
cs_new_protected:Nn __danijar_mid:
 
 mathrell__danijar_size_tlvert
 

ExplSyntaxOff

begindocument

$p(x) neq p(x|y)$
qquad
$p[big](x) neq p[big](x|y)$
qquad
$p[Big](x) neq p[Big](x|y)$
qquad
$p*(dfracab)neq p*(dfracab|y)$

enddocument


enter image description here



The idea is to locally make | math active, with an appropriate definition, which is ;middlevert; when automatic sizing is declared, or mathrel<size>vert when a manual size is selected.



If you want to add the “P” for “probability”:



documentclassarticle
usepackageamsmath
usepackagexparse
usepackagemleftright

ExplSyntaxOn

NewDocumentCommandpsOr()
 
 operatornameP
 IfBooleanTF#1
 
 mleft(
 danijar_middlevert:
 #3
 mright)
 
 
 group_begin:
 danijar_sizedvert:n #2
 mathopen#2(
 #3
 mathclose#2)
 group_end:
 
 

cs_new_protected:Nn danijar_middlevert:
 __danijar_middle:
 mathcode`
cs_new_protected:Nn __danijar_middle:
 
 ;middlevert;
 

cs_new_protected:Nn danijar_sizedvert:n
 __danijar_mid:
 mathcode`
cs_new_protected:Nn __danijar_mid:
 
 mathrell__danijar_size_tlvert
 

ExplSyntaxOff

begindocument

$p(x) neq p(x|y)$

$p[big](x) neq p[big](x|y)$

$p[Big](x) neq p[Big](x|y)$

$p*(dfracab)neq p*(dfracab|y)$

enddocument


enter image description here






share|improve this answer






















  • Wow, that's amazing. It's a bit more than what I need right now, but if I need symbols of vastly different height inside the parentheses I can go back here and replace the macro with this one.
    – danijar
    Aug 19 at 16:24












up vote
11
down vote










up vote
11
down vote









This also supports the usual options for DeclarePairedDelimiter:



documentclassarticle
usepackageamsmath
usepackagexparse
usepackagemleftright

ExplSyntaxOn

NewDocumentCommandpsOr()
 
 IfBooleanTF#1
 
 mleft(
 danijar_middlevert:
 #3
 mright)
 
 
 group_begin:
 danijar_sizedvert:n #2
 mathopen#2(
 #3
 mathclose#2)
 group_end:
 
 

cs_new_protected:Nn danijar_middlevert:
 __danijar_middle:
 mathcode`
cs_new_protected:Nn __danijar_middle:
 
 ;middlevert;
 

cs_new_protected:Nn danijar_sizedvert:n
 __danijar_mid:
 mathcode`
cs_new_protected:Nn __danijar_mid:
 
 mathrell__danijar_size_tlvert
 

ExplSyntaxOff

begindocument

$p(x) neq p(x|y)$
qquad
$p[big](x) neq p[big](x|y)$
qquad
$p[Big](x) neq p[Big](x|y)$
qquad
$p*(dfracab)neq p*(dfracab|y)$

enddocument


enter image description here



The idea is to locally make | math active, with an appropriate definition, which is ;middlevert; when automatic sizing is declared, or mathrel<size>vert when a manual size is selected.



If you want to add the “P” for “probability”:



documentclassarticle
usepackageamsmath
usepackagexparse
usepackagemleftright

ExplSyntaxOn

NewDocumentCommandpsOr()
 
 operatornameP
 IfBooleanTF#1
 
 mleft(
 danijar_middlevert:
 #3
 mright)
 
 
 group_begin:
 danijar_sizedvert:n #2
 mathopen#2(
 #3
 mathclose#2)
 group_end:
 
 

cs_new_protected:Nn danijar_middlevert:
 __danijar_middle:
 mathcode`
cs_new_protected:Nn __danijar_middle:
 
 ;middlevert;
 

cs_new_protected:Nn danijar_sizedvert:n
 __danijar_mid:
 mathcode`
cs_new_protected:Nn __danijar_mid:
 
 mathrell__danijar_size_tlvert
 

ExplSyntaxOff

begindocument

$p(x) neq p(x|y)$

$p[big](x) neq p[big](x|y)$

$p[Big](x) neq p[Big](x|y)$

$p*(dfracab)neq p*(dfracab|y)$

enddocument


enter image description here






share|improve this answer














This also supports the usual options for DeclarePairedDelimiter:



documentclassarticle
usepackageamsmath
usepackagexparse
usepackagemleftright

ExplSyntaxOn

NewDocumentCommandpsOr()
 
 IfBooleanTF#1
 
 mleft(
 danijar_middlevert:
 #3
 mright)
 
 
 group_begin:
 danijar_sizedvert:n #2
 mathopen#2(
 #3
 mathclose#2)
 group_end:
 
 

cs_new_protected:Nn danijar_middlevert:
 __danijar_middle:
 mathcode`
cs_new_protected:Nn __danijar_middle:
 
 ;middlevert;
 

cs_new_protected:Nn danijar_sizedvert:n
 __danijar_mid:
 mathcode`
cs_new_protected:Nn __danijar_mid:
 
 mathrell__danijar_size_tlvert
 

ExplSyntaxOff

begindocument

$p(x) neq p(x|y)$
qquad
$p[big](x) neq p[big](x|y)$
qquad
$p[Big](x) neq p[Big](x|y)$
qquad
$p*(dfracab)neq p*(dfracab|y)$

enddocument


enter image description here



The idea is to locally make | math active, with an appropriate definition, which is ;middlevert; when automatic sizing is declared, or mathrel<size>vert when a manual size is selected.



If you want to add the “P” for “probability”:



documentclassarticle
usepackageamsmath
usepackagexparse
usepackagemleftright

ExplSyntaxOn

NewDocumentCommandpsOr()
 
 operatornameP
 IfBooleanTF#1
 
 mleft(
 danijar_middlevert:
 #3
 mright)
 
 
 group_begin:
 danijar_sizedvert:n #2
 mathopen#2(
 #3
 mathclose#2)
 group_end:
 
 

cs_new_protected:Nn danijar_middlevert:
 __danijar_middle:
 mathcode`
cs_new_protected:Nn __danijar_middle:
 
 ;middlevert;
 

cs_new_protected:Nn danijar_sizedvert:n
 __danijar_mid:
 mathcode`
cs_new_protected:Nn __danijar_mid:
 
 mathrell__danijar_size_tlvert
 

ExplSyntaxOff

begindocument

$p(x) neq p(x|y)$

$p[big](x) neq p[big](x|y)$

$p[Big](x) neq p[Big](x|y)$

$p*(dfracab)neq p*(dfracab|y)$

enddocument


enter image description here







share|improve this answer














share|improve this answer



share|improve this answer








edited Aug 19 at 16:17

























answered Aug 19 at 16:12









egreg

683k8418203066




683k8418203066











  • Wow, that's amazing. It's a bit more than what I need right now, but if I need symbols of vastly different height inside the parentheses I can go back here and replace the macro with this one.
    – danijar
    Aug 19 at 16:24
















  • Wow, that's amazing. It's a bit more than what I need right now, but if I need symbols of vastly different height inside the parentheses I can go back here and replace the macro with this one.
    – danijar
    Aug 19 at 16:24















Wow, that's amazing. It's a bit more than what I need right now, but if I need symbols of vastly different height inside the parentheses I can go back here and replace the macro with this one.
– danijar
Aug 19 at 16:24




Wow, that's amazing. It's a bit more than what I need right now, but if I need symbols of vastly different height inside the parentheses I can go back here and replace the macro with this one.
– danijar
Aug 19 at 16:24










up vote
9
down vote













Probably @Werner's answer is the way to go (robust and easily modified), but in this case, plain TeX also seems to work: 



documentclassarticle

defpr(#1|#2)(#1 mid #2)

begindocument

$pr(a|b)$
$pr(a_r|b^2)$

enddocument


resulting output






share|improve this answer
















  • 2




    This makes the use of | also mandatory (for conditional probability), which might not be the case in general. You'll have to update the definition of pr to accommodate for that conditional use.
    – Werner
    Aug 19 at 15:40














up vote
9
down vote













Probably @Werner's answer is the way to go (robust and easily modified), but in this case, plain TeX also seems to work: 



documentclassarticle

defpr(#1|#2)(#1 mid #2)

begindocument

$pr(a|b)$
$pr(a_r|b^2)$

enddocument


resulting output






share|improve this answer
















  • 2




    This makes the use of | also mandatory (for conditional probability), which might not be the case in general. You'll have to update the definition of pr to accommodate for that conditional use.
    – Werner
    Aug 19 at 15:40












up vote
9
down vote










up vote
9
down vote









Probably @Werner's answer is the way to go (robust and easily modified), but in this case, plain TeX also seems to work: 



documentclassarticle

defpr(#1|#2)(#1 mid #2)

begindocument

$pr(a|b)$
$pr(a_r|b^2)$

enddocument


resulting output






share|improve this answer












Probably @Werner's answer is the way to go (robust and easily modified), but in this case, plain TeX also seems to work: 



documentclassarticle

defpr(#1|#2)(#1 mid #2)

begindocument

$pr(a|b)$
$pr(a_r|b^2)$

enddocument


resulting output







share|improve this answer












share|improve this answer



share|improve this answer










answered Aug 19 at 15:33









Rmano

6,97121446




6,97121446







  • 2




    This makes the use of | also mandatory (for conditional probability), which might not be the case in general. You'll have to update the definition of pr to accommodate for that conditional use.
    – Werner
    Aug 19 at 15:40












  • 2




    This makes the use of | also mandatory (for conditional probability), which might not be the case in general. You'll have to update the definition of pr to accommodate for that conditional use.
    – Werner
    Aug 19 at 15:40







2




2




This makes the use of | also mandatory (for conditional probability), which might not be the case in general. You'll have to update the definition of pr to accommodate for that conditional use.
– Werner
Aug 19 at 15:40




This makes the use of | also mandatory (for conditional probability), which might not be the case in general. You'll have to update the definition of pr to accommodate for that conditional use.
– Werner
Aug 19 at 15:40

















 

draft saved


draft discarded















































 


draft saved


draft discarded














StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2ftex.stackexchange.com%2fquestions%2f446677%2fhow-can-i-define-a-command-that-uses-round-parentheses-around-its-arguments%23new-answer', 'question_page');

);

Post as a guest
































































-

Popular posts from this blog

How to check contact read email or not when send email to Individual?

Image
Clash Royale CLAN TAG #URR8PPP up vote 1 down vote favorite I'm using WordPress 4.9.8, CiviCRM to 5.5.1, I usually send email to contact by Search> Find contacts View contact details Action> Send email Send email ok, Contact received mail ok like picture But status only Email sent though contact read email or not. So, can CiviCRM can change status to Email read when contact read email? wordpress email share | improve this question asked Sep 26 at 0:12 ToanLuong 49 9 add a comment  |  up vote 1 down vote favorite I'm using WordPress 4.9.8, CiviCRM to 5.5.1, I usually send email to contact by Search> Find contacts View contact details Action> Send email Send email ok, Contact received mail ok like picture But status only Email sent though contact read email or not. So, can CiviCRM can change status to Email read when contact read email? wordpress email share | improve this questi...
Read more

Displaying single band from multi-band raster using QGIS

Image
Clash Royale CLAN TAG #URR8PPP 1 How can I extract a single band from multi-band raster in QGIS? I have an remote sensed image which has 6 bands (including NDVI band), I want to display each band separately, but have no idea how to do. I have seen some questions similar here but none worked for me. The original image (has 6 bands) is: I want to display the band 6 which should be like this: But I tried gdal_translate, and couldn't get the correct result. What I have got is: qgis raster multi-band share | improve this question edited Mar 5 at 0:53 Summer asked Mar 4 at 6:42 Summer Summer 23 6 Is this any help gis.stackexchange.com/questions/220658/… ? if not gis.stackexchange.com/questions/62133/… might help. – Michael Stimson Mar 4 at 6:46 Thanks for answering but when I used gdal_translate, qgis showed that 'Error 4: Kayena.tif: No such file or directory". Would you know how to fi...
Read more

How many registers does an x86_64 CPU actually have?

Image
Clash Royale CLAN TAG #URR8PPP up vote 2 down vote favorite I am currently learning reverse engineering and am studying the flags register. I had in my mind that rflags was just another name for one of the 16 general purpose registers, for example rax or rbx . But it looks like rflags is actually an additional register. So that makes 17 registers in total... how many more could there be? I have spent at least an hour on this and found numerous different answers. The best answer so far is this, which says that there are 40 registers in total. 16 General Purpose Registers 2 Status Registers 6 Code Segment Registers 16 SSE Registers 8 FPU/MMX Registers But if I add that up, I get 48. Could anybody provide an official answer on how many registers an x86_64 CPU has (e.g. an Intel i7). Additionally, I have seen references to 'hardware' and 'architectural' registers. What are those registers and how many are there? register x86-64 share | improve this...
Read more