Marcelo de Moraes Serpa celose...@gmail.com writes:
Another thing: I'm considering setting the commit cron job to every
hour. So, every hour I would have a fresh copy of org pushed to my
dropbox volume.
I forgot to share the commit.sh (I don't usually program in bash, so
bear with me :)):
Hi Jambunathan,
Jambunathan K kjambunat...@gmail.com writes:
[...]
I am not sure if (and when) my changes would get formally integrated.
I can commit non-trivial effort cycles for bug fixing integration for
maybe next 3 weeks. Further down the road, as a maintainer of
org-odt.el, I am
Matt Lundin m...@imapmail.org writes:
Hi Jambunathan,
Jambunathan K kjambunat...@gmail.com writes:
[...]
I am not sure if (and when) my changes would get formally integrated.
I can commit non-trivial effort cycles for bug fixing integration for
maybe next 3 weeks. Further down the
On 30.4.2011, at 21:45, Eric S Fraga wrote:
Eric S Fraga e.fr...@ucl.ac.uk writes:
[...]
The problem with the multiple overlays that were created
during native fontification is now fixed. I would be interested
to know if this improves the situation.
- Carsten
Thanks. I've
From: Robert P. Goldman rpgold...@real-time.com
---
The previous patch wasn't quite right because, e.g., it would index
#+INDEX: =Class=
as
\\index{=Class=}
instead of
\\index{\texttt{Class}}
This patch attempts to fix that.
Question: would you prefer to have this reformulated as some kind of
On 4/30/11 Apr 30 -5:14 PM, Eric S Fraga wrote:
Robert Goldman rpgold...@sift.info writes:
On 4/29/11 Apr 29 -1:21 PM, Nick Dokos wrote:
[...]
amsmath conflicts with wasysym (redefines \iint), so you have to
redefine your headers to omit wasysym or include amsmath *first*: for
some
On 4/29/11 Apr 29 -4:07 PM, Robert Goldman wrote:
I have this header in my org-mode file:
Documentation documentationPseudoProp
it gets translated into the following, which formats poorly:
\item Documentation \label{documentationPseudoProp}documentationPseudoProp\\
Any idea why
On Sat, Apr 30, 2011 at 11:13 PM, Ben Finney Those aren't even
“smart quotes” (the term usually applied to the quote
characters from Microsoft's standards-violating character set). Those
are what might be called “TeX quotes” (though the convention pre-dates
even TeX), since TeX uses ‘`’ for an
Avdi Grimm gro...@inbox.avdi.org wrote:
So I'm writing an eBook with lots of source code listings, using
org-mode-LaTeX-PDF with the minted package providing source code
highlighting. For the most part I'm really, really happy with the
toolchain; thank you to those that pointed me in the
Ben Finney ben+em...@benfinney.id.au wrote:
Avdi Grimm gro...@inbox.avdi.org writes:
...
...
Nowadays with Unicode available ubiquitously we can simply use the
correct typographical quotation marks directly in the plain text file,
but TeX and some other legacy systems don't work very
Bernt,
That's amazing!
Much more complex, and I really liked the idea of tracking every
directory that has important files (including configuration files).
Thank you for sharing.
As for deleting files, I just rm -rf when I need to, so the next
commit -a will catch it.
But yours is definitely a
Hi Nick,
Nick Dokos wrote:
Ben Finney ben+em...@benfinney.id.au wrote:
Avdi Grimm gro...@inbox.avdi.org writes:
Nowadays with Unicode available ubiquitously we can simply use the
correct typographical quotation marks directly in the plain text file,
but TeX and some other legacy systems
Hi -
I'm wondering if there's a way to treat a heading more like a block, such that
it has begin/end markers that explicitly mark its boundaries.
What I frequently find happening is that while I'm editing a heading, I have a
need for a subtopic. Easy: C-RET, Tab. Now I want to keep editing at
* lisp/org-bibtex.el (org-bibtex-tags): New variable
(org-bibtex-tags-are-keywords): New variable
(org-bibtex-no-export-tags): New variable
(org-bibtex-headline): Export tags as comma-separated bibtex keywords
(org-bibtex-read): Import bibtex keywords field as tags
Bibtex users often
* lisp/org-bibtex.el (org-bibtex-key-property): When storing key in
ID, warn if a duplicate ID is generated.
---
lisp/org-bibtex.el | 18 +-
1 files changed, 13 insertions(+), 5 deletions(-)
diff --git a/lisp/org-bibtex.el b/lisp/org-bibtex.el
index f54a6bf..cf7fc49 100644
* lisp/org-bibtex.el (org-bibtex-headline): Don't export TYPE property
as field
---
lisp/org-bibtex.el | 12 +++-
1 files changed, 7 insertions(+), 5 deletions(-)
diff --git a/lisp/org-bibtex.el b/lisp/org-bibtex.el
index cf7fc49..513519b 100644
--- a/lisp/org-bibtex.el
+++
* lisp/org-bibtex.el: (org-bibtex-search): New function.
(org-bibtex-export-to-kill-ring): New function. Export to kill ring.
(org-bibtex-create-in-current-entry): New function
(org-bibtex-create): Make it easier to add bib fields to an
existing headline
The subject should be patch 3/4 - sorry.
Matt Lundin m...@imapmail.org writes:
* lisp/org-bibtex.el (org-bibtex-headline): Don't export TYPE property
as field
---
lisp/org-bibtex.el | 12 +++-
1 files changed, 7 insertions(+), 5 deletions(-)
diff --git a/lisp/org-bibtex.el
Nick Dokos nicholas.do...@hp.com writes:
Ben Finney ben+em...@benfinney.id.au wrote:
TeX and some other legacy systems don't work very well with Unicode.
AFAIK, TeX works fine with UTF8, given the defaults that org-mode
export uses.
To be clear, I don't have any issue with Org and Unicode
I'm having exactly this same problem.
I have a file, suggestions.org, in directory ~/x/y/z/top/child/ that
contains many images. These are included by means of links such as
[[./foo.pdf]]
Now, I have a parent file in top/, manual.org, and I want to #+include
child/suggestions.org
Here's the problem: when org-babel goes to look for parameters when executing
a source block, it looks for them in the parent source file, and not in the
parent source file with the included materials. Here is the function that goes
awry:
(defmacro org-babel-exp-in-export-file (lang rest
Robert Goldman rpgold...@sift.info wrote:
foo.org:
* Purpose
This document is intended to demonstrate that src buffer evaluation in
subsidiary, included files, does not work.
* Demo
#+include ~/src/org-test/bar.org
bar.org:
* Here's the demo
#+begin_src sh :exports results
Sorry, I think I have created a red herring here by leaving that code block in
both files. To see what the problem really is, consider the case where the
source code block appears ONLY in the included file.
(I tested the source block in the master file to make sure it worked before I
copied it
Also note that if you have an included file with MULTIPLE code blocks, this
approach won't generalize
Best,
--
Sent from my Android phone with K-9 Mail. Please excuse my brevity.
Nick Dokos nicholas.do...@hp.com wrote:
Robert Goldman rpgold...@sift.info wrote: foo.org: * Purpose This
Aloha all,
Org-bibtex is working out nicely. The crossref field was defined in
org-bibtex, but not used.
The attached patches add the crossref field to reference types that
might use it.
All the best,
Tom
0002-lisp-org-bibtex.el-Added-crossref-field-to-other-fie.patch
Description:
Looking over this some more, I see that the challenge is to:
1. read the file parameters (whatever they are) from the original file
(hence opening the file from the link) and
2. read the header parameters from the export buffer, since the header
may not actually be contained in the original
I was hit by this last week when I was investigating why my emacs
initialization was taking so long. Later I found out that org-crypt was the
culprit, since it added a sit for 5s in order for the user to actually
see this warning.
The problem is that org-crypt tests the value of the
Robert P. Goldman rpgold...@sift.info wrote:
Sorry, I think I have created a red herring here by leaving that code blo=
ck in both files. To see what the problem really is, consider the case wh=
ere the source code block appears ONLY in the included file.
(I tested the source block in the
Yes. That's right, the single source block was a simplification for the
example. It was abstracted from a more complicated case with a dozen or so
source blocks in the subordinate filter. But thanks for the suggestion.
Hope we can find a fix!
Best
R
--
Sent from my Android phone with K-9
29 matches
Mail list logo
