Eric Schulte writes:
> Hi,
>
> I've recently put together a web server which runs in Emacs and exports
> local Org-mode files to HTML in such a way that they may be edited from
> within a web browser with the edits saved to local files on disk. The
> code is available from github.
Eric,
I have
On Fri, Sep 14, 2012 at 1:01 AM, Bastien wrote:
> Hi John,
>
> John Hendy writes:
>
>> Just wondering if a capture template could be setup to file into the
>> "Tasks" headline (sub-headline) of the matching top level headline
>> with that tag or something similar?
>
> You could use a function in
Kyle Sexton writes:
> ** App Store
> A new version of the application has been published on iTunes connect
> and is awaiting Apple's review before being added to the Apple
> store.
>
> Because of encryption export laws, the feature to do encryption
> on org files has been *removed* until I can g
Samuel Wales writes:
> I can't reproduce this now, but recently I have had issues with
> capture encrypting upon finalizing. The entry was not encrypted to
> begin with.
>
> It only occurred with a certain template.
>
> Is this a known bug?
This started happening to me late last week as well.
Vikas Rawal writes:
> If the result of an R source block contains a data frame with NA, the
> NAs are replaced by "nil" when I evaluate the source block. When I
> export the file, these appear as nil in the resulting pdf/latex file.
>
> I would like the NAs to be replaced by blank cells or by a
If the result of an R source block contains a data frame with NA, the
NAs are replaced by "nil" when I evaluate the source block. When I
export the file, these appear as nil in the resulting pdf/latex file.
I would like the NAs to be replaced by blank cells or by a less
obstrusive character like
Hello,
Here a first patch to do the above announced thing. Surely, this should be
extended to more types of lists, but I first wait for comments...
>From 49e516a175e658469088181bb0c364136198360e Mon Sep 17 00:00:00 2001
From: Sebastien Vauban
Date: Mon, 1 Oct 2012 23:43:43 +0200
Subject: [PATCH
Hello,
Looking at the presentation of the clocktable, I find that its "summary" line
should be converted into a caption, as any legend would be for any regular
table.
You can test it, and see its effect, with such a ECM file:
--8<---cut here---start->8---
* De
All,
I've been working with Richard Moreland on the transition to being the
new maintainer of MobileOrg on iOS.
* Things that have happened during transition
** Mailing list
A new mailing list for application discussion has been created which
you can register for at
http://www.org-mobile.org/mai
Dear Eric,
Many thanks for this; it was very useful: I've got the Remembrance Agent
up and running now.
Eric Fraga writes:
> Hi,
>
> sorry I am coming late to this thread. I use the Remembrance Agent. It
> works great for me, trawling both emails and all my text (org, latex,
> etc.) document
This is an automatic notification regarding your Bug report
which was filed against the org-mode package:
#685154: Bug: org-export-with-priority: t broken [7.8.11]
It has been closed by Sebastien Delafond .
Their explanation is attached below along with your original report.
If this explanation
Hi George,
George McNinch writes:
> I'm no longer seeing
>
>org-agenda-timerange-leaders
>
> with org-version 7.9.2 (org-20121001 from elpa). I don't know for how
> long this has not been working (I just noticed it this morning).
Thanks for reporting this!
I'm no longer seeing
org-agenda-timerange-leaders
with org-version 7.9.2 (org-20121001 from elpa). I don't know for how
long this has not been working (I just noticed it this morning).
If the following agenda item appears in the file "agenda.org":
--
* foo
<
Hi Myles,
"Myles English" wrote:
> Using git master 2bd95b6b of Fri Sep 28 10:05:20 2012, if I tangle this
> with org-babel-tangle:
>
> #+BEGIN_SRC sh :tangle file.sh
> a
> #+END_SRC
>
> then file.sh would contain a blank line at the top, which I would not
> have expected to be there.
Add ":padli
Alan Lue,
Alan Lue wrote:
> I find that code block header arguments specified with `#+HEADERS:'
> consistently appear in the exported document. For example, exporting the
> following document to PDF or HTML will include the "exports" header in
> the output:
>
> * Manifestation of Problem
>
> Loo
Alan,
Alan Lue wrote:
> I find that code block header arguments specified with `#+HEADERS:'
> consistently appear in the exported document. For example, exporting the
> following document to PDF or HTML will include the "exports" header in
> the output:
>
> * Manifestation of Problem
>
> Look, o
Following up.
Does anyone else see this behavior? Headers always appear in the export
whenever my document includes a code block with a separate `#+HEADERS:'
line.
Alan Lue writes:
> I find that code block header arguments specified with `#+HEADERS:'
> consistently appear in the exported docum
17 matches
Mail list logo
