Re: [O] API for manipulating #+PROPERTY entries?

Hello, Nik Clayton writes: > Is there an API for manipulating properties that are set in #+PROPERTY > lines before the first headline of a file (i.e., not in a property > drawer)? There is no API for keywords. > Using org-entry-put when point is before the first headline throws a > "Before

[O] API for manipulating #+PROPERTY entries?

Hoi, Is there an API for manipulating properties that are set in #+PROPERTY lines before the first headline of a file (i.e., not in a property drawer)? I've got some properties that (a) make sense when set for the whole file, and (b) the file contains multiple first level headings (which isn't

[O] [Discuss] make :tangle header argument respect :dir could save info typing

I realized one thing, the combination of ~:mkdir~, ~:dir~, and ~:tangle~ does not work good enough. Can make ~:tangle~ respect ~:dir~ too. WDYT? Here is an example: #+begin_src clojure :mkdirp yes :dir "data/code/clj-crawler-demo" :tangle "src/clj_crawler_demo/core.clj" (ns

Re: [O] [FEATURE] Make header argument :mkdirp yes work for other header arguments not just :tangle

Nicolas Goaziou writes: > Hello, > > stardiviner writes: > >> New patch in attachment. > > Thank you. > >> From aafdd41f7ae5f6218a2be890f58d45be443de4a9 Mon Sep 17 00:00:00 2001 >> From: stardiviner >> Date: Sat, 2 Mar 2019 12:11:47 +0800 >> Subject: [PATCH] ob-core.el: Make :mkdirp work for

Re: [O] manual: stale bindings for org-clock-report and org-columns-insert-dblock

I don't use Icicles, but I cannot reproduce it. What are the exact steps to do so? Sorry, it's not clear whether you use Icicles. At the moment the recipe is: 1. Install icicles as described here . Enable it by doing icy-mode. 2. Do

Re: [O] Bug: clocktable error in org-agenda [9.2.2 (release_9.2.2-245-g9d7b1e @ /home/dortmann/src/git-org-mode/lisp/)]

Actually I think it is a bug. This weird behaviour has been around for a very long time (years probably). I have noticed similar behaviour with log mode, and clock check mode as well. I can reproduce the issue at with the following recipe: C-c a a (start org agenda) j -3 RET (go back 3 days

Re: [O] [RFC] Fixing link encoding once and for all

Hello, Neil Jerram writes: > On Fri, 1 Mar 2019 at 08:14, Nicolas Goaziou wrote: >> The regexp for bracket links could be, in its simple (!) form: >> >> \[\[\(.*?[^\\]\(?:\\\)*\)\]\(?:\[\([^\000]+?\)\]\)?\] > > [then a bit later] >> Small update, in its string form now: >> >> >>

Re: [O] [RFC] Fixing link encoding once and for all

On Fri, 1 Mar 2019 at 08:14, Nicolas Goaziou wrote: > > Hello, > > Neil Jerram writes: > > > Do you mean Windows file names in existing Org files? I.e. the > > back-compatibility concern? > > > > If so, yes, I confess I didn't think at all about back-compatibility, > > with my suggestion above.

Re: [O] [FEATURE] Make header argument :mkdirp yes work for other header arguments not just :tangle

Hello, stardiviner writes: > New patch in attachment. Thank you. > From aafdd41f7ae5f6218a2be890f58d45be443de4a9 Mon Sep 17 00:00:00 2001 > From: stardiviner > Date: Sat, 2 Mar 2019 12:11:47 +0800 > Subject: [PATCH] ob-core.el: Make :mkdirp work for :dir too > > * lisp/ob-core.el

Re: [O] Bug: clocktable error in org-agenda [9.2.2 (release_9.2.2-245-g9d7b1e @ /home/dortmann/src/git-org-mode/lisp/)]

This is crazy!  After months of problems, I myself no longer can reproduce this issue!  :-/ Comments welcome (Please!) ... but this issue no longer is actually a bug.  On 3/4/19 3:22 PM, Daniel Ortmann wrote: > Remember to cover the basics, that is, what you expected to happen and > what in fact

[O] Bug: clocktable error in org-agenda [9.2.2 (release_9.2.2-245-g9d7b1e @ /home/dortmann/src/git-org-mode/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 https://orgmode.org/manual/Feedback.html#Feedback Your bug report will be posted to the Org mailing list.

Re: [O] ob-core, org-outline-overlay-data error and byte-compile warning

.org/elpa/;)) > (package-initialize) > (use-package org > :ensure org-plus-contrib) > > Then the version 9.2 lives locally: >Org mode version 9.2.2 (9.2.2-elpaplus >@ /home/simon/.emacs.d/elpa/org-plus-contrib-20190304/) > > > The issue is when I evaluate `org-bab

Re: [O] manual: stale bindings for org-clock-report and org-columns-insert-dblock

Nikolay Kudryavtsev writes: > ... > Also can someone explain how do I get from org elpa version to the git > commit it's based on? E. g., in org-version.el I have > "9.2.1-33-g029cf6-elpaplus" but g029cf6 does not seem like a real > commit in the git repo. Try it without the 'g': that's just a

Re: [O] manual: stale bindings for org-clock-report and org-columns-insert-dblock

Hello, Nikolay Kudryavtsev writes: > The first is that drop in clock reports now use :scope file by > default, instead of :scope subtree. Indeed. This is because clocktable default properties include :scope property. I removed it. Thank you. > The second is that the clock report function is

Re: [O] manual: stale bindings for org-clock-report and org-columns-insert-dblock

Thanks for the tip. After reading that discussion and a few hours of research, there are actually three different problems I have with org-clock-report. The first is that drop in clock reports now use :scope file by default, instead of :scope subtree. The second is that the clock report

Re: [O] manual: stale bindings for org-clock-report and org-columns-insert-dblock

Nikolay Kudryavtsev writes: > Am I reading it correctly that C-c C-x C-r is no longer a valid keybinding? Is > this the reason why it now behaves so stupidly, creating a block with :scope > file and asking for that file? Can someone point me to a discussion of that > change? Manual is still

[O] ob-core, org-outline-overlay-data error and byte-compile warning

in my init.el: (add-to-list 'package-archives '("org" . "http://orgmode.org/elpa/;)) (package-initialize) (use-package org :ensure org-plus-contrib) Then the version 9.2 lives locally: Org mode version 9.2.2 (9.2.2-elpaplus @ /home/simon/.emacs.d/elpa/org-plus-c

Re: [O] New bug in org-agenda?

Hi Roland and Nicolas, Nicolas Goaziou writes: > I think it already is. Otherwise, it should happen today: IIRC, Org is > automatically updated every Monday. the process is kinda broken right now, I have to do this manually. It's probably just a permission issue, I'll fix it ASAP. > Anyway,

Re: [O] New bug in org-agenda?

Thanks, then I will try it later today. Regards, Roland. Nicolas Goaziou writes: > Hello, > > Roland Everaert writes: > >> I am facing the same issue with that version on emacs 25.2.2 (Ubuntu >> 18.04.2 LTS). >> >> >> When will it be available throu the Org Mode ELPA repo? > > I think it

Re: [O] New bug in org-agenda?

Hello, Roland Everaert writes: > I am facing the same issue with that version on emacs 25.2.2 (Ubuntu > 18.04.2 LTS). > > > When will it be available throu the Org Mode ELPA repo? I think it already is. Otherwise, it should happen today: IIRC, Org is automatically updated every Monday.

Re: [O] New bug in org-agenda?

On Mon, Mar 04 2019, Roland Everaert wrote: I am facing the same issue with that version on emacs 25.2.2 (Ubuntu 18.04.2 LTS). When will it be available throu the Org Mode ELPA repo? I got the update this morning (finally...) -- Joost Kremers Life has its moments

Re: [O] New bug in org-agenda?

Hi, I am facing the same issue with that version on emacs 25.2.2 (Ubuntu 18.04.2 LTS). When will it be available throu the Org Mode ELPA repo? Regards, Roland. Nicolas Goaziou writes: > Hello, > > Richard Stanton writes: > >> Using Org mode version 9.2.1 (9.2.1-33-g029cf6-elpaplus), I get

Re: [O] Mutually-exclusive Org tags still inherit each other

Hello, Tina Russell writes: > Well, I think it’s unreasonable to ask users to reinforce manually and > continuously something they’ve already specified in their settings. > Besides, my example was intentionally trivial—imagine managing a large > tree and having to remember which tags are