#84 scrlttr2 conflicts with [newcommands]{ragged2e}

[Uwe Siart]

Don't know if it's related to #82 and therefore a duplicate. I observe another scrlttr2 conflict with the latest releases. The MWE

\documentclass{scrlttr2}
\usepackage[newcommands]{ragged2e}
\begin{document}
\begin{letter}{Test}
  \opening{Test}
  Test
  \closing{Test}
\end{letter}
\end{document}

dies away with

! Undefined control sequence.
\@gnewline ...\@nolnerr \else \unskip \reserved@e 
                                                  {\reserved@f #1}\nobreak \...
l.7   \closing{Test}

Without the [newcommands] option the error is gone.

[Markus Kohm]

I have always pointed out that the newcommands option of ragged2e is a bad idea and should not be used. KOMA script classes and packages are not the only ones that rely on certain properties of the original commands.

I don't consider it a bug of KOMA-Script when other packages break things like that.

[Uwe Siart]

Ok, understood. I just thought it should be reported because it doesn't appear in 3.43. I'll avoid using the option. One can live quite well without it.

[Markus Kohm]

Yes, thank you. Reporting is always a good idea.

[Markus Kohm]

From [r4161] \closing does not result in an error with \usepackage[newcommands]{ragged2e} and even setting \raggedsignature to \LaTeXraggedright, \LaTeXraggedleft or \LaTeXcentering is recognized and results in valid definitions of \sigalign. Additionally I've documented the new feature of multiple signatures in one signature separated by \and (→ [wiki-en:HowTo_MultipleSignatures] or [wiki-de:HowTo_MultipleSignatures]).

Cross your fingers!