Hello,
I have the following files I want to export to html:
common.org:
--8<---cut here---start->8---
#+TITLE: Unison Binaries
#+OPTIONS: toc:nil num:nil
#+HTML_HEAD:
* sidebar
:PROPERTIES:
:CUSTOM_ID: sidebar
:HTML_CONTAINER_CLASS: container-sidebar
On Thu, Dec 10, 2015 at 8:50 PM, Skip Collins wrote:
> Herbert Sitz wrote:
>> * Main tree :myexporttree:
>> fkjaldfk
>> ** subhead
>> ** subhead
>> * anoher heading 1
>> * another heading level 1
>> ** subhead
>> ** subhead
>
> I did try using the default SELECT_TAG :export: on my main docume
No, this still doesn't work. I just tested with my .emacs having only two
lines:
#+BEGIN_SRC emacs-lisp
(require 'org "/usr/local/share/emacs/site-lisp/org/org")
(require 'ox-koma-letter
(locate-user-emacs-file
"path/to/org-mode/contrib/lisp/ox-koma-letter"))
#+END_SRC
the org-mode
Ondřej Grover writes:
[...]
>> But what about when :results != value? Doesn't your proposal only
>> handle returning the last value?
>>
> You mean :results output ? In that case it could just omit the
> "open(...).write(...) " part and capture anything the console prints before
> the primary pr
Herbert Sitz wrote:
> * Main tree :myexporttree:
> fkjaldfk
> ** subhead
> ** subhead
> * anoher heading 1
> * another heading level 1
> ** subhead
> ** subhead
I did try using the default SELECT_TAG :export: on my main document
subtree. The problem is that the subtree is not "promoted" to th
On Thu, Dec 10, 2015 at 6:27 PM, Herbert Sitz wrote:
> Not a perfect solution, buy I think you can use the #+SELECT_TAGS option to
> set which tress will be exported by default, then tag your desired export
> tree with that tag. Then when you export the full buffer (not just a
> subtree) it will
Not a perfect solution, buy I think you can use the #+SELECT_TAGS option to
set which tress will be exported by default, then tag your desired export
tree with that tag. Then when you export the full buffer (not just a
subtree) it will choose the tree with that tag.
E.g.,
Andreas Leha wrote:
> Skip Collins writes:
>>> Try to run `org-export-dispatch' with a prefix from the second time
>>> onwards (so, do C-u C-c C-e).
>>
>> Good try, but it does not do what I want. It selects the subtree
>> currently at point, just as if I ran the dispatcher again and selected
>>
Hi list,
I have org-agenda-todo-list-sublevels set to nil. However, given this
tree:
* DONE task
** TODO subtask
it turns out that the todo list in the agenda shows the "subtask" anyway.
Should it be so? I would guess not.
The reason I'd like to exclude this "subtask" from displaying is
some
Hi Skip,
Skip Collins writes:
> Andreas Leha wrote:
>>> The export dispatcher allows me to export only the current subtree.
>>> This is nice, but I would like to avoid having to put point in just
>>> the right place before invoking the dispatcher. I have a document with
>>> lots of things in it.
Andreas Leha wrote:
>> The export dispatcher allows me to export only the current subtree.
>> This is nice, but I would like to avoid having to put point in just
>> the right place before invoking the dispatcher. I have a document with
>> lots of things in it. One of the top-level headlines contai
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Arun Isaac writes:
> Currently, the feed URL is assumed to be html-link-home or
> publishing-directory concatenated with the output filename of the
> feed. This need not necessarily be so. So, the RSS_FEED_URL option
> keyword is introduced to let
Hi,
I have implemented a new option keyword, RSS_FEED_URL, for the RSS
exporter backend.
The RSS_FEED_URL goes into the atom:link element that identifies the
feed's own URL.
http://www.rssboard.org/rss-profile#namespace-elements-atom-link
Currently, the feed URL is assumed to be html-link-home
Hi,
When I attempt to export an Org document using the HTML backend (and
Org backend) I get (after the initial tangle, even a normal Org
document with the word "Example" fails):
╭
│ Wrong number of arguments: setq, 1
╰
So I proceed to use Edebug to find out why this is happening:
Line 2
Hi Skip,
Skip Collins writes:
> The export dispatcher allows me to export only the current subtree.
> This is nice, but I would like to avoid having to put point in just
> the right place before invoking the dispatcher. I have a document with
> lots of things in it. One of the top-level headlines
The export dispatcher allows me to export only the current subtree.
This is nice, but I would like to avoid having to put point in just
the right place before invoking the dispatcher. I have a document with
lots of things in it. One of the top-level headlines contains the
content of what I want to
Remember to cover the basics, that is, what you expected to happen and
what in fact did happen. You don't know how to make a good report? See
http://orgmode.org/manual/Feedback.html#Feedback
Your bug report will be posted to the Org-mode mailing list.
Rasmus writes:
> Out of curiosity, why is it "more" consistent to return paragraph
> here?
Notwithstanding this case, if `org-element-at-point' returns
`special-block', you /know/ that you are either on block boundaries
(#+begin_special or #+end_special) or on any affiliated keyword above,
but /
Hi,
York Zhao writes:
> Thanks for your help. However, adding the :EXPORT_DATE: property doesn't
> work. Firstly, there's an error: "PDF file produced with errors.".
You have to add an address, e.g.
* letter 1
:PROPERTIES:
:EXPORT_DATE: 2015-10-26 Monday
:END:
** to
Hi Nicolas,
Thanks for the helpful reply.
Nicolas Goaziou writes:
>> Is there a reason why org-element-at-point reports the type to be a
>> paragraph for special blocks? E.g. in the examples at the bottom of this
>> mail, where | is the cursor, the types are: export-block, src-block and
>> par
> You haven't modified your load-path in this minimal config, so you're
> using the built-in Org version, as indicated in your Org version output
> above.
That was it! Thanks! Sorry for the noise.
--
Zack Piper http://apertron.net
Zack Piper writes:
> When attempting to open an Org file (such as my own `config.org'), I
> get "org-mode fontification error" appear in the mini-buffer.
>
> I can reproduce it using the following:
>
> Org-mode version 8.2.10 (release_8.2.10 @
> /home/zack/ins/share/emacs/25.0.50/lisp/org/) (late
Please refer to the second email I sent (14:35) as I feel this is
better.
Due to technical problems with my email system I sent two different
ones and didn’t think to look in the logs, my apologies.
(Apologies for the second email, didn’t see it go through...)
When attempting to open an Org file (such as my own `config.org'), I
get "org-mode fontification error" appear in the mini-buffer.
I can reproduce it using the following:
Org-mode version 8.2.10 (release_8.2.10 @
/home/zack/ins/share/
Hi,
I'm using Org mode from master, when I attempt to open an Org file
with code blocks while `org-src-fontify-natively' as `t' I get
"org-mode fontification error", I appear to be able to reproduce this
using a minimal config.
╭
│ (require 'org)
│ (require 'ob-tangle)
│ (setq org-src-fontif
>>> "Uwe" == Uwe Brauer writes:
> Hello
> I swear that usually worked in my latex files.
> Situation:
Sorry the problem was caused by these lines in my init file:
(add-hook
'orgtbl-mode-hook
(lambda ()
(org-defkey orgtbl-mode-map "\C-c\C-c"
(orgtbl-make-bin
Hello
I swear that usually worked in my latex files.
Situation:
In my latex file I have orgtbl-mode enabled, I insert
A radio table and I obtain
,
|
| \documentclass[12pt]{article}
| \begin{document}
| % BEGIN RECEIVE ORGTBL test
| % END RECEIVE ORGTBL test
| \begin{comment}
| #+ORGTBL: SE
Am 09.12.2015 12:45 schrieb Eric S Fraga:
On Tuesday, 8 Dec 2015 at 21:07, zang_n...@posteo.de wrote:
Dear fellow Orgers,
I like the metropolis beamer theme a lot [1], and I use it with Org
frequently. metropolis has a \plain macro that inserts a new,
minimally
styled slide optimal for a shor
28 matches
Mail list logo
