emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Daan Ro <daanturo@gmail.com>
To: Ihor Radchenko <yantar92@posteo.net>
Cc: "emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>
Subject: Re: [BUG] Patch: Add an option to silence org-latex-preview (also a feature request) [9.7.11 (release_9.7.11 @ /usr/local/share/emacs/30.0.91/lisp/org/)]
Date: Sun, 13 Oct 2024 13:18:49 +0700	[thread overview]
Message-ID: <1C8D502B-2E47-45C3-A794-FFF7B57DFA23@getmailspring.com> (raw)
In-Reply-To: <87ttdhqq33.fsf@localhost>

[-- Attachment #1: Type: text/plain, Size: 1813 bytes --]

Currently I have minor mode that automates `org-latex-preview` every some idle
seconds so that newly typed fragments are automatically rendered. Having an
option to disable messages would make Emacs's interface much cleaner.

About org-mode's similar messages, I just saw that some `message` calls are
conditioned on `(called-interactively-p 'any)`. IMO `org-latex-preview`'s
messages should do the same as the latter (only notify when called
interactively) by default, but maybe that's a breakage for some people.

Additionally, I'd love to make `org-latex-preview` asynchronous. First, that
will definitely speedup opening org files with `org-startup-with-latex-preview`
as Emacs doesn't freeze while generating images. Second, auto preview minor
modes such as mine would be smoother.

I have a rough idea of implementation by passing `org-place-formula-image` as a
callback closure to `org-create-formula-image` and `org-compile-file`. Would
such a feature request/patch be accepted?

Daanturo

On Oct 12 2024, at 10:49 pm, Ihor Radchenko <yantar92@posteo.net> wrote:
> Daan Ro <daanturo@gmail.com> writes:
>
> > [PATCH] org-latex-preview: add org-latex-preview-quiet customization
> >
> > * lisp/org.el (org-latex-preview): define customizable boolean
> > org-latex-preview-quiet.
>
> Thanks for the patch, but may you please elaborate why you want the
> messages to be suppressed? And why in org-latex-preview specifically?
>
> Many Org mode commands display messages, so I'd like to know your
> motivation as it may affect how we want handle messages across Org mode.
>
> --
> Ihor Radchenko // yantar92,
> Org mode contributor,
> Learn more about Org mode at <https://orgmode.org/>.
> Support Org development at <https://liberapay.com/org-mode>,
> or support my work at <https://liberapay.com/yantar92>
>


[-- Attachment #2: Type: text/html, Size: 2821 bytes --]

  reply	other threads:[~2024-10-13  6:19 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-04 18:43 [BUG] Patch: Add an option to silence org-latex-preview (also a feature request) [9.7.11 (release_9.7.11 @ /usr/local/share/emacs/30.0.91/lisp/org/)] Daan Ro
2024-10-12 15:49 ` Ihor Radchenko
2024-10-13  6:18   ` Daan Ro [this message]
2024-10-13 11:27     ` Ihor Radchenko
2024-10-13 17:32       ` Daan Ro
2024-10-14 14:19         ` Ihor Radchenko

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=1C8D502B-2E47-45C3-A794-FFF7B57DFA23@getmailspring.com \
    --to=daanturo@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=yantar92@posteo.net \
    /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).