On Fri, Jul 05, 2013 at 09:26:22PM +0200, Uwe Brauer wrote:
On 07/05/2013 07:40 PM, Eric S Fraga wrote:
#+begin_comment ... #+end_comment?
does not work, the odt file contains
#+begin_comment
my text
#+end_comment ?
the issue is I want to write say one paragraph in Spanish
and
When I publish my website, orgmode gives me the sitemap as an html.
Google requires sitemap as an xml, rss or text file
(https://support.google.com/webmasters/answer/183668).
Any suggestions on how to get orgmode to create a google-compatible
sitemap?
You seem to have missed my
Suvayu == Suvayu Ali fatkasuvayu+li...@gmail.com writes:
On Fri, Jul 05, 2013 at 09:26:22PM +0200, Uwe Brauer wrote:
the issue is I want to write say one paragraph in Spanish
and the next in German, again spanish then German, etc
but the odt file should only display one
Hi, Bastien,
Bastien b...@gnu.org écrivit :
value for : org-tag-alist-for-agenda
((:startgroup)
(prêté . 112)
(emprunté . 101)
(:endgroup)
(note . 110)
(noexport . 120)
(lien . 98)
(crypt . 99)
(projet . 112)
(suspendu . 122)
(:startgroup lieu)
(@dehors . 100)
Suvayu Ali writes:
On Fri, Jul 05, 2013 at 09:26:22PM +0200, Uwe Brauer wrote:
the issue is I want to write say one paragraph in Spanish
and the next in German, again spanish then German, etc
but the odt file should only display one language.
Try drawers:
--8---
As the export option `#+TEXT:' is completely ignored I assume that
something has changed. What is now the correct way to insert some
descriptive text before the toc?
I'm using org from git:
Org-mode version 8.0.3 (release_8.0.3-324-gb61ef4)
--
web: http://literaturlatenight.de
jabberID:
Hello,
henry atting s...@online.de writes:
As the export option `#+TEXT:' is completely ignored I assume that
something has changed. What is now the correct way to insert some
descriptive text before the toc?
By default (i.e. with :toc option), TOC is included at the beginning of
the
Hello Uwe,
On Sat, Jul 06, 2013 at 10:37:07AM +0200, Uwe Brauer wrote:
While I would like to have some tags which I could toggle on and off,
for example in the example of Eric, I would just substitute
the tag :noexport: for :export:
If you want to use tags, but then say you would prefer
Hi Bastien,
b...@gnu.org writes:
Hi Alan,
Alan Schmitt alan.schm...@polytechnique.org writes:
I'm trying to find a way to create an agenda bloc (of type agenda) that
is restricted to a set of tags. I tried using a skip function but (as I
explained in another mail) I cannot get it to work.
Hi Maurice,
Maurice za...@aliceadsl.fr writes:
No, this value was the result of the command « describe-variable
org-tag-alist-for-agenda »
Yes -- but somehow the value of this variable is not correctly set.
I will try your minimal example and check, thanks for sharing it.
--
Bastien
Nicolas Goaziou n.goaz...@gmail.com writes:
Hello,
henry atting s...@online.de writes:
As the export option `#+TEXT:' is completely ignored I assume that
something has changed. What is now the correct way to insert some
descriptive text before the toc?
By default (i.e. with :toc option),
Hi Maurice,
Bastien b...@gnu.org writes:
I will try your minimal example and check, thanks for sharing it.
I pushed a fix. Please try against the maint or master branch when
you get a chance. Thanks for reporting this!
--
Bastien
Hi List,
when parsing an Org file with org-element-parse-buffer, headline titles
and section contents (e.g.) end up as secondary strings in the
parse-tree that do have a ':parent' attribute.
When I try to modify all :parent attributes inside a parse-tree with
`org-element-map' (by mapping over
Hi Eric,
Eric Schulte schulte.e...@gmail.com writes:
Andreas Leha andreas.l...@med.uni-goettingen.de writes:
Hi Eric,
Eric Schulte schulte.e...@gmail.com writes:
Hi Andreas,
This should be easy to turn on or off using the newly introduced
:prologue and :epilogue header arguments. See
El Sat, 6 Jul 2013 13:03:01 +0200 Suvayu Ali va escriure:
If you or any other user wants this kind of feature, you have to come up
with a syntax that is not intrusive and doesn't break basic Org
features.
I created such a syntax for normal text files [1] but have been struggling to
port
Hello,
Thorsten Jolitz tjol...@gmail.com writes:
when parsing an Org file with org-element-parse-buffer, headline titles
and section contents (e.g.) end up as secondary strings in the
parse-tree that do have a ':parent' attribute.
When I try to modify all :parent attributes inside a
Daniel Clemente n142...@gmail.com writes:
El Sat, 6 Jul 2013 13:03:01 +0200 Suvayu Ali va escriure:
If you or any other user wants this kind of feature, you have to come up
with a syntax that is not intrusive and doesn't break basic Org
features.
I created such a syntax for normal
I'd like to be able to produce a TODO list that is sorted by timestamp
independently of category. I'm still new to elisp and so don't yet
understand all the code involved. What I've been able to do so far is
create a separate version of org-todo-list by changing a single line:
18 matches
Mail list logo
