I am trying to publish a project where the files have a custom extension
using the new exporter:
("org-ianbarton"
:base-directory
"~/Documents/emacs/web_sites/ianbarton/org/_posts"
:base-extension "org"
:publishing-directory
"~/Documents/emacs/web_sites/ianbart
Hello Ian,
On Sun, Mar 31, 2013 at 10:43:21AM +0100, Ian Barton wrote:
>
> However, all files are published with an .html extension. My Emacs customize
> interface claims that org-export-html-extension doesn't exist. Grepping the
> source for org-export-html-extension doesn't find anything. So ha
On Sat, Mar 30, 2013 at 06:43:30PM -0600, Eric Schulte wrote:
> Rick Frankel writes:
> > *Note* =wrap= and =raw= give same results
> > #+begin_src perl :results raw
> > q[|c1|c2|
> > |-
> > |a|1|
> > |b|2|];
> > #+end_src
> >
> > #+results:
> > | | c1 | c2 |
> > | | - ||
> > |
Hi List,
'outline-promotion-headings' is a variable defined in Carsten Dominik's
'outline-magic.el' library (and is thus part of my 'outshine.el' which
merges 'outline-magic').
When I wrote 'navi-mode.el' (see https://github.com/tj64/navi and
http://orgmode.org/worg/org-tutorials/index.html) I
Rick Frankel writes:
> On Sat, Mar 30, 2013 at 06:43:30PM -0600, Eric Schulte wrote:
>> Rick Frankel writes:
>
>> > *Note* =wrap= and =raw= give same results
>> > #+begin_src perl :results raw
>> > q[|c1|c2|
>> > |-
>> > |a|1|
>> > |b|2|];
>> > #+end_src
>> >
>> > #+results:
>> > | | c
On 31/03/13 11:01, Suvayu Ali wrote:
Hello Ian,
On Sun, Mar 31, 2013 at 10:43:21AM +0100, Ian Barton wrote:
However, all files are published with an .html extension. My Emacs customize
interface claims that org-export-html-extension doesn't exist. Grepping the
source for org-export-html-extens
Hi Guys,
long time ago, but I tried again to go into taskjuggling with
org-mode.
I still feel the lack of the support for all tj properties a
major drawback.
@Christian: Did you work on something like the prefix proposal below?
This would be real cool as we could then just use any property we wo
On Sun, Mar 31, 2013 at 9:01 AM, Thorsten Jolitz wrote:
>
> 'outline-promotion-headings' is a variable defined in Carsten Dominik's
> 'outline-magic.el' library (and is thus part of my 'outshine.el' which
> merges 'outline-magic').
>
> When I wrote 'navi-mode.el' (see https://github.com/tj64/navi
Hi,
org-html-publish-to-html is defined in ox-html.el and looks like this
(sans doc):
(defun org-html-publish-to-html (plist filename pub-dir)
(org-publish-org-to 'html filename ".html" plist pub-dir))
You could define your own publishing function, e.g.
(defun my-org-html-publish-to-htm
Nick Dokos writes:
> On Sun, Mar 31, 2013 at 9:01 AM, Thorsten Jolitz wrote:
>
>
> 'outline-promotion-headings' is a variable defined in Carsten Dominik's
> 'outline-magic.el' library (and is thus part of my 'outshine.el' which
> merges 'outline-magic').
>
> When I wrote 'na
G'day,
Some time back there was mention of converting Local footnoted (defined
at end of outline node) to inline footnotes and vice-versa.
Is there a way to do this? Or has anyone defined private functions to do
it?
Local footnotes are easier to read, but inline notes a easier to cut and
paste.
On Fri, Mar 22, 2013 at 10:40 AM, Yagnesh Raghava Yakkala
wrote:
>
> On Mar 22 2013, Yann Hodique wrote:
>
> > If so, it might be worth waiting for me to fix it (I'm afraid it's not
> > there simply because I didn't need it :)). It would be sad to limit
> > yourself just because of that. Assuming
org-html-publish-to-html is defined in ox-html.el and looks like this
(sans doc):
(defun org-html-publish-to-html (plist filename pub-dir)
(org-publish-org-to 'html filename ".html" plist pub-dir))
You could define your own publishing function, e.g.
(defun my-org-html-publish-to-ht
Hi Nicolas and others,
I think I found an outdated statement on backend variable names in the
commentary section in ox.el. I have attached a patch correcting it.
Needless to say, ignore this if I'm mistaken.
Cheers,
--
Suvayu
Open source is the future. It sets us free.
>From ef8a9c484f21f8a43
On Fri, Mar 29, 2013 at 4:58 PM, Andreas Röhler <
andreas.roeh...@easy-emacs.de> wrote:
> Am 29.03.2013 21:10, schrieb Gary Oberbrunner:
>
> On Fri, Mar 29, 2013 at 11:29 AM, Andreas Röhler <
>> andreas.roeh...@easy-emacs.de> wrote:
>>
>> IMO org-babel should be able to run source code as is.
>>
Hello,
Suvayu Ali writes:
> I think I found an outdated statement on backend variable names in the
> commentary section in ox.el. I have attached a patch correcting it.
> Needless to say, ignore this if I'm mistaken.
The statement is correct. The hierarchy is, for example:
Org > Org Export
Hi Nicolas,
2013ko martxoak 21an, Nicolas Goaziou-ek idatzi zuen:
> Aaron Ecay writes:
>
>> I have noticed a difficulty with :results table drawer babel blocks. It
>> isn’t possible to put ATTR_LATEX keywords on the table in that case. If
>> they are placed outside of the drawer, they apply to
On Sun, Mar 31, 2013 at 7:04 PM, John Hendy wrote:
> I seem to be having trouble getting custom task_id values used for my
> taskjuggler file. From ox-taskjuggler.el:
>
> #+begin_quote
> (defun org-taskjuggler--build-task (task info)
> "Return a task declaration.
>
> TASK is a headline. INFO is
[I can never get the reply-all thing down on this list! See below.]
On Sun, Mar 31, 2013 at 7:02 PM, John Hendy wrote:
> On Sun, Mar 31, 2013 at 11:03 AM, Gary Oberbrunner
> wrote:
> >
> > On Fri, Mar 29, 2013 at 4:53 PM, John Hendy wrote:
> >>
> >> On Fri, Mar 29, 2013 at 3:16 PM, Gary Oberb
I seem to be having trouble getting custom task_id values used for my
taskjuggler file. From ox-taskjuggler.el:
#+begin_quote
(defun org-taskjuggler--build-task (task info)
"Return a task declaration.
TASK is a headline. INFO is a plist used as a communication
channel.
All valid attributes fr
On Sun, Mar 31, 2013 at 7:16 PM, John Hendy wrote:
> On Sun, Mar 31, 2013 at 7:04 PM, John Hendy wrote:
>> I seem to be having trouble getting custom task_id values used for my
>> taskjuggler file. From ox-taskjuggler.el:
>>
>> #+begin_quote
>> (defun org-taskjuggler--build-task (task info)
>>
Hi,
I've been wanting to add the ability to post-process the results of a
code block for some time, and some recent threads (e.g., [1] and [2])
could both have benefited from post-processing of code block output.
The attached patch [3] adds a new :post header argument, which may be
used to specif
* lisp/ox-latex.el:
(org-latex-plain-text): Properly escape ~ for LaTeX export
In LaTeX, \~ gives a tilde diacritic (as in ã). \textasciitilde{} is
the correct escape for a tilde.
---
lisp/ox-latex.el | 8 ++--
1 file changed, 6 insertions(+), 2 deletions(-)
diff --git a/lisp/ox-latex.el b/
* contrib/lisp/org-bibtex-extras.el: convert to using cl-lib functions
(obe-bibtex-file),
(obe-html-link-base): add a 'group argument to defcustoms
(obe-citations): replace non-existent org-babel-clean-text-properties
with org-no-properties
* contrib/lisp/org-git-link.el: add an eval-and-co
This patch series is an attempt to add synctex support to org mode.
With synctex, you can click on a spot in a document in a PDF viewer,
and have emacs jump to the line of code that generated that part of
the pdf. (See http://emacswiki.org/emacs/AUCTeX for tips on getting
synctex set up with emacs
* lisp/ox-latex.el (org-latex-patch-synctex): New function
(org-latex-export-to-pdf): Call it, if appropriate
This teaches the latex backend how to patch synctex files. The patch
will be done automatically if exporting directly to pdf. If not, the
user must call the org-latex-patch-synctex funct
* lisp/org-element.el: Add :begin-line and :end-line to parser results
These properties give the line on which an element begins/ends
---
lisp/org-element.el | 120
1 file changed, 120 insertions(+)
diff --git a/lisp/org-element.el b/lisp/org-
* lisp/ox.el (org-export-concordance): New buffer-local variable
(org-export-with-concordance): New user option
(org-export--concordance-propertize),
(org-export--concordance-propertize-pre),
(org-export--build-concordance),
(org-export--read-concordance): New functions
(org-export-data): Call org-
Back in the day, when I C-x C-e to export from an org file, I could tap
a key and put all the control factors into the top of the file.
Now I don't see that option when I do this.
Are they gone? Or is it still possible to do this?
Dave
In order to better describe the problem I see, I set up a simple example
file:
* H 1
SCHEDULED: <2013-03-31 Sun>
** H 1a
SCHEDULED: <2013-03-31 Sun>
** H 1b
*** H 1b1
SCHEDULED: <2013-03-31 Sun>
H 1b1a
SCHEDULED: <2013-03-31 Sun>
** H 1b1a1
SCHEDULED: <2013-03-31 Sun>
On Sat, Mar 30, 2013 at 8:45 AM, Bastien wrote:
> Hi John,
>
> thanks for the great work so far! This is of huge help.
No problem -- In the absence of lisp ability... the least I can do, in fact.
>
> John Hendy writes:
>
>> My thinking on this is that Org-8.0 is a significant step, however it
Found the problem. Some color themes boldface the 3rd and 4th heading
levels and that causes the minibuffer to jump to 2 lines. No more
themes, no more jumping.
-ED-
Hi Eric,
2013ko martxoak 23an, Eric Schulte-ek idatzi zuen:
> Unless you actually try :var and find it lacking in some way, I'd prefer
> to stick with simply using :var to identify dependencies between code
> blocks. We've seen in other places how providing multiple alias for
> header arguments
Hi Eric
2013ko martxoak 31an, Eric Schulte-ek idatzi zuen:
>
> Hi,
>
> I've been wanting to add the ability to post-process the results of a
> code block for some time, and some recent threads (e.g., [1] and [2])
> could both have benefited from post-processing of code block output.
This looks
Here are several patches to fix things in and around org-babel.
They're each independent of the others (and hopefully all apply
cleanly, without depending on other members of the series). Here's a
little summary of each:
Aaron Ecay (10):
Fix org-babel-R-initiate-session
-> An obvious bugfix
* lisp/ob-R.el (org-babel-R-initiate-session): handle case where the
session buffer exists, but does not have a live process
If the session buffer exists, but the user has exited the R process
manually, then the (R) command will create a new buffer, then try to
rename it over the old buffer, cau
* lisp/ob-core.el (org-babel-do-key-sequence-in-edit-buffer),
(org-babel-expand-noweb-references),
* lisp/ob-tangle.el (org-babel-tangle):
Use 'light argument to `org-babel-get-src-block-info'.
---
lisp/ob-core.el | 4 ++--
lisp/ob-tangle.el | 2 +-
2 files changed, 3 insertions(+), 3 deletions(
* lisp/ob-core.el (org-babel-load-in-session),
(org-babel-initiate-session),
(org-babel-switch-to-session)
(org-babel-switch-to-session-with-code): Remove info optional arg
The info arg is threaded through this code, but never used by
callers (at least in org code).
---
lisp/ob-core.el | 17
* lisp/ob-core.el (org-babel-if-in-src-block): New macro
(org-babel-execute-src-block-maybe),
(org-babel-expand-src-block-maybe),
(org-babel-load-in-session-maybe),
(org-babel-pop-to-session-maybe): Use it
org-babel-get-src-block-info is a potentially expensive operation, which
is why its ‘light’
* lisp/ob-awk.el (org-babel-expand-body:awk),
lisp/ob-picolisp.el (org-babel-expand-body:picolisp): remove optional
arg from these functions
The optional argument is apparently never passed by org-babel code.
Maybe this is a relic of an earlier calling convention?
---
lisp/ob-awk.el | 2
* lisp/ob-core.el (org-babel-execute-src-block): Simplify control flow
Avoid potential duplication of org-babel-process-params call. Also
makes the code simpler.
---
lisp/ob-core.el | 15 ++-
1 file changed, 6 insertions(+), 9 deletions(-)
diff --git a/lisp/ob-core.el b/lisp/ob-core
* testing/lisp/test-ob-emacs-lisp.el: Move stray test inside ert-deftest
---
testing/lisp/test-ob-emacs-lisp.el | 19 +++
1 file changed, 11 insertions(+), 8 deletions(-)
diff --git a/testing/lisp/test-ob-emacs-lisp.el
b/testing/lisp/test-ob-emacs-lisp.el
index 94092e4..d03f048 1
* lisp/org.el (org-edit-special): Use prefix arg, as docstring says we
do
Only makes a difference for src-block editing.
---
lisp/org.el | 7 ---
1 file changed, 4 insertions(+), 3 deletions(-)
diff --git a/lisp/org.el b/lisp/org.el
index 04ce386..1edfbc4 100644
--- a/lisp/org.el
+++ b/lis
* lisp/ob-core.el (org-babel-check-confirm-evaluate): remove
(org-babel-check-evaluate),
(org-babel-confirm-evaluate): move logic here
This macro is used in only two places, and has two almost-independent
complex logics coded into it. So, suppress the macro and move the logic
into the respect
* doc/org.texi: Document how :var introduces code block dependencies.
---
doc/org.texi | 9 +
1 file changed, 9 insertions(+)
diff --git a/doc/org.texi b/doc/org.texi
index 6791570..dda922e 100644
--- a/doc/org.texi
+++ b/doc/org.texi
@@ -13211,6 +13211,15 @@ include anything in the Org m
* lisp/ob-exp.el (org-export-babel-evaluate): Update defcustom to
provide 'inline-only option
(org-babel-exp-results): Implement 'inline-only for
org-export-babel-evaluate
This is useful because there is no way for inline results to be stored.
The imagined usecase is that all non-inline sour
46 matches
Mail list logo
