From: Anders Johansson <mejlaandersj@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: Bug: Problems with sub/super-script when using: org-cdlatex + org-pretty-entities + org-catch-invisible-edits
Date: Sun, 23 Feb 2014 12:50:30 +0100 [thread overview]
Message-ID: <5309E086.8030505@gmail.com> (raw)
In-Reply-To: <5309DA59.3070905@gmail.com>
> Hi,
> I used the configuration:
>
> org-catch-invisible-edits 'show
> org-pretty-entities t
>
> together with org-cdlatex. This breaks the insertion of subscripts and
> superscripts through org-cdlatex because _{} is fontified and the {}
> are hidden so typing for example: "a _ bc" results in "a_{b}c" (or
> sometimes "a_bc", but should be "a_{bc}") and gives the message
> "Unfolding invisible region around point before editing".
>
> Setting org-catch-invisible-edits to nil let's cdlatex do it's work so
> I guess an easy solution would be to "let" that in
> org-cdlatex-underscore-caret.
>
>
> Cheers,
> Anders Johansson
Hi,
I realized that my solution won't work since
"org-check-before-invisible-edit" does it's work after
"org-cdlatex-underscore-caret" has called "cdlatex-sub-superscript" and
inserted "_{}".
Maybe then org-catch-invisible-edits should be nil all the time in
org-cdlatex-mode? But this would be unexpected. Maybe this can be
treated as a special case in "org-check-before-invisible-edit" in some way?
Cheers,
Andes Johansson
next prev parent reply other threads:[~2014-02-23 11:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-23 11:24 Bug: Problems with sub/super-script when using: org-cdlatex + org-pretty-entities + org-catch-invisible-edits Anders Johansson
2014-02-23 11:50 ` Anders Johansson [this message]
2014-02-23 15:20 ` Anders Johansson
2014-03-15 13:54 ` Anders Johansson
2014-03-04 22:26 ` shwouchk
2014-03-15 6:29 ` Bastien
2014-03-15 16:31 ` Shwouchk
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=5309E086.8030505@gmail.com \
--to=mejlaandersj@gmail.com \
--cc=emacs-orgmode@gnu.org \
/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).