Eric S Fraga writes:
> On Friday, 11 Sep 2015 at 18:42, Ramon Diaz-Uriarte wrote:
>
> [...]
>
>> I use syncthing (https://syncthing.net/) which, admittedly, does not
>> require a server nor uses SSH :-). I keep four computers in sync this way,
>> and also use it to send/receive the org files (wit
Hi all,
where would you write personal (not to be exported) notes in an
org/beamer presentation?
In a :noexport: subtree? How would you conveniently review them?
Thanks,
Giacomo
Hi,
Giacomo M writes:
> where would you write personal (not to be exported) notes in an
> org/beamer presentation?
> In a :noexport: subtree? How would you conveniently review them?
You could use the B_Note and B_noteNH properties/tags and set how they are
exported with beamer. AFAIK, beamer n
Dear Ramsus, thanks for the hint.
That led me to find the snippet
:PROPERTIES:
:BEAMER_env: note
:END:
to add to the notes subtree, which in combination w/ a "notes" beamer class
option creates an additional slide w/ notes.
Alone, "B_note" used as a tag didn't work, but I'm surely using it wrongl
Giacomo M writes:
> Dear Ramsus, thanks for the hint.
> That led me to find the snippet
> :PROPERTIES:
> :BEAMER_env: note
> :END:
>
> to add to the notes subtree, which in combination w/ a "notes" beamer class
> option creates an additional slide w/ notes.
>
> Alone, "B_note" used as a tag didn'
I found out that the error is related to the ob-ipython package. They
currently only allow png's. Using the normal ob-python everything works.
Thanks for the help though.
On 09/09/2015 06:02 PM, Aaron Ecay wrote:
Hi Max,
What version of org are you using? Latex export should support svg
sinc
Hi,
I have been busy.
So was the consensus to fix this using "old-style" advice or can I use
nadvice syntax? As Nicolas mentioned, the latter bumps the requirement of
master to 24.4 instead of 24.3, but it's much nicer to write, read and
debug.
BTW: I think recently AUCTeX made changes that req
Sorry, Nick, not following you. Could you elaborate more? As a rank
beginner, I'm not sure what a backtrace is or how to produce one or how it
read it. What do you mean by "master" and "maint"?
On Sun, Sep 13, 2015 at 5:41 AM, Nick Dokos wrote:
> Lawrence Bottorff writes:
>
> > Again, this code
On Fri, Sep 11, 2015 at 1:23 PM, Ken Mankoff wrote:
> Hi Jorge,
>
> My mobile capture work flow is:
> [...]
Thank you, this is quite better than what I had.
Hi,
This series of patches adds support for specifying a latex program,
i.e. {pdf,lua,xe}latex (plain latex is not in the list since we don't
really target dvi output).
You can add lines like
#+latex_program: lualatex
This is fairly useful as I typically is doing some weighting of the
usefu
In "The export dispatcher", the phrase "from which it is possible to
select an export format and to toggle export options." is repeated.
This removes the duplication.
--
Joe Riel
>From b6319a36e57fdeb3318bcb02b2d76ba3e21e34c5 Mon Sep 17 00:00:00 2001
From: Joe Riel
Date: Sat, 12 Sep 2015 14:2
Joe Riel writes:
> In "The export dispatcher", the phrase "from which it is possible to
> select an export format and to toggle export options." is repeated.
> This removes the duplication.
Thanks.
I think you need to add a TINYCHANGE cookie to the commit message unless
you have a copyright ass
On Sun, 13 Sep 2015 18:25:12 +0200
Rasmus wrote:
> Joe Riel writes:
>
> > In "The export dispatcher", the phrase "from which it is possible to
> > select an export format and to toggle export options." is repeated.
> > This removes the duplication.
>
> Thanks.
>
> I think you need to add a TI
Joe Riel writes:
> Thanks for the notice.
>
> I didn't see that when I first read it. Hmm. I posted two others
> yesterday. What should I do now? Edit the commit messages and
> post the patches? Would the duplicate posts be an issue?
Thanks, I hadn't seen those patches. Just reply to the
Hi,
I get lilypond errors when running make test now and I didn't see any old
messages about this.
The errors persists even after installing lilypond.
For ob-lilypond/ly-attempt-to-open-pdf:
pdf-info-query: epdfinfo: Error opening
/home/rasmus/src/code/org-mode/testing/examples/ob-lilypond
On Sun, 13 Sep 2015 09:12:37 -0700
Joe Riel wrote:
> In "The export dispatcher", the phrase "from which it is possible to
> select an export format and to toggle export options." is repeated.
> This removes the duplication.
The attached adds TINYCHANGE to the commit message.
--
Joe Riel
>Fro
On Sat, 12 Sep 2015 11:50:23 -0700
Joe Riel wrote:
> The attached two patches make small improvements to
> the "Working with source code".
>
> This is my first time submitting patches to org, it's
> not entirely clear that I'm doing this correctly
> (i.e. sending them to the correct place).
T
On Sun, 13 Sep 2015 18:40:12 +0200
Rasmus wrote:
> Joe Riel writes:
>
> > Thanks for the notice.
> >
> > I didn't see that when I first read it. Hmm. I posted two others
> > yesterday. What should I do now? Edit the commit messages and
> > post the patches? Would the duplicate posts be an
On Fri, 11 Sep 2015 19:30:20 +
Marco Maggesi wrote:
> I also have a few questions about ob-template.el
>
> 1. Can we assume that the HEAD version of ob-template.el is adequate as a
> basis for an implementation which is compatible with org version 8.2.xx
> (i.e., with older versions of org-m
Joe Riel writes:
> On Sat, 12 Sep 2015 11:50:23 -0700
> Joe Riel wrote:
>
>> The attached two patches make small improvements to
>> the "Working with source code".
>>
>> This is my first time submitting patches to org, it's
>> not entirely clear that I'm doing this correctly
>> (i.e. sending
Aloha all,
Links to graphic files in one section of a long-lived document now
display the graphic in the Org mode buffer. This new behavior is
surprising and unwanted.
Links to graphic files in other sections of the same document are
displayed correctly as links.
I'd like to have all the links
Joe Riel writes:
> On Sun, 13 Sep 2015 09:12:37 -0700
> Joe Riel wrote:
>
>> In "The export dispatcher", the phrase "from which it is possible to
>> select an export format and to toggle export options." is repeated.
>> This removes the duplication.
>
> The attached adds TINYCHANGE to the commit
Aloha all,
Answering myself ...
Thomas S. Dye writes:
> Aloha all,
>
> Links to graphic files in one section of a long-lived document now
> display the graphic in the Org mode buffer. This new behavior is
> surprising and unwanted.
>
> Links to graphic files in other sections of the same docum
On Sun, 13-09-2015, at 09:07, Paul Rudin wrote:
> Eric S Fraga writes:
>
>> On Friday, 11 Sep 2015 at 18:42, Ramon Diaz-Uriarte wrote:
>>
>> [...]
>>
>>> I use syncthing (https://syncthing.net/) which, admittedly, does not
>>> require a server nor uses SSH :-). I keep four computers in sync th
Rasmus writes:
> Hi,
>
> I get lilypond errors when running make test now and I didn't see any old
> messages about this.
>
> The errors persists even after installing lilypond.
>
> For ob-lilypond/ly-attempt-to-open-pdf:
>
> pdf-info-query: epdfinfo: Error opening
> /home/rasmus/src/code/or
Lawrence Bottorff writes:
> Sorry, Nick, not following you. Could you elaborate more? As a rank
> beginner, I'm not sure what a backtrace is or how to produce one or
> how it read it. What do you mean by "master" and "maint"?
>
It's a debugging aid: it's a dump of the call stack at the time of t
Hello,
Jarmo Hurri writes:
> The attached test case demonstrates a problem I ran into: exporting
> footnotes as PDF fails when the footnote contains brackets inside Latex
> formulas.
>
> Questions.
> 1. Can this be fixed?
This is not a bug. Inline footnotes only allow paired square brackets
ins
Hello,
dbito...@wanadoo.fr (Denis Bitouzé) writes:
> The following file:
>
> #+NAME: test.org
> #+begin_src org
> Foo |bar_baz|
>
> Foo \vert{}bar\under{}baz\vert{}
> #+end_src
>
> is exported to markdown as follows:
>
> #+NAME: test.md
> #+begin_src markdown
> Foo |bar\_baz|
>
> Foo |bar_baz|
>
Hi,
>> Links to graphic files in one section of a long-lived document now
>> display the graphic in the Org mode buffer. This new behavior is
>> surprising and unwanted.
>>
>> Links to graphic files in other sections of the same document are
>> displayed correctly as links.
>>
>> I'd like to have
Hello,
Leonard Randall writes:
> The new smart quotes algorithm does not seem to capture British style
> quoting (single outer quotes, double inner quotes) correctly. It
> treats all single quotes that are not enclosed in double quotes as
> apostrophes. I assume that it was revised to deal with
Le 13/09/15 à 22h04, Nicolas Goaziou a écrit :
> Hello,
Hello,
> dbito...@wanadoo.fr (Denis Bitouzé) writes:
>
>> The following file:
>>
>> #+NAME: test.org
>> #+begin_src org
>> Foo |bar_baz|
>>
>> Foo \vert{}bar\under{}baz\vert{}
>> #+end_src
>>
>> is exported to markdown as follows:
>>
>> #+
Hello,
dbito...@wanadoo.fr (Denis Bitouzé) writes:
> When exported to markdown, an extra blank line is added in subitem
> lists, as shown by the following minimal example.
>
> #+NAME: test.org
> #+begin_src org
> - Foo 1
> - Foo2:
> - Foo21
> - Foo22
> End of Foo2 item.
> #+end_src
>
> *Exp
Denis Bitouzé writes:
> 1. For _, \under{} is necessary since _ at the org mode level is
>exported as \_.
> 2. For |, source | could be okay. But I'd like to use strings as above
>in tables and, AFAIK, the only way to have pipe symbols in a table at
>the org mode level is to code th
On Sun, 13 Sep 2015, Nicolas Goaziou wrote:
Denis Bitouzé writes:
[...]
Markdown export back-end use :html conventions to translate entities.
For some reason, HTML prefers | over |, and so does markdown.
There are a few options available:
1. Prefer | over | in HTML
2. Overwrite "vert"
Hi Rasmus,
Rasmus writes:
>
> I cannot reproduce. What is your "user-entities" code block?
>
> This is my test file:
>
> [[file:/tmp/test.png]]
>
> #+name: user-entities
> #+BEGIN_SRC emacs-lisp
> 1
> #+END_SRC
>
> # Local Variables:
> # org-entities-user: nil
> # eval: (and (fboundp 'org-sbe)
I think this (
https://mobiusengineering.wordpress.com/2015/01/11/using-emacs-org-with-mit-scheme/)
describes my problem. Basically, it's with ob-scheme.el. The article seems
to say that my problem is scheme stuff being handled improperly by the
elisp of ob-scheme.el. I'll try his workaround and se
Nicolas Goaziou writes:
> This is not a bug. Inline footnotes only allow paired square brackets
> inside.
>
>> 2. Is there a workaround?
>
> You can use non-inline footnotes.
Thanks!
Jarmo
37 matches
Mail list logo
