Re: [O] Personal notes in org/beamer presentation

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

Re: [O] Favorite way of syncing?

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

[O] Personal notes in org/beamer presentation

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

Re: [O] Personal notes in org/beamer presentation

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

[O] Footnotes confused by brackets inside Latex

Greetings. 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? 2. Is there a workaround? Jarmo fntest.org Description: fn test case

Re: [O] [patch] small fix to org.texi

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.

Re: [O] Scheme code block gives false error message

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

Re: [O] What is the most practical workflow for capturing things in Mobileorg and later integrating them into the main files?

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.

[O] [patch] support latex variants

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

Re: [O] [patch] small fix to org.texi

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.

Re: [O] [bug] org-cycle changed behavior in orgstruct-mode

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

[O] ob-lilypond test failures

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

Re: [O] Personal notes in org/beamer presentation

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,

Re: [O] create vector-graphics with org-babel

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

[O] [patch] small fix to org.texi

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:

Re: [O] [patch] small fix to org.texi

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

Re: [O] [PATCH] small improvements to info page, Working with source code; add TINYCHANG

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

[O] Graphic files displayed in buffer?

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

Re: [O] Bug: \vert{} exported to markdown not as expected [8.3.1 (8.3.1-103-g366dc4-elpa @ /home/bitouze/.emacs.d/elpa/org-20150907/)]

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 >

Re: [O] Bug: Extra blank line in subitem list when exported to markdown [8.3.1 (8.3.1-103-g366dc4-elpa @ /home/bitouze/.emacs.d/elpa/org-20150907/)]

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 > >

Re: [O] [patch] small fix to org.texi add TINYCHANGE

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.

Re: [O] [patch] small fix to org.texi

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?

Re: [O] [PATCH] small improvements to info page, Working with source code; add TINYCHANG

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

Re: [O] Favorite way of syncing?

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

Re: [O] ob-lilypond test failures

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 >

Re: [O] Scheme code block gives false error message

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

Re: [O] Footnotes confused by brackets inside Latex

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

Re: [O] Single outer smart quotes.

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

Re: [O] obtain ob-template.el for Babel language extension

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

Re: [O] Graphic files displayed in buffer?

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

Re: [O] [patch] small fix to org.texi add TINYCHANGE

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

Re: [O] Graphic files displayed in buffer?

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

Re: [O] Bug: \vert{} exported to markdown not as expected [8.3.1 (8.3.1-103-g366dc4-elpa @ /home/bitouze/.emacs.d/elpa/org-20150907/)]

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

Re: [O] Bug: \vert{} exported to markdown not as expected [8.3.1 (8.3.1-103-g366dc4-elpa @ /home/bitouze/.emacs.d/elpa/org-20150907/)]

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

Re: [O] Graphic files displayed in buffer?

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

Re: [O] Bug: \vert{} exported to markdown not as expected [8.3.1 (8.3.1-103-g366dc4-elpa @ /home/bitouze/.emacs.d/elpa/org-20150907/)]

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:

Re: [O] Scheme code block gives false error message

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

Re: [O] Footnotes confused by brackets inside Latex

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