Hi Jonathan,
Jonathan Leech-Pepin writes:
> The following sample org file does not export as possibly expected.
>
> ,---
> | #+TITLE: Bug?
> | #+OPTIONS: *:nil toc:nil author:nil
> |
> | - hello (*) I would like to have two items
> | - may (*) I please?
>
Hi François,
pin...@iro.umontreal.ca (François Pinard) writes:
> Given this Org fragment:
>
> * Essai
> - Le
> - petit :: chaperon
> - rouge
>
> with the cursor on the "L", command `C-u C-c C-c' yields:
>
> * Essai
> - [ ] Le
> - petit :: chaperon
> - [ ] rouge
>
> while I was expecting:
>
> * Es
Hi, Org people.
Given this Org fragment:
--8<---cut here---start->8---
* Essai
- Le
- petit :: chaperon
- rouge
--8<---cut here---end--->8---
with the cursor on the "L", command `C-u C-c C-c' yields:
--8<---cut
since a url uses the forward slash as do italicized items, i'm having
difficulty italicizing urls on the html export.
/just [[http://gohere.com][go here]] will you?/
shows up as
/just go here will you?/
on the html export (though the go here link is valid) with nothing
italicized and the forwar
Thanks Martyn,
that was a big help.
aaron.
On 27 January 2012 14:04, Martyn Jago wrote:
> Martyn Jago writes:
>
> > Hi Aaron
> >
> > aaron barclay writes:
> >
> >> Hi,
> >>
> >> I am having trouble finding the correct way to export a document without
> >> the code blocks included. Should I
Hi Dov,
Dov Grobgeld wrote:
> A solution would be that all org-mode faces would inherit a common
> org-mode-face. You could then customize this font to a variable-pitch
> without using the ~variable-pitch-mode~ command. Is this feasible?
There is `org-default', but I don't know if it solves your
Hi all,
I've written an iCalendar import script in ruby (I know, not emacs lisp,
but at the least I should let you be aware).
I think it's an improvement over the awk script, so you may consider
mentioning it in the appropriate places. See
https://github.com/simonthum/ical2org
It has more
The following question came up on Stack Overflow:
http://stackoverflow.com/questions/9051330/possible-bug-in-org-mode-export-of-item-with
The following sample org file does not export as possibly expected.
,---
| #+TITLE: Bug?
| #+OPTIONS: *:nil toc:nil aut
Uwe Brauer wrote:
> >> On Sat, 28 Jan 2012 19:13:57 -0500, Nick Dokos
> >> wrote:
>
>>>
>
>> ... and bonus points if you also fix the problems described in
>
> Now I am confused, from the link, you provided, I conclude
> you are talking about GNU Emacs, however I only wanted my chan
>> On Sat, 28 Jan 2012 19:13:57 -0500, Nick Dokos
>> wrote:
>>
> ... and bonus points if you also fix the problems described in
Now I am confused, from the link, you provided, I conclude
you are talking about GNU Emacs, however I only wanted my changes to
work with Xemacs and therefore
Am 29.01.2012 11:42, schrieb Andreas Leha:
:colnames yes
Hi Andreas,
Thanx, that is definitely a solution !
And I agree with you, that its a bit puzzling, that both cases behave
differently;
the #+call-line should just have the same result as the #+begin_src-line, to
which after all
it just
Marc-Oliver Ihm writes:
> Hello !
>
> Generally enjoying babel very much, I have stumbled across a behaviour, that
> I do not quite understand:
> As it seems, a #+call in babel removes hlines from the results.
>
> Here is an example:
>
> #+call: foo()
> | 3 | 4 |
> #+name: foo
> #+begin_src emac
Bastien writes:
> thanks for this patch -- it on my radar now, along with these
> other changes that I want to incorporate before the new release:
>
> - Patch by Niels to customize output table in LaTeX, combined
> with the patch of Christophe Rhodes. (Carsten, are you still
> on it or can
Hi Andrew,
Andrew Hyatt writes:
> I've fixed all the reported issues, and am attaching the modified
> patch. I'd love for this to get into the next release. If anyone has
> a desire to try this out, I'd love to hear if it is clear how to use
> it, and if you encounter any issues.
thanks for th
Achim Gratz writes:
> Bastien writes:
>> This is quite a hypothetical case: the default value for `org-drawers'
>> contains drawers that are hardcoded and correspond to key features: I
>> cannot figure out a good reason for *not* having these drawers in the
>> configuration.
>
> As a customized
Hello,
Christian Wittern writes:
> Exactly. The reason for wanting to do this is that the above is my
> setup for translating, but in some cases the publication will have
> only the translation, for such cases, I want to extract just the
> translation. This should then produce a new org file,
On 2012-01-28 22:59, rick frankel wrote:
The dot executable is part of the graphviz package. Installing graphviz should
install the dot command line executable alongw w/ neato, circo and and other
layout engines.
Rick
Thanks to all who pointed this out.
$sudo port install graphviz
did the t
Hello !
Generally enjoying babel very much, I have stumbled across a behaviour, that I
do not quite understand:
As it seems, a #+call in babel removes hlines from the results.
Here is an example:
#+call: foo()
| 3 | 4 |
#+name: foo
#+begin_src emacs-lisp
'((1 2) hline (3 4))
#+end_src
#+resu
Bastien writes:
> This is quite a hypothetical case: the default value for `org-drawers'
> contains drawers that are hardcoded and correspond to key features: I
> cannot figure out a good reason for *not* having these drawers in the
> configuration.
As a customized variable org-drawers can have a
19 matches
Mail list logo
