I think that a solution more integrated with the rest of Org-mode's
property handling would be preferable. That is to say, there should be
a way to collect multiple value for a property in Org-mode, and Babel
should simply make use of the more general facility.
This doesn't exist yet, but I'd rat
Hi Christian,
I took a look at these functions, while they do seem to work they don't
provide for any inheritance from higher-level subtrees. I think this is
a deal-breaker for use resolving header arguments as inheritance is
generally more useful than multiple values.
Thanks for pointing these
I just checked with make targets and the Makefile has no rule to show
available targets. Such a rule would give builders a clue as to what
additional possibilities exist with the Makefile if it existed.
On Thu, 23 Jun 2011, Jude DaShiell wrote:
> Okay, I found the typing error I was making. I
Okay, I found the typing error I was making. I used make info but
neglected to use make install-info. So info was being made but not
installed. As soon as I used make install-info, and then ran info org
came up as version 7.5 on an info org command. I've done a few makes
already before I ev
Nick Dokos wrote:
> I got tired of dealing with info setup in .emacs and have resorted to
> setting the following env variable in my .profile:
> INFOPATH=
> /home/nick/src/emacs/org/org-mode/doc:/usr/local/info:/usr/local/share/info:/usr/info:/usr/share/info
If you see the texinfo docs
http://www
This is slackware 13.0 and another disk has debian squeeze on it and
both exhibit identical behavior. What I did was to edit the makefile
and change prefix from /usr/local to /usr but there was no immediate
change after build and install. It could be though there will be by
tomorrow morning s
Eric S Fraga writes:
>> I see no difference between the paragraph and the list item: in both
>> cases, the table doesn't appear, as it has been moved right after the
>> headline by `org-export-blocks-preprocess' during export.
>>
>> Are we observing the same phenomenon?
>
> No, I don't believe so
Ian Barton writes:
[...]
> A more subtle approach would be to edit the Makefile to put the info
> file in the right place. However, on Ubuntu it's not all clear where
> this should be.
Interesting,
,[ (info "(org)Installation") ]
| Check your system documentation to find out which of the fo
Nicolas Goaziou writes:
> Hello,
>
> Eric S Fraga writes:
>
>> For completeness, I've attached a file which shows that it *can* work
>> but also that it confuses the export of lists (Nicolas?) if the inline
>> code is in a list item.
>
> I see no difference between the paragraph and the list ite
PATCH-1/5 for org-odt compatibility
>From 06379ccef996e8dabd8dcced6cbe430aacdef3f0 Mon Sep 17 00:00:00 2001
From: Jambunathan K
Date: Thu, 23 Jun 2011 01:53:37 +0530
Subject: [PATCH 1/5] org-export: Reserve a slot for OpenDocumentExporter.
* lisp/org-exp.el (org-export): Reserve keys 'o' and
Cool! Thanks.
Yours,
Christian
On 6/23/11 2:56 PM, Eric S Fraga wrote:
Memnon Anon writes:
(...)
C-c C-l C-a C-k C-g
Memnon
And if you do this, saving it as a kmacro, you can generate code that
does this:
#+begin_src emacs-lisp
(fset 'getlink
(lambda (&optional arg)
"Key
PATCH-4/5 org-odt compatibility patch
Addtional Note: Diff looks primarily because of
un-indentation. Effective changes are just couple of lines.
>From 923402f12f30a39d54e16c0b105db2b1f20c2a7c Mon Sep 17 00:00:00 2001
From: Jambunathan K
Date: Thu, 23 Jun 2011 12:06:33 +0530
Subject: [PATCH 4/5
Jude DaShiell wrote:
> Once git pull has been run and the build of org and documentation have
> been done and installed, should info org provide the org version of 6.33x?
> Also, orgguide doesn't get added to my info files is it supposed to be
> held separate for some reason? orgguide has ve
PATCH-3/5 org-odt compatibility patch
>From a7881b8d146ddb27452b00ff19c345899d356536 Mon Sep 17 00:00:00 2001
From: Jambunathan K
Date: Thu, 23 Jun 2011 11:24:32 +0530
Subject: [PATCH 3/5] Support custom formatters for marking up source or example blocks.
* lisp/org-exp.el (org-export-format-so
PATCH-2/5: org-odt compatibility
>From 2bc4854fb86a96b69e53db00603e0b2f8f47fe08 Mon Sep 17 00:00:00 2001
From: Jambunathan K
Date: Thu, 23 Jun 2011 02:16:30 +0530
Subject: [PATCH 2/5] org-exp.el: Allow easy plugging in of new backends.
* lisp/org-exp.el (org-export-backends): New variable.
(org
On Thu, Jun 23, 2011 at 10:47 AM, Nick Dokos wrote:
> Rustom Mody wrote:
>
>> Ive just found that org is capitalizing my titles in html export. [I
>> had not noticed this earlier]
>> I would like to capitalize my titles slightly differently: for example
>> propositions like 'to' 'with' etc I woul
I have been following this thread with interest. When I export Eric's
babelcall.org, the result of the octave calculation is =nil= in both cases.
Is this the expected behaviour? I can confirm Nicolas' observations as well.
Chris
On Jun 23, 2011 9:49am, Nicolas Goaziou wrote:
Hello,
Eri
PATCH-5/5 org-odt compatibility patch
>From 22c4feee78ff9a1ab7cc48275ec29d322a3472a1 Mon Sep 17 00:00:00 2001
From: Jambunathan K
Date: Thu, 23 Jun 2011 13:17:18 +0530
Subject: [PATCH 5/5] Control insertion point for footnote definitions during pre-process.
* lisp/org-footnote.el
(org-footnote-
I am following up this mail with 5 patches. These are small patches that
would help me float org-odt tarball with minimum of hassle (to the
users).
The new capabilities introduced are strictly for consumption by
org-odt. Wrt master branch, these changes should essentially be NOOPs.
I would appr
On Thu, Jun 23, 2011 at 7:42 AM, Ian Barton wrote:
> A more subtle approach would be to edit the Makefile to put the info file in
> the right place. However, on Ubuntu it's not all clear where this should be.
Or something like this in the emacs init file:
;; Info directory
(add-to-list 'Info-def
On 6/23/11 2:17 PM, Memnon Anon wrote:
(defun my-extract-link ()
"Extract the link location at point and put it on the killring."
(interactive)
(when (org-in-regexp org-bracket-link-regexp 1)
(kill-new (org-link-unescape (org-match-string-no-properties 1)
Thanks, that seems to
Hello,
Eric S Fraga writes:
> I've gone through my whole config and have tracked down the problem:
>
> : (setq org-src-preserve-indentation t)
Nice. It helps a lot.
> if I have this line present, the latex export doesn't work; if I remove
> this line, the export works as it should. This would
Hello,
Eric S Fraga writes:
> For completeness, I've attached a file which shows that it *can* work
> but also that it confuses the export of lists (Nicolas?) if the inline
> code is in a list item.
I see no difference between the paragraph and the list item: in both
cases, the table doesn't ap
On 23/06/11 10:54, Jude DaShiell wrote:
Once git pull has been run and the build of org and documentation have
been done and installed, should info org provide the org version of 6.33x?
Also, orgguide doesn't get added to my info files is it supposed to be
held separate for some reason? orgguide
Memnon Anon writes:
> Christian Moe writes:
>
>>> Does anyone know a way to copy a link at point with fewer keystrokes than
>>>
>>> C-c C-l to edit the link
>>> C-a C-k C-y to go to the beginning of the link line, kill and re-yank
>>> the link
>>> to finish editing the link without changing an
Hi,
I use booktabs from library of babel for LaTeX export.
I want to export an booktab-org-table as an actual latex-table (i.e. not
tabular only).
An example follows. The question is how to make #+call be recognized
and treated as a 'first-class' table. (I could do it in LaTeX manner,
but I am
On 06/22/2011 10:35 PM, Rustom Mody wrote:
Ive just found that org is capitalizing my titles in html export. [I
had not noticed this earlier]
I would like to capitalize my titles slightly differently: for example
propositions like 'to' 'with' etc I would like to leave as lowercase.
Is it possibl
Christian Moe writes:
> That wasn't clear -- I meant to copy the URL part (link type and path)
> of the link (not the description part).
Does this work?
I did only some quick testing, this is "C-c C-l" cut down
for this purpose only.
--8<---cut here---start-
Christian Moe writes:
>> Does anyone know a way to copy a link at point with fewer keystrokes than
>>
>> C-c C-l to edit the link
>> C-a C-k C-y to go to the beginning of the link line, kill and re-yank
>> the link
>> to finish editing the link without changing anything
What about:
C-c C-l C
> Hello
>
> I want a simple function which allows me to insert a new row
> before I wrap a region. (Because otherwise rows which
> already contain information get disordered.)
>
> Like
>
> (defun my-org-wrap-cell ()
> (interactive)
> (save-excursion
> (progn
> (org-table-insert-ro
That wasn't clear -- I meant to copy the URL part (link type and path)
of the link (not the description part).
CM
On 6/23/11 11:31 AM, Christian Moe wrote:
Hi,
Does anyone know a way to copy a link at point with fewer keystrokes than
C-c C-l to edit the link
C-a C-k C-y to go to the beginni
Once git pull has been run and the build of org and documentation have
been done and installed, should info org provide the org version of 6.33x?
Also, orgguide doesn't get added to my info files is it supposed to be
held separate for some reason? orgguide has version of 7.50 on it and I
expe
Hello
I want a simple function which allows me to insert a new row
before I wrap a region. (Because otherwise rows which
already contain information get disordered.)
Like
(defun my-org-wrap-cell ()
(interactive)
(save-excursion
(progn
(org-table-insert-row 1)
(org
Hi,
Does anyone know a way to copy a link at point with fewer keystrokes than
C-c C-l to edit the link
C-a C-k C-y to go to the beginning of the link line, kill and re-yank
the link
to finish editing the link without changing anything
?
Yours,
Christian
+1 for inline calls. No hurry, though.
Yours,
Christian
On 6/23/11 7:32 AM, Eric Schulte wrote:
Eric S Fraga writes:
Eric Schulte writes:
Hi Eric,
Hi Eric! ;-)
So the problem is that the results are inserted as a separate block,
when you want them to be inserted inline? If so perhap
Eric Schulte writes:
[...]
>> Yes and no. I *do* want the effect that is achieved by using an inline
>> block but I do *not* want to write the whole block inline
>
> I find the following pattern
>
> #+source: big-block
> #+begin_src emacs-lisp :exports none
> "something complex"
> #+e
36 matches
Mail list logo
