From: "Christopher M. Miles" <numbchild@gmail.com>
To: Tim Cross <theophilusx@gmail.com>
Cc: William Denton <wtd@pobox.com>, emacs-orgmode@gnu.org
Subject: Re: org-modern
Date: Thu, 03 Mar 2022 20:14:33 +0800 [thread overview]
Message-ID: <PAXPR08MB6640230AB40F2B1F2B2C215CA3049@PAXPR08MB6640.eurprd08.prod.outlook.com> (raw)
In-Reply-To: <87czj5qtcw.fsf@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1229 bytes --]
Tim Cross <theophilusx@gmail.com> writes:
> William Denton <wtd@pobox.com> writes:
>
>> I noticed org-modern in the list of new packages available:
>>
>> https://github.com/minad/org-modern
>>
>> Worth a look by any Org users, just for the screenshots comparing Org buffers normally and with
>> org-modern. Fine work from Daniel Mendler, who I think is on this list. I'm trying it out
>> right now.
>>
>
> I was looking at this package and it looks interesting. However, I do
> wonder how much of an impact it has on org performance. I suspect it
> will have a significant impact on large org files. Would be interested
> in hearing how people find it with larger files.
It does not affect performance a lot. I almost can't feel the latency difference between disable or
enabled org-modern. I have 3M org file which has lot of source blocks and tags list etc. (I know 3M
is not very large.)
I like this package indeed beatified org-mode a lot.
--
[ stardiviner ]
I try to make every word tell the meaning that I want to express.
Blog: https://stardiviner.github.io/
IRC(freenode): stardiviner, Matrix: stardiviner
GPG: F09F650D7D674819892591401B5DF1C95AE89AC3
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2022-03-03 12:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-01 18:50 org-modern William Denton
2022-03-01 21:00 ` org-modern Tim Cross
2022-03-03 12:14 ` Christopher M. Miles [this message]
2022-03-03 13:09 ` org-modern Ihor Radchenko
-- strict thread matches above, loose matches on Subject: below --
2022-03-02 17:34 org-modern autofrettage
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=PAXPR08MB6640230AB40F2B1F2B2C215CA3049@PAXPR08MB6640.eurprd08.prod.outlook.com \
--to=numbchild@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=theophilusx@gmail.com \
--cc=wtd@pobox.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).