Re: [BUG] ox-beamer uses ox-latex private functions

On Sat, 23 Dec 2023 at 11:19, Ihor Radchenko wrote: > Both ox-beamer and ox-latex are parts of Org mode. So, there is nothing > wrong with using these internal functions - we have the control over all > parts of Org mode. If we decide to make a breaking change in any > internal function in Org

[BUG] ox-beamer uses ox-latex private functions

In three separate places (lines 779, 825 and 874) ox-beamer uses ox-latex private functions namely: line779: `org-latex--wrap-label' line 825: `org-latex--insert-compiler' line 874: `org-latex--format-spec' I appreciate ox-beamer is a backend backend derived from ox-latex but isn't this bad

[QUESTION] Should KEYWORD values in org-export-options-alist be lowercase?

Should the KEYWORD values in `org-export-options-alist' that are uppercase be lowercase to reflect what users see say when using a template and/or for consistency? Similarly, for the KEYWORD values in :options-alist in `org-export-define-backend' for example in ox-latex.el? For example the TITLE

Re: [Bug] Some parentheses are not visible in the html export but are present

On Thu, 7 Sept 2023 at 12:07, Ihor Radchenko wrote: > I am unable to reproduce. May you please provide a more detailed recipe > starting from emacs -Q? See https://orgmode.org/manual/Feedback.html#Feedback With your suggestion it no longer occurs. Off to bisect my init.el. Sorry for the noise.

[Bug] Some parentheses are not visible in the html export but are present

Some parentheses are not visible in the html export but are present. This was not always the case with the provided example. --- Begin Example --- * islower() ** Front *String method* that returns =True= if the string is a lowercase string, =False= otherwise. ** Back *String method:*

[BUG] org-texinfo-compile docstring sentence ends abruptly

The `org-texinfo-compile' docstring contains the following sentence which ends abruptly. "Processing is done through the command specified in `org-texinfo-info-process', which see." I think it is sufficient to remove the "which see" at the end. Thanks for Org and your time.

Re: [BUG] org-texinfo-export-to-info docstring describes a non-existing optional argument

On Wed, 24 May 2023 at 16:55, Ihor Radchenko wrote: > > Aside, when invoking this command on an org file I get the following error > > which may or not be a bug also: > > > > org-compile-file: File "/org-gtd.el/doc/org-gtd.info" > > wasn’t producedSee "Org INFO Texinfo Output" for details > > It

[BUG] org-texinfo-export-to-info docstring describes a non-existing optional argument

The `org-texinfo-export-to-info' docstring describes a non-existing optional argument PUB-DIR but no such argument is given in the definition. Perhaps it did in the past? Aside, when invoking this command on an org file I get the following error which may or not be a bug also: org-compile-file:

[BUG] Some Org mode files require org-macs.el more than once

Reviewing some Org files I noted the following files require org-macs.el more than once: - ob.el - ob-python.el - org-fold.el There are likely others too. The additional require seems redundant to my ignorant self. I appreciate this should cause no issue but is there a reason why such lines

Bug: 9.4.4 - ob-sql inserts page break (^L) in first cell of results table and truncates some column names

Using ob-sql for the first time. It works great and I no longer need to deal with the ugly output from the SQL command line. However, I noted that after submitting a query the first cell (first column name) of the results table includes a page break (^L). I use the purcell/page-break-lines

Bug 9.4.4; org babel blocks show unexpected colors with leuven theme

Reporting this bug to the mailing list on request of the leuven theme author as they believe the issue may be within Org and/or Emacs. The bug as reported to the theme author can be found here [1] and includes screenshots to illustrate what I mean. In short, the colors defined by the leuven

Re: [O] Bug: ? org-log-done-with-time set as a file local variable does not have the desired effect

On Sat, 16 Mar 2019 at 16:25, Niall Dooley wrote: > I've set org-log-done-with-time as a file local variable (in my habits.org) to > nil. Oddly, the Local Variables section was initially visible at the end of > this file but is no longer visible (when visiting this file in subsequent &

[O] Bug: ? org-log-done-with-time set as a file local variable does not have the desired effect

Firstly, this may or may not be a bug so apologies if I've incorrectly labelled the subject line. I use org-habits to track my habits defined in a habits.org file. I log each time I perform the habit with a :LOGGING: DONE(!) property. This adds an entry to a :LOGBOOK: drawer each time I mark the

[O] Question on org-agenda-custom-commands tags-todo match syntax

Firstly, I've searched online and even posted to both the emacs and orgmode subreddits but to no avail. Consider the following snippet: (setq org-agenda-custom-commands '(("p" "List Non-done projects" tags-todo "-CANCELLED+PROJECT/!+TODO"))) My understanding is that in the tags-todo match that

Re: [O] Bug: org-agenda-span value not quoted via customize interface

stead of (org-agenda-span 'day). Niall Niall On 30 August 2017 at 14:55, Sébastien Le Maguer <slemag...@coli.uni-saarland.de> wrote: > Hello > > I might say something stupid buy isn't it 'day (with a simple quote) ? > > Sent from Blue > On 30 Aug 2017, at 14:45, Niall Do

[O] Bug: org-agenda-span value not quoted via customize interface

Hi all, This is my first mail to this list so please tell me if I haven't followed the expected conventions. I created the following org-agenda-custom-command via the customise interface '(org-agenda-custom-commands (quote (("A" "Priority #A tasks" agenda "" ((org-agenda-span day)