Reputation
2,694
Top tag
Next privilege 3,000 Rep.
Cast close & reopen votes
Badges
3 21 50
Impact
~150k people reached

  • 0 posts edited
  • 0 helpful flags
  • 55 votes cast
Jun
29
comment Can I have a curly brace as macro argument delimiter?
no. nothing confusing now. Thanks for all the answers. :) And yes, \fin sounds like \end, you are right ! ;)
Jun
29
accepted Can I have a curly brace as macro argument delimiter?
Jun
29
comment Can I have a curly brace as macro argument delimiter?
well, it seems to me, that the idea you wrote in your comment above is precisely egreg's solution. Is it something more ?
Jun
29
comment Can I have a curly brace as macro argument delimiter?
ok, i guess i could try to learn it in tabularx...
Jun
29
comment Can I have a curly brace as macro argument delimiter?
can you make this in an expandable way ? I would appreciate a few lines of code.
Jun
28
comment Can I have a curly brace as macro argument delimiter?
yes, it gives the output I mentioned... but does not solve the problem of my EDIT1.
Jun
28
revised Can I have a curly brace as macro argument delimiter?
added 207 characters in body
Jun
28
accepted Long version of \edef, \xdef, \protected@edef
Jun
28
accepted Can I define a macro with same name as an already defined command?
Jun
28
accepted Can I redefine the dollar
Jun
28
asked Can I have a curly brace as macro argument delimiter?
Jun
28
accepted How to output a tabulation into a file
Jun
25
comment How to redefine commands and environments, and make them acceptable for `\write`
I tried to implement a solution with a simple redefinition of \begin, etc., but it fails. Please see my edit.
Jun
25
revised How to redefine commands and environments, and make them acceptable for `\write`
added 1456 characters in body
Jun
25
comment how to redefine the `\\` in a tabular environment?
Yes, you're right. Actually, i needed to redefine \\, not only in tabular, but generally speaking. The point is, i did not know i can do it simply with \def\\{new def}...
Jun
24
comment How to redefine commands and environments, and make them acceptable for `\write`
my guesses : (1) the name of the command is \mwx\temp, and therefore not accessible by a direct call. (2) without the \string, TeX will try to expand \temp inside the \csname and produce an error, since it does not exists. Am i right ?
Jun
24
comment How to redefine commands and environments, and make them acceptable for `\write`
I try to understand your construction \def\mywritedef#1{\expandafter\def\csname mwx\string#1\endcsname}. Could you tell me what is the name of the macro constructed by e.g. \mywritedef\temp. I expected \mwxtemp, but i think i'm wrong. Can I access this command directly ? And why do you put a \string ? What would it be without ? (sorry for the stupid questions, but i'm not used to \csname...
Jun
24
comment How to redefine commands and environments, and make them acceptable for `\write`
I think I understand : through your definitions of \begin, you remove the \begingroup which is in the usual definition of \begin and which is not expandable. Am I right ?
Jun
24
comment how to create a fully-expandable environment
Ok, thanks. Other question : i don't think \def\tabular#1#2\end{tabular}{<tabular=#1>#2</tabular>} can work because you can't use \end{tabular} as delimiter since it contains {}, can you ?
Jun
24
comment how to create a fully-expandable environment
@egreg: I don't understand the need of \def\begin#1{\csname #1\endcsname} ; I though \begin{env} does precisely \env. What did i miss ?