[O] How to turn off flyspell for source code blocks?

[Leo Alekseyev]

How does one prevent flyspell from operating on code blocks in org?
I've tried adding ("+begin_src" . "+end_src") to
ispell-skip-region-alist, but it didn't seem to work.

Re: [O] [code] Small elisp snippet to search among toplevel headlines in a file

[Leo Alekseyev]

Another possible way to do it might be to create a wrapper around
org-goto with alternative interface where you set org-goto-max-level
to 1.  I've been using org-goto (alt. interface) with ido mode for a
while, and it's great (although I haven't tried restricting headlines
to just the top level).

On Sat, Feb 4, 2012 at 10:03 PM, Jude DaShiell  wrote:
> Another possible idea may be to write project titles in bold while on
> headlines.  That way all you need search for is the beginning of a line
> followed by a single * followed by a blank followed by the opening mark
> for bolding and if this is only done with project titles you got yourself
> an index.On Sat, 4 Feb 2012, Marc-Oliver Ihm wrote:
>
>> Hello,
>>
>> I have one big org-file for a lot of smaller projects,
>> each of them represented by a toplevel item.
>>
>> And I have difficulties finding them quickly:
>> In most cases I know a buzzword from the headline;
>> however, if I do a search-forward I normally find
>> some other text within the body of an unrelated project
>> further above in the file; and only after several
>> repetitions of search I find the toplevel heading
>> (i.e. the project) I was looking for.
>>
>> To make it easier to search only among toplevel headings
>> (i.e. among the the titles of my projects),
>> I wrote this small piece of elisp,
>> which lives in my initialization-file (e.g. .emacs):
>>
>> (define-key org-mode-map
>>   [(f11)]
>>   (lambda () (interactive)
>>     (progn
>>       (occur (concat "^\\* .*"
>>                      (read-from-minibuffer
>>                       "Occur for toplevel headlines containing: "))
>>              nil)
>>       (pop-to-buffer "*Occur*")
>>       (use-local-map (copy-keymap (current-local-map)))
>>       (local-set-key (kbd "RET")
>>                      (lambda () (interactive)
>>                        (progn
>>                          (occur-mode-goto-occurrence)
>>                          (delete-other-windows)))
>>
>>
>> To find a project I just press f11 (please choose your own key) and
>> enter a keyword to do an occur for this keyword. Normally several toplevel
>> headings are found and the right one is chosen by typing return.
>>
>> I hope, that someone might find this useful too.
>>
>> with kind regards, Marc-Oliver Ihm
>>
>>
>>
>>
>
> 
> Jude 
> 
>
>

Re: [O] Updating the Babel section of Worg Was: Generating plot with org-babel-R

[Thomas S. Dye]

Hi Eric,

Yes, this is overdue.  I think your plan is a good one.

Perhaps a few of the individual use cases could be moved to FIXME,
instead?  I'm thinking here of Feiming Chen's R setup and some of my
contributions when I was experimenting writing LaTeX inside source
code blocks.  The authors could resurrect these as they see fit.

Hopefully, others will contribute use examples.  My sense from reading
the list is there are many interesting ones.

I'd like it if Org mode users designed a template for the language
specific pages.  Currently, these seem to me a mixed bag and it would be
good to regularize them.  It would also be nice to have one for each of
the supported languages.  There are 11 language specific pages now,
which leaves quite a few languages under-documented.

I'll be happy to work on this as I can.

All the best,
Tom


Eric Schulte  writes:

> Thanks for raising this point.  The bulk of the content in the Babel
> portion of worg is fairly old, predating the syntax standardization
> efforts this fall.  I've just pushed some minor updates to the main
> babel pages, but updating the language-specific tutorials and the
> individual use cases will be a much larger effort.
>
> I'm not sure how to proceed.  One option would be to go through and add
> a [uses deprecated syntax] tag to the top of each such page, which could
> be removed after the page has been checked and possibly updated to
> ensure consistency with the latest syntax.
>
> Given that the Babel syntax will not be changing significantly moving
> forward now would be a good time to do such a review.  Ideally this
> could be completed before the release of Emacs 24 in a couple of months.
>
> Any other ideas for update/reorganization or volunteers?
>
> Cheers,
>
> t...@tsdye.com (Thomas S. Dye) writes:
>
>> Hi Riccardo,
>>
>> Thanks for the URL.  Org mode has evolved since this article was
>> written.  It should probably be revised or taken off Worg.  I've copied
>> Eric Schulte, who is better able than me to determine the correct course
>> of action here.
>>
>> In the meantime, an up-to-date description of how Org mode can be used
>> to write literate programs has appeared in the Journal of Statistical
>> Software.  You can find it here: http://www.jstatsoft.org/v46/i03
>>
>> Perhaps you could use the examples in the JSS article to get started?
>> If these don't work for you, or if they raise questions that are difficult
>> to answer, please do come back to the list with your queries.
>>
>> All the best,
>> Tom
>>
>> Riccardo Romoli  writes:
>>
>>> Hi, this is the URL:
>>>
>>> http://orgmode.org/worg/org-contrib/babel/how-to-use-Org-Babel-for-R.html
>>>
>>> Best
>>> R
>>>
>>> 2012/2/5 Thomas S. Dye 
>>>
 Hi Riccardo,

 This code appears to be outdated.  I don't recall this code on the org
 site.  Could you send a URL?

 All the best,
 Tom

 Riccardo Romoli  writes:

 > Hi, I'm trying to generate some figure with R, into an org session.
 Firstly
 > I use the code in the org site. The problem is that the code do not
 > generate any figure.
 >
 > This is the code:
 >
 > #+TITLE:Test
 > #+AUTHOR: Your Name
 > #+EMAIL: your-em...@server.com
 > #+BABEL: :session *R* :cache yes :results output graphics :exports
 > both :tangle yes
 >
 > * Example of Org-Babel for R Literate Programming
 > ** R text output
 > A simple summary.
 > #+begin_src R
 >   x <- rnorm(10)
 >   summary(x)
 > #+end_src
 >
 > ** R graphics output
 > Note we use the object =x= generated in previous code block, thanks to
 > the header option =:session *R*=.  The output graphics file is
 > =a.png=.
 >
 > #+begin_src R  :file a.png
 >   y <- rnorm(10)
 >   plot(x, y)
 > #+end_src
 >
 > Same plot with larger dimension:
 >
 > #+begin_src R  :file b.png :width 800 :height 800
 >   plot(x, y)
 > #+end_src
 >
 >
 > Where do I wrong?
 >
 > Best
 > Riccardo
 > Hi, I'm trying to generate some figure with R, into an org session.
 Firstly I use the code in the org site. The problem is that the code do not
 generate any figure. This is the code:
 > #+TITLE:Test
 > #+AUTHOR: Your Name
 > #+EMAIL: mailto:your-em...@server.com
 > #+BABEL: :session *R* :cache yes :results output graphics :exports both
 :tangle yes
 >
 > * Example of Org-Babel for R Literate Programming
 > ** R text output
 > A simple summary.
 > #+begin_src R
 >   x <- rnorm(10)
 >   summary(x)
 > #+end_src
 >
 > ** R graphics output
 > Note we use the object =x= generated in previous code block, thanks to
 > the header option =:session *R*=.  The output graphics file is
 > =a.png=.
 >
 > #+begin_src R  :file a.png
 >   y <- rnorm(10)
 >   plot(x, y)
 > #+end_src
 >
 > Same plot with larger dimension:
 >
>

[O] bugfix for org-agenda-follow-indirect

[Dave Abrahams]

Please try/apply enclosed patch:

--8<---cut here---start->8---
diff --git a/lisp/org-agenda.el b/lisp/org-agenda.el
index 780794e..3ae5e0c 100644
--- a/lisp/org-agenda.el
+++ b/lisp/org-agenda.el
@@ -7202,16 +7202,17 @@ use the dedicated frame)."
   (if (and current-prefix-arg (listp current-prefix-arg))
   (org-agenda-do-tree-to-indirect-buffer)
 (let ((agenda-window (selected-window))
-  (indirect-window (get-buffer-window org-last-indirect-buffer)))
+	  (indirect-window 
+	   (get-buffer-window org-last-indirect-buffer)))
   (save-window-excursion (org-agenda-do-tree-to-indirect-buffer))
   (unwind-protect
-  (progn
-(unless indirect-window
+	  (progn
+(unless (window-live-p indirect-window)
   (setq indirect-window (split-window agenda-window)))
 (select-window indirect-window)
 (switch-to-buffer org-last-indirect-buffer :norecord)
 (fit-window-to-buffer indirect-window))
-(select-window agenda-window)
+	(select-window (get-buffer-window org-agenda-buffer-name))
 
 (defun org-agenda-do-tree-to-indirect-buffer ()
   "Same as `org-agenda-tree-to-indirect-buffer' without saving window."
--8<---cut here---end--->8---

-- 
Dave Abrahams
BoostPro Computing
http://www.boostpro.com

[O] [FYI] Libreplanet Events + RMS@India

[Jambunathan K]

FOSS enthusiasts, please mark your diaries.

RMS is touring India right now.
http://libreplanet.org/wiki/Current_events

He is giving a talk at IIT, Madras.
http://fsftn.org/content/richard-stallmans-visit-chennai
-- 

Re: [O] A bit more feedback on org-publish-all

[Nick Dokos]

François Pinard  wrote:

> pin...@iro.umontreal.ca (François Pinard) writes:
> 
> > When I execute org-publish-all, I would like to have some indication
> > of the progress, so I can follow what is going on.  [...]  Such
> > "Publishing PROJECT..." message would also be useful to me in another
> > way.  [...] the script execution is a bit longish [...] while being
> > too silent.
> 
> Hmph!
> 
> `emacs --batch' buffers its output.  So, "Publishing PROJECT" messages
> would not be written timely, and the delaying would remove the
> entertaining virtues.
> 
> Yet, such "Publishing PROJECT" messages would be helpful in case of any
> error, as a kind of title prefixing it, and would ease debugging.
> 

[I haven't looked at earlier messages in this thread, so I hope I
am not misinterpreting.]

(message "foo") prints to stderr in batch mode, which is an unbuffered
stream. E.g ``emacs --batch -l foo.el'' with foo.el containing

--8<---cut here---start->8---
(message "foo")
(sit-for 10)
--8<---cut here---end--->8---

prints out ``foo'' and then sits for 10 seconds before exiting.

Also, don't you get messages for every file? The only publishing I've
done recently is worg publishing (I publish locally to test any changes
I make before pushing). That gives me a fairly detailed list of what it
is doing. AFAICT, that's the default behavior, but there may be settings
I've overlooked. I would recommend looking at the worg publishing
mechanism in general. See

  http://orgmode.org/worg/worg-setup.html


particularly the sections entitled 

  - What .emacs.el file is used on the server?
  - I want it for my own server!

Nick

Re: [O] [ANN] ASCII back-end for new export engine

[Thomas S. Dye]

Nicolas Goaziou  writes:

> Hello,
>
> I've commited an ASCII back-end for new export engine.
>
> Assuming contrib directory is in your load-path, you just need to
> (require 'org-export) to have both LaTeX and ASCII exporters ready to
> boot.
>
> You can then access to the dispatcher with M-x org-export-dispatch and
> test various configurations from there.
>
> As a reminder, you can ask for a table of contents, list of tables and
> list of listings with, respectively, "#+toc: headlines", "#+toc: tables"
> and "#+toc: listings". Also, drawers[1] are exported transparently by
> default.
>
> Feedback is welcome.
>
>
> Regards,
>
> [1] properties drawers excepted: those are different elements anyway.
Hi Nicolas,

This docstring at line 186 of org-e-latex.el is incomplete:

If your header or `org-export-latex-default-packages-alist'
inserts \"\\usepackage[AUTO]{inputenc}\", AUTO will automatically
be replaced with a coding system derived from
`buffer-file-coding-system'.

AUTO is automatically replaced when org-export-latex-packages-alist
inserts it, as well.

BTW, I have the experimental LaTeX exporter working on a real project
now.  It is performing very well for me.  Great work!

All the best,
Tom
-- 
Thomas S. Dye
http://www.tsdye.com

Re: [O] A bit more feedback on org-publish-all

[François Pinard]

pin...@iro.umontreal.ca (François Pinard) writes:

> When I execute org-publish-all, I would like to have some indication
> of the progress, so I can follow what is going on.  [...]  Such
> "Publishing PROJECT..." message would also be useful to me in another
> way.  [...] the script execution is a bit longish [...] while being
> too silent.

Hmph!

`emacs --batch' buffers its output.  So, "Publishing PROJECT" messages
would not be written timely, and the delaying would remove the
entertaining virtues.

Yet, such "Publishing PROJECT" messages would be helpful in case of any
error, as a kind of title prefixing it, and would ease debugging.

François

Re: [O] Hyphens for tags, todo keywords, and properties

[Nick Dokos]

Samuel Wales  wrote:

> On 2012-02-05, Bernt Hansen  wrote:
> > Nick Dokos  writes:
> >> I suspect that this is going to be difficult, if not impossible.
> >> In particular, tags and properties search uses - as a metacharacter,
> >> so having it appear as part of a tag or property would probably
> >> break things there.
> >
> > How is tag filtering where you remove a tag with '-TAG' going to
> > distinguish between a tag with a - and tag you want to remove?
> >
> >  (tags-todo "-WAITING-CANCELLED/!NEXT"
> >
> > is that one tag to remove - WAITING-CANCELLED or is it two (-WAITING and
> > -CANCELLED)?
> 
> With \\- in the middle, it should be one.
> 

[NB: gut feeling, unsupported by actual evidence.]

The trouble is that org in general does not have an escaping mechanism
(something that causes problems in various places).  I'm willing to bet
that there is no such escaping mechanism i tags/properties searching
e.g. To add an escaping mechanism would require, at the very least, some
(probably substantial) number of regexps to be rewritten in order to
deal with escapes, with all the collateral damage that that would
entail: at this point, that's probably a cure that's worse than the
disease.

It might be that ngz's parser might have an escape mechanism already
built-in (my guess is that it probably does not however) or it might be
possible to graft one in without doing too much violence to it. But I'd
guess that trying to do something like this on the existing code base
would be ... difficult.

Nick

[O] Updating the Babel section of Worg Was: Generating plot with org-babel-R

[Eric Schulte]

Thanks for raising this point.  The bulk of the content in the Babel
portion of worg is fairly old, predating the syntax standardization
efforts this fall.  I've just pushed some minor updates to the main
babel pages, but updating the language-specific tutorials and the
individual use cases will be a much larger effort.

I'm not sure how to proceed.  One option would be to go through and add
a [uses deprecated syntax] tag to the top of each such page, which could
be removed after the page has been checked and possibly updated to
ensure consistency with the latest syntax.

Given that the Babel syntax will not be changing significantly moving
forward now would be a good time to do such a review.  Ideally this
could be completed before the release of Emacs 24 in a couple of months.

Any other ideas for update/reorganization or volunteers?

Cheers,

t...@tsdye.com (Thomas S. Dye) writes:

> Hi Riccardo,
>
> Thanks for the URL.  Org mode has evolved since this article was
> written.  It should probably be revised or taken off Worg.  I've copied
> Eric Schulte, who is better able than me to determine the correct course
> of action here.
>
> In the meantime, an up-to-date description of how Org mode can be used
> to write literate programs has appeared in the Journal of Statistical
> Software.  You can find it here: http://www.jstatsoft.org/v46/i03
>
> Perhaps you could use the examples in the JSS article to get started?
> If these don't work for you, or if they raise questions that are difficult
> to answer, please do come back to the list with your queries.
>
> All the best,
> Tom
>
> Riccardo Romoli  writes:
>
>> Hi, this is the URL:
>>
>> http://orgmode.org/worg/org-contrib/babel/how-to-use-Org-Babel-for-R.html
>>
>> Best
>> R
>>
>> 2012/2/5 Thomas S. Dye 
>>
>>> Hi Riccardo,
>>>
>>> This code appears to be outdated.  I don't recall this code on the org
>>> site.  Could you send a URL?
>>>
>>> All the best,
>>> Tom
>>>
>>> Riccardo Romoli  writes:
>>>
>>> > Hi, I'm trying to generate some figure with R, into an org session.
>>> Firstly
>>> > I use the code in the org site. The problem is that the code do not
>>> > generate any figure.
>>> >
>>> > This is the code:
>>> >
>>> > #+TITLE:Test
>>> > #+AUTHOR: Your Name
>>> > #+EMAIL: your-em...@server.com
>>> > #+BABEL: :session *R* :cache yes :results output graphics :exports
>>> > both :tangle yes
>>> >
>>> > * Example of Org-Babel for R Literate Programming
>>> > ** R text output
>>> > A simple summary.
>>> > #+begin_src R
>>> >   x <- rnorm(10)
>>> >   summary(x)
>>> > #+end_src
>>> >
>>> > ** R graphics output
>>> > Note we use the object =x= generated in previous code block, thanks to
>>> > the header option =:session *R*=.  The output graphics file is
>>> > =a.png=.
>>> >
>>> > #+begin_src R  :file a.png
>>> >   y <- rnorm(10)
>>> >   plot(x, y)
>>> > #+end_src
>>> >
>>> > Same plot with larger dimension:
>>> >
>>> > #+begin_src R  :file b.png :width 800 :height 800
>>> >   plot(x, y)
>>> > #+end_src
>>> >
>>> >
>>> > Where do I wrong?
>>> >
>>> > Best
>>> > Riccardo
>>> > Hi, I'm trying to generate some figure with R, into an org session.
>>> Firstly I use the code in the org site. The problem is that the code do not
>>> generate any figure. This is the code:
>>> > #+TITLE:Test
>>> > #+AUTHOR: Your Name
>>> > #+EMAIL: mailto:your-em...@server.com
>>> > #+BABEL: :session *R* :cache yes :results output graphics :exports both
>>> :tangle yes
>>> >
>>> > * Example of Org-Babel for R Literate Programming
>>> > ** R text output
>>> > A simple summary.
>>> > #+begin_src R
>>> >   x <- rnorm(10)
>>> >   summary(x)
>>> > #+end_src
>>> >
>>> > ** R graphics output
>>> > Note we use the object =x= generated in previous code block, thanks to
>>> > the header option =:session *R*=.  The output graphics file is
>>> > =a.png=.
>>> >
>>> > #+begin_src R  :file a.png
>>> >   y <- rnorm(10)
>>> >   plot(x, y)
>>> > #+end_src
>>> >
>>> > Same plot with larger dimension:
>>> >
>>> > #+begin_src R  :file b.png :width 800 :height 800
>>> >   plot(x, y)
>>> > #+end_src
>>> > Where do I wrong?BestRiccardo
>>>
>>> --
>>> Thomas S. Dye
>>> http://www.tsdye.com
>>>
>> Hi, this is the 
>> URL:http://orgmode.org/worg/org-contrib/babel/how-to-use-Org-Babel-for-R.htmlBestR
>> 2012/2/5 Thomas S. Dye Hi 
>> Riccardo,
>>
>>
>> This code appears to be outdated.  I don't recall this code on the org
>> site.  Could you send a URL?
>>
>> All the best,
>> Tom
>>
>> Riccardo Romoli  writes:
>>
>>> Hi, I'm trying to generate some figure with R, into an org session. 
>>> Firstly
>>> I use the code in the org site. The problem is that the code do not
>>> generate any figure.
>>>
>>> This is the code:
>>>
>>> #+TITLE:Test
>>> #+AUTHOR: Your Name
>>> #+EMAIL: mailto:your-em...@server.com
>>> #+BABEL: :session *R* :cache yes :results output graphics :exports
>>> both :tangle yes
>>>
>>> * Example of Org-Babel for R Literate Programming
>>> ** R text 

Re: [O] Generating plot with org-babel-R

[Thomas S. Dye]

Hi Riccardo,

Thanks for the URL.  Org mode has evolved since this article was
written.  It should probably be revised or taken off Worg.  I've copied
Eric Schulte, who is better able than me to determine the correct course
of action here.

In the meantime, an up-to-date description of how Org mode can be used
to write literate programs has appeared in the Journal of Statistical
Software.  You can find it here: http://www.jstatsoft.org/v46/i03

Perhaps you could use the examples in the JSS article to get started?
If these don't work for you, or if they raise questions that are difficult
to answer, please do come back to the list with your queries.

All the best,
Tom

Riccardo Romoli  writes:

> Hi, this is the URL:
>
> http://orgmode.org/worg/org-contrib/babel/how-to-use-Org-Babel-for-R.html
>
> Best
> R
>
> 2012/2/5 Thomas S. Dye 
>
>> Hi Riccardo,
>>
>> This code appears to be outdated.  I don't recall this code on the org
>> site.  Could you send a URL?
>>
>> All the best,
>> Tom
>>
>> Riccardo Romoli  writes:
>>
>> > Hi, I'm trying to generate some figure with R, into an org session.
>> Firstly
>> > I use the code in the org site. The problem is that the code do not
>> > generate any figure.
>> >
>> > This is the code:
>> >
>> > #+TITLE:Test
>> > #+AUTHOR: Your Name
>> > #+EMAIL: your-em...@server.com
>> > #+BABEL: :session *R* :cache yes :results output graphics :exports
>> > both :tangle yes
>> >
>> > * Example of Org-Babel for R Literate Programming
>> > ** R text output
>> > A simple summary.
>> > #+begin_src R
>> >   x <- rnorm(10)
>> >   summary(x)
>> > #+end_src
>> >
>> > ** R graphics output
>> > Note we use the object =x= generated in previous code block, thanks to
>> > the header option =:session *R*=.  The output graphics file is
>> > =a.png=.
>> >
>> > #+begin_src R  :file a.png
>> >   y <- rnorm(10)
>> >   plot(x, y)
>> > #+end_src
>> >
>> > Same plot with larger dimension:
>> >
>> > #+begin_src R  :file b.png :width 800 :height 800
>> >   plot(x, y)
>> > #+end_src
>> >
>> >
>> > Where do I wrong?
>> >
>> > Best
>> > Riccardo
>> > Hi, I'm trying to generate some figure with R, into an org session.
>> Firstly I use the code in the org site. The problem is that the code do not
>> generate any figure. This is the code:
>> > #+TITLE:Test
>> > #+AUTHOR: Your Name
>> > #+EMAIL: mailto:your-em...@server.com
>> > #+BABEL: :session *R* :cache yes :results output graphics :exports both
>> :tangle yes
>> >
>> > * Example of Org-Babel for R Literate Programming
>> > ** R text output
>> > A simple summary.
>> > #+begin_src R
>> >   x <- rnorm(10)
>> >   summary(x)
>> > #+end_src
>> >
>> > ** R graphics output
>> > Note we use the object =x= generated in previous code block, thanks to
>> > the header option =:session *R*=.  The output graphics file is
>> > =a.png=.
>> >
>> > #+begin_src R  :file a.png
>> >   y <- rnorm(10)
>> >   plot(x, y)
>> > #+end_src
>> >
>> > Same plot with larger dimension:
>> >
>> > #+begin_src R  :file b.png :width 800 :height 800
>> >   plot(x, y)
>> > #+end_src
>> > Where do I wrong?BestRiccardo
>>
>> --
>> Thomas S. Dye
>> http://www.tsdye.com
>>
> Hi, this is the 
> URL:http://orgmode.org/worg/org-contrib/babel/how-to-use-Org-Babel-for-R.htmlBestR
> 2012/2/5 Thomas S. Dye Hi 
> Riccardo,
>
>
> This code appears to be outdated.  I don't recall this code on the org
> site.  Could you send a URL?
>
> All the best,
> Tom
>
> Riccardo Romoli  writes:
>
>> Hi, I'm trying to generate some figure with R, into an org session. 
>> Firstly
>> I use the code in the org site. The problem is that the code do not
>> generate any figure.
>>
>> This is the code:
>>
>> #+TITLE:Test
>> #+AUTHOR: Your Name
>> #+EMAIL: mailto:your-em...@server.com
>> #+BABEL: :session *R* :cache yes :results output graphics :exports
>> both :tangle yes
>>
>> * Example of Org-Babel for R Literate Programming
>> ** R text output
>> A simple summary.
>> #+begin_src R
>>   x <- rnorm(10)
>>   summary(x)
>> #+end_src
>>
>> ** R graphics output
>> Note we use the object =x= generated in previous code block, thanks to
>> the header option =:session *R*=.  The output graphics file is
>> =a.png=.
>>
>> #+begin_src R  :file a.png
>>   y <- rnorm(10)
>>   plot(x, y)
>> #+end_src
>>
>> Same plot with larger dimension:
>>
>> #+begin_src R  :file b.png :width 800 :height 800
>>   plot(x, y)
>> #+end_src
>>
>>
>> Where do I wrong?
>>
>> Best
>> Riccardo
>> Hi, I'm trying to generate some figure with R, into an org session. 
>> Firstly I use the code in the org site. The problem is that the code do not 
>> generate any figure. This is the code:
>> #+TITLE:Test
>> #+AUTHOR: Your Name
>> #+EMAIL: mailto:mailto:your-em...@server.com
>> #+BABEL: :session *R* :cache yes :results output graphics :exports both 
>> :tangle yes
>>
>> * Example of Org-Babel for R Literate Programming
>> ** R text output
>> A simple summary.
>> #+begin_src R
>>   x <- rnorm(10)
>>   summary(x)
>> #+end_

Re: [O] [babel] Is there an elisp-way to see the header-arguments, that are passed to a #+call-line ?

[Marc-Oliver Ihm]

Phewww !

Hi Eric, Thanx a lot !

Not quite through with understanding your post, but I already see, that there 
is everything I need in there.

Thanx a lot and Thanx again !

with kind regards, Marc

Re: [O] Hyphens for tags, todo keywords, and properties

[Samuel Wales]

On 2012-02-05, Bernt Hansen  wrote:
> Nick Dokos  writes:
>> I suspect that this is going to be difficult, if not impossible.
>> In particular, tags and properties search uses - as a metacharacter,
>> so having it appear as part of a tag or property would probably
>> break things there.
>
> How is tag filtering where you remove a tag with '-TAG' going to
> distinguish between a tag with a - and tag you want to remove?
>
>  (tags-todo "-WAITING-CANCELLED/!NEXT"
>
> is that one tag to remove - WAITING-CANCELLED or is it two (-WAITING and
> -CANCELLED)?

With \\- in the middle, it should be one.

Re: [O] [babel] Is there an elisp-way to see the header-arguments, that are passed to a #+call-line ?

[Eric Schulte]

Marc-Oliver Ihm  writes:

> Hi again,
>
> is there an elisp-way to see the header-arguments, that are passed to a 
> #+call-line ?
>
> (This relates to my previous question "[babel] #+call-line removes hlines and 
> headings ?", but has
>   shifted in subject, so I would like to start a new thread, which can be 
> understood on its own ...)
>
> I have tried the internal variable "params", but that only gives me the 
> header-arguments
> of the #+begin_src-block and NOT of the #+call-line.
>
> This is illustrated in the example below:
>

This was trickier than I expected to cobble together.  See the example
in the attached Org-mode file in which a call line prints out its
parameters.  Explanation of the mechanisms used are included.

Cheers,

#+Title: How to view the information present at a call line

This call line passes its in-buffer location to a code block.  Notice
that the call to =(point)= in the call line is saved into a header
argument named =:my-point= and is then retrieved by the variable
initialization.  This indirection is required because of /when/ and
/where/ the elisp forms in header arguments are evaluated, a simpler
call line like =#+call: show:((point))= would not work because the
form =(point)= would not be evaluated in the correct place.

#+call: show[:my-point (point)]((cdr (assoc :my-point (nth 2 info :special-header "foo"

The special header argument =:special-header= may be seen in the
output below.  The =results= variable is due to the way that call
lines are evaluated.  During evaluation a call line is converted into
a trivial elisp code block of the form
: #+begin_src emacs-lisp :var results=called-function()
:   results
: #+end_src
which is evaluated in place.

#+RESULTS: show[:my-point (point)]((cdr (assoc :my-point (nth 2 info
| (:var results ((:var nil)) ((:colname-names)) ((:rowname-names)) ((:result-params replace)) ((:result-type . value)) ((:comments . )) ((:shebang . )) ((:cache . no)) ((:padline . )) ((:noweb . yes)) ((:tangle . no)) ((:exports . code)) ((:results . replace)) ((:padnewline . yes)) ((:hlines . no)) ((:session . none))) |
| (:colname-names)   |
| (:rowname-names)   |
| (:result-params replace)   |
| (:result-type . value) |
| (:comments . ) |
| (:shebang . )  |
| (:cache . no)  |
| (:padline . )  |
| (:noweb . yes)

[O] org-mobile : checksum errors

[Richard Riley]

I reduced my mobile org file set to a single file "general.org" by
adjusting org-mobile-files.

I did an org-mobile-push but the mobile app falls over when I try to
sync it saying "error downloading checksums". I read on the org-mobile
web page that one should manally run md5 (which was a surprise) and did
this and still I get the same error ("md5 *.org > checksums.dat") : the
full text is "an error was encountered while downloading checksums.dat
from the server. The file isnt required but the error was unusual, The
error was 'unexpected eror'". So not much to go on there.

I even tried deleting the mobile app with ll its data and reinitialising
drop box but still no joy.

I would be intersted to hear from anyone using this suite that might
have come across similar issues.

Re: [O] repeted scheduled item in agenda next week

[Glasspen]

Thanks. I had that one set. I missed that the scheduled repeted items
that do not show up have property style, habit (module). I have
scheduled repeted items that shows but the do not have this specific
property.

When I deleted property style, habit the missing scheduled repeted item
appeared.

[O] org mobile problems

[Richard Riley]

I have a certain journal (journal.org) which causes org-mobile-push to
crash and leave a massive backtrace. I havent attached it here as it
takes my netbook abot ten minutes to copy it and another ten to paste it
in emacs for some reason, so delaying providing that I though I would
exclude it :

if org-mobile-files-exclude-regexp is set to "journal" and org-mobile-files is
set to "(org-agenda-files)" then the excludes are not applied : indeed
the doc says the full contents of org-agenda-files is used unrestricted.

I would like a way to rely on org-agenda-files since the files alter
daily - some added some removed and I dont want an explcit filename
list. Indeed, org-agenda-files is set to  ("~/.orgfiles"
"~/.orgfiles/projects") so the agenda is all the files in these
directories.

So, how to exclude certain files from the mobile ones based on regexp
when the org-files variable is set to point to directories?

regards

r.

Re: [O] repeted scheduled item in agenda next week

[Bernt Hansen]

Glasspen  writes:

> This is about repeted scheduled item that not shows in agenda next week
> or month. I want to be able to see every todo item for next week. How
> can I accomplish that? Now I can see scheduled items but not repeted
> scheduled items. Why?

Maybe try the following setting?

(setq org-agenda-repeating-timestamp-show-all t)

Regards,
Bernt

Re: [O] Custom agenda views: display date, not tags

[Bernt Hansen]

knubee  writes:

> I am trying to create a custom agenda view that displays the deadline date 
> (rather than the tags) associated with certain entries.
>
> So, rather than:
>
>  todo:  TODO Finish the task   :Work:
>
> I want to display:
>
>  todo:  TODO Finish the task   5 February 2012
>
> I haven't been able to find the appropriate variables to control this. 
> Suggestions?

I don't think you can do this ... but you can use column view to overlay
the deadline on the agenda.

--8<---cut here---start->8---
#+COLUMNS: %50ITEM %DEADLINE
* Deadline agenda view:sometag:
DEADLINE: <2012-02-04 Sat>
[2012-02-05 Sun 09:39]
--8<---cut here---end--->8---

With this org file open

C-c C-c on the #+COLUMNS: line once to set the value

C-c a 1 a   - goes to the agenda with only this file
C-c C-x C-c - start column view displaying deadlines

You can set this as your default agenda view with

--8<---cut here---start->8---
(setq org-columns-default-format "%50ITEM %DEADLINE"
--8<---cut here---end--->8---

then you can use it in any agenda view to overlay the deadline details.

HTH,
Bernt

[O] A bit more feedback on org-publish-all

[François Pinard]

Hi, Orger friends.

When I execute org-publish-all, I would like to have some indication of
the progress, so I can follow what is going on.

The *Messages* buffer indeed gets crowded with many noisy lines, and I
can find hints about the project being processed though "Skipping
unmodified file SUCH-AND-SUCH" or "Loading .../PROJECT.cache" messages.
These lines may undoubtedly be useful when something goes wrong, but
otherwise, they just prevent the mini-buffer, say, to display some
clear "Publishing PROJECT..." message at the start of each project.

Such "Publishing PROJECT..." message would also be useful to me in
another way.  I'm using a script which launches "emacs -batch ... -f
org-publish-all" under the scene and filters its output to get rid of
all the noisy lines.  My hope is that errors, if any, will stand out.  I
could let such "Publishing" messages go through the filter, however.
Currently, I find that the script execution is a bit longish (I have a
few dozen projects), while being too silent.

I could probably manage with hooks of various kind and more
configuration to the org-publish-project-alist structure, but it would
look as overkill to me for getting such a benign feedback.

François

Re: [O] Hyphens for tags, todo keywords, and properties

[Bernt Hansen]

Nick Dokos  writes:

> Samuel Wales  wrote:
>
>> For some reason I can't get used to underscores[1] and I
>> want to use hyphens (i.e. "-") for tags, todo keywords, and
>> properties.
>> 
>
> I suspect that this is going to be difficult, if not impossible.
> In particular, tags and properties search uses - as a metacharacter,
> so having it appear as part of a tag or property would probably
> break things there.

How is tag filtering where you remove a tag with '-TAG' going to
distinguish between a tag with a - and tag you want to remove?

 (tags-todo "-WAITING-CANCELLED/!NEXT"

is that one tag to remove - WAITING-CANCELLED or is it two (-WAITING and 
-CANCELLED)?

-Bernt

Re: [O] A visibility (ellipsis) problem with `C-c .'

[Bernt Hansen]

pin...@iro.umontreal.ca (François Pinard) writes:

> So I have to fight a tiny bit for being able to edit the contents.  I go
> one level up, collapse then expand, and everything becomes OK.

I just use C-u C-u C-u TAB to expand everything wihtout moving point in
that case and fold it again later.

-Bernt

Re: [O] [ANN] ASCII back-end for new export engine

[Nicolas Goaziou]

Hello,

t...@tsdye.com (Thomas S. Dye) writes:

> References to org-e-latex-packages-alist in org-e-latex.el docstrings
> should be to org-export-latex-packages-alist.

This should be fixed (along with your other report). Thanks for both
reports.


Regards,

-- 
Nicolas Goaziou

Re: [O] Turning a link into a non-link

[François Pinard]

pin...@iro.umontreal.ca (François Pinard) writes:

>>> I sometimes want to turn [[POINTER][COMMENT]] into COMMENT.

>> [...] you should write a separate function that unlinks the link.

> OK, should easily be done on my side.

Just in case useful to others, I did it this way:


(defun fp-org-kill-link ()
  (interactive)
  (when (org-in-regexp org-bracket-link-regexp 1)
(replace-match (match-string 3


François

Re: [O] Recurring multiple days events

[Simon Thum]

On 02/04/2012 11:45 PM, Brian van den Broek wrote:

On 4 Feb 2012 22:55, "Simon Thum"  wrote:


Hi all,

it seems to me that specifying recurring multi-days things like

<2012-12-24 +1y>--<2012-12-15>  do not show up in the agenda. I know there

sexp dates, but these have other drawbacks.




I've not tried such things, but if that is your actual example, your start
date is for a date after your end date. That can't be helping :-)
Well, I meant <2012-12-24 +1y>--<2012-12-25> but I didn't get it to work 
nonetheless ;(


Cheers,

Simon

Re: [O] Turning a link into a non-link

[François Pinard]

Nick Dokos  writes:

> François Pinard  wrote:

>> I sometimes want to turn [[POINTER][COMMENT]] into COMMENT.

> This is done by org-make-link-string: it considers an empty link to be
> an error.  If you toggle-debug-on-error, you will get a backtrace.

>> Could it [`C-c C-l' given an empty link] keep COMMENT in the text,
>> instead of deleting it?

> [...] you should write a separate function that unlinks the link.

OK, should easily be done on my side.  I perceived `C-c C-l' as a little
tool for editing links in various ways.  As it can already create a link
out of no link, it already "communicates with the void" enough, so I
thought it could delete a link as well as part of its general function.

May I guess that, given a dangling link, Org mode does not offer a way
for cleaning the link part without losing its text?  Shouldn't it?

François

Re: [O] A visibility (ellipsis) problem with `C-c .'

[François Pinard]

Nick Dokos  writes:

> François Pinard  wrote:

>> Consider a header having many sub-headers, and which is closed.  So I
>> only see that header, followed by an ellipsis at the end of that line.
>> On that header, command `C-c .' turns the initial star (or string
>> thereof) into a dash.

> I don't understand: C-c . does org-time-stamp

Oops, Nick, sorry!  I meant `C-c -' (a dash, not a period).

>> Now, I see an item with the same text as the previous header, still
>> followed by an ellipsis at the end of that line.  Now, TAB has no
>> effect: it does not expand the ellipsis into the previous contents
>> (the minibuffer writes "EMPTY ENTRY", which is likely improper)
>> 
>> So I have to fight a tiny bit for being able to edit the contents.  I go
>> one level up, collapse then expand, and everything becomes OK.

François

[O] repeted scheduled item in agenda next week

[Glasspen]

Hi!

This is about repeted scheduled item that not shows in agenda next week
or month. I want to be able to see every todo item for next week. How
can I accomplish that? Now I can see scheduled items but not repeted
scheduled items. Why?


Regards

Re: [O] Generating plot with org-babel-R

[Riccardo Romoli]

Hi, this is the URL:

http://orgmode.org/worg/org-contrib/babel/how-to-use-Org-Babel-for-R.html

Best
R

2012/2/5 Thomas S. Dye 

> Hi Riccardo,
>
> This code appears to be outdated.  I don't recall this code on the org
> site.  Could you send a URL?
>
> All the best,
> Tom
>
> Riccardo Romoli  writes:
>
> > Hi, I'm trying to generate some figure with R, into an org session.
> Firstly
> > I use the code in the org site. The problem is that the code do not
> > generate any figure.
> >
> > This is the code:
> >
> > #+TITLE:Test
> > #+AUTHOR: Your Name
> > #+EMAIL: your-em...@server.com
> > #+BABEL: :session *R* :cache yes :results output graphics :exports
> > both :tangle yes
> >
> > * Example of Org-Babel for R Literate Programming
> > ** R text output
> > A simple summary.
> > #+begin_src R
> >   x <- rnorm(10)
> >   summary(x)
> > #+end_src
> >
> > ** R graphics output
> > Note we use the object =x= generated in previous code block, thanks to
> > the header option =:session *R*=.  The output graphics file is
> > =a.png=.
> >
> > #+begin_src R  :file a.png
> >   y <- rnorm(10)
> >   plot(x, y)
> > #+end_src
> >
> > Same plot with larger dimension:
> >
> > #+begin_src R  :file b.png :width 800 :height 800
> >   plot(x, y)
> > #+end_src
> >
> >
> > Where do I wrong?
> >
> > Best
> > Riccardo
> > Hi, I'm trying to generate some figure with R, into an org session.
> Firstly I use the code in the org site. The problem is that the code do not
> generate any figure. This is the code:
> > #+TITLE:Test
> > #+AUTHOR: Your Name
> > #+EMAIL: mailto:your-em...@server.com
> > #+BABEL: :session *R* :cache yes :results output graphics :exports both
> :tangle yes
> >
> > * Example of Org-Babel for R Literate Programming
> > ** R text output
> > A simple summary.
> > #+begin_src R
> >   x <- rnorm(10)
> >   summary(x)
> > #+end_src
> >
> > ** R graphics output
> > Note we use the object =x= generated in previous code block, thanks to
> > the header option =:session *R*=.  The output graphics file is
> > =a.png=.
> >
> > #+begin_src R  :file a.png
> >   y <- rnorm(10)
> >   plot(x, y)
> > #+end_src
> >
> > Same plot with larger dimension:
> >
> > #+begin_src R  :file b.png :width 800 :height 800
> >   plot(x, y)
> > #+end_src
> > Where do I wrong?BestRiccardo
>
> --
> Thomas S. Dye
> http://www.tsdye.com
>

[O] [babel] Is there an elisp-way to see the header-arguments, that are passed to a #+call-line ?

[Marc-Oliver Ihm]

Hi again,

is there an elisp-way to see the header-arguments, that are passed to a 
#+call-line ?

(This relates to my previous question "[babel] #+call-line removes hlines and 
headings ?", but has
 shifted in subject, so I would like to start a new thread, which can be 
understood on its own ...)

I have tried the internal variable "params", but that only gives me the 
header-arguments
of the #+begin_src-block and NOT of the #+call-line.

This is illustrated in the example below:

#+call: parameters() :colnames yes

#+results: parameters()
| :colname-names | nil  |
|+--|
| :rowname-names | nil  |
| :result-params | (silent replace) |
| :result-type   | value|
| :comments  |  |
| :shebang   |  |
| :cache | no   |
| :padline   |  |
| :noweb | no   |
| :tangle| no   |
| :exports   | code |
| :results   | silent   |
| :session   | none |
| :padnewline| yes  |
| :hlines| yes  |
| :colnames  | no   |
| :result-type   | value|
| :result-params | (replace)|
| :rowname-names | nil  |
| :colname-names | nil  |

#+name: parameters
#+begin_src emacs-lisp
(mapcar (lambda (x) (list (car x) (cdr x))) params)
#+end_src

#+results: parameters
| :colname-names | nil   |
| :rowname-names | nil   |
| :result-params | (replace) |
| :result-type   | value |
| :comments  |   |
| :shebang   |   |
| :cache | no|
| :padline   |   |
| :noweb | no|
| :tangle| no|
| :exports   | code  |
| :results   | replace   |
| :colnames  | no|
| :hlines| yes   |
| :padnewline| yes   |
| :session   | none  |


The #+call line calls a #+begin_src-block named "parameters", which simple 
dumps the
content of the params-variable, which contains all the header arguments.

If I pass ":colnames yes" as a header argument, I nevertheless get dumped "no" 
in the example !
This is probably because the #+begin_src-block only has only access to its
own header-arguments (via the variable "params").

Therefore my question:

Is there any way to access the header-arguments of the #+call-line within the 
#+begin_src-block ?
Maybe with the "params" variable or maybe any other way ?

The reason I need to know this: The value of the header-argument ":colnames" of 
the #+call-line
governs, whether the #+begin_src-block is expected to return a table with or 
without column-names;
so to react accordingly (and not surprise users) I need to know within the 
#+begin_src-block
the value of the ":colnames" header-argument from the #+call-line.

Thanx a lot !

with kind regards, Marc-Oliver Ihm

P.s.: Possible solutions I can think of:
- Access the variable "params" not from the local scope but from the outer 
scope, however
  I do not know, if elisp allows this.
- Pass the header-arguments of the #+call-line to the #+begin_src-block, but 
this would probably
  require a patch to babel.
- Something even more elegant I just cannot figure out :-)

Am 30.01.2012 17:10, schrieb Eric Schulte:

>
> To explain the cause (if not rationale) for the current behavior; when
> executing a call line, an ephemeral code block is created at the point
> of the call line.  The result of the called function is passed into this
> ephemeral block, and the output of the block is inserted into the
> buffer.
>
> This is why call lines have *two* possible sets of header arguments, one
> to pass to the original called code block, and one for local effect in
> the ephemeral block.
>
> The reason the colnames header argument is required for the call line
> and not the code block, is because hlines are only stripped when data
> passes *into* a code block as a variable.  In this case the 'hlines are
> stripped when the table passes into the ephemeral code blocks.
>
> Hope the above is more illuminating that confusing,
>

[O] using org-edit-special to edit javascript embeded in HTML

[Le Wang]

Hi,

I would like to use "C-c '" to edit the current