Re: [O] Default silent results

Hello you can tweek the default behaviour using org-babel-default-header-args:org variable My default configuration for org is the following. I did not modify it. org-babel-default-header-args:org is a variable defined in ‘ob-org.el’. Its value is ((:results . "raw silent") (:exports .

Re: [O] [babel] Working dir incorrect

"Loris Bennett" writes: > Hi, > > In a file that used to work, when I now try to run some R code which > generates an image, I get the error: > > cannot open file './usage_users_historical_facet.pdf' > > If I check the working directory for the R session I see > >

Re: [O] Default silent results

Jérémie Juste writes: Greetings. > you can tweek the default behaviour using > org-babel-default-header-args:org variable > > My default configuration for org is the following. I did not modify > it. > > org-babel-default-header-args:org is a variable defined in

[O] [babel] Working dir incorrect

Hi, In a file that used to work, when I now try to run some R code which generates an image, I get the error: cannot open file './usage_users_historical_facet.pdf' If I check the working directory for the R session I see getwd() [1] "/usr/share/emacs/site-lisp/ess" instead of the

[O] Default silent results

Greetings. An old org-code of mine stopped working, and while trying to fix it I bumped into the following. What am I missing here? Jarmo * test A simple code block. #+name: org-block #+BEGIN_SRC org | foo | bar | |-+-| | 1 | 2 | #+END_SRC A silent call produces no

Re: [O] New markup for revising manuscripts

Hi Eric, I really appreciate this. I will try it out too. Cheers, M On Friday, 10 Mar 2017 at 20:33, Doyley, Marvin M. wrote: > Hi there, > > When revising manuscripts, I usually highlight the changes (response > to reviewer) in red. I use typically do this as follows: > (1) #+latex_header:

[O] [PATCH] Fix custom timestamps during export (ox-groff)

Hi, this patch updates ox-groff.el in contrig to use the org-timestamp-translate function instead of the non-existing org-translate-time. Best regards Robert From 632764856ecbc0f6a733d3d919f4904c6465605c Mon Sep 17 00:00:00 2001 From: Robert Klein Date: Mon, 13 Mar 2017

Re: [O] org-bbdb-anniversaries-future

Hello, Nicolas Goaziou wrote: > > Hello, > > Michael Welle writes: > > > thank you for the valuable comments. I think I've incorporated them all. > > Furthermore I reworded some of the comments and I introduced a defvar, > > so that the point in time, when to switch to the

Re: [O] org-bbdb-anniversaries-future

Hello, oops, I think the double space after full stop rule applies here, too. Sorry for the noise. Michael Welle writes: [...] >> Could you provide an ORG-NEWS entry for the feature? > > *** More specific anniversary descriptions Anniversary descriptions (used in the agenda

Re: [O] Babel R source blocks problem

Aloha Chuck, Charles C. Berry writes: > On Fri, 10 Feb 2017, Thomas S. Dye wrote: > >> Aloha Chuck, >> >> Charles C. Berry writes: >>> >>> A look at the `slidify-example.org' file in the `org-9-plus' branch of my >>> (chasberry) `orgmode-accessories' github repo might be a good start with >>>

Re: [O] New markup for revising manuscripts

Hi John and Eric, I decided to adopt your approaches, thanks for the suggestions. So I can use either the response: or ++ to highlight changes in our manuscripts. Cheers, M #+BEGIN_SRC emacs-lisp (org-link-set-parameters "response" :export (lambda (keyword desc format) (cond

Re: [O] Default silent results

Jarmo Hurri writes: > Jérémie Juste writes: > > Greetings. > >> you can tweek the default behaviour using >> org-babel-default-header-args:org variable >> >> My default configuration for org is the following. I did not modify >> it. >> >>

Re: [O] Modified remote file name syntax

Heads-up: if you are using remote directories, you'll want to read this. Michael Albinus writes: > Hi, > > today I've committed a patch, which changes the remote file name syntax > in Emacs. The "method" part, optional until now, becomes > mandatory. Valid remote file

[O] Reproducing a table

Greetings (again). What is the smartest way to reproduce a table without defining the table as an Org source block (constraint explained below). I can do the following, but it doesn't seem very sane (need to use elisp or some other language just to funnel the table). #

Re: [O] How do you store web pages for reference?

By the way, you can definitely save a PDF with links if you prefer that. I use DevonThink, and I use this snippet to save a PDF of a webpage, complete with links.

[O] ox-epub

Hi list, I'm the author of ox-epub, which is a very recent extension to org-mode to author EPUB files directly via the org export layer. Pank (Rasmus) asked on Github, whether this could be part of org-mode. I'm all for it. I gather this would be added to the lisp/contrib directory? Are there

Re: [O] Allow #+SETUPFILE to point to an URL for the org file

On Thu, Dec 8, 2016 at 5:40 PM Nicolas Goaziou wrote: > Kaushal Modi writes: > > You can use something like `url-insert' and `url-retrieve' or > `url-retrieve-synchronously'. > Thanks. I am using url-retrieve-synchronously. > > Sure, but

Re: [O] Complex conversion of text to org table

OK that's a nice trick. Very useful for CSV files. Thanks! 2017-03-12 16:52 GMT+00:00 Scott Randby : > On 03/12/2017 11:35 AM, Xebar Saram wrote: > > Thx Vicente! > > > > Thats a decent idea. can this be all wrapped in a function (i have zero > > coding skills :)) ? i have

[O] export menu

Hello, Scanning the manual I don't see a hint on how to narrow the export menu shown by C-c C-e (`org-export-dispatch'). I'm using ox-pandoc, which has a lengthy export menu, which cannot display fully and gets cut off the screen. Ideally, it should be possible to sequentially narrow the

Re: [O] [babel] Working dir incorrect

On Mon, Mar 13, 2017 at 9:32 AM, Loris Bennett wrote: > Hi, > > In a file that used to work, when I now try to run some R code which > generates an image, I get the error: > > cannot open file './usage_users_historical_facet.pdf' > > If I check the working directory

Re: [O] ox-epub

Sorry, the code lives here: https://github.com/ofosos/ox-epub Also available on MELPA. Cheers, Mark -- Mark Meyer m...@ofosos.org

[O] org-publish issue

Aloha, Running 9.0.5. I have a strange problem with org-publish. Only the first entry of my :components gets processed. I've tried tracing code and fail to find the problem. Can anyone give a suggestion? I'm appending my project alist. Mahalo! (setq org-publish-project-alist (quote (

Re: [O] org-publish issue

Okay, solved, but it does point to a problem. I had misspellings in the project names. So this happens: ("generalweb" :components ("generalimages" "generalother" "generalorg")) "generalimages" is processed. "generalother" isn't found because of a misspelling. But there is no error message and