On 4/28/11 10:56 PM, amscopub-m...@yahoo.com wrote:
Is there a way to apply text transformations to arguments in macros?
For example, say that you want to change the first argument to capital letters?
or transpose the letters of the second argument?
How would you do that? I imagine you would
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
Hello,
Samuel Wales samolog...@gmail.com 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
#
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,
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
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
Eric Abrahamsen e...@ericabrahamsen.net 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
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
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
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
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
Jason Dunsmore emacs-orgm...@dunsmor.com 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
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
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
Robert Goldman rpgold...@sift.info 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
On 4/24/2011 1:44 PM, Nicolas Goaziou wrote:
Hello,
amscopub-m...@yahoo.com writes:
#+MACRO: start #+BEGIN_HTML\nmydiv \n#+END_HTML
#+MACRO: end #+BEGIN_HTML\n/mydiv \n#+END_HTML
* Hello world
{{{start}}}
1. Item 1
{{{end}}}
[...]
Anyway, the above code worked fine in 7.4. Then I
From: Eric S Fraga e.fr...@ucl.ac.uk
[...]
FWIW, in Emacs I typed:
C-h v orgTAB
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-
Michael Hannon jm_han...@yahoo.com wrote:
From: Eric S Fraga e.fr...@ucl.ac.uk
[...]
FWIW, in Emacs I typed:
C-h v orgTAB
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
From: Nick Dokos nicholas.do...@hp.com
[...]
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
On 4/29/11 Apr 29 -1:21 PM, Nick Dokos wrote:
Robert Goldman rpgold...@sift.info 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
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
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/div\n/body\n/html\n))
#+end_src
... the closing /div
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
* 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
* 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
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): 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
+++
Matt Lundin m...@imapmail.org 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
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 this would happen? Seems like a bona fide bug, but perhaps
From: Nick Dokos nicholas.do...@hp.com
[...]
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
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
Nick Dokos nicholas.do...@hp.com 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
Memnon Anon gegendosenflei...@googlemail.com writes:
Nick Dokos nicholas.do...@hp.com 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
(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 seem to do the
34 matches
Mail list logo
