From: arthur miller <arthur.miller@live.com>
To: Bastien <bzg@gnu.org>,
William Rankin via General discussions about Org-mode.
<emacs-orgmode@gnu.org>
Cc: "emacs-devel@gnu.org" <emacs-devel@gnu.org>,
William Rankin <william@bydasein.com>
Subject: RE: Re Org 9.4 is out. Can you help? // breaking apart Org Mode
Date: Wed, 23 Sep 2020 13:03:51 +0000 [thread overview]
Message-ID: <VI1PR06MB4526F962D95F9BCC94F113C596380@VI1PR06MB4526.eurprd06.prod.outlook.com> (raw)
In-Reply-To: <87pn6c29a6.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1658 bytes --]
Not long time ago I posted a bug report about superscripts and subscripts not rendered when in-between italics markings, '/'. I would definitely like to see that code, and rest for prettie-fying entities factored out into a minor mode that can be activated in any Emacs buffer.
What do you think, is it to much work and where can you point out (just generally) where to look in the source for the code responsible for that?
-------- Originalmeddelande --------
Från: Bastien <bzg@gnu.org>
Datum: 2020-09-23 10:21 (GMT+01:00)
Till: "William Rankin via General discussions about Org-mode." <emacs-orgmode@gnu.org>
Kopia: William Rankin <william@bydasein.com>, emacs-devel@gnu.org
Ämne: Re: Re Org 9.4 is out. Can you help? // breaking apart Org Mode
Hi William,
thanks a lot for bringing this up.
Of course, Org would benefit from code cleanup and code refactoring.
And yes, we can collectively push toward (1) modularizing Org a little
more, (2) making Org features better interact with Emacs core features
and (3) integrating some of Org's features into Emacs core as Emacs
features.
IMHO the good examples you give fall into one of the category above,
and I think such efforts are likely to happen in that order: 1, 2, 3.
The better way to make this happen is to start a discussion with a
patch explaining how it makes 1, 2 or 3, then discussing the patch
here on this list - the smaller the better.
If you cannot make a patch, first discuss your idea, and once the
implementation seems clear, call for help by using a mail header:
X-Woof-Help: Help with making X a new module
Thanks,
--
Bastien
[-- Attachment #2: Type: text/html, Size: 2494 bytes --]
next prev parent reply other threads:[~2020-09-23 13:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-15 10:05 Re Org 9.4 is out. Can you help? // breaking apart Org Mode William Rankin via General discussions about Org-mode.
2020-09-15 13:00 ` Nicholas Savage
2020-09-15 13:49 ` Russell Adams
2020-09-23 8:28 ` Bastien
2020-09-23 14:44 ` Dr. Arne Babenhauserheide
2020-09-23 8:25 ` Bastien
2020-09-23 8:21 ` Bastien
2020-09-23 13:03 ` arthur miller [this message]
2020-09-23 13:27 ` 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=VI1PR06MB4526F962D95F9BCC94F113C596380@VI1PR06MB4526.eurprd06.prod.outlook.com \
--to=arthur.miller@live.com \
--cc=bzg@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=emacs-orgmode@gnu.org \
--cc=william@bydasein.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).