Re: [O] is it bad to have both org and org-plus-contrib installed?

Hi all, I just discovered a bug in this advice that I suggested earlier in this thread.. I needed to fix the order of packages in the new-ret list that is returned. The bug was that the order of pkgs in new-ret was flipped compared to that in orig-ret.. so I needed to flip it back using reverse.

Re: [O] org-link-search failing to find links created by clock table

*** Some additional information, by example Emacs : GNU Emacs 25.2.1 (x86_64-apple-darwin16.4.0, Carbon Version 157 AppKit 1504.81) of 2017-03-07 Package: Org mode version 9.0.5 (release_9.0.5-351-g0e0fda.dirty @ /Users/stacey/.emacs.d/org-mode/lisp/) In this buffer the TODO keywords are

[O] [PATCH] lisp/ob-sql.el: Fix filename conversion in minGW environment.

Hi, Regarding a patch I made early. Ref. title: [PATCH] ob-sql.el: Support sqlcmd and cygwin environment. I found it does not for Emacs for Windows. More generally, it does not work in minGW or MSYS environments. I think it is because minGW is not a POSIX environment, and applications in minGW

Re: [O] is it bad to have both org and org-plus-contrib installed?

Hi, Coming late to this fray and responding to original Subject If you (require 'use-package) Then you might find the following to work, as I do: (use-package org :ensure org-plus-contrib ; following

[O] org-link-search failing to find links created by clock table

created a clock table and the resulting links fail to work. I get a message: condition-case: No match for fuzzy expression: DONE private data removed". Tracked that down to lisp/org.el org-link-search() where there are two identical messages. Changing the first to add the word "heading" confirms

Re: [O] Radio targets

Hi, Please see attached. The org file is just: * <<>> heading The discussion in *abc* highlights the issue. On Tue, Apr 11, 2017 at 5:28 AM, Nicolas Goaziou wrote: > Hello, > > R C writes: > > > I set up radio targets such as <<>> in a heading,

Re: [O] Radio targets

Hello, R C writes: > I set up radio targets such as <<>> in a heading, which makes all > occurrences of the word analysis to be links to the heading. However this > seems to override the boldface settings such *Analysis*, so that the > asterisks show up in the exported text.