emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Rasmus <rasmus@gmx.us>
To: mail@nicolasgoaziou.fr
Cc: dominik@uva.nl, emacs-orgmode@gnu.org
Subject: Re: [bug?] org-inside-latex-fragment-p broken?
Date: Sat, 24 Jun 2017 13:13:14 +0200	[thread overview]
Message-ID: <87y3shljud.fsf@gmx.us> (raw)
In-Reply-To: <87zicy4orq.fsf@nicolasgoaziou.fr> (Nicolas Goaziou's message of "Fri, 23 Jun 2017 19:06:33 +0200")

Nicolas Goaziou <mail@nicolasgoaziou.fr> writes:

> Hello,
>
> Carsten Dominik <dominik@uva.nl> writes:
>
>> Yes, these can be used in partially written fragments.
>
> OK. Does it make sense to use them outside of any fragment? For example,
> you don't need to be in a LaTeX fragment to insert \alpha.

First, we have to be careful because the cdlatex keys occupy a precious
key.

Second, it depends on the cdlatex function in question.
cdlatex-math-symbol-alist already works outside of fragments and it
probably should as it can be used to insert entities, such as "β".

On the other hand, cdlatex-math-modify probably only makes sense inside
fragments.  It is used to change characteristics of already inserted
entity, e.g. make a character bold.  That typically only makes sense
inside a math environment of some sort.  Add to this, that something like
"\mathbf{x}" isn’t "correctly" exported via ox, (it should then produce
"$\mathbf{x}$").  So cdlatex-math-modify should only work inside latex
fragments IMO.

-- 
m-mm-mmm-mmmm bacon!

  reply	other threads:[~2017-06-24 11:13 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-23 10:26 [bug?] org-inside-latex-fragment-p broken? Rasmus
2017-06-23 11:55 ` Nicolas Goaziou
2017-06-23 12:43   ` Rasmus
2017-06-23 13:45     ` Nicolas Goaziou
2017-06-23 16:43       ` Carsten Dominik
2017-06-23 17:06         ` Nicolas Goaziou
2017-06-24 11:13           ` Rasmus [this message]
2017-06-29 13:17             ` Nicolas Goaziou

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87y3shljud.fsf@gmx.us \
    --to=rasmus@gmx.us \
    --cc=dominik@uva.nl \
    --cc=emacs-orgmode@gnu.org \
    --cc=mail@nicolasgoaziou.fr \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).