Re: [O] MobileOrg

On 11/21/15 00:14, Peter Davis wrote: Hi pd, > I'm just starting out with MobileOrg, using Dropbox, but I'm confused by the > setup instructions. I've gotten the app linked to my > Dropbox account, but the next step in the setup instructions >

[O] [PATCH] lisp/ox-publish.el: Handle includes with searches

* lisp/ox-publish.el (org-publish-cache-file-needs-publishing): Ignore any link search suffix on an include so that the path represents a valid file during the publishing check. TINYCHANGE --- lisp/ox-publish.el | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/lisp/ox-p

[O] How to print only visible elements of org-agenda

Hello! I run org-agenda and then I do some filtering of the agenda by tags. Then I simply want to print the lines which I now see on the screen. My problem is - I am getting printed _all_ lines of org-agenda, including those I just filtered out and do not see on my screen! My desired outcome i

[O] bug#21938:

Also if I have no items with priority indication ([A], [B], [C]) - then "PostScript Print Buffer" works just fine and gives printout just fine on all emacs versions, with all Linux/Windows hosts. So may I suggest that it is the face of ([A], [B], [C]) priority marks what is confusing "PostScript

[O] bug#21938: 24.5; PostScript Print Buffer fails on Agenda buffer

> sgeorgii writes: > I launch emacs (-q switch makes no difference), open my .org file and > proceed as follows: > M-x org-agenda I've forwarded this to the Org-mode mailing list. John

[O] [sgeorgii .] bug#21938: 24.5; PostScript Print Buffer fails on Agenda buffer

Copying bug report. John --- Begin Message --- I launch emacs (-q switch makes no difference), open my .org file and proceed as follows: M-x org-agenda a (agenda for current week or day) menu "File" -> "PostScript Print Buffer" instead of printout of agenda on my printer I get the following

[O] All source block properties on one line -- or foldied?

Is there a way to put all of these prelim header lines on one line, such as turning this #+NAME: named-block #+HEADER: :var data=2 #+BEGIN_SRC emacs-lisp (message "data:%S" data) #+END_SRC to, perhaps, this #+NAME: named-block; #+HEADER: :var data=2; #+BEGIN_SRC emacs-lisp (message "data:%S" dat

[O] asynchronous python code blocks in org-mode

Hi everyone, I worked out some ideas on running Python blocks asynchronously in org-mode, while seeing the output of the code, /and/ still capturing the output in org-mode! The post is here: http://kitchingroup.cheme.cmu.edu/blog/2015/11/20/Asynchronously-running-python-blocks-in-org-mode/ It se

Re: [O] Exporting a subtree

Peter Davis writes: > For the first time, I'm trying to export just a single subtree of my overall > document, by typing > > C-c C-e C-s H O > > However, I get this error: > > apply: Wrong type argument: listp, #("Details, November 2015" 0 22 (:parent > (#0))) FWIW, I had this problem on my ho

Re: [O] Global visibility cycling broken: before first heading

"Loris Bennett" writes: > Hi, > > Yesterday I updated to version 8.3.2 (8.3.2-37-gd45217-elpaplus) and > today cycling global visibility seems to have stopped working. No > matter where the cursors is in an org file, I get the error: > > outline-back-to-heading: before first heading > > This hap

Re: [O] 24.5; PostScript Print Buffer fails on Agenda buffer

On Friday, 20 Nov 2015 at 13:05, sgeorgii . wrote: > Hello! > > I filed this in debugs > > http://debbugs.gnu.org/cgi/bugreport.cgi?bug=21938 > > but may be this list is better place to ask? > > Please anyone could help me with the above (bug?) of Org-mode? Maybe post the details here? (I read a

[O] MobileOrg

I'm just starting out with MobileOrg, using Dropbox, but I'm confused by the setup instructions. I've gotten the app linked to my Dropbox account, but the next step in the setup instructions involve setting up some emacs stuff on my

Re: [O] [odt-export] Setting Text Colour for odt export

Rasmus writes: > Hi, > > Rainer M Krug writes: > >> I am using >> >> \color{red} some red text \color{black} and we continue with black >> >> to set the text colour for sections in my document for LaTeX export, but >> this does obviously does not org for odt export. >> >> What can I use to achi

Re: [O] bug#21818: 24.5; org-set-tags-to indentation problems when called programmatically

Emanuel Evans writes: > Nicolas Goaziou writes: > >> I don't consider it to be a bug. >> >> `org-element-interpret-data' produces a string, which is expected to be >> syntactically correct, but doesn't guarantee aesthetics. In particular, >> `org-element-headline-interpreter' tries to align tags

[O] Global visibility cycling broken: before first heading

Hi, Yesterday I updated to version 8.3.2 (8.3.2-37-gd45217-elpaplus) and today cycling global visibility seems to have stopped working. No matter where the cursors is in an org file, I get the error: outline-back-to-heading: before first heading This happens both with S- and M-x org-global-cycl

Re: [O] [odt-export] Setting Text Colour for odt export

Hi, Rainer M Krug writes: > I am using > > \color{red} some red text \color{black} and we continue with black > > to set the text colour for sections in my document for LaTeX export, but > this does obviously does not org for odt export. > > What can I use to achieve the same for odt export? Y

Re: [O] [BUG] in export to odt -

Hi, Rainer M Krug writes: > Rasmus writes: > >> Rainer M Krug writes: >> >>> I tried in LibreOffice, and indeed it does not seem to be possible. I >>> don't know what the convention is, but I don't like that an invald .odt >>> file is produced. Maybe give a warning about "incompatible features

[O] [odt-export] Setting Text Colour for odt export

Hi I am using --8<---cut here---start->8--- \color{red} some red text \color{black} and we continue with black --8<---cut here---end--->8--- to set the text colour for sections in my document for LaTeX export, but this does

Re: [O] [BUG] in export to odt -

Rasmus writes: > Rainer M Krug writes: > >> I tried in LibreOffice, and indeed it does not seem to be possible. I >> don't know what the convention is, but I don't like that an invald .odt >> file is produced. Maybe give a warning about "incompatible features" or >> just drop the footnote in the

Re: [O] [BUG] in export to odt -

Rainer M Krug writes: > I tried in LibreOffice, and indeed it does not seem to be possible. I > don't know what the convention is, but I don't like that an invald .odt > file is produced. Maybe give a warning about "incompatible features" or > just drop the footnote in the footnote? Dropping it

Re: [O] interaction between org-latex-custom-lang-environments and name when exporting to latex

On 2015-11-20 11:41, Rasmus writes: > Alan Schmitt writes: > >> I was wondering if someone had been able to reproduce this, and if so >> should I file it as a bug? > > Sure. It's how org-latex-src-block handles custom environments (see "Case > 2."). At the moment this is hardcoded. > > Perhaps

Re: [O] [BUG] in export to odt -

Rasmus writes: > Rainer M Krug writes: > >> The odt is attached for reference. > > Please also provide an odt document with the expected, working result. > (I could not produce such a document in LO within 20s, but perhaps it’s > possible). I am not a LibreOffice / MS Word person (but my co-aut

Re: [O] interaction between org-latex-custom-lang-environments and name when exporting to latex

Alan Schmitt writes: > I was wondering if someone had been able to reproduce this, and if so > should I file it as a bug? Sure. It's how org-latex-src-block handles custom environments (see "Case 2."). At the moment this is hardcoded. Perhaps the second element of org-latex-custom-lang-enviro

Re: [O] [BUG] in export to odt -

Rainer M Krug writes: > The odt is attached for reference. Please also provide an odt document with the expected, working result. (I could not produce such a document in LO within 20s, but perhaps it’s possible). Thanks, Rasmus -- You people at the NSA are becoming my new best friends!

[O] 24.5; PostScript Print Buffer fails on Agenda buffer

Hello! I filed this in debugs http://debbugs.gnu.org/cgi/bugreport.cgi?bug=21938 but may be this list is better place to ask? Please anyone could help me with the above (bug?) of Org-mode?

[O] [BUG] in export to odt -

The following .org file produces an invalid .odt file upon export to odt because of the footnote in the footnote: --8<---cut here---start->8--- #+TITLE: Footnote in footnote produces invalid .odt #+AUTHOR: Rainer M. Krug * A Footnote in a Footnote Some footnot