[texhax] problem with a defined command

[Victor Ivrii]

On Fri, Jan 17, 2014 at 4:12 AM, Philip Taylor <P.Taylor at rhul.ac.uk> wrote:

>
>
> Lars Madsen wrote:
>
> > Please do not do things like this, it really annoys editors and makes
> > the code a lot less readable. If you find it annoying to write
> > \begin{align} then consider finding a better editor that can help you
> > insert these
>
> "Please do not use LaTeX as a programmable markup language" ?
> Surely not.  If users were not intended to extend LaTeX by
> defining their own commands, Lamport would never have provided
> \newcommand and \renewcommand, and Mittelbach et al would not
> have carried these across to LaTeX2e.  If editors require authors
> to use only a specific subset of LaTeX, then their style/class files
> should disable \newcommand and friends.
>
>

Nobody denies that \newcommand is very useful and nobody denies the right
of the author to introduce as many command as he/she wants for the personal
consumption. However for people dealing with the source the orgy of all
these macros and so on are rather annoying.

But more than this: then the author writes an abstract using these macros,
then goes somewhere to give a talk and sends this abstract (which does not
contain definitions) and the announcement contains lots of \eeq, \beq,
\ups, \eps, \alp,

I really want to tell the speaker: \smek! \wthis? your abstract is pure
\drek!


-- 

Victor Ivrii
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://tug.org/pipermail/texhax/attachments/20140117/a9173224/attachment-0001.html>