Dear all
with the aim to show properties in custom match views, I have been
experimenting with new variables:
org-agenda-overriding-agenda-format
org-agenda-property-list
then, tweaking the function org-scan-tags this enables custom format for
the agenda lines, optionally showing properties (wi
rk for you?
Bastien writes:
> Hi Thomas,
>
> Thomas Alexander Gerds writes:
>
>> with the aim to show properties in custom match views, I have been
>> experimenting with new variables:
>>
>> org-agenda-overriding-agenda-format
>> org-agenda-property-
Hi Bastien
thanks for looking into this! I understand your general point of
view. however, the proposed changes would only slow down agenda creating
if org-agenda-property-list is set, right?
also, it certainly requires some insights to write
org-agenda-overriding-agenda-format which could displa
`org-agenda-property-list'.
Bastien writes:
> Hi Thomas,
>
> Thomas Alexander Gerds writes:
>
>> thanks for looking into this! I understand your general point of
>> view. however, the proposed changes would only slow down agenda creating
>> if org-agend
Hi Bastien
ok. will investigate. thanks for now.
Best Thomas
Bastien writes:
> Hi Thomas,
>
> Thomas Alexander Gerds writes:
>
>> I feel that your proposal to first create the agenda using the standard
>> `org-agenda-format-item' function and then to replace all
here is a (beginner) question regarding the following org-file with
buffer-local function and keybinding:
,
|
| * Lisp header (C-c C-c to activate)
| #+BEGIN_SRC emacs-lisp
| (defun blue-file ()
| (interactive)
| (org-table-insert-row 'below)
| (org-table-goto-column 1)
|
this works. thanks for the hint!
Eric Schulte writes:
> Thomas Alexander Gerds writes:
>
>> here is a (beginner) question regarding the following org-file with
>> buffer-local function and keybinding:
>>
>> ,
>> |
>> | * Lisp header (C-c C-
in worg it would be great if (as in emacs muse) there was a link to the
underlying .org file which was used to generate the page. my naiive
attempt to catch a glimpse of the source of
http://orgmode.org/worg/org-contrib/babel/languages/ob-doc-R.html
was to browse-url
http://orgmode.org/worg/org
still a beginner, and maybe therefore, in my setup (release is: 7.8.03,
emacs 23.2.1) the following occurs
-org.snip---
* here it works: org-ctrl-c-ctrl-c and export
#+begin_src R :results output :exports results
foo=matrix(1:2)
foo
#+end_src
#+RESULTS:
:
:
> On Thu, Feb 09 2012, Thomas Alexander Gerds wrote:
>
>> in worg it would be great if (as in emacs muse) there was a link to
> the
>> underlying .org file which was used to generate the page. my naiive
>> attempt to catch a glimpse of the source of
>>
>> ht
Hi Chris,
maybe I cannot follow exactly what you are trying to do, but when I
start emacs -q and evaluate (setq-default TeX-master nil) and then open
a new file test.tex, then I get the same prompt "Master file:".
so maybe, if you do not want to get prompted, you could try setting
(setq-default
Dear Babel developers
I may have found two bugs (org-mode: 7.8.03
release_7.8.03.330.gc804.dirty), emacs: 23.2.1):
1. when I have case-fold-search set to nil, I get problems with the
begin/end src notation:
, lower case works as expected
|
| #+begin_src emacs-lisp :results list
| (mapcar
but, you can always do this:
,
| ** sec 1
|
| bla
|
| #+LaTeX: \section*{sec2}
`
Tomy
Marvin Doyley writes:
> Thanks nick,
>
> Can I use this to suppress the numbering selectively
> For example, lets say I have
>
> * Intro
> * Results
> * Figures and Tables
>
> Can I use this to su
finally I found the problem: it was not at all related to org or babel,
but due to a function in my ess-send-input-hook.
sorry for bothering :)
Thomas Alexander Gerds writes:
> still a beginner, and maybe therefore, in my setup (release is:
> 7.8.03,
> emacs 23.2.1) the followi
Hi
I would be grateful if someone could help me sort out my confusion
regarding references to headings (sections) in latex export.
I am used to latex section labels and references via reftex, e.g.
,
| \section{This is a test}
| \label{sec:testit}
|
| In Section \ref{sec:testit}
`
To a
hi
I would like to overlay the hash info in results lines of this type
#+RESULTS[6e22789c4866716ffb3d0966cbb07c80cacf2d3c]:
[1] 1
by a description which shows the evaluation time, e.g. like this
#+RESULTS[[6e22789c4866716ffb3d0966cbb07c80cacf2d3c][ evaluated 2013-01-28 Mon
09:33]]:
as far as
help to learn how caching works.
Cheers
Thomas
Bastien writes:
> Hi Thomas,
>
> Thomas Alexander Gerds writes:
>
>> (when hash (concat "[["hash"][" (with-temp-buffer
>> (org-insert-time-stamp (current-time) 'hm)) "]]"))
>>
Hi Eric
yes, it is in line 178 the call to
(defcustom org-babel-load-languages '((emacs-lisp . t)) ...
which seems to need `org-ts-regexp'
but, otherwise it works! Thank you very much for this option.
Best
Thomas
Bastien writes:
> Hi Eric,
>
> Eric Schulte writes:
>
>> I've just pushed
Hi
using org-mode "7.9.3f" and the new exporter I was desperately trying to
get line numbers back for exported R code blocks using the latex listing
package. first I tried
(setq org-latex-listings-options
'(("basicstyle" "\\small")
("numbers" "left")))
which gives
,
| \lstset{bas
thanks for the fast fix. now, I agree that there is no great need to put
a link into the doc-string of org-latex-listings-options.
Nicolas Goaziou writes:
> Hello,
>
> Thomas Alexander Gerds writes:
>
>> using org-mode "7.9.3f" and the new exporter I was despe
Using the silent option together with a remote R session block (started
via ssh.el and ess-remote), like this:
#+BEGIN_SRC R :results silent :exports results :session *ssh gauss* :cache
yes
a=1
1
#+END_SRC
produces:
,
| > > > [1] 1
| > Warning message:
| In file.rename(tfile, transfer.f
/babel-8270IwX/R-8270vVe', reason 'No such file or directory'
| > a=1
| 1
| 'org_babel_R_eoe'
| a=1
| > 1
| [1] 1
| > 'org_babel_R_eoe'
| [1] "org_babel_R_eoe"
| >
`
cheers Thomas
Eric Schulte writes:
> Thomas Alexander Gerds
the following page from the official manual
http://orgmode.org/manual/Images-in-LaTeX-export.html
says
#+ATTR_LaTeX: width=5cm,angle=90
however, the new exporter does not recognize this syntax. instead the
following works:
#+ATTR_LaTeX: :width 5cm
I was learning about this by guessing arou
sorry for this post. I should have read the mailing list more
carefully. looks as if a) the issue is already under discussion and b)
that the manual is for latest release whereas I had problems with the
pre-release.
Thomas Alexander Gerds writes:
> the following page from the official man
thanks for the reply!
when edebugging the function org-export-read-attribute it is unclear to
me which function generates (the text properties of) element.
do you have a script which translates from old syntax to new?
thanks.
Nicolas Goaziou writes:
> Hello,
>
> Thomas Alexan
is end let me note that there are at least two ways to start a
remote R session in emacs:
1) M-x shell
2) M-x ssh via ssh.el (not part of emacs)
Cheers
Thomas
Bastien writes:
> Hi Thomas,
>
> Thomas Alexander Gerds writes:
>
>> Using the silent option together with a remote
after upgrading to the latest bleeding edge version I have problems
executing org-babel R blocks where the session is named *R*. the error
is this:
ELISP> (org-babel-read "*R*")
*** Eval error *** Symbol's value as variable is void: *R*
did I miss any conventions or is this a bug?
cheers
thoma
works again. thanks very much for fixing this so quickly!
Eric Schulte writes:
> Charles Berry writes:
>
>> Thomas Alexander Gerds biostat.ku.dk> writes:
>>
>>>
>>>
>>> after upgrading to the latest bleeding edge version I have problems
&g
th the efforts and it would be sufficient to avoid the
endless loop when waiting for a file which never will generated.
cheers thomas
Eric Schulte writes:
> Bastien writes:
>
>> Hi Thomas,
>> thanks for the follow-up.
>> Thomas Alexander Gerds writes:
>>
>>>
l from the Babel
> source if the R session is remote?
>
> Thanks,
>
> Thomas Alexander Gerds writes:
>
>> yes, I am using ESS. ess-remote allows me to evaluate R-code from
>> the local emacs-session on a remote machine connected to via ssh.
>> there are two prob
Hi Vikas
I am not sure I understand the problem correctly, but how about this?
Here is a table produced by a R-src block
with some descriptive text in a minipage:
---snip--
#+BEGIN_SRC R :results output latex :exports results :s
sometimes after searching for mail with notmuch, I want to save a link
to one of the articles shown in the nnir summary. since nnir groups are
temporary I would like org-gnus-store-link to treat nnir groups
differently and to use the articles orginal group when creating the
link. the following 3 l
t; Hello,
>
> Thomas Alexander Gerds writes:
>
>> sometimes after searching for mail with notmuch, I want to save a
>> link to one of the articles shown in the nnir summary. since nnir
>> groups are temporary I would like org-gnus-store-link to treat nnir
>> groups differen
yes, I now found the "how to contribute" page :) the updated patch is
attached. thanks!
Nicolas Goaziou writes:
> Hello,
>
> Thomas Alexander Gerds writes:
>
>> great. the updated patch is attached.
>
> It looks good. Thank you. One mino
Hi
org's development version (I am using the one updated yesterday: 2b22d50
Nicolas Go 2016-09-28) seems to ignore the :results setting of a src
block. more specifically, the export of this
#+BEGIN_SRC R :results output :exports code :session *R* :cache yes
2+2
#+END_SRC
#+RESULTS[<2016-09-29
Hi
org's development version (I am using the one updated yesterday: 2b22d50
Nicolas Go 2016-09-28) seems to ignore the :results setting of a src
block. more specifically, the export of this
#+BEGIN_SRC R :results output :exports code :session *R* :cache yes
2+2
#+END_SRC
#+RESULTS[<2016-09-29
export process
where the :results option is interpreted?
Thomas
"Charles C. Berry" writes:
> On Thu, 29 Sep 2016, Thomas Alexander Gerds wrote:
>
>> Hi
>> org's development version (I am using the one updated yesterday:
>> 2b22d50 Nicolas Go 2016-09-28) seems
code"
persists when I set (setq org-babel-hash-show-time nil)
so, unfortunately my question remains. which function in the export
process interprets the "results code" option?
Thomas
"Charles C. Berry" writes:
> On Thu, 29 Sep 2016, Charles C. Berry wrote:
>
>
ry" writes:
> On Thu, 29 Sep 2016, Thomas Alexander Gerds wrote:
>
>>
> [deleted]
>
> Follow the advice in the docstring for
> `org-export-babel-evaluate'. Use `:eval never-export'. Set
> org-export-babel-evaluate to t.
>
> Chuck
>
>
--
sent from nil
again for your help and patience!
Thomas
"Charles C. Berry" writes:
> On Fri, 30 Sep 2016, Thomas Alexander Gerds wrote:
>
>> right, this is what changed and setting :eval never-export on a each
>> block solves the problem. however, the new way breaks all my
>
40 matches
Mail list logo