Re: [PATCH 0/1] Add option to delay fontification of source blocks

2021-04-02 Thread Leo Okawa Ericson
Kyle Meyer writes: > Have you explored whether jit-lock (e.g., jit-lock-defer-time) helps for > your use case? No I didn't know about it. I have tried it now and it seems to solve the same problem as my patch. > If we do go this route, I think the case needs to be made why this > spot is

[PATCH 0/1] Add option to delay fontification of source blocks

2021-03-27 Thread Leo Okawa Ericson
From: Leo Okawa Ericson I tried sending this patch once before, but I think it got caught as spam so I'm trying this again. Fontification of long code blocks can be very slow. The patch (in the reply to this email) mitigates this by adding an option to delay the fontification after the user has

[PATCH 1/1] org-src.el: Add option to delay fontification of source blocks

2021-03-27 Thread Leo Okawa Ericson
* lisp/org-src.el (org-src-font-lock-fontify-block): Add option to delay fontification of source blocks. If `org-src-font-lock-fontify-idle-delay' is non-nil fontification of code blocks is delayed until the user has become idle. Fontification of source blocks can be very slow. This will add an

[PATCH 0/1] Add option to delay fontification of source blocks

2021-03-27 Thread Leo Okawa Ericson
that shouldn't be a problem. This is my first patch submission so any suggestions for improvement are welcome. Leo Okawa Ericson (1): org-src.el: Add option to delay fontification of source blocks lisp/org-src.el | 29 + 1 file changed, 29 insertions(+) -- 2.25.1

[PATCH 1/1] org-src.el: Add option to delay fontification of source blocks

2021-03-27 Thread Leo Okawa Ericson
* lisp/org-src.el (org-src-font-lock-fontify-block): Add option to delay fontification of source blocks. If `org-src-font-lock-fontify-idle-delay' is non-nil fontification of code blocks is delayed until the user has become idle. Fontification of source blocks can be very slow. This will add an

Re: Clock tables and two ways to categorize tasks

2020-11-20 Thread Leo Okawa Ericson
Some time ago I hacked together a bunch of elisp to create a clock table based on tags. [1] It uses org's dynamic block feature[2] to create a piechart with gnuplot and a simple table that shows percentages of time spent on different tags. I should say that it has basically no documentation at

Re: Get Grades Done: the joys of Org's simple power

2020-06-13 Thread Leo Okawa Ericson
Diego Zamboni writes: > Hi Leo, > > Thanks - I had seen that one too, and couldn't figure out which one > was a fork of the other one. Both have recent activity - do you know > what are the main differences between them? > Well the changelog in org-web hasn't been updated in quite a while:

Re: Get Grades Done: the joys of Org's simple power

2020-06-12 Thread Leo Okawa Ericson
Diego Zamboni writes: > Hi Devin, > > Your could try https://org-web.org/ - it allows online editing of Org files > and a quick test shows that it supports the automatic update of checkbox > counts. Or you could try https://github.com/200ok-ch/organice - it is a friendly fork of org-web.

Re: Is there a way to export only a subtree of a document to LaTeX (or anywhere)?

2020-05-25 Thread Leo Okawa Ericson
Kyle Meyer writes: > Vladimir Nikishkin writes: > > When you enter the export dispatch, you should see an "Export scope" > option bound to C-s. That toggles between buffer and subtree export. I think it also works to narrow the buffer to what you want to export. Calling org-narrow-to-subtree