[O] [FEATURE] exporting with write partially to solve big Org file slowing exporting

When I export a big Org file which is a big reference has about 36285 lines to epub format through package "ox-epub". I found it write to HTML is very slow. Is there any solution to solve this? I guess this could be Org exporter problem. If Org exporter can write partly to file one by one. it w

[O] time range, timestamps // was: docstring typoes in org-read-date-force-compatible-dates

> Kyle Meyer wrote: > > In the future, please send > generated patches with git format-patch so that they include a commit > message (see > for instructions). Thanks Kyle. Noted. I am muddling my way through [info:org#Creating timesta

Re: [O] docstring typoes in org-read-date-force-compatible-dates

Van L writes: > Hello, > > I found and fixed the following typoes. > > diff --git a/lisp/org.el b/lisp/org.el Thank you. I've applied your changes. In the future, please send generated patches with git format-patch so that they include a commit message (see

[O] docstring typoes in org-read-date-force-compatible-dates

Hello, I found and fixed the following typoes. diff --git a/lisp/org.el b/lisp/org.el index 5dd5c024d..755c190cf 100644 --- a/lisp/org.el +++ b/lisp/org.el @@ -3329,7 +3329,7 @@ Depending on the system Emacs is running on, certain dates cannot be represented with the type used internally to rep

[O] Change in order of tag collation from #+filetags plus heading tags [Regression 9.1 -> 9.2]

Hello, I have noticed a minor regression in the order in which Org collects the "ALLTAGS" tags at point. Here is a simple Org file to reproduce that issue: = #+filetags: a * Level 1 :b: ** Level 2 :c: *** Level 3 :d: = With point anywhere under ~* Level 3~ heading, evaluate: M-: (org

[O] Fix C-u C-c C-q (align all tags in visible buffer)

Hello, This minor bug had been bothering me for a while and I eventually got to looking into the source code for it. As of current master, C-u C-c C-q doesn't work as in the doc-string i.e. "When optional argument ALL is non-nil, align all tags in the visible part of the buffer.". Here's an exam

Re: [O] Bug: C-u M-x org-footnote-action sort deletes footnotes used in #+include:’d files [8.2.10 (release_8.2.10 @ /usr/share/emacs/25.3/lisp/org/)]

> Arne Babenhauserheide writes: > > > In my setup, it deletes footnote [fn:2]. > > > > Damn, I missed one important part in the ECM: Set > > > > org-footnote-section > > > > to nil. Does it still leave them untouched? > > I still cannot reproduce it. Then I’ll need to test this in org 9

Re: [O] Exporting description list without description

Hi, On Thu, Jan 3, 2019, 22:40 Eric S Fraga wrote: > yes, and I get the same as you do, but that whitespace difference should > make no difference in the PDF result? I guess it may make a difference > for other export targets. > Yes. I know some backends don't care. I just couldn't find a re

[O] Bug: Inconsistent usage of org-capture-get [9.2 (release_9.2 @ /Users/xristos/code/elisp/third-party/org-mode/lisp/)]

At some point, the optional argument LOCAL was added to org-capture-get: (org-capture-get PROP &optional LOCAL) "When LOCAL is set, use the local variable ‘org-capture-current-plist’, this is necessary after initialization of the capture process, to avoid conflicts with other active capture pro

Re: [O] Bug: Latex preview fg color w/tikz (known problem, fix suggested) [9.1.9 (release_9.1.9-65-g5e4542 @ /home/carlos/local/stow/emacs-26/share/emacs/26.1.90/lisp/org/)]

Hi Nicolas, I've improved the commit message to better fit org mode conventions and also added a note to ORG-NEWS about the new feature. Let me know if there still is something I should change or feel free to amend it to your liking. One question for future patches: is it ok to add a link to the

Re: [O] [Patch] [Feature request] Add option to natively fontify latex snippets and environment

I've improved the commit message to better align org mode conventions and also added a note to ORG-NEWS about the new feature. From 19d1d83901d3cc959b0cef5d2832da307e01 Mon Sep 17 00:00:00 2001 From: memeplex Date: Wed, 2 Jan 2019 19:43:21 -0300 Subject: [PATCH] Add option to natively fontify

Re: [O] Bug: links are not highlighted anymore with Org Mode 9.2

ghItlhpu' Daniel Borchmann : > I get (in the *scratch* buffer): > > (facep nil) → [face unspecified unspecified unspecified unspecified > unspecified unspecified unspecified unspecified unspecified unspecified > unspecified ...] Seems this an issue with my configuration, not Emacs itself, as

Re: [O] Bug: links are not highlighted anymore with Org Mode 9.2

ghItlhpu' Nicolas Goaziou : >> The reason for this seems to be that >> ‘org-activate-links’ uses the following code to determine which face to >> use: >> >> --8<---cut here---start->8--- >> (pcase (org-link-get-parameter type :face) >> ((and (pred functionp) fa

Re: [O] Bug: C-u M-x org-footnote-action sort deletes footnotes used in #+include:’d files [8.2.10 (release_8.2.10 @ /usr/share/emacs/25.3/lisp/org/)]

Hello, Arne Babenhauserheide writes: > In my setup, it deletes footnote [fn:2]. > > Damn, I missed one important part in the ECM: Set > > org-footnote-section > > to nil. Does it still leave them untouched? I still cannot reproduce it. > It does not reference between included files, but

Re: [O] Bug: links are not highlighted anymore with Org Mode 9.2

Hello, Daniel Borchmann writes: > links in Org Mode 9.2 are not highlighted anymore if no :face keyword is > given in ‘org-link-parameters’. I cannot reproduce this. > The reason for this seems to be that > ‘org-activate-links’ uses the following code to determine which face to > use: > > --8<

Re: [O] Exporting description list without description

On Thursday, 3 Jan 2019 at 19:24, Yasushi SHOJI wrote: > Hi, > > On Wed, Jan 2, 2019 at 11:52 PM Eric S Fraga wrote: >> What export target? I don't see any difference when exporting to LaTeX. > > Even Latex backed does it differently. Note the space between one and two. yes, and I get the same

[O] Bug: links are not highlighted anymore with Org Mode 9.2

Hey, links in Org Mode 9.2 are not highlighted anymore if no :face keyword is given in ‘org-link-parameters’. The reason for this seems to be that ‘org-activate-links’ uses the following code to determine which face to use: --8<---cut here---start->8--- (pcas

[O] [SOLVED] How about Org Mode invalid link handling strategy for exporting?

I have not found that option. Thanks. I checked the org-manual.org now, it's mentioned. -- [ stardiviner ] I try to make every word tell the meaning what I want to express. Blog: https://stardiviner.github.io/ IRC(freenode): stardiviner, Matrix: stardiviner GPG: F0

Re: [O] [Feature Request] Add an dispatcher command (keybinding) for inserting dynamic blocks

Nicolas Goaziou writes: > Hello, > > stardiviner writes: > >> As always, add patch as attachment. > > Thank you! I applied your patch, with minor tweaks. > > Regards, Thanks Nicolas. I will continue contribute in Org Mode. -- [ stardiviner ] I try to make every word tell the meanin

Re: [O] Org-drill edit feature request

John Kitchin writes: > My experience with this is that you have to get the word by some means > (e.g. it is a property, or it is selected some how) and then send it to > a platform specific speech program. It is easy on a mac as there is a > command line tool called "say". So, something like th

Re: [O] Bug: Latex preview fg color w/tikz (known problem, fix suggested) [9.1.9 (release_9.1.9-65-g5e4542 @ /home/carlos/local/stow/emacs-26/share/emacs/26.1.90/lisp/org/)]

Hello, Carlos Pita writes: > Here is a patch. It removes quite a few LOC. Thank you. > Every other previewer has :use-xcolor t. I assume it's safe to simply > ignore :use-xcolor if it's there except that some user has configured > a converter that for some reason requires the color command lin

Re: [O] Bug: Secondary smart quotes are exported as apostrophes. [9.1.14 (9.1.14-1-g4931fc-elpa @ /home/coleman/.emacs.d/elpa/org-9.1.14/)]

Hello, Coleman Gariety writes: > Also, it occurs to me that one can make use of single quotation marks as > primary quotes when mentioning a word without using it. Moreover, when > italics and double quotation marks are also present, the use of single > quotations as primary is necessary. > > Fo

Re: [O] Exporting description list without description

Hi, On Wed, Jan 2, 2019 at 11:52 PM Eric S Fraga wrote: > What export target? I don't see any difference when exporting to LaTeX. Even Latex backed does it differently. Note the space between one and two. Here are both outputs: \begin{description} \item[{one}] \item[{two}] \end{description}