Re: [O] Bug: Fix for org-make-link-description-function use in org-insert-link [9.0.10 (9.0.10-5-g1654a5-elpa @ /home/rrt/.emacs.d/elpa/org-20170904/)]

On 5 September 2017 at 23:02, Nicolas Goaziou wrote: > Reuben Thomas writes: > > > ​If you (or someone) can confirm your interpretation above, I would be > > happy to update my patch to implement the two behaviours required, > namely, > > that

[O] Bug: View scheduled tasks that have a specific state [8.2.10 (release_8.2.10 @ /usr/share/emacs/24.5/lisp/org/)]

Hello, I'm on Org-mode 8.2.10 on Xubuntu 16.04 and despite having tried many combinations, I can't manage to view all scheduled tasks that don't have "DONE" and "CANCELLED" as a state. For example, when I do :  (setq org-agenda-custom-commands       '(     ("+" "Scheduled"        ((todo ""       

Re: [O] Bug: Symbol's value as variable is void: org-src-lang-modes

On Thu, Sep 7, 2017 at 1:38 PM Elliott Slaughter wrote: > Hi all, > > I have learned (thanks to the el-get developers) that org-mode uses > with-eval-after-load, which was added in Emacs 24.4. (See discussion [1].) > > I confirmed that the master branch of org-mode

Re: [O] Bug: Symbol's value as variable is void: org-src-lang-modes

Hi all, I have learned (thanks to the el-get developers) that org-mode uses with-eval-after-load, which was added in Emacs 24.4. (See discussion [1].) I confirmed that the master branch of org-mode loads (via el-get) successfully in 24.4.1 and fails to load in 24.3.1. I'm not sure what the

Re: [O] Bug: org-split-string handles empty strings differently in 9.1

Hello, Erik Sjöstrand writes: > It seems that org-split-string was rewritten and handles empty strings > differently in org-mode 9.1. Before (org-split-string "" " ") would > return nil, but now it returns '(""). Correct. > I couldn't see any information in the

[O] Bug: org-split-string handles empty strings differently in 9.1

Hi! It seems that org-split-string was rewritten, and handles empty strings differently in org-mode 9.1. Before (org-split-string "" " ") would return nil, but now it returns '(""). I couldn't see any information in the changelog about this. A side effect (among others, I would guess) of this is

Re: [O] Bug: Fix for org-make-link-description-function use in org-insert-link [9.0.10 (9.0.10-5-g1654a5-elpa @ /home/rrt/.emacs.d/elpa/org-20170904/)]

Reuben Thomas writes: > ​If you (or someone) can confirm your interpretation above, I would be > happy to update my patch to implement the two behaviours required, namely, > that org-make-link-description-function is only called if the > default-description argument to

Re: [O] Bug: Fix for org-make-link-description-function use in org-insert-link [9.0.10 (9.0.10-5-g1654a5-elpa @ /home/rrt/.emacs.d/elpa/org-20170904/)]

On 5 September 2017 at 21:49, Nicolas Goaziou wrote: > Hello, > ​Hi, thanks for looking at this.​ > Reuben Thomas writes: > > > This seems to be incorrect behaviour, as the docstring for > > org-insert-link says: > > > > If

Re: [O] Bug: Fix for org-make-link-description-function use in org-insert-link [9.0.10 (9.0.10-5-g1654a5-elpa @ /home/rrt/.emacs.d/elpa/org-20170904/)]

Hello, Reuben Thomas writes: > This seems to be incorrect behaviour, as the docstring for > org-insert-link says: > > If `org-make-link-description-function' is non-nil, this function will be > called with the link target, and the result will be the default > link

[O] Bug: Fix for org-make-link-description-function use in org-insert-link [9.0.10 (9.0.10-5-g1654a5-elpa @ /home/rrt/.emacs.d/elpa/org-20170904/)]

Remember to cover the basics, that is, what you expected to happen and what in fact did happen. You don't know how to make a good report? See http://orgmode.org/manual/Feedback.html#Feedback Your bug report will be posted to the Org mailing list.

Re: [O] Bug: markdown export errors on headers [9.0.9 (9.0.9-82-gb862c2-elpaplus @ /home/fommil/.emacs.d/elpa/org-plus-contrib-20170814/)]

Tim Cross writes: > Loris Bennett writes: > >> Adam Porter writes: >> >>> "Loris Bennett" writes: >>> I didn't know about this function either. Is it correct that the org parts of 'org-plus-contrib' shadow the

Re: [O] Bug: markdown export errors on headers [9.0.9 (9.0.9-82-gb862c2-elpaplus @ /home/fommil/.emacs.d/elpa/org-plus-contrib-20170814/)]

This is an artefact of having the two packages. The package system does not support alternatives. I have posted a few times regarding this. I don't think it does any harm, but many people will find they have both org-plus-contrib as well as org installed. The main draw back is that updates can

Re: [O] Bug: markdown export errors on headers [9.0.9 (9.0.9-82-gb862c2-elpaplus @ /home/fommil/.emacs.d/elpa/org-plus-contrib-20170814/)]

Adam Porter writes: > "Loris Bennett" writes: > >> I didn't know about this function either. Is it correct that the org >> parts of 'org-plus-contrib' shadow the whole of 'org', e.g. >> >> ... >>

Re: [O] Bug: markdown export errors on headers [9.0.9 (9.0.9-82-gb862c2-elpaplus @ /home/fommil/.emacs.d/elpa/org-plus-contrib-20170814/)]

"Loris Bennett" writes: > I didn't know about this function either. Is it correct that the org > parts of 'org-plus-contrib' shadow the whole of 'org', e.g. > > ... > /home/loris/.emacs.d/elpa/org-plus-contrib-20170828/org hides >

Re: [O] Bug: markdown export errors on headers [9.0.9 (9.0.9-82-gb862c2-elpaplus @ /home/fommil/.emacs.d/elpa/org-plus-contrib-20170814/)]

Kaushal Modi writes: > On Fri, Sep 1, 2017, 10:49 PM Adam Porter wrote: > > Kaushal Modi writes: > > > M-x list-load-path-shadows will also help. Pay attention to shadows on org > packages. > > Wow, I did not know about

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

Hello, Niall Dooley writes: > 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"

Re: [O] Bug: markdown export errors on headers [9.0.9 (9.0.9-82-gb862c2-elpaplus @ /home/fommil/.emacs.d/elpa/org-plus-contrib-20170814/)]

Wow, thanks, that is comprehensive. :)

Re: [O] Bug: markdown export errors on headers [9.0.9 (9.0.9-82-gb862c2-elpaplus @ /home/fommil/.emacs.d/elpa/org-plus-contrib-20170814/)]

On Fri, Sep 1, 2017, 10:49 PM Adam Porter wrote: > Kaushal Modi writes: > > > M-x list-load-path-shadows will also help. Pay attention to shadows on > org packages. > > Wow, I did not know about that command. I have a bit of cleaning-up to > do. :)

Re: [O] Bug: markdown export errors on headers [9.0.9 (9.0.9-82-gb862c2-elpaplus @ /home/fommil/.emacs.d/elpa/org-plus-contrib-20170814/)]

Kaushal Modi writes: > M-x list-load-path-shadows will also help. Pay attention to shadows on org > packages. Wow, I did not know about that command. I have a bit of cleaning-up to do. :)

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

Hi Sébastien, That's my point. I'm reporting that if such a custom command is created through the customise interface with a setting of "Number of days in agenda: org-agenda-span" and a choice of "day" then the quote (') is not included. It appears as (org-agenda-span day) instead of

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

Hello I might say something stupid buy isn't it 'day (with a simple quote) ? ⁣Sent from Blue ​ On 30 Aug 2017, 14:45, at 14:45, Niall Dooley wrote: >Hi all, > >This is my first mail to this list so please tell me if I haven't >followed the expected conventions. > >I created

[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)

Re: [O] Bug: ODT export priority styling [9.0.9 (9.0.9-88-g251f88-elpaplus @ ~/.emacs.d/elpa/org-plus-contrib-20170821/)]

Hello, Henry Todd writes: > What I did: exported an Org doc to ODT via org-odt-export-to-odt > > Expected: priorities have "OrgPriority-A/B/C" styles assigned > > Observed: priorities have "Default Style" assigned > > > I've been working with ODT exports, and custom styling via an

Re: [O] Bug: error sorting outline items [9.0.10 (9.0.10-elpa @ c:/users/ian/.emacs.d/elpa/org-20170827/)]

Hello, Ian Garmaise writes: > Often (but not always) when I attempt to sort some headlines, the sort > fails, and the following error message occurs (usually same after > reloading org uncompiled) > > Sorting entries... > eq: Symbol’s function definition is void:

[O] Bug: ODT export priority styling [9.0.9 (9.0.9-88-g251f88-elpaplus @ ~/.emacs.d/elpa/org-plus-contrib-20170821/)]

What I did: exported an Org doc to ODT via org-odt-export-to-odt Expected: priorities have "OrgPriority-A/B/C" styles assigned Observed: priorities have "Default Style" assigned I've been working with ODT exports, and custom styling via an ODT_STYLES_FILE header. While I can style the TODO

[O] Bug: error sorting outline items [9.0.10 (9.0.10-elpa @ c:/users/ian/.emacs.d/elpa/org-20170827/)]

Often (but not always) when I attempt to sort some headlines, the sort fails, and the following error message occurs (usually same after reloading org uncompiled) Sorting entries... eq: Symbol’s function definition is void: org-clocking-buffer Here is the backtrace: Debugger entered--Lisp

Re: [O] Bug: Deleting region in table [9.0.8 (9.0.8-dist @ /Users/nick/.emacs.d/lisp/org/)]

Hi Nicholas, I see the fix for this bug (commit 91c68865c64422028faca96b7ff03541e7cf) was merged for org 9.0.10. However, I installed 9.0.10 this morning and the bug still occurs. Apologies if I am missing something. With thanks, Nick H On Thu, Aug 17 2017, Nicolas Goaziou wrote: > Nick

Re: [O] Bug: org-copy-visible includes emphasis markerse hidden by org-hide-emphasis-markers [8.2.10 (release_8.2.10 @ /usr/share/emacs/25.2/lisp/org/)]

Hello, Gary Cheng writes: > With evil-mode enabled (bug still applies without using evil, see: > https://github.com/emacs-evil/evil/issues/907), start Emacs, evaluate (setq > org-hide-emphasis-markers t). > > Open a org file containing the following line: > > ~$ firejail

Re: [O] Bug in the sorting of clocktables with ":sort (4 . ?T)" for clock sums over "100:00" hours

Am 25.08.2017 um 00:07 schrieb Nicolas Goaziou: Hello, Rainer Stengele writes: I may have found a bug in the sorting of clocktables. I am summing up clocked time over time periods. [...] As soon as the sum grows higher than 100:00 sorting is corrupted:

Re: [O] Bug in the sorting of clocktables with ":sort (4 . ?T)" for clock sums over "100:00" hours

Hello, Rainer Stengele writes: > I may have found a bug in the sorting of clocktables. > I am summing up clocked time over time periods. [...] > As soon as the sum grows higher than 100:00 sorting is corrupted: > > #+BEGIN: clocktable :maxlevel 1 :properties

[O] Bug: org-copy-visible includes emphasis markerse hidden by org-hide-emphasis-markers [8.2.10 (release_8.2.10 @ /usr/share/emacs/25.2/lisp/org/)]

Emacs : GNU Emacs 25.2.1 (x86_64-unknown-linux-gnu, GTK+ Version 3.22.16) of 2017-07-15 Package: Org-mode version 8.2.10 (release_8.2.10 @ /usr/share/emacs/25.2/lisp/org/)

[O] Bug in the sorting of clocktables with ":sort (4 . ?T)" for clock sums over "100:00" hours

Hi, I may have found a bug in the sorting of clocktables. I am summing up clocked time over time periods. As long as the clocksum is under "100:00" (6 characters including ":") sorting seems to be ok: #+BEGIN: clocktable :maxlevel 1 :properties ("CATEGORY") :fileskip0 t :scope

Re: [O] Bug: export to markdown invalid URL

Hi, > Isn't it already the case? Sorry, I sent that email without reading the 'applied' email, so it was premature. The fix looks good currently. > I think the current patch is fine. Yours is equivalent, but since we > already bound `raw-path', we might as well use it. yup, that is true, I'm

Re: [O] Bug: export to markdown invalid URL

Jay Kamat writes: > sorry for the repeated emails, but I think I've come up with a better > solution to this issue, to just use the raw link target in the target > of the markdown export, which I've attached to this email. Feel free > to pick either one of these patches or

Re: [O] Bug: export to markdown invalid URL

Hi again, sorry for the repeated emails, but I think I've come up with a better solution to this issue, to just use the raw link target in the target of the markdown export, which I've attached to this email. Feel free to pick either one of these patches or come up with something better. Hope

Re: [O] Bug: export to markdown invalid URL

Hello, Jay Kamat writes: > Subject: [PATCH] ox-md.el: Fix missing ':' in exported markdown image links > > * lisp/ox-md.el (org-md-link): Append ':' to the type of non-file > image links. Applied. Thank you. Regards, -- Nicolas Goaziou

Re: [O] Bug: export to markdown invalid URL

Hi, Thanks for catching that. That was my fault, for failing to test commit f3d7284ebd0c6e8248f7c3c444937270402b0ba6 properly. See http://lists.gnu.org/archive/html/emacs-orgmode/2017-08/msg00147.html for the previous thread. I've attached a trivial patch which appears to fix the issue for me,

[O] Bug: export to markdown invalid URL

Hello everyone, using latest master, an org file containing just the link #+BEGIN_SRC org [[http://orgmode.org/img/org-mode-unicorn-logo.png]] #+END_SRC on export to markdown with =C-c C-e m m= produces the md file #+BEGIN_EXAMPLE # Table of Contents

Re: [O] Bug: markdown export errors on headers [9.0.9 (9.0.9-82-gb862c2-elpaplus @ /home/fommil/.emacs.d/elpa/org-plus-contrib-20170814/)]

By running this (cl-delete-if (lambda (el) (string-match-p "/usr/share/.*org" el)) load-path) I'm able to hide org and now the org-plus-contrib loads up, yay! Thanks for the hints. On 21 August 2017 at 01:40, Kaushal Modi wrote: > On Sun, Aug 20, 2017, 4:25 PM

Re: [O] Bug: markdown export errors on headers [9.0.9 (9.0.9-82-gb862c2-elpaplus @ /home/fommil/.emacs.d/elpa/org-plus-contrib-20170814/)]

On Sun, Aug 20, 2017, 4:25 PM Nicolas Goaziou wrote: > > > then I can try to investigate what could be causing the Emacs org > > to load. I cannot see how that is possible since it is not even > > available on the elisp path anymore. > > > > Is there a way to check which

Re: [O] Bug: markdown export errors on headers [9.0.9 (9.0.9-82-gb862c2-elpaplus @ /home/fommil/.emacs.d/elpa/org-plus-contrib-20170814/)]

Sam Halliday writes: > If you are confirming that org is definitely compatible with my .org > file It is, although I didn't check the details of the output. It didn't error in the process anyway. > then I can try to investigate what could be causing the Emacs org > to

Re: [O] Bug: markdown export errors on headers [9.0.9 (9.0.9-82-gb862c2-elpaplus @ /home/fommil/.emacs.d/elpa/org-plus-contrib-20170814/)]

On 20 August 2017 at 16:07, Nicolas Goaziou wrote: > Hello, > > Sam Halliday writes: > >> To ensure that the Emacs-installed org-mode is not interfering, I >> added this to my init >> >> (cl-delete-if >>(lambda (el) (string-match-p ".*org"

Re: [O] Bug: markdown export errors on headers [9.0.9 (9.0.9-82-gb862c2-elpaplus @ /home/fommil/.emacs.d/elpa/org-plus-contrib-20170814/)]

Hello, Sam Halliday writes: > To ensure that the Emacs-installed org-mode is not interfering, I > added this to my init > > (cl-delete-if >(lambda (el) (string-match-p ".*org" el)) >load-path) > > and I can confirm that emacs/org is not in my load-path. > >

Re: [O] Bug: markdown export errors on headers [9.0.9 (9.0.9-82-gb862c2-elpaplus @ /home/fommil/.emacs.d/elpa/org-plus-contrib-20170814/)]

Hi Nicholas, To ensure that the Emacs-installed org-mode is not interfering, I added this to my init (cl-delete-if (lambda (el) (string-match-p ".*org" el)) load-path) and I can confirm that emacs/org is not in my load-path. However, the backtrace still occurs. For a much larger file

Re: [O] Bug: Explicit <6> table column width [9.0.9 (release_9.0.9-754-g940c90)]

Hello, Paul Stansell writes: > I think there might be a something wrong when explicitly setting a width > of a table column. > > For example, for this table > > |---+--| > | | <6> | > | 1 | one

Re: [O] Bug: markdown export errors on headers [9.0.9 (9.0.9-82-gb862c2-elpaplus @ /home/fommil/.emacs.d/elpa/org-plus-contrib-20170814/)]

Hello, Sam Halliday writes: > Regression in org-plus-contrib from http://orgmode.org/elpa/ vs version > distributed with Emacs 25.2.1 > > Running > > M-x md-org-export-to-markdown > > on a simple org file such as the following > >

[O] Bug: markdown export errors on headers [9.0.9 (9.0.9-82-gb862c2-elpaplus @ /home/fommil/.emacs.d/elpa/org-plus-contrib-20170814/)]

Regression in org-plus-contrib from http://orgmode.org/elpa/ vs version distributed with Emacs 25.2.1 Running M-x md-org-export-to-markdown on a simple org file such as the following == #+TITLE: Functional Programming in Scala for Mortals

Re: [O] Bug: Deleting region in table [9.0.8 (9.0.8-dist @ /Users/nick/.emacs.d/lisp/org/)]

Hello, Nick Helm writes: > Deleting a region within an org table causes point to jump. > > Recipe: > > Emacs -Q > org-mode > > ;make a table > | this is a simple | table | > > double-click "simple" ;place region over a word > > > With the last command, I expect

Re: [O] Bug: Symbol's value as variable is void: org-src-lang-modes

On Tue, Aug 15, 2017 at 3:48 PM Elliott Slaughter < elliottslaugh...@gmail.com> wrote: > Actually, the backtrace goes through the el-get loaddefs file, so maybe > something is going wrong there. Let me check with the el-get developers and > see if they know what is going on. > Yes, that's very

[O] Bug: Symbol's value as variable is void: org-src-lang-modes

When I install a fresh copy of org-mode via el-get, I see the following error: Bug: Symbol's value as variable is void: org-src-lang-modes I don't believe this is a problem in el-get, but if I'm wrong, let me know and I will take this up with the el-get developers. Here is the backtrace:

Re: [O] Bug: Symbol's value as variable is void: org-src-lang-modes

Actually, the backtrace goes through the el-get loaddefs file, so maybe something is going wrong there. Let me check with the el-get developers and see if they know what is going on. On Tue, Aug 15, 2017 at 12:27 PM, Elliott Slaughter < elliottslaugh...@gmail.com> wrote: > When I install a fresh

Re: [O] Bug? Setting #+OPTIONS: title:nil Seems to Be Ignored in HTML Export.

On Wed, Aug 9, 2017 at 5:58 AM Rasmus wrote: > There’s definitely some sort of issue... > > I guess this is for a local file? Correct. I was testing it out only on an HTML file (local) exported from org. > I guess it needs to be publicly > available. But it doesn’t seem to

[O] Bug: Deleting region in table [9.0.8 (9.0.8-dist @ /Users/nick/.emacs.d/lisp/org/)]

Remember to cover the basics, that is, what you expected to happen and what in fact did happen. You don't know how to make a good report? See http://orgmode.org/manual/Feedback.html#Feedback Your bug report will be posted to the Org mailing list.

[O] Bug: python code block single import line [9.0.9 (release_9.0.9-754-g940c90)]

Hello, When executing the python code block #+begin_src python :session python1 import numpy as np #+end_src I get this error in my python buffer Python 3.5.1 |Anaconda 2.5.0 (64-bit)| (default, Dec 7 2015, 11:16:01) [GCC 4.4.7 20120313 (Red Hat 4.4.7-1)] on linux Type "help",

[O] Bug: Explicit <6> table column width [9.0.9 (release_9.0.9-754-g940c90)]

Hello, I think there might be a something wrong when explicitly setting a width of a table column. For example, for this table |---+--| | | <6> | | 1 | one | | 2 | This is a long chunk of text | | 3 |

Re: [O] Bug: Babel result block '#+end_example' not indented [9.0.9 (release_9.0.9-748-g3359e0 @ /Users/xcy/src/org-mode/lisp/)]

Hello, Chunyang Xu writes: > I find my last patch breaks at least ":result org", please see the newer > patch. Thank you for the report and the patch. I ended up applying a slightly different patch, however. Regards, -- Nicolas Goaziou

Re: [O] Bug: Latex math mode not set in footnotes [9.0.9 (9.0.9-68-g492420-elpa @ /Home/ps/.emacs.d/elpa/org/)]

Hello, Paul Stansell writes: > Hello, > > Latex math mode is not set in a footnote when exporting an org file to > tex or pdf. Below and attached is a simple example. > > Thanks > > ---cut here-- > * Example > > When exporting

Re: [O] Bug: Babel result block '#+end_example' not indented [9.0.9 (release_9.0.9-748-g3359e0 @ /Users/xcy/src/org-mode/lisp/)]

I find my last patch breaks at least ":result org", please see the newer patch. >From 4ef5b67af22469bf2591dda0b9b90db1f4df8617 Mon Sep 17 00:00:00 2001 From: Chunyang Xu Date: Sun, 13 Aug 2017 15:08:52 +0800 Subject: [PATCH] ob-core: Fix indentation * lisp/ob-core.el

[O] Bug: Babel result block '#+end_example' not indented [9.0.9 (release_9.0.9-748-g3359e0 @ /Users/xcy/src/org-mode/lisp/)]

For example (noticing the last line '#+end_example' is not indented with two space) * test #+BEGIN_SRC sh :results output seq 10 #+END_SRC #+RESULTS: #+begin_example 1 2 3 4 5 6 7 8 9 10 #+end_example By reading the source code, I think 'indent-rigidly' doesn't

Re: [O] Bug: Beamer export error

Rasmus writes: > It should be fixed by commit 323fc95b4. Thank you very much, seems to be in order again. Jarmo

[O] Bug: Latex math mode not set in footnotes [9.0.9 (9.0.9-68-g492420-elpa @ /Home/ps/.emacs.d/elpa/org/)]

Hello, Latex math mode is not set in a footnote when exporting an org file to tex or pdf. Below and attached is a simple example. Thanks ---cut here-- * Example When exporting to pdf math $\hat{x}$ is okay in the main text but not in this

Re: [O] Bug: Marking repeated tasks with two tags as DONE causes problems

> "Nicolas" == Nicolas Goaziou writes: Nicolas> I still cannot reproduce it. Nicolas> Does the very recent Nicolas> 10b1cfb0317274a91500562a2872f2626160f079 fix this? Things seem ok for me too. I had a separate issue with empty tags appearing in habits,

Re: [O] Bug: Marking repeated tasks with two tags as DONE causes problems

Nicolas Goaziou writes: > > I still cannot reproduce it. > > Does the very recent 10b1cfb0317274a91500562a2872f2626160f079 fix this? > Yup. That commit seems to fix it. Thanks! Best, Josh

Re: [O] Bug: Marking repeated tasks with two tags as DONE causes problems

Dear Josh, > "Josh" == Josh Moller-Mara writes: Josh> Hello, Josh> I'm starting to encounter a strange, silent problem when Josh> switching the state of a task with multiple tags. With the Josh> following minimal example: Josh> #+STARTUP: logdone

Re: [O] Bug: Marking repeated tasks with two tags as DONE causes problems

Hello, Colin Baxter writes: > Dear Josh, >> "Josh" == Josh Moller-Mara writes: > > Josh> Hello, > > Josh> I'm starting to encounter a strange, silent problem when > Josh> switching the state of a task with multiple tags. With the > Josh>

[O] Bug: Marking repeated tasks with two tags as DONE causes problems

Hello, I'm starting to encounter a strange, silent problem when switching the state of a task with multiple tags. With the following minimal example: #+STARTUP: logdone #+STARTUP: logdrawer * TODO Hello :hi:there: SCHEDULED: <2017-08-11 Fri .+1d> Switching The "hello" task from "TODO" to

Re: [O] Bug: Beamer export error

Hello, Rasmus writes: > It should be fixed by commit 323fc95b4. Thank you. Regards, -- Nicolas Goaziou

Re: [O] Bug: Beamer export error

Nicolas Goaziou writes: > Hello, > > Rasmus writes: > >> This is caused by this commit, which changes how org-split-string works. >> >> f776e65373fa135fffb51e201698823fbfb3865b >> >> Before (org-split-string "" ",") would return ‘nil’. Now it returns

Re: [O] Bug: Beamer export error

Hello, Rasmus writes: > This is caused by this commit, which changes how org-split-string works. > > f776e65373fa135fffb51e201698823fbfb3865b > > Before (org-split-string "" ",") would return ‘nil’. Now it returns "". > > Depending on whether the new behavior is desired or

Re: [O] Bug: Beamer export error

Hi Jarmo, Thanks for your report. Jarmo Hurri writes: > I get an error (pdflatex hangs up) when trying to Beamer export the > following simple Org file (key command C-c C-e l O). > > # - > > #+STARTUP: beamer >

Re: [O] Bug: Beamer export error

While the bug is being fixed, here is a quick band-aid for anyone else struggling with this problem. 1. When the export hangs up, press C-g to interrupt. 2. Run the following on the intermediate tex file, here exported.tex : sed -i 's/\[,/\[/g' exported.tex 3. Run pdflatex by hand:

[O] Bug: Beamer export error

Greetings. I get an error (pdflatex hangs up) when trying to Beamer export the following simple Org file (key command C-c C-e l O). # - #+STARTUP: beamer * This is a simple test - let us see what happens #

Re: [O] Bug? Setting #+OPTIONS: title:nil Seems to Be Ignored in HTML Export.

Rasmus writes: > Hi, > > Kaushal Modi writes: > >> Thanks for checking. The validator (the default one in org-html-postamble) >> never worked for me, probably because of something being blocked at work.. >> I get this when I click the validator link: >> >>

Re: [O] Bug? Setting #+OPTIONS: title:nil Seems to Be Ignored in HTML Export.

Hi, Kaushal Modi writes: > Thanks for checking. The validator (the default one in org-html-postamble) > never worked for me, probably because of something being blocked at work.. > I get this when I click the validator link: > > = > Sorry! This document cannot be

Re: [O] Bug: Wrong type argument: integer-or-marker-p, nil on refile

Hello, Michaël Cadilhac writes: > Hi there everyone; > > Here's the ECM. > > init.el: > (require 'org) > (setq org-refile-use-outline-path (quote file)) > > Now open an Org file, say foo.org, and type C-u C-c C-w foo.org/ RET > At org.el:11832, pos is nil. Fixed. Thank

Re: [O] Bug: org-clock-sum-current-item/org-clock-get-sum-start not respecting LAST_REPEAT [9.0.9 (release_9.0.9-697-gb0776e @ /usr/local/share/emacs/site-lisp/org/)]

Hello, Josh Moller-Mara writes: > Recently I've found that clocking in to a repeating task is giving me an > incorrect "task time since last repeat". Normally, when I clock into a task, > mark it as done, and clock in again, I expect the starting clock time to > be 0. In this

[O] Bug: org-clock-sum-current-item/org-clock-get-sum-start not respecting LAST_REPEAT [9.0.9 (release_9.0.9-697-gb0776e @ /usr/local/share/emacs/site-lisp/org/)]

Hey there, Recently I've found that clocking in to a repeating task is giving me an incorrect "task time since last repeat". Normally, when I clock into a task, mark it as done, and clock in again, I expect the starting clock time to be 0. In this example: * TODO Stuff SCHEDULED: <2017-08-04

Re: [O] Bug: Wrong type argument: integer-or-marker-p, nil on refile

Michaël Cadilhac writes: > Here's the ECM. > > init.el: > (require 'org) > (setq org-refile-use-outline-path (quote file)) > > Now open an Org file, say foo.org, and type C-u C-c C-w foo.org/ RET > At org.el:11832, pos is nil. Confirmed here with Org 9.0.5. I think it's

[O] Bug: org-tag-alist defcustom does not allow ("tag") [9.0.9 (9.0.9-40-gb7fdc3-elpaplus @ elpa/org-plus-contrib-20170710/)]

`org-tag-alist' and `org-tag-persistent-alist' defcustom types are not set up to accept non-cons cell tags like ("tag"). Emacs : GNU Emacs 25.2.1 (x86_64-pc-linux-gnu, GTK+ Version 3.10.8), modified by Debian Package: Org mode version 9.0.9 (9.0.9-40-gb7fdc3-elpaplus @

[O] Bug: Wrong type argument: integer-or-marker-p, nil on refile

Hi there everyone; Here's the ECM. init.el: (require 'org) (setq org-refile-use-outline-path (quote file)) Now open an Org file, say foo.org, and type C-u C-c C-w foo.org/ RET At org.el:11832, pos is nil. Cheers; M.

Re: [O] Bug: Git repository doesn't ignore contributed lisp/*.el files [9.0.9 (release_9.0.9-690-g27e5be @ /home/cassou/.emacs.d/lib/org/lisp/)]

Hello, Damien Cassou writes: > I've just cloned the repository and ran this command: > > make compile autoloads info ORG_ADD_CONTRIB="org-notmuch" > > Now, the lisp/ directory contains both org-notmuch.el and > org-notmuch.elc. My problem is that the former is not ignored

Re: [O] Bug: emphasis crosses quotation marks [9.0.9 (release_9.0.9 @ /usr/new/share/emacs/26.0.50/lisp/org/)]

Nicolas Goaziou wrote: > Mike Kupfer writes: > > I would not expect emphasis to cross quotation marks. > > This was done because it allows to write, e.g., ~C-x "~. See > . [...] > I cannot see a generic solution

Re: [O] Bug? Setting #+OPTIONS: title:nil Seems to Be Ignored in HTML Export.

While I totally agree with your sentiments, I don't think we should worry about how/what the browser renders. We should ensure valid HTML and leave how this is interpreted/rendered to the browsers. Alternative is we jump through lots of hoops trying to get something which looks reasonable in all

Re: [O] Bug? Setting #+OPTIONS: title:nil Seems to Be Ignored in HTML Export.

I think I agree. All HTML documents should have a title tag. Not all HTML documents need a h1-title. I think the easy solution is to just default to document name when no title is set and don't add a h1-title. If a title block is set, then do as is now the case. tim Rasmus writes: > Kaushal

Re: [O] Bug? Setting #+OPTIONS: title:nil Seems to Be Ignored in HTML Export.

On Tue, Aug 1, 2017 at 4:48 PM Rasmus wrote: > Thanks for looking into this. That hack really leaves the title on the > tabs completely blank! That was the idea.. If someone sets "#+TITLE:", they expect *no* title :) > I’ve never seen anything like it. It’s in line > with

Re: [O] Bug? Setting #+OPTIONS: title:nil Seems to Be Ignored in HTML Export.

Hi Kaushal, Kaushal Modi writes: > Your patch to fix printing of h1 title when :with-title is nil looks good. > > More comments below. OK I’ll push it then. > Here is my attempt to fix it (below is a whitespace ignored diff): Thanks for looking into this. That hack

Re: [O] Bug? Setting #+OPTIONS: title:nil Seems to Be Ignored in HTML Export.

Hi Rasmus, Your patch to fix printing of h1 title when :with-title is nil looks good. More comments below. On Tue, Aug 1, 2017 at 7:18 AM Rasmus wrote: > Yes, but that’s a feature. It’s how ox-{latex,odt} works as well (via > hyperref). > OK, I agree that the title being made

Re: [O] Bug: Blank line when logging state changes [9.0.9 (9.0.9-692-gfbf31d.dirty-elpaplus @ /tmp/emacs/.emacs.d/elpa/org-plus-contrib-20170801/)]

Hello, Dale Sedivec writes: > I think a recent change to org-split-string in master may have made logging > of state changes a little uglier, adding "\\" and an empty line with > trailing whitespace. Steps to reproduce: > [...] > IMHO the new behavior of org-split-string

Re: [O] Bug: emphasis crosses quotation marks [9.0.9 (release_9.0.9 @ /usr/new/share/emacs/26.0.50/lisp/org/)]

Hello, Mike Kupfer writes: > In Emacs master ("GNU Emacs 26.0.50 (build 3, x86_64-pc-linux-gnu, X > toolkit, Xaw scroll bars) of 2017-07-30", git changeset c8f44e4b; Org > mode 9.0.9), I get strikeout text from "+" to "+" in > > "+" word "+" > > (I also see the

[O] Bug: Blank line when logging state changes [9.0.9 (9.0.9-692-gfbf31d.dirty-elpaplus @ /tmp/emacs/.emacs.d/elpa/org-plus-contrib-20170801/)]

Hi! I think a recent change to org-split-string in master may have made logging of state changes a little uglier, adding "\\" and an empty line with trailing whitespace. Steps to reproduce: 1. Start fresh Emacs with no local configuration (e.g. mkdir /tmp/emacs && HOME=/tmp/emacs emacs) 2.

Re: [O] Bug? Setting #+OPTIONS: title:nil Seems to Be Ignored in HTML Export.

Hi, Kaushal Modi writes: > With the new patch, wouldn't the title, that was not intended to be shown, > still show up in places like browser tabs and bookmarks? I have to yet try > it. Yes, but that’s a feature. It’s how ox-{latex,odt} works as well (via hyperref). >

Re: [O] Bug? Setting #+OPTIONS: title:nil Seems to Be Ignored in HTML Export.

On Tue, Aug 1, 2017, 5:52 AM Rasmus wrote: > > That is wrong IMO. Title is mandatory in at least HTML{4,5}. > > https://www.w3schools.com/tags/tag_title.asp Thanks, I was not aware of that. AFAIR Org already allows invalid HTML document to be produced when the > TITLE is

Re: [O] Bug? Setting #+OPTIONS: title:nil Seems to Be Ignored in HTML Export.

Kaushal Modi writes: > This patch fixes this: > > From e57e9e798dd1a54cae7a633fc67e2f825b967eea Mon Sep 17 00:00:00 2001 > From: Kaushal Modi > Date: Mon, 31 Jul 2017 14:30:40 -0400 > Subject: [PATCH] Respect :with-title in ox-html > > *

Re: [O] Bug? Setting #+OPTIONS: title:nil Seems to Be Ignored in HTML Export.

Hello, Kaushal Modi writes: > From e57e9e798dd1a54cae7a633fc67e2f825b967eea Mon Sep 17 00:00:00 2001 > From: Kaushal Modi > Date: Mon, 31 Jul 2017 14:30:40 -0400 > Subject: [PATCH] Respect :with-title in ox-html > > * lisp/ox-html.el

Re: [O] Bug? Setting #+OPTIONS: title:nil Seems to Be Ignored in HTML Export.

This patch fixes this: >From e57e9e798dd1a54cae7a633fc67e2f825b967eea Mon Sep 17 00:00:00 2001 From: Kaushal Modi Date: Mon, 31 Jul 2017 14:30:40 -0400 Subject: [PATCH] Respect :with-title in ox-html * lisp/ox-html.el (org-html--build-meta-info): Do not insert tag in

Re: [O] Bug? Setting #+OPTIONS: title:nil Seems to Be Ignored in HTML Export.

On Mon, Jul 31, 2017 at 1:37 PM wrote: > I don't know if this is intended behaviour or not. > > Save the following as setuop.org > > #+BEGIN_SRC > > :SETUP: > #+LANGUAGE: en > #+DRAWERS: SETUP NOTES PROPERTIES > #+OPTIONS: author:nil date:nil d:nil title:nil ':t tex:t >

[O] Bug? Setting #+OPTIONS: title:nil Seems to Be Ignored in HTML Export.

I don't know if this is intended behaviour or not. Save the following as setuop.org #+BEGIN_SRC :SETUP: #+LANGUAGE: en #+DRAWERS: SETUP NOTES PROPERTIES #+OPTIONS: author:nil date:nil d:nil title:nil ':t tex:t #+STARTUP: content indent :END: #+END_SRC Now include setup.org in test.org

Re: [O] Bug: http://orgmode.org/cgit.cgi/org-mode.git/ - 502 Bad Gateway

Hi, it works again now. Best regards Robert On Mon, 31 Jul 2017 18:50:44 +0800 Chunyang Xu wrote: > I visited the URL by clicking "cgit" on http://orgmode.org/. > > >

[O] Bug: http://orgmode.org/cgit.cgi/org-mode.git/ - 502 Bad Gateway

I visited the URL by clicking "cgit" on http://orgmode.org/.

[O] Bug: Git repository doesn't ignore contributed lisp/*.el files [9.0.9 (release_9.0.9-690-g27e5be @ /home/cassou/.emacs.d/lib/org/lisp/)]

Remember to cover the basics, that is, what you expected to happen and what in fact did happen. You don't know how to make a good report? See http://orgmode.org/manual/Feedback.html#Feedback Your bug report will be posted to the Org mailing list.

<    12   13   14   15   16   17   18   19   20   21   >