Re: [O] Possible bug with coderef highlighting in HTML export

Hello, Thibault Marin writes: > Hi the attach patch fixes the issue for me. Please let me know if you > have any suggestions. It looks good. Applied. Thank you. Regards, -- Nicolas Goaziou

[O] bug#18870: bug#18870: \emsp and alignment in org clock report

Hello, Ben Finney writes: > On 22-Aug-2016, Nicolas Goaziou wrote: >> The display for clock reports has been changed some months ago in >> development version. > > Which version contains this change? > >> I think this bug can be closed. > > How can we test the change,

[O] How can I obtain Org via HTTPS?

Hello all, It does not appear to be possible to obtain the Git repository for Org via HTTPS or SSH, only via HTTP. I have checked the manual and searched the Internet to see if there is a way, but no luck. I only found an unanswered inquiry from earlier this year [1]. —Why is HTTPS/SSH necessary

[O] bug#18870: bug#18870: \emsp and alignment in org clock report

On 22-Aug-2016, Nicolas Goaziou wrote: > The display for clock reports has been changed some months ago in > development version. Which version contains this change? > I think this bug can be closed. How can we test the change, to know whether this bug is resolved? -- \ “Instead of

Re: [O] org-depend: TRIGGER XYZ(KEYWORD) not working

Hi Karl, > Examples: > > * Top-Heading > > ** TODO Here I invoke org-todo to DONE > :PROPERTIES: > :TRIGGER: 2017-12-03-target(TODO) > :END: > > ** This should be changed to TODO > :PROPERTIES: > :ID: 2017-12-03-target > :END: > > ... this is working

Re: [O] Possible bug with coderef highlighting in HTML export

Hi, Hi the attach patch fixes the issue for me. Please let me know if you have any suggestions. As always, thanks for the guidance. thibault >From a78dc91c9fd1aacb2c65f66ae5afa9ee25f56e01 Mon Sep 17 00:00:00 2001 From: thibault Date: Sun, 3 Dec 2017 17:42:13 -0600

[O] Bug: org-attach-directory should be safe [9.1.3 (9.1.3-10-gadfbfd-elpaplus @ /home/ionasal/.emacs.d/elpa/org-plus-contrib-20171127/)]

org-attach-directory should be safe to set as a file local or directory local string. This allows the user to set a directory local attachment directory for all Org files in a directory tree recursively. I do not believe there are any security issues to enable arbitrary Org files to set

[O] bug#20090: improperly closed

Boruch Baum writes: > Bug report 20090 was perfunctorily closed today: > 1] without the person who performed the action consulting with the bug > reporter; You're free to re-open the bug or create another one if you disagree. For the record, I don't consider this to be a

[O] bug#20090: improperly closed

Bug report 20090 was perfunctorily closed today: 1] without the person who performed the action consulting with the bug reporter; 2] without any discussion for over 2.5 years; 3] with a reason given that demonstrates that the person who performed the action didn't give the action much of any

Re: [O] org-depend: TRIGGER XYZ(KEYWORD) not working

Hi Adrian, Glad that you replied - I was worrying that this thread is going to die before any improvement can be developed ... * Adrian Bradd wrote: > > First observation: >> >> When I set the heading 1 to DONE (without assigning it any other >> keyword), the TRIGGER

[O] bug#20090: 24.4: linking to a position within an info node

Closing the bug report.

[O] bug#20090: 24.4: linking to a position within an info node

Hello, Boruch Baum writes: > On 03/12/2015 03:50 PM, Juri Linkov wrote: >>> When the org mode manual discusses creating links, it gives an example >>> of linking to an info node (the self-referencing example is >>> `info:org#External' links). The manual continues, at node

[O] bug#4068: 23.1; M-x org-cdlatex-mode: cdlatex not found

Hello, David Reitter writes: > Selecting M-x org-cdlatex-mode brings up the error message shown below. > This command is also available via a menu, so it should really work > out-of-the-box. As specified in the manual, you need to install cdlatex from

[O] bug#7528: 24.0.50; (org) Visibility Cycling

Hello, "Drew Adams" writes: > The node says: > > `C-c C-k' (`show-branches') > Expose all the headings of the subtree, CONTENT view for just one > subtree. > > But both `C-c C-k' and `show-branches' seem to be undefined in Org mode. > > The doc does

[O] bug#21818: 24.5; org-set-tags-to indentation problems when called programmatically

Nicolas Goaziou writes: > Nicolas Goaziou writes: > >> After a quick glance, I think you are right: invisible characters are >> not treated the same way in both cases. I'll investigate deeper soon. > > Fixed in d5767ad. Closing this bug report,

[O] bug#18877: 25.0.50; org-mode fontification error

Hello, Davor Rotim writes: > GNU Emacs 25.0.50.1 (i686-pc-linux-gnu, GTK+ Version 3.14.4) of 2014-10-26 > > emacs -Q, then (setq org-src-fontify-natively t) and try visiting an org > file with source code blocks, the message "org-mode fontification error" > will appear

[O] bug#28999: 25.3.50; org export : exclude-tags not working with org-export-filter-options-functions

Hello, Kyle Meyer writes: > Michel Damiens writes: > >> Adding : >> >> (defun my-org-export-change-options (plist backend) >> (cond >> ((equal backend 'html) >>(plist-put plist :exclude-tags "NOHTML") >>(plist-put plist

[O] bug#27068: 25.2; org-odt-export-to-odt error when filename contains Chinese chars

Hello, "steven.y...@china-hicloud.com" writes: > When execute `org-odt-export-to-odt` command, if the org filename > contains Chinese, and under Windows 7 OS default encoding GBK. An error > occurs that the zipped obt file's name is not correct. I think we > can

[O] bug#22635: 25.1.50; wrong-type-argument when using org-beamer-select-environment

Hello, Kyle Meyer writes: > Derek Feichtinger writes: > >> When executing C-c C-b (org-beamer-select-environment) in an org beamer >> using the current emacs head (git hash ae928ae), I reproducibly get >> the following >> error and backtrace,

[O] bug#26765: 25.2; org-babel: Inserting list of cons cells fails

Hello, Lucas Groenendaal writes: > Please describe exactly what actions triggered the bug, and > the precise symptoms of the bug. If you can, give a recipe > starting from 'emacs -Q': > > First off, I found a fix for this problem. I wasn't sure how to best > submit

[O] bug#29329: 27.0.50; Missing requirement in org-gnus.el

Hello, Glenn Morris writes: > In org-gnus-store-link: > org-gnus.el:121:49:Warning: reference to free variable ‘gnus-newsgroup-name’ > org-gnus.el:127:42:Warning: reference to free variable ‘gnus-summary-buffer’ > > In org-gnus-follow-link: > org-gnus.el:203:9:Warning: reference

Re: [O] org-depend: TRIGGER XYZ(KEYWORD) not working

Hi, First observation: > > When I set the heading 1 to DONE (without assigning it any other > keyword), the TRIGGER events are ignored totally. I guess this is > an edge-case that may be considered as a bug. > ​This is the result of Line 219 in org-depend.el: (unless (and (member from

Re: [O] Possible bug with coderef highlighting in HTML export

Hello, Thibault Marin writes: > I am using Org mode version 9.1.3 (release_9.1.3-216-g259656 @ > /.../org-mode/lisp/) and I am experiencing an issue with the exported > HTML of the following org file: > > , > | this links get highlighted [[(link0)]]. > | > | this

Re: [O] using org-global-properties in capture templates

Hi thank you Adrian so so much, i hugely appreciate this! this works perfectly now, thx for pointing me in the right direction have a great week! Z On Sun, Dec 3, 2017 at 3:28 AM, Adrian Bradd wrote: > Hello, > > It looks like you have one too many parenthesis around

[O] Possible bug with coderef highlighting in HTML export

Hi all, I am using Org mode version 9.1.3 (release_9.1.3-216-g259656 @ /.../org-mode/lisp/) and I am experiencing an issue with the exported HTML of the following org file: , | this links get highlighted [[(link0)]]. | | this link does not get highlighted [[(link1)]]. | | #+begin_src