From: Ihor Radchenko <yantar92@gmail.com>
To: Timothy <tecosaur@gmail.com>
Cc: Org Mode List <emacs-orgmode@gnu.org>,
Nicolas Goaziou <mail@nicolasgoaziou.fr>
Subject: Re: [PATCH] Don't fill displayed equations
Date: Sun, 03 Oct 2021 17:13:07 +0800 [thread overview]
Message-ID: <87o8865v4s.fsf@localhost> (raw)
In-Reply-To: <875yueij6r.fsf@gmail.com>
Timothy <tecosaur@gmail.com> writes:
> Hi Ihor,
>
>> What about making org-fill-element modular? We may define separate fill
>> functions for different elements and let the user override them
>> individually if the user prefer so. It may be implemented similar to
>> export functionality with customisable formatters for different
>> elements.
>
> Thanks for that idea. Perhaps something along those lines may be the best
> solution here. If we don’t want to make the whole function modular, perhaps we
> could make a setting for this?
I personally would prefer modular function as a whole. For my taste,
Org code has too much of (case (variant 1) (variant 2) ...)-style
functions (i.e. org-todo, org-cycle, org-ctrl-c-ctrl-c, org-store-link,
etc) and they are a pain to debug and advice for users.
Best,
Ihor
next prev parent reply other threads:[~2021-10-03 9:12 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-30 17:20 [PATCH] Don't fill displayed equations Timothy
2021-09-30 17:44 ` Timothy
2021-09-30 18:51 ` Nicolas Goaziou
2021-09-30 18:54 ` Timothy
2021-09-30 19:02 ` Nicolas Goaziou
2021-09-30 19:17 ` Colin Baxter
2021-09-30 22:11 ` Nicolas Goaziou
2021-09-30 22:26 ` Tim Cross
2021-09-30 19:28 ` Timothy
2021-09-30 20:45 ` Timothy
2021-09-30 22:55 ` Nicolas Goaziou
2021-10-01 7:38 ` Stefan Nobis
2021-10-01 20:41 ` Nicolas Goaziou
2021-10-02 8:17 ` Org syntax: \[ \] as block element instead of inline object Max Nikulin
2021-10-02 10:47 ` Stefan Nobis
2021-10-02 9:57 ` [PATCH] Don't fill displayed equations Stefan Nobis
2021-10-02 10:04 ` Eric S Fraga
2021-10-02 10:18 ` Timothy
2021-10-02 11:24 ` Eric S Fraga
2021-10-02 14:21 ` Max Nikulin
2021-10-02 17:51 ` Tom Gillespie
2021-10-02 18:28 ` Timothy
2021-10-02 18:57 ` Tom Gillespie
2021-10-02 20:25 ` org-latex-preview and latex export blocks Timothy
2021-10-03 8:50 ` [PATCH] Don't fill displayed equations Max Nikulin
2021-10-03 10:56 ` Stefan Nobis
2021-10-03 12:04 ` Max Nikulin
2021-10-04 5:57 ` Tom Gillespie
2021-10-04 17:11 ` Max Nikulin
2021-10-03 12:35 ` Ihor Radchenko
2021-10-01 7:43 ` Timothy
2021-10-02 11:06 ` Nicolas Goaziou
2021-10-02 11:24 ` Timothy
2021-10-03 8:49 ` Ihor Radchenko
2021-10-03 8:50 ` Timothy
2021-10-03 9:13 ` Ihor Radchenko [this message]
2021-10-03 9:14 ` Timothy
2021-10-03 9:41 ` Ihor Radchenko
2021-10-03 9:42 ` Timothy
2022-06-18 6:00 ` Ihor Radchenko
2021-10-01 14:42 ` Greg Minshall
2021-10-04 6:05 ` Timothy
2021-10-04 7:11 ` Tom Gillespie
2021-10-04 7:15 ` Timothy
2021-10-04 8:11 ` Przemysław Pietrzak
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=87o8865v4s.fsf@localhost \
--to=yantar92@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=mail@nicolasgoaziou.fr \
--cc=tecosaur@gmail.com \
/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).