Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

9
  • 1
    Please provide code we can compile to reproduce the error and tell us the exact text of the error message. But it looks as if you are trying to redefine a command in terms of itself. An environment's contents being italic will not cause text outside that environment to be italic unless you are doing something-wrong-we-know-not-what. But it is hard to help without a minimal example. Commented Mar 25, 2017 at 2:15
  • 1
    If you have an environment called example, you cannot also have a command \example because an environment already defines a command by the same name. But the redefinition you show makes no sense anyway. Why would you not use \begin{example} whatever \end{example}? There is nothing to be gained from the proposed command that would in any way affect italicisation. Commented Mar 25, 2017 at 2:17
  • Just simply because typing the whole thing is kind of slow...and not conforming to my other environment format. Commented Mar 25, 2017 at 2:42
  • What does that have to do with italics? If you want a shortcut - not really to be recommended especially, but sometimes useful - just pick a different name. Commented Mar 25, 2017 at 2:44
  • 1
    @Shiyue: This lazyness will bite you in the end. Rather keep the usual \begin{example}...\end{example}. Commented Mar 25, 2017 at 13:00