Re: [O] org-protocol-check-filename-for-protocol obscures other errors

Hello, Adam Porter writes: > I've found that catching errors at this spot in > org-protocol-check-filename-for-protocol (currently line 618 in the > file): > > file:~/src/org-mode/lisp/org-protocol.el::(error > > Is causing a couple of problems. > > 1. Any error in the

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

Hello, "Stacey Marshall" writes: > Sorry, I'm trying out MailMate and forgot to select Plain Text when > copying in from Emacs. > > * Example of the issue > > Emacs : GNU Emacs 25.2.1 (x86_64-apple-darwin16.4.0, Carbon Version 157 > AppKit 1504.81) > of

Re: [O] [PATCH] lisp/org-el: Fix explanation, if state change is blocked by contained checkboxes

Hello, Marc Ihm writes: > The patch below fixes a minor problem: > > Consider a node, which contains unchecked checkboxes; if you have set > org-enforce-todo-checkbox-dependencies and try to change the node to > DONE, you will be denied with a message explaining why. However in

Re: [O] [PATCH] ox-confluence.el: Blank org table cells[...]

Hello, Stephen Mackenzie writes: > First post.. > Disclaimer, I have no idea what I'm doing. (Don't know lisp, don't know how > to use git format-patch correctly(?), etc. > Fixed this for myself and wanted to try my hand at submitting it. > If I did a terrible job, let me know

Re: [O] Bug: Using org-capture with a template adds an unnecessary newline regardless of flags set [9.0.5 (9.0.5-elpa @ /home/igor/.emacs.d/elpa/org-20170210/)]

Hello, Igor Perepelytsya writes: > Using a template with org-capture to create a new org entry will add an > unwanted newline after it. This occurs regardless of the contents of the > template file, whether or not the 'empty-lines 1' / 'empty-lines-after > 1' checkboxes are

Re: [O] Failure in compiling org-capture.el

To add, I am using emacs build from the master branch as of today. Doing M-x byte-compile-file on org-capture.el gives: - Compiling file /home/kmodi/.emacs.d/elisp/org-mode/lisp/org-capture.el at Mon Apr 17 10:48:22 2017 org-capture.el:1586:1:Error: Unknown pattern ‘nil’ - On Mon, Apr

Re: [O] Failure in compiling org-capture.el

This patch works: >From 5edec74298a0140c5ebf55e7be0d64de6c702b17 Mon Sep 17 00:00:00 2001 From: Kaushal Modi Date: Mon, 17 Apr 2017 11:01:28 -0400 Subject: [PATCH] Fix nil case in pcase * lisp/org-capture.el (org-capture-fill-template): Use `nil for the nil case in

Re: [O] Failure in compiling org-capture.el

While that error is fixed, we still have this byte compilation warning: org-capture.el:1586:1:Warning: Unused lexical variable ‘first-value’ I haven't used pcase extensively, but based on the warning, the below doesn't work as intended in the compiled elc: ((or "C" "L") (let ((insert-fun

[O] Failure in compiling org-capture.el

I am on master branch: ea3754f. A recent change in org-capture.el breaks compilation: In toplevel form: org-capture.el:1586:1:Error: Unknown pattern ‘nil’ Compiling /home/kmodi/.emacs.d/elisp/org-mode/lisp/org-install.el... Compiling /home/kmodi/.emacs.d/elisp/org-mode/lisp/org-loaddefs.el...

Re: [O] Bug: :session doesn't honor :verbatim [8.2.10 (release_8.2.10 @ /usr/local/share/emacs/26.0.50/lisp/org/)]

"Charles C. Berry" writes: >> However, I don't want to change this globally. Is there an org mean to >> change this locally just for the session? >> >> Maybe the shell prompt could be customizable for a session in ob-sh.el? > > That happens in the shell. You can do this to

[O] [PATCH] ob-C.el: Fix command to perform on remote host

Date: Mon, 17 Apr 2017 12:45:39 +0300 /host:/tmp/C-bin/tempfilename.exe". Processing name of binary file >From 1525efb65438f006be742b18d27804bf8409feae Mon Sep 17 00:00:00 2001 * lisp/ob-C.el (org-babel-C-execute): Made sure name of compiled program is converted to local representation before

Re: [O] Bug: Clipboard history is empty when using %^C in capture template [9.0.5 (9.0.5-elpaplus @ /home/mir/.emacs.d/elpa/org-plus-contrib-20170210/)]

Hello, Allen Li writes: > Using the %^C expansion in a capture template brings up a minibuffer > prompt to read/select a clipboard value, but there are no values to > select from. > > The relevant code is in the function org-capture-fill-template. > > ("C" > (cond >

Re: [O] Bug: Image export with link does not support query delimiter [8.2.10 (release_8.2.10 @ /usr/local/share/emacs/25.2/lisp/org/)]

Hello, Damien Cassou writes: > 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

Re: [O] ANN/RFC: ox-epub

Hi Eric, > "Eric" == Eric S Fraga writes: Eric> this sounds potentially very useful (to me, at least). Will Eric> it export equations and tables, even if as images? I guess I Eric> could simply try it... which I'll aim to do this week. Tables should be no

[O] [PATCH] Don't push url to kill-ring when invoking org-protocol-capture

From: Matt Lundin To: Org Mode Date: Mon, 17 Apr 2017 20:58:30 -0500 Subject: [PATCH] Don't push url to kill-ring when invoking org-protocol-capture --text follows this line-- * lisp/org-protocol.el: (org-protocol-do-capture) Don't push link to

Re: [O] ANN/RFC: ox-epub

> "Eric" == Eric S Fraga writes: Hi Eric, Eric> this sounds potentially very useful (to me, at least). Will Eric> it export equations and tables, even if as images? I guess I Eric> could simply try it... which I'll aim to do this week. epubtest.org is

Re: [O] Failure in compiling org-capture.el

Hello, Kaushal Modi writes: > While that error is fixed, we still have this byte compilation warning: > > org-capture.el:1586:1:Warning: Unused lexical variable ‘first-value’ > > I haven't used pcase extensively, but based on the warning, the below > doesn't work as

Re: [O] Failure in compiling org-capture.el

On Mon, Apr 17, 2017 at 2:05 PM Nicolas Goaziou wrote: > This was a typo of mine. Fixed. Thank you. > > Regards, > Thanks. I confirm the fix. -- Kaushal Modi

[O] Handling custom link types for html export in v 9.0 - Replacement for deprecated `org-add-link-type`?

Hi: I have a question about how to define custom link type, which before 9.0 used the (9.0) deprecated `org-add-link-type`. 1. Let me first provide the context: There is often a need to generate, for org links export/publish to Html, elements where img src URL starts with a slash, like this

Re: [O] Radio targets

Hi, OK, thank you. I am using emacs with spacemacs and it is still using the melpa version of orgmode as I am unable to get it to load the git branch of orgmode. I will try it out once I make the switch. On Sun, Apr 16, 2017 at 2:54 AM, Nicolas Goaziou wrote: > Hello, >

Re: [O] org-protocol-check-filename-for-protocol obscures other errors

Nicolas Goaziou writes: > I tried to improve the situation in maint branch. Please let me know if > it makes your life easier ! Looks great, thanks!

Re: [O] ANN: org-sticky-header

Adam Porter writes: > Hi friends, > > I've posted another package which you might find useful: > > https://github.com/alphapapa/org-sticky-header > > It's modeled on semantic-stickyfunc-mode. When you scroll down and push > an Org heading out of view, it displays that

[O] ANN: org-sticky-header

Hi friends, I've posted another package which you might find useful: https://github.com/alphapapa/org-sticky-header It's modeled on semantic-stickyfunc-mode. When you scroll down and push an Org heading out of view, it displays that heading in the Emacs header line at the top of the window so

Re: [O] org-mobile-push needs a visible frame ?

Bingo writes: > Hi, > > I see that when there is an emacs server without a visible frame, > > emacsclient --eval "(org-mobile-push)" , gives the error : > > *ERROR*: Unknown terminal type > > Only when there is a visible frame does org-mobile-push succeed. Is there a >

Re: [O] ANN/RFC: ox-epub

On Sunday, 16 Apr 2017 at 15:18, Mark Meyer wrote: > Hi, > this is to announce that ox-epub is now in a somewhat working state and > pretty much aligned with the rest of the ox framework. > > https://github.com/ofosos/ox-epub Hi Mark, this sounds potentially very useful (to me, at least). Will