Re: org-capture with :prepend t breaks :clock-resume functionality in 9.1.9

A little different solution that takes advantage of the fact that adding a newline preserves the clock in the narrowed buffer. Maybe the right thing to do is to widen/re-narrow buffer to include the clock within org-clock-in though if it detects it's in an org capture buffer? Here is my working

org-capture with :prepend t breaks :clock-resume functionality in 9.1.9

I found a bug and traced down relevant pieces of it, but haven't figured out how to fix the behavior of org-capture where `:prepend t` `:clock-resume` works with and clock data from `:clock-in t` is visible with: ``` (setq org-capture-templates '(("t" "Todo" entry (file+headline "file.org"

[O] Quoting of noweb references and variable noweb function arguments

I'm having an issue with quoting noweb functions. Since quote is used to signify a variable being passed into the noweb syntax function call I cannot put a quote around theno web function call and end up with invalid bash. I feel like I had this working at some point and it turned out that

[O] Any easy way to use multiple indirect buffers based on subtrees?

I would like to be able to create N indirect buffers per subtree because I like working on each subtree in it's own eyebrowse workspace. Does anyone already do this? I didn't see config options to achieve what I wanted, so wanted to ask here before I look at the indirect buffer implementation to

Re: [O] Org habits is showing up faded after switching to emacs config from spacemacs

It looks like I was calling load-theme twice! Problem solved I suppose. On 8/16/18, Cody Goodman wrote: > For some reason my org habit colors are washed out. > > Before: https://imgur.com/a/EgcPrng > > Now washed out: https://imgur.com/a/nX9xHzG > > Here is my init.el >

[O] Org habits is showing up faded after switching to emacs config from spacemacs

For some reason my org habit colors are washed out. Before: https://imgur.com/a/EgcPrng Now washed out: https://imgur.com/a/nX9xHzG Here is my init.el https://gist.github.com/codygman/7b41f511547c47cb2a94d33f528c47d8 I'm guessing spacemacs was doing something I'm not? Thanks, Cody

Re: [O] How do you get the LOGBOOK information from the current heading at point?

(goto-char (org-element-property :contents-begin logbook)) > (setq current-element (org-element-at-point)) > (while (eq 'clock (car current-element)) > (push current-element clock-entries) > (forward-line) > (setq current-element (org-

[O] How do you get the LOGBOOK information from the current heading at point?

Given a TODO that looks like this: *** DONE put into spacemacs file CLOSED: [2018-08-04 Sat 21:18] :LOGBOOK: CLOCK: [2018-08-04 Sat 21:16]--[2018-08-04 Sat 12:18] => 0:02 :END: What function will get me the parts in CLOCK: [2018-08-04 Sat 21:16]--[2018-08-04 Sat 12:18] => 0:02,

[O] Override :clock-in (hence org-clock-in) behavior for a specific capture template

Here is my detailed problem exposition exported from org: 1 executive summary === I want to start at a child node and clock into the grandparent rather than the current child at point in a capture task 2 my capture , | ("f" "video game" entry

[O] Org alerts on osx

I tried using org alerts on osx but kept running into dbus errors. So I'm curious, does anyone have org alerts working on osx? Preferably something free I can install on work and home computers.

[O] Org mode notes collapse parser brittle

Does anyone else use notes extensively with src blocks and results drawers? It seems that the regex to parse src blocks and collapse them breaks on drawer :END: markers and possibly other things. Here's an image of the error: https://i.imgur.com/dqDsO5g.png And the example that it happens with: