+1.
I've tested Jambunathan's ODT backend some, and love it. It should
considerably simplify things for those of us who would like to do
nearly everything in Org, but are usually required to submit our work
in MS Word or (with luck) ODT.
People will want to test the all new HTML backend care
> This is a formal request to integrate my org-html.el & org-odt.el
> changes in to the master branch.
>
> This patch introduces 3 major features:
> 1. A generic exporter
> 2. All new html backend re-implemented as a plugin to (1).
> 3. A odt backend as a plugin to (1).
>
> The patch is based on
Michael Hannon wrote:
>
> > From: Nick Dokos
>
>
> [...]
>
> >> Heh. Yes, thanks, Eric. I'm not crazy enough to try to bootstrap my way
> >> through 900+ variables, but that sets the scale of the challenge for me.
> >>
>
> > IIRC, Carsten had run a poll for the nomination of the 50 most-
(Forwarding it - Looks like the original mail didn't make it's way to
the list)
> Hi Neilen,
>
> Neilen Marais wrote:
>> Is it possible to caption a #+begin_src or #+begin_example block? Doing
>>
>> #+CAPTION: dipole_analytical_balanis.mac
>> #+begin_example
>>
>> #+end_example
>>
>> doesn't
Memnon Anon writes:
> Nick Dokos writes:
>
>> IIRC, Carsten had run a poll for the nomination of the 50 most-use{d|ful}
>> variables. The results must be somewhere (Worg? Mailing list?). That
>> would probably serve as a better starting point than a 931-element list
>> with no other indicator of
Nick Dokos writes:
> IIRC, Carsten had run a poll for the nomination of the 50 most-use{d|ful}
> variables. The results must be somewhere (Worg? Mailing list?). That
> would probably serve as a better starting point than a 931-element list
> with no other indicator of importance.
,[http://or
> Hi Michael,
>
> Thank you for your suggestion. However, I would prefer not to clutter
> the text with repeating the protocol there. Also, the example I gave
> is mainly for illustration, in the way I use it, the description would
> not show the filename, but some other text.
>
> Chris
>
> On 2
> From: Nick Dokos
> [...]
> Here is a link to basic customization:
>
> http://orgmode.org/worg/org-configs/org-customization-guide.html
>
> It includes a link to the list of "40 variables that are changed by
> many users".
Very useful. Thanks again, Nick.
-- Mike
I have this header in my org-mode file:
Documentation <>
it gets translated into the following, which formats poorly:
\item Documentation \label{documentationPseudoProp}documentationPseudoProp\\
Any idea why this would happen? Seems like a bona fide bug, but perhaps
I'm just doing somethi
Matt Lundin writes:
> * lisp/org-bibtex.el (org-bibtex-treat-headline-as-title): Fix
> incorrect defcustom type.
> ---
> lisp/org-bibtex.el |2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/lisp/org-bibtex.el b/lisp/org-bibtex.el
> index b3d151c..8070755 100644
> -
* lisp/org-bibtex.el (org-bibtex-treat-headline-as-title): Fix
incorrect defcustom type.
---
lisp/org-bibtex.el |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/lisp/org-bibtex.el b/lisp/org-bibtex.el
index b3d151c..8070755 100644
--- a/lisp/org-bibtex.el
+++ b/lisp/org-
Drat. This patch isn't quite right; it mis-handles typeface
specifications. E.g.
#+index: =Class=
generates an index entry for =Class= instead of an entry for "Class" set
in monospace font.
Maybe someone who understands the intricacies of exporting can figure
out a fix. The problem is likely
* lisp/org-bibtex.el (org-bibtex-treat-headline-as-title): New
variable
(org-bibtex-fleshout): Query for title depending on value of
org-bibtex-treat-headline-as-title
---
Some users might want to modify the headings of their bibtex entries,
adding authors, etc. In this case, the heading shou
* lisp/org-bibtex.el (org-bibtex-headline): When taking title from
headline, grab only the headline text, not metadata.
---
When generating an autokey or exporting to bibtex, the metadata (e.g.,
the TODO keyword) was being included in the title. This patch ensures
that only the headline text is
Hi Michael,
Thank you for your suggestion. However, I would prefer not to clutter the
text with repeating the protocol there. Also, the example I gave is mainly
for illustration, in the way I use it, the description would not show the
filename, but some other text.
Chris
On 2011-04-30 00:
Hello,
After a couple of tests, I've observed that the postamble is forced to be
included *inside* the div "content".
Proof on Line 1764... These are the ending tags of every HTML page:
#+begin_src emacs-lisp
(unless body-only (insert "\n\n\n\n"))
#+end_src
... the closing referring to t
At Fri, 29 Apr 2011 10:56:51 -0400,
Nick Dokos wrote:
> Indeed: it would require a bit of refactoring of Simon's code to provide the
> function(s) to apply to each entry, and changes to the top level functions to
> use the mapping API instead of looping explicitly.
That sounds like a good idea. I
On 4/29/11 Apr 29 -1:21 PM, Nick Dokos wrote:
> Robert Goldman wrote:
>
>> On 4/29/11 Apr 29 -11:44 AM, Thomas S. Dye wrote:
>>> Aloha Robert,
>>>
>>> Yep. It should be "One of these, amssymb, requires amsmath, which
>>> conflicts with several LaTeX fonts."
>>
>> I don't /believe/ amssymb requir
> From: Nick Dokos
[...]
>> Heh. Yes, thanks, Eric. I'm not crazy enough to try to bootstrap my way
>> through 900+ variables, but that sets the scale of the challenge for me.
>>
> IIRC, Carsten had run a poll for the nomination of the 50 most-use{d|ful}
> variables. The results must be so
Michael Hannon wrote:
>
> > From: Eric S Fraga
>
>
> > [...]
>
> >> FWIW, in Emacs I typed:
> >>
> >> C-h v org
> >>
> >> and got no fewer than 931 completions. A lot of knobs to turn!
> >
> > yes, indeed! the info manual is your friend here. it is very difficult
> > to figure out wh
> From: Eric S Fraga
> [...]
>> FWIW, in Emacs I typed:
>>
>> C-h v org
>>
>> and got no fewer than 931 completions. A lot of knobs to turn!
>
> yes, indeed! the info manual is your friend here. it is very difficult
> to figure out what you need to set from just the list of org- variab
On 4/24/2011 1:44 PM, Nicolas Goaziou wrote:
Hello,
amscopub-m...@yahoo.com writes:
#+MACRO: start #+BEGIN_HTML\n \n#+END_HTML
#+MACRO: end #+BEGIN_HTML\n \n#+END_HTML
* Hello world
{{{start}}}
1. Item 1
{{{end}}}
[...]
Anyway, the above code worked fine in 7.4. Then I upgraded to
Robert Goldman wrote:
> On 4/29/11 Apr 29 -11:44 AM, Thomas S. Dye wrote:
> > Aloha Robert,
> >
> > Yep. It should be "One of these, amssymb, requires amsmath, which
> > conflicts with several LaTeX fonts."
>
> I don't /believe/ amssymb requires amsmath. I have been working on a
> document wh
Aloha Robert,
You're right again. Sorry for the noise. The amssymb package is the
source of the font conflicts.
Thanks for pointing this out.
I don't use amsmath, so can't help with your queries. When you've
sorted them out, please consider adding the solution to the LaTeX
export tuto
On 4/29/11 Apr 29 -11:44 AM, Thomas S. Dye wrote:
> Aloha Robert,
>
> Yep. It should be "One of these, amssymb, requires amsmath, which
> conflicts with several LaTeX fonts."
I don't /believe/ amssymb requires amsmath. I have been working on a
document where I wanted to use some of the stuff in
Jason Dunsmore writes:
> I've changed the Worg publishing process so that it always updates the
> version of Org used to publish Worg before publishing. Until we have a
> way to gracefully handle publishing/export errors, this should help
> prevent and troubleshoot the publishing errors that fre
Aloha Robert,
Yep. It should be "One of these, amssymb, requires amsmath, which
conflicts with several LaTeX fonts."
Thanks for pointing this out.
All the best,
Tom
On Apr 29, 2011, at 6:26 AM, Robert Goldman wrote:
The document http://orgmode.org/worg/org-tutorials/org-latex-export.html
The document http://orgmode.org/worg/org-tutorials/org-latex-export.html
claims
"The Org-mode LaTeX exporter uses several packages to support special
characters used by org-entities. One of these, amsmath, conflicts with
several LaTeX fonts. If you want finer control over which packages are
loaded
Hello Worg contributors,
I've changed the Worg publishing process so that it always updates the
version of Org used to publish Worg before publishing. Until we have a
way to gracefully handle publishing/export errors, this should help
prevent and troubleshoot the publishing errors that frequently
For links with a description I always just repeat the protocol tag
there manually:
[[file://path/to/my file][file: myfile]]
[[http://www.example.com/path/to/my file][http: myfile]]
Together with the space after the colon this shows, also immediately,
if you look only at the link description or at
Eric Abrahamsen wrote:
> > The mapping API allows you to walk through the entries, filter the ones
> > you want and apply a function on each remaining entry. So cribbing heavily
> > from Simon's code, the following should count all the entries with tag
> > "foo":
>
> Nice! Seems like the mappi
Hi,
The following patch adds an option to remove extensions of files linked
from the auto generated sitemap. This is useful if you want to follow
this: http://www.w3.org/Provider/Style/URI
>From 32ca3e459e759fbf6312c0154b1f1ba5b2cb7b13 Mon Sep 17 00:00:00 2001
From: Manuel Giraud
Date: Fri, 29
Hi Marcelo,
Marcelo de Moraes Serpa wrote:
> I'd like to know if it's possible to create custom agenda search
> commands that will search only specific files (a subset) from the
> agenda list. It would be nice if we could also override the agenda
> file list and just specify the file(s) in the com
Hi there,
In the archives, I have seen on and off references to a new, extensible
syntax that would go beyond /italic/, *bold* and =code=, but I have seen no
traces of seeing it implemented.
For the time being, therefore I am settling on having different linktypes
coming up in different colors, w
Hello,
Samuel Wales writes:
> Bug 1: commented incomplete footnote interacts with link in
> later text. Result is that comments get exported. IMO
> comments should be absolute except in the case of #+ lines.
>
> # [fn::I will call this the status quo effect for lack of an
> # existing term. I
Hello John,
search for allowframebreak, a LaTeX beamer option. Maybe this will fit your
needs. For org-mode this may be placed in org-beamer-frame-default-options.
However, when it is present, you will not be able to use overlays anymore.
Daniel
Am Mittwoch, 27. April 2011, 11:01:40 schrieb T
36 matches
Mail list logo
