<#multipart type=alternative><#part type=text/plain>

Nicolas Goaziou <mail@nicolasgoaziou.fr> writes:

> That would be undesirable. LaTeX fragments (inline type) and LaTeX
> environments (block type) are different beasts. This is clearly outside
> the scope of `org-edit-special’ to move from one type to the other.

Inline LaTeX, and Environments are indeed different. I failed to consider that
there may be additional complications if switching an inline environment to an
environment. Quite frankly I’m not too sure how org handles an environment in
the middle of a line. I’ll do some quick tests.

I was also referring to \( \) → \[ \] (inline to inline) as something one could
well want to change, in which case I don’t think this is a concern.

Lastly, I feel like it may be a good idea to give some example

inline → inline

::INITIAL
\(\epsilon_0 = \binom{n}{b} \sqrt{\alpha_2 + \frac{\partial z}{\partial x \partial y}} ... \)g
::CHANGE INLINE STYLE
\[\epsilon_0 = \binom{n}{b} \sqrt{\alpha_2 + \frac{\partial z}{\partial x \partial y}} ... \]
::END

inline → environment

::INITIAL
\[ \alpha = \psi(0) \quad \beta = \psi(1) \quad \gamma = \psi(2) \]
::CHANGE STYLE

::END

However this ends up being implemented, I think it would be good not to prevent
the user from making these changes in the pop-up edit buffer.

> This is clearly outside the scope of `org-edit-special’ to move from one type
> to the other.

To be honest I don’t quite see this point, in both cases it’s just a LaTeX buffer…
<#multipart type=related><#part type=text/html><p>
Nicolas Goaziou &lt;mail@nicolasgoaziou.fr&gt; writes:<br />
</p>

<p>
&gt; That would be undesirable. LaTeX fragments (inline type) and LaTeX<br />
&gt; environments (block type) are different beasts. This is clearly outside<br />
&gt; the scope of `org-edit-special&rsquo; to move from one type to the other.<br />
</p>

<p>
Inline LaTeX, and Environments are indeed different. I failed to consider that<br />
there may be additional complications if switching an inline environment to an<br />
environment. Quite frankly I&rsquo;m not too sure how org handles an environment in<br />
the middle of a line. I&rsquo;ll do some quick tests.<br />
</p>

<p>
I was also referring to \( \) → \[ \] (inline to inline) as something one could<br />
well want to change, in which case I don&rsquo;t think this is a concern.<br />
</p>

<p>
Lastly, I feel like it may be a good idea to give some example<br />
</p>

<hr />

<p>
inline → inline<br />
</p>

<p>
::INITIAL<br />
\(\epsilon_0 = \binom{n}{b} \sqrt{\alpha_2 + \frac{\partial z}{\partial x \partial y}} ... \)g<br />
::CHANGE INLINE STYLE<br />
\[\epsilon_0 = \binom{n}{b} \sqrt{\alpha_2 + \frac{\partial z}{\partial x \partial y}} ... \]<br />
::END<br />
</p>

<p>
inline → environment<br />
</p>

<p>
::INITIAL<br />
\[ \alpha = \psi(0) \quad \beta = \psi(1) \quad \gamma = \psi(2) \]<br />
::CHANGE STYLE<br />
</p>

<p>
::END<br />
</p>

<hr />

<p>
However this ends up being implemented, I think it would be good not to prevent<br />
the user from making these changes in the pop-up edit buffer.<br />
</p>

<p>
&gt; This is clearly outside the scope of `org-edit-special&rsquo; to move from one type<br />
&gt; to the other.<br />
</p>

<p>
To be honest I don&rsquo;t quite see this point, in both cases it&rsquo;s just a LaTeX buffer&#x2026;<br />
</p>
<#/multipart>
<#/multipart>