From: Carlos Pita <carlosjosepita@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: Bug: org-toggle-latex-fragment doesn't work as documented [9.2.1 (release_9.2.1-60-gb0379f @ /home/carlos/local/stow/emacs/share/emacs/site-lisp/org/)]
Date: Mon, 11 Feb 2019 20:15:36 -0300 [thread overview]
Message-ID: <CAELgYhfzeXubb-1r-5Oi8Qh4++t20D65_rrkCj4f8GYt-0+0aA@mail.gmail.com> (raw)
In-Reply-To: <CAELgYhf2AXtuq+PTNFzpPC9iA+PZYDVP-BO9MpJJ9WGsCFjR=w@mail.gmail.com>
A last suggestion. Incidentally the toggle returns nil when at least a
fragment is unpreviewed and non-nil otherwise (as a side effect of
message). This can be documented and made part of the interface, so
that something like the following can be put together by the end user:
(defun my-org-preview-latex (&optional arg)
(interactive "P")
(unless (org-toggle-latex-fragment arg)
(org-toggle-latex-fragment arg)))
I insist on the importance of the use case "force preview" because
it's very useful to quickly jot down a paragraph or part of a
paragraph with many simple latex fragments like $x_i$, $f(x)$, etc.
and then, afterwards, type C-c C-x C-l to preview the last entered
part of the paragraph, instead of painfully entering C-c C-x C-l after
any single $x$ or similar. Now, if the toggle prefers removing
previews as it's the case, this won't work because, in general, you
already have some preview in the same section or paragraph.
next prev parent reply other threads:[~2019-02-11 23:16 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-11 22:30 Bug: org-toggle-latex-fragment doesn't work as documented [9.2.1 (release_9.2.1-60-gb0379f @ /home/carlos/local/stow/emacs/share/emacs/site-lisp/org/)] Carlos Pita
2019-02-11 22:33 ` Carlos Pita
2019-02-11 22:51 ` Carlos Pita
2019-02-11 23:15 ` Carlos Pita [this message]
2019-02-12 21:45 ` Nicolas Goaziou
2019-02-12 22:00 ` Carlos Pita
2019-02-12 22:43 ` Nicolas Goaziou
2019-02-12 23:23 ` Carlos Pita
2019-02-13 14:25 ` Nicolas Goaziou
2019-02-13 14:53 ` Carlos Pita
2019-02-13 15:10 ` Carlos Pita
2019-02-13 16:24 ` Nicolas Goaziou
2019-02-13 16:43 ` Carlos Pita
2019-02-13 19:38 ` Carlos Pita
2019-02-14 0:23 ` Nicolas Goaziou
2019-02-14 1:31 ` Carlos Pita
2019-02-14 14:52 ` 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=CAELgYhfzeXubb-1r-5Oi8Qh4++t20D65_rrkCj4f8GYt-0+0aA@mail.gmail.com \
--to=carlosjosepita@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).