How to write a macro that is braces sensitive?Context-sensitive newline macroCreate my own NSDHow to write a...

Why do falling prices hurt debtors?

Is a conference paper whose proceedings will be published in IEEE Xplore counted as a publication?

Watching something be written to a file live with tail

Pattern match does not work in bash script

What defenses are there against being summoned by the Gate spell?

tikz: show 0 at the axis origin

What does it mean to describe someone as a butt steak?

Why don't electron-positron collisions release infinite energy?

What would happen to a modern skyscraper if it rains micro blackholes?

Is a tag line useful on a cover?

Adding span tags within wp_list_pages list items

Is it important to consider tone, melody, and musical form while writing a song?

"to be prejudice towards/against someone" vs "to be prejudiced against/towards someone"

Is it legal for company to use my work email to pretend I still work there?

TGV timetables / schedules?

What's the point of deactivating Num Lock on login screens?

How did the USSR manage to innovate in an environment characterized by government censorship and high bureaucracy?

Can an x86 CPU running in real mode be considered to be basically an 8086 CPU?

Replacing matching entries in one column of a file by another column from a different file

How do we improve the relationship with a client software team that performs poorly and is becoming less collaborative?

"You are your self first supporter", a more proper way to say it

The use of multiple foreign keys on same column in SQL Server

Minkowski space

The Clique vs. Independent Set Problem



How to write a macro that is braces sensitive?


Context-sensitive newline macroCreate my own NSDHow to write a parameter-driven macro?How can I create a better cryptogram environment?How to write a TeX macro that accepts a number or a count register as argument?Macro to close all open environments, groups and argument delimitersTexshop macro for bracesWrite an unpar macroInput length sensitive optional argument macrocontext-sensitive macro: look behind?













2















In the xparse package, there is the g type of argument which captures things inside a pair of TeX group tokens. This makes it possible to define commands foo that behaves differently for foo{a} and foo a. I am interested in whether such type of macro is possible in plain TeX (I guess yes) and if it is possible, how can it be implemented. I am new to plain TeX and I appreciate detailed explanation of the workflow of such a macro. I would also be happy to learn about other possibilities such as in e-TeX instead of plain TeX.










share|improve this question







New contributor




Weijun Zhou is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.





















  • It's possible, but it's bad syntax. Under normal TeX conventions, foo a and foo{a} should be considered equivalent (when the argument consists of a single token as in this case).

    – egreg
    42 mins ago













  • Thank you for your quick reply. I know it's bad syntax otherwise xparse would not declare it as obsolete, but it is (extensively) used in e.g. physics package. I am just not sure about whether it can be done in plain, or it requires some features of the engine.

    – Weijun Zhou
    38 mins ago








  • 1





    It's indeed used in physics. My opinion about the package is that it has good ideas, but I can't recommend its usage. The weird syntax is just one among the several reasons for not recommending it.

    – egreg
    37 mins ago













  • Due to the weird syntax I end up adding relax here and there ... but I guess I will still use it.

    – Weijun Zhou
    29 mins ago
















2















In the xparse package, there is the g type of argument which captures things inside a pair of TeX group tokens. This makes it possible to define commands foo that behaves differently for foo{a} and foo a. I am interested in whether such type of macro is possible in plain TeX (I guess yes) and if it is possible, how can it be implemented. I am new to plain TeX and I appreciate detailed explanation of the workflow of such a macro. I would also be happy to learn about other possibilities such as in e-TeX instead of plain TeX.










share|improve this question







New contributor




Weijun Zhou is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.





















  • It's possible, but it's bad syntax. Under normal TeX conventions, foo a and foo{a} should be considered equivalent (when the argument consists of a single token as in this case).

    – egreg
    42 mins ago













  • Thank you for your quick reply. I know it's bad syntax otherwise xparse would not declare it as obsolete, but it is (extensively) used in e.g. physics package. I am just not sure about whether it can be done in plain, or it requires some features of the engine.

    – Weijun Zhou
    38 mins ago








  • 1





    It's indeed used in physics. My opinion about the package is that it has good ideas, but I can't recommend its usage. The weird syntax is just one among the several reasons for not recommending it.

    – egreg
    37 mins ago













  • Due to the weird syntax I end up adding relax here and there ... but I guess I will still use it.

    – Weijun Zhou
    29 mins ago














2












2








2








In the xparse package, there is the g type of argument which captures things inside a pair of TeX group tokens. This makes it possible to define commands foo that behaves differently for foo{a} and foo a. I am interested in whether such type of macro is possible in plain TeX (I guess yes) and if it is possible, how can it be implemented. I am new to plain TeX and I appreciate detailed explanation of the workflow of such a macro. I would also be happy to learn about other possibilities such as in e-TeX instead of plain TeX.










share|improve this question







New contributor




Weijun Zhou is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.












In the xparse package, there is the g type of argument which captures things inside a pair of TeX group tokens. This makes it possible to define commands foo that behaves differently for foo{a} and foo a. I am interested in whether such type of macro is possible in plain TeX (I guess yes) and if it is possible, how can it be implemented. I am new to plain TeX and I appreciate detailed explanation of the workflow of such a macro. I would also be happy to learn about other possibilities such as in e-TeX instead of plain TeX.







macros plain-tex braces






share|improve this question







New contributor




Weijun Zhou is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.











share|improve this question







New contributor




Weijun Zhou is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.









share|improve this question




share|improve this question






New contributor




Weijun Zhou is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.









asked 46 mins ago









Weijun ZhouWeijun Zhou

1134




1134




New contributor




Weijun Zhou is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.





New contributor





Weijun Zhou is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.






Weijun Zhou is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.













  • It's possible, but it's bad syntax. Under normal TeX conventions, foo a and foo{a} should be considered equivalent (when the argument consists of a single token as in this case).

    – egreg
    42 mins ago













  • Thank you for your quick reply. I know it's bad syntax otherwise xparse would not declare it as obsolete, but it is (extensively) used in e.g. physics package. I am just not sure about whether it can be done in plain, or it requires some features of the engine.

    – Weijun Zhou
    38 mins ago








  • 1





    It's indeed used in physics. My opinion about the package is that it has good ideas, but I can't recommend its usage. The weird syntax is just one among the several reasons for not recommending it.

    – egreg
    37 mins ago













  • Due to the weird syntax I end up adding relax here and there ... but I guess I will still use it.

    – Weijun Zhou
    29 mins ago



















  • It's possible, but it's bad syntax. Under normal TeX conventions, foo a and foo{a} should be considered equivalent (when the argument consists of a single token as in this case).

    – egreg
    42 mins ago













  • Thank you for your quick reply. I know it's bad syntax otherwise xparse would not declare it as obsolete, but it is (extensively) used in e.g. physics package. I am just not sure about whether it can be done in plain, or it requires some features of the engine.

    – Weijun Zhou
    38 mins ago








  • 1





    It's indeed used in physics. My opinion about the package is that it has good ideas, but I can't recommend its usage. The weird syntax is just one among the several reasons for not recommending it.

    – egreg
    37 mins ago













  • Due to the weird syntax I end up adding relax here and there ... but I guess I will still use it.

    – Weijun Zhou
    29 mins ago

















It's possible, but it's bad syntax. Under normal TeX conventions, foo a and foo{a} should be considered equivalent (when the argument consists of a single token as in this case).

– egreg
42 mins ago







It's possible, but it's bad syntax. Under normal TeX conventions, foo a and foo{a} should be considered equivalent (when the argument consists of a single token as in this case).

– egreg
42 mins ago















Thank you for your quick reply. I know it's bad syntax otherwise xparse would not declare it as obsolete, but it is (extensively) used in e.g. physics package. I am just not sure about whether it can be done in plain, or it requires some features of the engine.

– Weijun Zhou
38 mins ago







Thank you for your quick reply. I know it's bad syntax otherwise xparse would not declare it as obsolete, but it is (extensively) used in e.g. physics package. I am just not sure about whether it can be done in plain, or it requires some features of the engine.

– Weijun Zhou
38 mins ago






1




1





It's indeed used in physics. My opinion about the package is that it has good ideas, but I can't recommend its usage. The weird syntax is just one among the several reasons for not recommending it.

– egreg
37 mins ago







It's indeed used in physics. My opinion about the package is that it has good ideas, but I can't recommend its usage. The weird syntax is just one among the several reasons for not recommending it.

– egreg
37 mins ago















Due to the weird syntax I end up adding relax here and there ... but I guess I will still use it.

– Weijun Zhou
29 mins ago





Due to the weird syntax I end up adding relax here and there ... but I guess I will still use it.

– Weijun Zhou
29 mins ago










1 Answer
1






active

oldest

votes


















3














Fundamentally you just need to use futurelet as you do for any other look ahead



deffoo{futureletfooauxfootoken}
deffooaux{%
ifxfootokenbgroup
% Brace group
else
% Something else
fi
}


The only reason this 'looks different' to other peek ahead situations is that you can't use an explicit {, but rather the implicit token bgroup.






share|improve this answer
























  • That's clear enough and much simpler than I originally imagined.

    – Weijun Zhou
    33 mins ago












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
});


}
});






Weijun Zhou is a new contributor. Be nice, and check out our Code of Conduct.










draft saved

draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2ftex.stackexchange.com%2fquestions%2f483588%2fhow-to-write-a-macro-that-is-braces-sensitive%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









3














Fundamentally you just need to use futurelet as you do for any other look ahead



deffoo{futureletfooauxfootoken}
deffooaux{%
ifxfootokenbgroup
% Brace group
else
% Something else
fi
}


The only reason this 'looks different' to other peek ahead situations is that you can't use an explicit {, but rather the implicit token bgroup.






share|improve this answer
























  • That's clear enough and much simpler than I originally imagined.

    – Weijun Zhou
    33 mins ago
















3














Fundamentally you just need to use futurelet as you do for any other look ahead



deffoo{futureletfooauxfootoken}
deffooaux{%
ifxfootokenbgroup
% Brace group
else
% Something else
fi
}


The only reason this 'looks different' to other peek ahead situations is that you can't use an explicit {, but rather the implicit token bgroup.






share|improve this answer
























  • That's clear enough and much simpler than I originally imagined.

    – Weijun Zhou
    33 mins ago














3












3








3







Fundamentally you just need to use futurelet as you do for any other look ahead



deffoo{futureletfooauxfootoken}
deffooaux{%
ifxfootokenbgroup
% Brace group
else
% Something else
fi
}


The only reason this 'looks different' to other peek ahead situations is that you can't use an explicit {, but rather the implicit token bgroup.






share|improve this answer













Fundamentally you just need to use futurelet as you do for any other look ahead



deffoo{futureletfooauxfootoken}
deffooaux{%
ifxfootokenbgroup
% Brace group
else
% Something else
fi
}


The only reason this 'looks different' to other peek ahead situations is that you can't use an explicit {, but rather the implicit token bgroup.







share|improve this answer












share|improve this answer



share|improve this answer










answered 38 mins ago









Joseph WrightJoseph Wright

205k23563891




205k23563891













  • That's clear enough and much simpler than I originally imagined.

    – Weijun Zhou
    33 mins ago



















  • That's clear enough and much simpler than I originally imagined.

    – Weijun Zhou
    33 mins ago

















That's clear enough and much simpler than I originally imagined.

– Weijun Zhou
33 mins ago





That's clear enough and much simpler than I originally imagined.

– Weijun Zhou
33 mins ago










Weijun Zhou is a new contributor. Be nice, and check out our Code of Conduct.










draft saved

draft discarded


















Weijun Zhou is a new contributor. Be nice, and check out our Code of Conduct.













Weijun Zhou is a new contributor. Be nice, and check out our Code of Conduct.












Weijun Zhou is a new contributor. Be nice, and check out our Code of Conduct.
















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














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2ftex.stackexchange.com%2fquestions%2f483588%2fhow-to-write-a-macro-that-is-braces-sensitive%23new-answer', 'question_page');
}
);

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







Popular posts from this blog

What is the “three and three hundred thousand syndrome”?Who wrote the book Arena?What five creatures were...

Gersau Kjelder | Navigasjonsmeny46°59′0″N 8°31′0″E46°59′0″N...

Hestehale Innhaldsliste Hestehale på kvinner | Hestehale på menn | Galleri | Sjå òg |...