Re: [O] How to export an Org file to LaTeX's book class, but without parts?

[Eric S Fraga]

On Wednesday, 22 Apr 2015 at 00:33, Marcin Borkowski wrote:

[...]

> I want to export my Org file to the book class (actually, a class
> similar to it, but never mind), but I want my first-level headings to
> be chapters, not parts.  OTOH, I don't want to modify
> org-latex-classes.  Is that possible, and if yes, how to achieve that?

The easiest way is, unfortunately, to modify org-latex-classes but the
modification is simply adding an element to the list:

#+begin_src emacs-lisp
  (add-to-list 'org-latex-classes
   '("bookwithnoparts" "\\documentclass{book}"
 ("\\chapter{%s}" . "\\chapter*{%s}")
 ("\\section{%s}" . "\\section*{%s}")
 ("\\subsection{%s}" . "\\subsection*{%s}")
 ("\\subsubsection{%s}" . "\\subsubsection*{%s}")))
#+end_src

or similar...
-- 
: Eric S Fraga (0xFFFCF67D), Emacs 25.0.50.1, Org release_8.3beta-1030-g65bbb1

Re: [O] ox-latex and small caps links

[Thomas S. Dye]

Aloha David,

David Dynerman  writes:

>> ,-
>> | Code within @@latex:some code@@ a paragraph.
>> `-
>
> This works great! Thanks Tom!

Good news.

> It might be nice to document this somehwere, to make the transition a
> little easier when 8.3 rolls out and the old [[latex:textsc][Hello]]
> links cause export errors.

I just tested the latex link type and it seems to work fine here with a
recent Org mode from master.

I executed the source code block and then exported the following buffer
to LaTeX.

,--
| #+LATEX_CLASS: article   
| #+DATE: \today   
|  
| * Test link type 
| This is [[latex:textsc][small caps]].
|  
| * Link type:noexport:
| #+begin_src emacs-lisp   
| (org-add-link-type   
|  "latex" nil 
|  (lambda (path desc format)  
|(cond 
| ((eq format 'html)   
|  (format "%s" path desc))  
| ((eq format 'latex)  
|  (format "\\%s{%s}" path desc)   
| #+end_src
`--

The LaTeX output looks fine:

,-
| \begin{document}
| 
| \tableofcontents
| 
| \section{Test link type}
| \label{sec-1}   
| This is \textsc{small caps}.
| \end{document}  
`-

Did your recent Org mode upgrade lose the latex link type somehow?

All the best,
Tom

-- 
Thomas S. Dye
http://www.tsdye.com

Re: [O] ox-latex and small caps links

[David Dynerman]

> ,-
> | Code within @@latex:some code@@ a paragraph.
> `-

This works great! Thanks Tom!

It might be nice to document this somehwere, to make the transition a
little easier when 8.3 rolls out and the old [[latex:textsc][Hello]]
links cause export errors.

I'd be happy to write something. Where would a good place be? The NEWS
file? The wiki?

David


signature.asc
Description: PGP signature

Re: [O] How to export an Org file to LaTeX's book class, but without parts?

[Nick Dokos]

Marcin Borkowski  writes:

> Hi all,
>
> this is an actual question, but it can be viewed as a continuation of
> the "why use LaTeX directly and not Org" thread (disclaimer: from the
> POV of an experienced LaTeX user and much less experienced Org-exporter
> user).
>
> So, I tried to do the opposite, just to learn something/unlock the "Org
> Exporter" skill;-).  I want to export my Org file to the book class
> (actually, a class similar to it, but never mind), but I want my
> first-level headings to be chapters, not parts.  OTOH, I don't want to
> modify org-latex-classes. Is that possible, and if yes, how to achieve
> that?

AFAIK, no, not without modifying org-latex-classes - why don't you want
to modify it?

Nick

Re: [O] ox-latex and small caps links

[Thomas S. Dye]

Aloha David,

David Dynerman  writes:

> This
> latex: trick in a link was the standard way to bracket text with any
> latex command, right?

The latex: link trick was invented for pre Org mode 8.  AFAIK, it
should still work, but I haven't been paying full attention.

However, in the meantime a syntax for inline latex code has been
developed:

,-
| Code within @@latex:some code@@ a paragraph.
`-

This new syntax might prove to be more robust in the long run.

hth,
Tom

-- 
Thomas S. Dye
http://www.tsdye.com

[O] ox-latex and small caps links

[David Dynerman]

Hi there,

I've been using links to render text in small caps when exporting to
LaTeX and HTML, e.g.

[[latex:textsc][this is in small caps]]

This worked fine in 8.2.10, but causes an error in latest. When I try to
export the file to LaTeX, the export fails with:

Unable to resolve link latex:textsc

Is this a bug? Is there a better way to render text in small caps? This
latex: trick in a link was the standard way to bracket text with any
latex command, right?

Thanks,
David


signature.asc
Description: PGP signature

Re: [O] Sparse tree for undated TODOs, or hierachical agenda?

[Nikolaus Rath]

On Apr 21 2015, Nikolaus Rath  wrote:
>> Now, if you want to narrow the agenda (C-c a) or org-sparse-tree 
>> (C-c /) to show TODO items not SCHEDULED or DEADLINE'd use the key 
>> 'm' and the following match:
>>
>> -SCHEDULED={.+}-DEADLINE={.+}+TODO="TODO"
>
> This, however, works perfectly, thanks a lot! Is this explained anywhere
> in the documentation? Because I certainly searched for it but could not
> find anything.

Now that I knew what to look for, I finally found it myself. Here's a
link for the benefit of future people trying to Google this:

Match syntax:
http://orgmode.org/org.html#Matching-tags-and-properties

..and the special properties that automatically exist:
http://orgmode.org/org.html#Special-properties

Best,
-Nikolaus

-- 
GPG encrypted emails preferred. Key id: 0xD113FCAC3C4E599F
Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F

 »Time flies like an arrow, fruit flies like a Banana.«

[O] How to match TODO items not SCHEDULED or DEADLINE'd (was: Sparse tree for undated TODOs, or hierachical agenda?)

[Nikolaus Rath]

On Apr 21 2015, Nikolaus Rath  wrote:
> On Apr 21 2015, jorge.alfaro-muri...@yale.edu (Jorge A. Alfaro-Murillo) wrote:
>> Now, if you want to narrow the agenda (C-c a) or org-sparse-tree 
>> (C-c /) to show TODO items not SCHEDULED or DEADLINE'd use the key 
>> 'm' and the following match:
>>
>> -SCHEDULED={.+}-DEADLINE={.+}+TODO="TODO"
>
> This, however, works perfectly, thanks a lot!

Actually, it seems it does not work for some cases. If I have a file
with

* TODO Item 1
* TODO Item 2
  SCHEDULED: <2015-04-24 Fri>
* Heading
** TODO Subitem 1
** TODO Subitem 1
  SCHEDULED: <2015-04-24 Fri>

end do the above procedure, I'm getting

* TODO Item 1
* TODO Item 2...
* Heading
** TODO Subitem 1...

Why is "Item 2" not being hidden?


Thanks,
-Nikolaus

-- 
GPG encrypted emails preferred. Key id: 0xD113FCAC3C4E599F
Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F

 »Time flies like an arrow, fruit flies like a Banana.«

[O] How to export an Org file to LaTeX's book class, but without parts?

[Marcin Borkowski]

Hi all,

this is an actual question, but it can be viewed as a continuation of
the "why use LaTeX directly and not Org" thread (disclaimer: from the
POV of an experienced LaTeX user and much less experienced Org-exporter
user).

So, I tried to do the opposite, just to learn something/unlock the "Org
Exporter" skill;-).  I want to export my Org file to the book class
(actually, a class similar to it, but never mind), but I want my
first-level headings to be chapters, not parts.  OTOH, I don't want to
modify org-latex-classes.  Is that possible, and if yes, how to achieve
that?

TIA,

-- 
Marcin Borkowski
http://octd.wmi.amu.edu.pl/en/Marcin_Borkowski
Faculty of Mathematics and Computer Science
Adam Mickiewicz University

Re: [O] Sparse tree for undated TODOs, or hierachical agenda?

[Nikolaus Rath]

On Apr 21 2015, jorge.alfaro-muri...@yale.edu (Jorge A. Alfaro-Murillo) wrote:
> Nikolaus Rath writes:
>
>> Jorge A. Alfaro-Murillo writes: 
>>> If you want to restrict to your current document before 
>>> building the agenda use '<', so if 'C-c a' calls your agenda 
>>> (suggested org key), then you can do 'C-c a < a' to get the 
>>> agenda restricted to the buffer that you are in. 
>> 
>> Well, yes, but that still throws away all the headings. E.g. 
>> 
>> * Task 1 ** TODO Do A ** Other stuff * Task 2 ** TODO Do B ** 
>> TODO Do C 
>>SCHEDULED: <2015-05-31 Sun> 
>> 
>> becomes (after C-c a t): 
>> 
>> * TODO Do A * TODO Do B 
>> 
>> What I would like to get is 
>> 
>> * Task 1 ** TODO Do A * Task 2 ** TODO Do B
>  
>>> I do not know what you mean by sparse tree, 
>> 
>> The sparse tree is what you get with C-c \ t (org-sparse-tree). 
>> For the above example, you get: 
>> 
>> * Task 1 ** TODO Do A * Task 2 ** TODO Do B ** TODO Do C 
>>SCHEDULED: <2015-05-31 Sun> 
>> 
>> so the structure is conserved like I want, but even with.. 
>> 
>>> but this excludes  anything scheduled or with a deadline from 
>>> the global todo list: 
>>> 
>>> #+BEGIN_SRC emacs-lisp 
>>>   (setq org-agenda-todo-ignore-scheduled 'all) (setq 
>>>   org-agenda-todo-ignore-deadlines 'all) 
>>> #+END_SRC 
>> 
>> .. the scheduled items are still included (because the todo-* 
>> settings apply only to the Agenda view, not the sparse tree 
>> view).
>
> It seems to me that these are two different issues. If you want 
> the TODO list in the org-agenda to show your headlines you can 
> configure the view to show breadcrumbs (and order by category):
>
> #+BEGIN_SRC emacs-lisp
>   (setq org-agenda-prefix-format
> '((agenda . " %i %-12:c%?-12t% s")
>   (timeline . "  % s")
>   (todo . " %i %-12:c%-24:b")
>   (tags . " %i %-12:c")
>   (search . " %i %-12:c")))
>
>   (setq org-agenda-sorting-strategy
> ((agenda habit-down time-up priority-down category-keep)
>  (todo category-keep)
>  (tags priority-down category-keep)
>  (search category-keep)))
> #+END_SRC

For me the second assignment fails with:

Debugger entered--Lisp error: (void-variable >)
  (setq org-agenda-sorting-strategy > ((agenda habit-down time-up priority-down 
category-keep) > (todo category-keep) > (tags priority-down category-keep) > 
(search category-keep)))
  eval((setq org-agenda-sorting-strategy > ((agenda habit-down time-up 
priority-down category-keep) > (todo category-keep) > (tags priority-down 
category-keep) > (search category-keep))) nil)
  eval-last-sexp-1(nil)
  eval-last-sexp(nil)
  call-interactively(eval-last-sexp nil nil)
  command-execute(eval-last-sexp)

If I evaluate just the first one, I'm getting the headlines as an
additional column which is better but not yet perfect.

> Now, if you want to narrow the agenda (C-c a) or org-sparse-tree 
> (C-c /) to show TODO items not SCHEDULED or DEADLINE'd use the key 
> 'm' and the following match:
>
> -SCHEDULED={.+}-DEADLINE={.+}+TODO="TODO"

This, however, works perfectly, thanks a lot! Is this explained anywhere
in the documentation? Because I certainly searched for it but could not
find anything.

(I'm nevertheless interested in trying out your first solution for
changing the Agenda view as well).

Best,
-Nikolaus

-- 
GPG encrypted emails preferred. Key id: 0xD113FCAC3C4E599F
Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F

 »Time flies like an arrow, fruit flies like a Banana.«

Re: [O] HTML + RDFa export/publishing ?

[John Kitchin]

your code doesn't look any uglier than mine ;)

You could replace many of your (if ) constructs with (when ) since there
is no else clause, but your (if ) constructs work just fine.

Olivier Berger writes:

> Hi.
>
> I've finally devoted a bit more time to follow the lines you'd drawn in
> the post below, and here's the result :
>
> http://www-public.telecom-sudparis.eu/~berger_o/test-org-publishing-rdfa.html
>
> It's not perfect as it doesn't offer a universal compact way to map all
> RDFa constructs to some handy and compact org syntax, but given a small
> number of patterns, and the corresponding elisp converter code, I think
> it achieves a quite interesting solution.
>
> Many thanks for the suggestion.
>
> Also, any comments much welcome (and yes, my lisp is ugly ;).
>
> Best regards,
>
> John Kitchin  writes:
>
>> Can you give us an example of what you are trying to do? I don't think
>> org-mode supports this rich of behavior out of the box, but see
>> http://kitchingroup.cheme.cmu.edu/blog/2015/02/05/Extending-the-org-mode-link-syntax-with-attributes/
>> for an example idea of what you could imagine doing with a link type
>> approach that could be inline with text.
>>

--
Professor John Kitchin
Doherty Hall A207F
Department of Chemical Engineering
Carnegie Mellon University
Pittsburgh, PA 15213
412-268-7803
@johnkitchin
http://kitchingroup.cheme.cmu.edu

[O] New Org-HTML-theme!!

[Fabrice Niessen]

Hello,

I've just published a new theme, called ReadTheOrg, on
https://github.com/fniessen/org-html-themes.

It is a clone of the great Sphinx theme used in the
http://docs.readthedocs.org/en/latest/ site.  It gives a beautiful and
professional style to all your Org docs...

Wanna test it right away?  Just add the following to your Org files:

--8<---cut here---start->8---
#+HTML_HEAD: https://ajax.googleapis.com/ajax/libs/jquery/2.1.3/jquery.min.js";>
#+HTML_HEAD: https://maxcdn.bootstrapcdn.com/bootstrap/3.3.4/js/bootstrap.min.js";>
#+HTML_HEAD: http://www.pirilampo.org/styles/readtheorg/js/readtheorg.js";>
--8<---cut here---end--->8---

and export...

#+begin_note
  While the original theme shines on mobile devices as well, ReadTheOrg
  does not stay completely functional.

  I don't have a lot of time to maintain this project due to other
  responsibilities.  Help is welcome to work on that (and eventually
  improve the default structure of the HTML export)!
#+end_note

PS- I also have written a demo page for the themes that provides
a maximal working support of Org mode syntax.

Please see the
https://github.com/fniessen/org-html-themes/blob/master/demo/org-mode-syntax.org
page for full examples of headings, code, admonitions, footnotes, tables
and other details.

Best regards,
Fabrice

-- 
Fabrice Niessen
Leuven, Belgium
http://www.pirilampo.org/

Re: [O] Sparse tree for undated TODOs, or hierachical agenda?

[Jorge A. Alfaro-Murillo]

Nikolaus Rath writes:

Jorge A. Alfaro-Murillo writes: 
If you want to restrict to your current document before 
building the agenda use '<', so if 'C-c a' calls your agenda 
(suggested org key), then you can do 'C-c a < a' to get the 
agenda restricted to the buffer that you are in. 


Well, yes, but that still throws away all the headings. E.g. 

* Task 1 ** TODO Do A ** Other stuff * Task 2 ** TODO Do B ** 
TODO Do C 
   SCHEDULED: <2015-05-31 Sun> 

becomes (after C-c a t): 

* TODO Do A * TODO Do B 

What I would like to get is 


* Task 1 ** TODO Do A * Task 2 ** TODO Do B


I do not know what you mean by sparse tree, 


The sparse tree is what you get with C-c \ t (org-sparse-tree). 
For the above example, you get: 

* Task 1 ** TODO Do A * Task 2 ** TODO Do B ** TODO Do C 
   SCHEDULED: <2015-05-31 Sun> 

so the structure is conserved like I want, but even with.. 

but this excludes  anything scheduled or with a deadline from 
the global todo list: 

#+BEGIN_SRC emacs-lisp 
  (setq org-agenda-todo-ignore-scheduled 'all) (setq 
  org-agenda-todo-ignore-deadlines 'all) 
#+END_SRC 


.. the scheduled items are still included (because the todo-* 
settings apply only to the Agenda view, not the sparse tree 
view).


It seems to me that these are two different issues. If you want 
the TODO list in the org-agenda to show your headlines you can 
configure the view to show breadcrumbs (and order by category):


#+BEGIN_SRC emacs-lisp
 (setq org-agenda-prefix-format
   '((agenda . " %i %-12:c%?-12t% s")
 (timeline . "  % s")
 (todo . " %i %-12:c%-24:b")
 (tags . " %i %-12:c")
 (search . " %i %-12:c")))

 (setq org-agenda-sorting-strategy
   ((agenda habit-down time-up priority-down category-keep)
(todo category-keep)
(tags priority-down category-keep)
(search category-keep)))

#+END_SRC

Now, if you want to narrow the agenda (C-c a) or org-sparse-tree 
(C-c /) to show TODO items not SCHEDULED or DEADLINE'd use the key 
'm' and the following match:


-SCHEDULED={.+}-DEADLINE={.+}+TODO="TODO"

Best,
--
Jorge.

Re: [O] Cannot insert footnote here

[Thomas S. Dye]

Aloha Seb,

Sebastien Vauban 
writes:

> Thomas S. Dye wrote:
>> Vikas Rawal  
>> writes:
>>
>>> But a footnote at the end of a headline breaks LaTeX export. LaTeX
>>> needs an optional title as follows, to be able to include footnote in
>>> headline.
>>>
>>> http://tex.stackexchange.com/questions/47380/how-can-i-have-a-footnote-with-an-url-in-a-section-title
>>> 
>>>
>>> How does one get that in Org?
>>
>> I don't know how to get \section[short]{long} with Org mode.
>
> There is the ALT_TITLE property, which allows to set an alternate
> (shorter, for example) title for a given headline.

Thanks for this useful pointer.

All the best,
Tom

-- 
Thomas S. Dye
http://www.tsdye.com

Re: [O] Beamer export: heading tags rendered as \textsc{}

[Eric S Fraga]

On Tuesday, 21 Apr 2015 at 09:08, Joon Ro wrote:
> Hi,
> I just found that beamer export is rendering heading tags with \textsc. For 
> example, it looks like this in the latex file:
> \section{Section Name\hfill{}\textsc{tagname}}
> Which makes them show up in the navigation bar in beamer slides.Please let me 
> know if I can turn this off - I'm using org 8.3beta.

Try

#+options: tags:nil

which you can find in the manual: (org) Export settings

You may need to re-initialize the file (hit C-c C-c on the options
line).

-- 
: Eric S Fraga (0xFFFCF67D), Emacs 25.0.50.1, Org release_8.3beta-1030-g65bbb1

[O] Capture prepends instead of appending

[Marcin Borkowski]

Hi all,

I have this in my init.el:

,
| (setq org-capture-templates
|  '(("j" "Journal entry" plain
|  (file+datetree+prompt "~/works/marcin/journal/journal.org")
|  " %i%?\n")))
`

I thought that when calling it multiple times with the same date, new
entries will be appended to the date heading, but they get prepended
instead.  Is it a feature?  (I'm on Org-mode version 8.2.10
(8.2.10-37-gc000e8-elpa @ /home/marcin/.emacs.d/elpa/org-20150413/).)

Example calling this template twice, the first time typing "foo" and the
second time typing "bar", yields:

,
| *** 2015-04-21 wtorek
|  bar
|  foo
`

(so that "bar" comes before "foo").

Regards,

-- 
Marcin Borkowski
http://octd.wmi.amu.edu.pl/en/Marcin_Borkowski
Faculty of Mathematics and Computer Science
Adam Mickiewicz University

Re: [O] Sparse tree for undated TODOs, or hierachical agenda?

[Nikolaus Rath]

On Apr 21 2015, jorge.alfaro-muri...@yale.edu (Jorge A. Alfaro-Murillo) wrote:
> Hi, Nikolaus.
>
> Nikolaus Rath writes:
>
>> Hello, 
>> 
>> I'm starting to like orgmode more and more. Thanks for working 
>> on this! 
>> 
>> However, for me the global todo list in the Agenda very hard to 
>> digest (even when excluding sublevels), so I'd rather have a 
>> view that conserves the document structure.
>
> If you want to restrict to your current document before building 
> the agenda use '<', so if 'C-c a' calls your agenda (suggested org 
> key), then you can do 'C-c a < a' to get the agenda restricted to 
> the buffer that you are in.

Well, yes, but that still throws away all the headings. E.g.

* Task 1
** TODO Do A
** Other stuff
* Task 2
** TODO Do B
** TODO Do C
   SCHEDULED: <2015-05-31 Sun>

becomes (after C-c a t):

* TODO Do A
* TODO Do B

What I would like to get is

* Task 1
** TODO Do A
* Task 2
** TODO Do B

>  
>> Is there a way to create a sparse tree that shows only undated 
>> TODOs (i.e., excludes anything that scheduled or has a 
>> deadline)?
>
> I do not know what you mean by sparse tree,

The sparse tree is what you get with C-c \ t (org-sparse-tree). For the
above example, you get:

* Task 1
** TODO Do A
* Task 2
** TODO Do B
** TODO Do C
   SCHEDULED: <2015-05-31 Sun>

so the structure is conserved like I want, but even with..

> but this excludes 
> anything scheduled or with a deadline from the global todo list:
>
> #+BEGIN_SRC emacs-lisp
>   (setq org-agenda-todo-ignore-scheduled 'all)
>   (setq org-agenda-todo-ignore-deadlines 'all)
> #+END_SRC

.. the scheduled items are still included (because the todo-* settings
apply only to the Agenda view, not the sparse tree view).


Best,
-Nikolaus

-- 
GPG encrypted emails preferred. Key id: 0xD113FCAC3C4E599F
Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F

 »Time flies like an arrow, fruit flies like a Banana.«

Re: [O] Portable way to insert and display images in an org entry ?

[Sebastien Vauban]

Xavier wrote:
> Hello,
>
> I use org-mode on many different OS (cygwin, OSX, GNU/linux), as such, I
> have problems when I want to include a link of the 'file:' family.
>
> Last example, I wanted to include a picture from my Dropbox into my org
> file which is ok. But, C-c C-x C-v can't do anything good on my cygwin
> installation since the link is:
>
> [[file:Captures d'écran/20150421-SOAINFRA-saturation.png][Illustration
> de la saturation du TBS I7_SOAINFRA_AA_DATA01]]

Can't you avoid the space in "Capture d'écran" (and maybe the accent as
well)?

Best regards,
  Seb

-- 
Sebastien Vauban

Re: [O] org-table relative reference questions

[Jeffrey Brent McBeth]

On Tue, Apr 21, 2015 at 10:13:53AM +0200, Michael Brand wrote:
> Hi Jeffrey
> 
> On Mon, Apr 20, 2015 at 3:35 PM, Jeffrey Brent McBeth  
> wrote:
> > I'm looking for a way to reference a row or column on both the left
> > side and right side of a table formula that is "easily" manipulable.
> 
> As you noticed the left side is very limited compared to the right
> side. The solution below keeps the left side simple. "x" is used as a
> movable marker to indicate the beginning of the range:
> 
> | F | A | B |  C |
> |---+---+---+|
> | x | 1 | 3 |  4 |
> |   | 2 | 4 | 69 |
> |---+---+---+|
> |   | 3 |   ||
> #+TBLFM: @>$2 = vsum(subvec(@I$2..@II$2, find(@I$1..@II$1, x), 0)); E
> :: @<<$4..@>>$4 = if("$1" == "(x)", $-2 + $-1, $0)

That is awesome.  subvec and if seem to be two very powerful tools that I've 
missed as I've trawled the documentation.  Thank you so much.

Jeff

-- 
"The man who does not read good books has no advantage over 
 the man who cannot read them."
 -- Mark Twain

Re: [O] Sparse tree for undated TODOs, or hierachical agenda?

[Jorge A. Alfaro-Murillo]

Hi, Nikolaus.

Nikolaus Rath writes:

Hello, 

I'm starting to like orgmode more and more. Thanks for working 
on this! 

However, for me the global todo list in the Agenda very hard to 
digest (even when excluding sublevels), so I'd rather have a 
view that conserves the document structure.


If you want to restrict to your current document before building 
the agenda use '<', so if 'C-c a' calls your agenda (suggested org 
key), then you can do 'C-c a < a' to get the agenda restricted to 
the buffer that you are in.


Is there a way to create a sparse tree that shows only undated 
TODOs (i.e., excludes anything that scheduled or has a 
deadline)?


I do not know what you mean by sparse tree, but this excludes 
anything scheduled or with a deadline from the global todo list:


#+BEGIN_SRC emacs-lisp
 (setq org-agenda-todo-ignore-scheduled 'all)
 (setq org-agenda-todo-ignore-deadlines 'all)
#+END_SRC

Instead of 'all you can also use 'past or 'future to exclude only 
scheduled and deadlines from the past or the future, respectively.


Best,
--
Jorge.

[O] Beamer export: heading tags rendered as \textsc{}

[Joon Ro]

Hi,
I just found that beamer export is rendering heading tags with \textsc. For 
example, it looks like this in the latex file:
\section{Section Name\hfill{}\textsc{tagname}}
Which makes them show up in the navigation bar in beamer slides.Please let me 
know if I can turn this off - I'm using org 8.3beta.
Thank you!Joon

  

Re: [O] Cannot insert footnote here

[Sebastien Vauban]

Thomas S. Dye wrote:
> Vikas Rawal  writes:
>
>> But a footnote at the end of a headline breaks LaTeX export. LaTeX
>> needs an optional title as follows, to be able to include footnote in
>> headline.
>>
>> http://tex.stackexchange.com/questions/47380/how-can-i-have-a-footnote-with-an-url-in-a-section-title
>> 
>>
>> How does one get that in Org?
>
> I don't know how to get \section[short]{long} with Org mode.

There is the ALT_TITLE property, which allows to set an alternate
(shorter, for example) title for a given headline.

Best regards,
  Seb

-- 
Sebastien Vauban

[O] howto disable infojs

[OSiUX]

I try in the .org file:

#+OPTIONS: html-use-infojs:nil

... and the .emacs rc file:

(setq org-html-use-infojs nil)

any configuration does not work :(

Org-mode version 8.3beta
(release_8.3beta-1055-g797023 @ /home/osiris/org-mode/lisp/)

GNU Emacs 24.4.1
(x86_64-pc-linux-gnu) of 2015-03-07 on trouble, modified by Debian

-- 

::

  Osiris Alejandro Gomez (OSiUX) os...@osiux.com.ar
  DC44 95D2 0D5D D544 FC1A F00F B308 A671 9237 D36C
  http://www.osiux.com.ar http://www.altermundi.net


signature.asc
Description: Digital signature

Re: [O] HTML + RDFa export/publishing ?

[Olivier Berger]

Hi.

I've finally devoted a bit more time to follow the lines you'd drawn in
the post below, and here's the result :

http://www-public.telecom-sudparis.eu/~berger_o/test-org-publishing-rdfa.html

It's not perfect as it doesn't offer a universal compact way to map all
RDFa constructs to some handy and compact org syntax, but given a small
number of patterns, and the corresponding elisp converter code, I think
it achieves a quite interesting solution.

Many thanks for the suggestion.

Also, any comments much welcome (and yes, my lisp is ugly ;).

Best regards,

John Kitchin  writes:

> Can you give us an example of what you are trying to do? I don't think
> org-mode supports this rich of behavior out of the box, but see
> http://kitchingroup.cheme.cmu.edu/blog/2015/02/05/Extending-the-org-mode-link-syntax-with-attributes/
> for an example idea of what you could imagine doing with a link type
> approach that could be inline with text.
>

-- 
Olivier BERGER 
http://www-public.telecom-sudparis.eu/~berger_o/ - OpenPGP-Id: 2048R/5819D7E8
Ingenieur Recherche - Dept INF
Institut Mines-Telecom, Telecom SudParis, Evry (France)

Re: [O] Portable way to insert and display images in an org entry ?

[Myles English]

Hello Xavier,

Xavier writes:
> I use org-mode on many different OS (cygwin, OSX, GNU/linux), as such, I
> have problems when I want to include a link of the 'file:' family.
>
> Last example, I wanted to include a picture from my Dropbox into my org
> file which is ok. But, C-c C-x C-v can't do anything good on my cygwin
> installation since the link is:
>
> [[file:Captures d'écran/20150421-SOAINFRA-saturation.png][Illustration
> de la saturation du TBS I7_SOAINFRA_AA_DATA01]]
>
> What can be a good alternative ? Add my file as an attachment and link
> from it ? (is it even possible ?)

If you want to try that last idea, the syntax for the link is:

[[att:20150421-SOAINFRA-saturation.png]]

Myles

[O] Portable way to insert and display images in an org entry ?

[Xavier]

Hello,

I use org-mode on many different OS (cygwin, OSX, GNU/linux), as such, I
have problems when I want to include a link of the 'file:' family.

Last example, I wanted to include a picture from my Dropbox into my org
file which is ok. But, C-c C-x C-v can't do anything good on my cygwin
installation since the link is:

[[file:Captures d'écran/20150421-SOAINFRA-saturation.png][Illustration
de la saturation du TBS I7_SOAINFRA_AA_DATA01]]

What can be a good alternative ? Add my file as an attachment and link
from it ? (is it even possible ?)

Regards
-- Xavier

Re: [O] org-table relative reference questions

[Michael Brand]

Hi Jeffrey

On Mon, Apr 20, 2015 at 3:35 PM, Jeffrey Brent McBeth  wrote:
> I'm looking for a way to reference a row or column on both the left
> side and right side of a table formula that is "easily" manipulable.

As you noticed the left side is very limited compared to the right
side. The solution below keeps the left side simple. "x" is used as a
movable marker to indicate the beginning of the range:

| F | A | B |  C |
|---+---+---+|
| x | 1 | 3 |  4 |
|   | 2 | 4 | 69 |
|---+---+---+|
|   | 3 |   ||
#+TBLFM: @>$2 = vsum(subvec(@I$2..@II$2, find(@I$1..@II$1, x), 0)); E
:: @<<$4..@>>$4 = if("$1" == "(x)", $-2 + $-1, $0)

| F | A | B |  C |
|---+---+---+|
|   | 1 | 3 | 42 |
| x | 2 | 4 |  6 |
|---+---+---+|
|   | 2 |   ||
#+TBLFM: @>$2 = vsum(subvec(@I$2..@II$2, find(@I$1..@II$1, x), 0)); E
:: @<<$4..@>>$4 = if("$1" == "(x)", $-2 + $-1, $0)

For the details see the Org manual about spreadsheet and the Calc
manual.

Michael

Re: [O] Bug: HTML export ignoring CUSTOM_ID properties

[Nicolas Goaziou]

Hello,

Daniel Clemente  writes:

> I also saw this change (diff format):
>
> -
> -1.4.3.1.2 
> tercer error con stash
> +
> +1.4.3.1.2 
> tercer error con stash
>
> The #sec-1-4-3-1-2 format was better. If I delete section 1.4.3.1.2,
> section 1.5 is still called 1.5, that's good.

And if you delete section 1.4, section 1.5 is no longer called 1.5. So
you need to update IDs most times you change headline numbering. I don't
think it is really better than the current state.

> With a flat numbering like #orgheadline129, deleting any headline
> would change the IDs of all headers after it.

True. This was already the case before, as explained above, or when
using unnumbered headlines.

> And what's the use of IDs if they're not permanent?

The point is that Org knows the ID associated to a given headline, and
provides tools to access them (`org-export-get-reference' for back-end
developers, [[*tercer error con stash]] for users).

I'm not against re-using CUSTOM_ID as in "outline-container-CUSTOM_ID",
but in the general case, where no CUSTOM_ID is defined, the current
state is fine by me.


Regards,

-- 
Nicolas Goaziou