Hi,
> It is rather annoying that github understands the org syntax but not
quite, so the sources appear almost but not quite right.
I maintain the parser that is being by Github =>
https://github.com/wallyqs/org-ruby
If you let me now the issues I can try to fix them, (or PRs are also
welcome)
John Peloquin writes:
> Greetings,
>
> I'm trying to define a custom link in org mode with custom export
> formatting, but I get unexpected results when exporting to markdown.
>
>
> Minimal example:
>
> `minimal-init.el`
>
> (add-to-list 'load-path "~/.emacs.d/elpa/org-20140217")
> (require 'org)
By which I mean, the bug should be reproducible if you do so.
On 2/11/14, Samuel Wales wrote:
> Try with:
>
> (setq org-babel-use-quick-and-dirty-noweb-expansion t)
>
> This setting is much, much faster, by the way.
>
> On 2/5/14, Eric Schulte wrote:
>> Samuel Wales writes:
>>
>>> hi eric,
>>
Greetings,
I'm trying to define a custom link in org mode with custom export
formatting, but I get unexpected results when exporting to markdown.
Minimal example:
`minimal-init.el`
(add-to-list 'load-path "~/.emacs.d/elpa/org-20140217")
(require 'org)
(add-to-list 'org-export-backends "md")
I've just solved a puzzle finding out why Python src blocks that exported
happily last year don't now. I'm using them for class tutorials and a of about
fifteen Python fragments, a couple of the blocks would expand in-situ (C-c C-c)
but when exported were treated as normal text.
I narrowed it
Hi Thomas,
I guess the fix hasn't made it to maint yet.
#+call: repeated-text(eg=example) :results raw
#+RESULTS:
1. this is the first line
2. this is the second line with %VARIANT% as the value
3. this is the third line
#+name: repeated-text
#+begin_src sh :results verbatim output :var eg=
Nicolas Goaziou writes:
> Alexis writes:
>
>> However, 'file+emacs:' links still exhibit the incorrect behaviour i
>> described in my original email, and which you experienced also. So it
>> looks like there is indeed a bug here - or, the 'file+emacs:' example
>> should be removed from section
Hi Samuel,
I think not. I get these results now:
#+call: repeated-text(x="foo",eg=example) :results raw
#+results:
1. this is the first line
2. this is the second line with foo as the value
3. this is the third line
All the best,
Tom
Samuel Wales writes:
> hi thomas,
>
> is this still a bug
you can do this with a filter, and conditional handling. I did something
like this at
http://kitchingroup.cheme.cmu.edu/blog/2013/09/28/Changing-links-to-files-so-they-work-in-a-blog/where
file links were handled differently depending on whether the file
link had content or not. you could do someth
Hi all,
there is the nice functionality in docview links, where
[[docview:papers/last.pdf::2]] will open the second page of the given
pdf.
Would it be hard to make [[file:papers/last.pdf::2]] export the second
page of the pdf to latex? I.e. to export to something like
\includegraphics[page=2]{pa
Rainer M Krug writes:
> Hi
>
> I would like to save all in org defined variables into an R data
> file. In general this works fine with the following code block:
>
>
> #+begin_src R :session null :results output
> dir.create("./data/", showWarnings=FALSE)
> save.image("./data/orgData.rda")
> #+en
On Sun, Feb 23, 2014 at 12:23 PM, Simon Thum wrote:
> A small update:
>
> org-export-babel-evaluate does what I need. I'm still a bit confused why it
> asks in this instance and not others, but it works.
That is interesting. I just checked my own config and I just have:
(setq org-confirm-babel-e
Greetings,
I've solved a couple of bugs in the Leanpub[1] markdown exporter[2]
(cross-links within the book using ids were not working, and footnotes
containing a colon neither). As far as I can tell using Orgmode and
Leanpub to publish books is now quite feasible, and produces rather
nice result
A small update:
org-export-babel-evaluate does what I need. I'm still a bit confused why
it asks in this instance and not others, but it works.
If that is unexpected behaviour you want to clarify, do not hestitate to
ask.
Cheers,
Simon
On 02/21/2014 10:12 PM, Simon Thum wrote:
Sorry, I w
Soapy Smith writes:
> Hi Tom-
>
> I'm not yet good at elisp, but looking at the ob-clojure.el file, the
> header option :package is only associated with slime, not cider?
>
> Regards,
> Greg
I think so. It looks like cider and nrepl use a different variable, ns,
which isn't exposed as a header a
Aloha Nicolas,
Nicolas Goaziou writes:
> Hello,
>
> t...@tsdye.com (Thomas S. Dye) writes:
>
>> I'm trying to generate a list of figures for LaTeX export. I thought to
>> use #+TOC: figures, but this didn't work.
>>
>> The Org Export Reference Documentation has this:
>>
>> “TOC” keyword. It a
Hi
I would like to save all in org defined variables into an R data
file. In general this works fine with the following code block:
#+begin_src R :session null :results output
dir.create("./data/", showWarnings=FALSE)
save.image("./data/orgData.rda")
#+end_src
but, as I have defined a file wide
Aloha Rasmus,
Rasmus writes:
> t...@tsdye.com (Thomas S. Dye) writes:
>
>> 1) Is there a reason that the TOC keyword doesn't accept the value
>> "figures"? The reference to org-export-collect-figures suggests that it
>> should accept this value.
>
> AFAIK it is not supported. It has puzzled me
Hi Volker-
I tried the your example code blocks on my system, and I concur with
most of the behavior you described.
org-babel-execute-buffer does not work, as it comes back with error
"repl not connected". It did not cause a crash.
However, if I add explicit namespace declaration to the 2nd bloc
Hi,
I used the configuration:
org-catch-invisible-edits 'show
org-pretty-entities t
together with org-cdlatex. This breaks the insertion of subscripts
and superscripts through org-cdlatex because _{} is fontified and the
{} are hidden so typing for example: "a _ bc" results in "a_{b}c" (or
Hi Tom-
I'm not yet good at elisp, but looking at the ob-clojure.el file, the
header option :package is only associated with slime, not cider?
Regards,
Greg
On Fri, 2014-02-21 at 12:36 -1000, Thomas S. Dye wrote:
> Aloha Volker,
>
> I don't use Clojure, but ob-clojure.el defines a header argu
Hello,
t...@tsdye.com (Thomas S. Dye) writes:
> I'm trying to generate a list of figures for LaTeX export. I thought to
> use #+TOC: figures, but this didn't work.
>
> The Org Export Reference Documentation has this:
>
> “TOC” keyword. It accepts three common values: “headlines”, “tables” and
Hello,
Alexis writes:
> However, 'file+emacs:' links still exhibit the incorrect behaviour i
> described in my original email, and which you experienced also. So it
> looks like there is indeed a bug here - or, the 'file+emacs:' example
> should be removed from section 4.3 of the Org manual.
Th
Hello there,
This is more of a bug report.
I get a 'Bad sexp at line ' when using org-contacts-anniversaries in my
org files like so.
* Calendar
:calendar:
%%(org-contacts-anniversaries)
I figured out that this occurs when you have a contact in your
contacts.orgfile with a BIRTHDAY property but
On Sun, Feb 23, 2014 at 10:30:57AM +0530, Jambunathan K wrote:
> Peter Davis writes:
>
> > I'm using org-mode to prepare a document that will ultimately be
> > exported to PDF. Unfortunately, I need to include a table whose contents
> > will wrap as needed.
>
> You can export to PDF via ODT. Us
"Blanchette, Marco" writes:
> Sorry if this has been answered before, can’t seem to find a way to search
> for it…
>
> Is there a way to configure the default content of the footer produced
> during html formatted export? There is a javaScript that I would like
> to be the last bit of my html ev
Hi,
I used the configuration:
org-catch-invisible-edits 'show
org-pretty-entities t
together with org-cdlatex. This breaks the insertion of subscripts and
superscripts through org-cdlatex because _{} is fontified and the {}
are hidden so typing for example: "a _ bc" results in "a_{b}c" (or
so
Hi,
I used the configuration:
org-catch-invisible-edits 'show
org-pretty-entities t
together with org-cdlatex. This breaks the insertion of subscripts and
superscripts through org-cdlatex because _{} is fontified and the {} are
hidden so typing for example: "a _ bc" results in "a_{b}c" (or som
Hi,
If you enter a table like this in org, the +4 will get a strike-through
line through it
incorrectly.
I expect it should not happen and only the hline below should appear as
a solid line.
| 1 | +4 |
|---+|
| ||
you can see a screenshot of what happens here:
http://monosnap.com/im
>
> So, use the class attribute.
>
> #+ATTR_HTML: :class table table-striped table-bordered table-condensed
> | a | b | c |
> |---+---+---|
> | 1 | 2 | 3 |
Thanks. That's what I need.
Vikas
Hi,
I noticed that in org-entities these symbols are defined:
("lang" "\\langle" t "⟨" "<" "<" "⟨")
("rang" "\\rangle" t "⟩" ">" ">" "⟩")
But nothing for "langle" and "rangle". I guess it seems pretty confusing
when you try to use the latex-macros you are used to.
Maybe these aliases c
Richard Lawrence writes:
> OK, I think I've got a patch now that addresses everything you asked
> for. It is attached. This has been quite a learning experience! Let
> me know if other changes are necessary.
http://orgmode.org/worg/org-contribute.html#sec-5
Please use complete sentences in the
Hello,
Richard Lawrence writes:
> OK, I think I've got a patch now that addresses everything you asked
> for. It is attached. This has been quite a learning experience! Let
> me know if other changes are necessary.
It looks good. I applied it.
Thank you for your work.
Regards,
--
Nicola
Christian Moe writes:
> Just to say, I reproduce it, so I think it's a bug. Note, the below
> only happens for me when using "file+emacs:" to force opening in
> emacs. The links work with regular "file:" links, or just starting the
> link with "./" Since my .org files open with emacs anyway, I n
34 matches
Mail list logo
