myq larson writes:
> Using that definition though, there are probably three paragraphs. I choose
> ASCII export as the easiest example to show in email, but exporting to
> LaTeX shows the problem more clearly. There will not be two new lines
> which means the two paragraphs will be interpreted as
Hello,
myq larson writes:
> When I try to archive an inlinetask, I get the following error:
>
> : The kill is not a (set of) tree(s) - please use to yank
> anyway
Archiving, or refiling inlinetasks is not supported.
Regards,
--
Nicolas Goaziou
On Sun, Jun 7, 2015 at 4:19 AM, Nicolas Goaziou
wrote:
> Hello,
>
> myq larson writes:
>
>> If there is an inline task at the end of a paragraph, when the document
>> is exported with the =inlinetask= option set to =nil=, the space after
>> the inline task and before the next paragraph will be ig
thx Eric
that's exactly what i needed. much appreciated!
z
On Sun, Jun 7, 2015 at 9:51 PM, Eric Abrahamsen
wrote:
> There are generally two ways: use the customize interface to customize
> `org-export-backends' (I think you *need* to use customize for that? Or
> at least, you do if you want it
There are generally two ways: use the customize interface to customize
`org-export-backends' (I think you *need* to use customize for that? Or
at least, you do if you want it to take immediate effect), or just
(require 'ox-odt). Personally I don't like customize very much, so I
just have a bunch of
Hi all
this must be trivial but google fails me on this. how does one add the ODT
exporter to the main orgmode export dialog?
kind regards
Z
"Charles C. Berry" writes:
> On Sat, 6 Jun 2015, Sharon Kimble wrote:
>
>> Nick Dokos writes:
>>
>>> Sharon Kimble writes:
>>>
I've been unable to sort an unordered list as per
http://orgmode.org/manual/Plain-lists.html where it says 'C-c ^' but
everytime I try on a highlighted r
Hello,
myq larson writes:
> If there is an inline task at the end of a paragraph, when the document
> is exported with the =inlinetask= option set to =nil=, the space after
> the inline task and before the next paragraph will be ignored and the
> two paragraphs will combine as one.
>
> For examp
If there is an inline task at the end of a paragraph, when the document
is exported with the =inlinetask= option set to =nil=, the space after
the inline task and before the next paragraph will be ignored and the
two paragraphs will combine as one.
For example, this document
#+BEGIN_EXAMPLE
,#+
When I try to archive an inlinetask, I get the following error:
: The kill is not a (set of) tree(s) - please use to yank anyway
The task was created with =C-c C-x t=, so it contains an END line. I get
the same error even when starting emacs with =emacs -Q= and then
enabling the Org-mode inlinet
10 matches
Mail list logo
