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

[Giacomo M]

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

Thanks a lot,

Giacomo



On Sun, Sep 13, 2015 at 12:23 PM, Rasmus  wrote:

> 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 notes can be printed on the right
> slide, separately or not at all.  See the beamer manual for details.
>
> Hope it helps,
> Rasmus
>
> --
> If you can mix business and politics wonderful things can happen!
>
>
>

Re: [O] Favorite way of syncing?

[Paul Rudin]

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 (with MobileOrg) to/from
>
> Thanks for the heads up on this.  The only thing I use Dropbox for is
> MobileOrg and I would love to avoid using a proprietary *and* closed
> system, especially as some of the content is sensitive.

If the content is sensitive you can either encrypt the data yourself
before it goes to Dropbox (see e.g. ecryptfs) or use a service that does
this as part of its process (see e.g. spideroak).

Not that I have anything against doing thing other ways - I'm just
pointing out that privacy concerns don't, of themselves, mean you can't
use Dropbox (or similar).

[O] Personal notes in org/beamer presentation

[Giacomo M]

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

[Rasmus]

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 notes can be printed on the right
slide, separately or not at all.  See the beamer manual for details.

Hope it helps,
Rasmus

-- 
If you can mix business and politics wonderful things can happen!

[O] Footnotes confused by brackets inside Latex

[Jarmo Hurri]

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

[Joe Riel]

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 TINYCHANGE cookie to the commit message unless
> you have a copyright assignment to FSF.  See
> 
> http://orgmode.org/worg/org-contribute.html#orgheadline6
> 
> Rasmus
> 

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?

-- 
Joe Riel

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

[Lawrence Bottorff]

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
> >
> > #+BEGIN_SRC scheme :session ch1 :exports both
> > (define (bool-imply a b)
> >   (if (or (not a) b) #t #f))
> > #+END_SRC
> >
> > gives the error
> >
> > org-babel-scheme-execute-with-geiser: Invalid read syntax: "#"
> >
> > and this time attempting to use the function
> >
> > #+BEGIN_SRC scheme :session ch1 :exports both
> > (bool-imply #t #f)
> > #+END_SRC
> >
> > produces no #RESULTS: block, rather, again, the error (in Messages
> buffer)
> >
> > org-babel-scheme-execute-with-geiser: Invalid read syntax: "#"
> >
> > even though this is perfectly healthy code, and it works in the
> accompanying "ch1" REPL. Any ideas what's happening?
> >
>
> Your previous example worked for me (both with master and maint - I use
> guile, not chicken, but that should make no difference).
>
> But this one fails with the "Invalid read syntax error" and with the
> attached backtrace (running on maint - master gave the same error but
> I didn't get a backtrace).
>
>
>
> HTH.
> --
> Nick
>
>

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

[Jorge]

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

[Rasmus]

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
usefulness of microtype versus unicode-math in a document-to-document
basis.

You can drop certain packages in org-latex-{default-,}packages-alist
depending on the selected program.  E.g. you'd only want {input,font}enc
with pdflatex.  Likewise, you'd only want polyglossia when using
{xe,lua}latex.  This is supported by an optional fourth argument in the
mentioned alists.

It makes it easier (IMO) to write declarations for org-latex-pdf-process
as you can simply specify %latex, which is then changed to the correct
form (though there's some hackery in org-latex-compile).

The patch-set drops "rubber" as it's not easy to configure a latex program
on the go.

There's also a %bibtex but it's not configurable on a file basis, though I
could add it, if there's a demand for it.

The "right" latex program is written to the file, optionally as a
file-variable (AUCTeX and latex-mode; I could add texworks as well, if
desirable).  Perhaps the latex program and the creation date should be
written on the same line?

Suvayu tested a previous version of the patch-set, though I don't know for
how long.

Rasmus

-- 
Don't panic!!!
>From 8470f65bf5be29d173e547ca16dd874306b43dd1 Mon Sep 17 00:00:00 2001
From: Rasmus 
Date: Sun, 13 Sep 2015 16:45:48 +0200
Subject: [PATCH 4/4] ox-latex: Small refactor

* ox-latex.el (org-latex-compile): Use format-spec.
---
 lisp/ox-latex.el | 34 ++
 1 file changed, 18 insertions(+), 16 deletions(-)

diff --git a/lisp/ox-latex.el b/lisp/ox-latex.el
index 0ee0c15..61594a9 100644
--- a/lisp/ox-latex.el
+++ b/lisp/ox-latex.el
@@ -3499,24 +3499,26 @@ Return PDF file name or an error if it couldn't be produced."
((functionp org-latex-pdf-process)
 	(funcall org-latex-pdf-process (shell-quote-argument texfile)))
;; A list is provided: Replace %b, %f and %o with appropriate
-   ;; values in each command before applying it.  Output is
-   ;; redirected to "*Org PDF LaTeX Output*" buffer.
+   ;; values in each command before applying it.  Note that while
+   ;; "%latex" and "%bibtex" is used in `org-latex-pdf-process',
+   ;; they are replaced with "%L" and "%B" to adhere to
+   ;; format-spec.  Output is redirected to "*Org PDF LaTeX
+   ;; Output*" buffer.
((consp org-latex-pdf-process)
 	(let ((outbuf (and (not snippet)
-			   (get-buffer-create "*Org PDF LaTeX Output*"
-	  (dolist (command org-latex-pdf-process)
-	(shell-command
-	 (replace-regexp-in-string
-	  "%bib" (shell-quote-argument org-latex-bib-process)
-	  (replace-regexp-in-string
-	   "%latex" (shell-quote-argument compiler)
-	   (replace-regexp-in-string
-		"%b" (shell-quote-argument base-name)
-		(replace-regexp-in-string
-		 "%f" (shell-quote-argument full-name)
-		 (replace-regexp-in-string
-		  "%o" (shell-quote-argument out-dir) command t t) t t) t t) t) t)
-	 outbuf))
+			   (get-buffer-create "*Org PDF LaTeX Output*")))
+	  (spec (list (cons ?B  (shell-quote-argument org-latex-bib-process))
+			  (cons ?L (shell-quote-argument compiler))
+			  (cons ?b (shell-quote-argument base-name))
+			  (cons ?f (shell-quote-argument full-name))
+			  (cons ?o (shell-quote-argument out-dir)
+	  (mapc (lambda (command)
+		  (shell-command (format-spec command spec) outbuf))
+		(mapcar (lambda (command)
+			  (replace-regexp-in-string "%\\(latex\\|bibtex\\)\\>"
+		(lambda (str) (upcase (substring str 0 2)))
+		command))
+			org-latex-pdf-process))
 	  ;; Collect standard errors from output buffer.
 	  (setq warnings (and (not snippet)
 			  (org-latex--collect-warnings outbuf)
-- 
2.5.1

>From c365b1e6016b3f11fc64a0fe0ce78e3848d5dfa9 Mon Sep 17 00:00:00 2001
From: Rasmus 
Date: Wed, 8 Jul 2015 18:32:40 +0200
Subject: [PATCH 3/4] ox-latex: Support arbitrary bibtex-like program.

* ox-latex.el (org-latex-bib-process): New defcustom.
  (org-latex-pdf-process, org-latex-compile): Use new defcustom.
---
 lisp/ox-latex.el | 27 ++-
 1 file changed, 22 insertions(+), 5 deletions(-)

diff --git a/lisp/ox-latex.el b/lisp/ox-latex.el
index 233e9e9..0ee0c15 100644
--- a/lisp/ox-latex.el
+++ b/lisp/ox-latex.el
@@ -1064,6 +1064,21 @@ during latex export it will output
 
  Compilation
 
+(defcustom org-latex-bib-process "bibtex"
+  "Command used to process a LaTeX files bibliography.
+
+The shorthand %bib in `org-latex-pdf-process' is replaced with
+this value.
+
+A better approach is to use a compiler suit such as `latexmk'.
+"
+  :group 'org-export-latex
+  :type '(choice (const :tag "BibTeX" "bibtex")
+		 (const :tag "Biber" "biber")
+		 (string :tag "Other 

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

[Rasmus]

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 mail with the
patches and attach the patch with updated commit message.

Since your git email suggests that you are associated with a major
software company, it's best if we follow the rules stringently.

Also, I believe there's a limit of 10 lines you can change without
copyright assignment.  Though you have only changed documentation, which
may or may not be within the same limit  Anyway, it's not an issue
presently.  Hopefully somebody knows to what extend there's a difference
between documentation and code, if at all.

Thanks for the patches and sorry to be a bother.

Rasmus

-- 
One thing that is clear: it's all down hill from here 

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

[Rasmus]

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 require 25, but I don't
 read that list carefully.

Rasmus

-- 
History is what should never happen again

[O] ob-lilypond test failures

[Rasmus]

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-test.pdf:No such 
file or directory

For ob-lilypond/ly-attempt-to-play-midi:

Test failed: ((should (equal "No midi file generated so can't play!" 
(org-babel-lilypond-attempt-to-play-midi midi-file))) :form (equal "No midi 
file generated so can't play!" "No midi file generated so can’t play!") :value 
nil :explanation (array-elt 29 (different-atoms (39 "#x27" "?'") (8217 "#x2019" 
"?’"

I don't know anything about lilypond.  I can make the tests not run when
lilypond is not present, but as said, they don't even seem to work when
lilypond is present.  I installed version 2.18.2.

Thanks,
Rasmus

-- 
There are known knowns; there are things we know that we know

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

[Rasmus]

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't work, but I'm surely using it wrongly.

No, the tag is a hint for you (and maybe sparse trees).  In general,
properties are used for such things (ox-koma-script and :(no)export: being
the main exceptions, I think).

However, once you use org-beamer-mode and annotate your headlines with
org-beamer-select-environment (typically, C-c C-b) both the property and
the tag should be inserted for you.

Rasmus

-- 
Don't panic!!!

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

[Max Linke]

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
since commit 0cef5b63e, which is in version 8.1+.  (You do need to
install and configure the “svg” package for latex in order to compile
the document.)

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

[Joe Riel]

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:23:42 -0700
Subject: [PATCH 3/3] * doc/org.texi: (The export dispatcher): elide duplicate
 phrase

The phrase "from which it is possible to select an export format and to toggle
export options." appeared both before and after the footnote.
---
 doc/org.texi | 3 +--
 1 file changed, 1 insertion(+), 2 deletions(-)

diff --git a/doc/org.texi b/doc/org.texi
index c630c7a..8de8efc 100644
--- a/doc/org.texi
+++ b/doc/org.texi
@@ -10600,8 +10600,7 @@ toggle export options@footnote{It is also possible to use a less intrusive
 interface by setting @code{org-export-dispatch-use-expert-ui} to a
 non-@code{nil} value.  In that case, only a prompt is visible from the
 minibuffer.  From there one can still switch back to regular menu by pressing
-@key{?}.} from which it is possible to select an export format and to toggle
-export options.
+@key{?}.}.
 
 @table @asis
 @orgcmd{C-c C-e,org-export-dispatch}
-- 
2.1.4

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

[Rasmus]

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 assignment to FSF.  See

http://orgmode.org/worg/org-contribute.html#orgheadline6

Rasmus

-- 
ツ

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

[Joe Riel]

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

The attached patches replace the previous.
The patches are identical, these add TINYCHANGE to the
commit messages.

 



-- 
Joe Riel

>From 358ec72642b091b0cc8e8ce87d5525f2dbd1e8ec Mon Sep 17 00:00:00 2001
From: Joe Riel 
Date: Sat, 12 Sep 2015 11:30:06 -0700
Subject: [PATCH 1/3] doc/org.texi: Rewrite paragraph

doc/org.texi (Evaluating code blocks):

Rewrite paragraph to state where to find information on enabling other
languages.  Without this, it isn't clear where to look.

TINYCHANGE.
---
 doc/org.texi | 7 +++
 1 file changed, 3 insertions(+), 4 deletions(-)

diff --git a/doc/org.texi b/doc/org.texi
index ac7d3a4..1e67b62 100644
--- a/doc/org.texi
+++ b/doc/org.texi
@@ -14972,10 +14972,9 @@ and/or the name of the evaluated code block.  The default value of
 @code{org-babel-results-keyword}.
 
 By default, the evaluation facility is only enabled for Lisp code blocks
-specified as @code{emacs-lisp}.  However, source code blocks in many languages
-can be evaluated within Org mode (see @ref{Languages} for a list of supported
-languages and @ref{Structure of code blocks} for information on the syntax
-used to define a code block).
+specified as @code{emacs-lisp}.  See @ref{Languages} to enable other
+supported languages.  See @ref{Structure of code blocks} for information on
+the syntax used to define a code block.
 
 @kindex C-c C-c
 There are a number of ways to evaluate code blocks.  The simplest is to press
-- 
2.1.4

>From 29679d5e5854e9a2ff0e41af92c451ccdcd82f73 Mon Sep 17 00:00:00 2001
From: Joe Riel 
Date: Sat, 12 Sep 2015 11:36:50 -0700
Subject: [PATCH 2/3] doc/org.texi: add link to relevant chapter

* doc/org.texi (Exporting code blocks) add link to Exporting

Coming into this section without having read the chapter 12
is pretty confusing.  The link is helpful.

TINYCHANGE.
---
 doc/org.texi | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/doc/org.texi b/doc/org.texi
index 1e67b62..c630c7a 100644
--- a/doc/org.texi
+++ b/doc/org.texi
@@ -14851,7 +14851,8 @@ of code block evaluation, @emph{both} the code and the results of code block
 evaluation, or @emph{none}.  For most languages, the default exports code.
 However, for some languages (e.g., @code{ditaa}) the default exports the
 results of code block evaluation.  For information on exporting code block
-bodies, see @ref{Literal examples}.
+bodies, see @ref{Literal examples}.  For information on exporting
+parts of Org documents, see @ref{Exporting}.
 
 The @code{:exports} header argument can be used to specify export
 behavior (note that these arguments are only relevant for code blocks, not
-- 
2.1.4

[O] Graphic files displayed in buffer?

[Thomas S . Dye]

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 displayed as links.  Any ideas how to fix
this?

I'm using the latest Org mode from git, if that matters.

All the best,
Tom
-- 
Thomas S. Dye
http://www.tsdye.com

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/)]

[Nicolas Goaziou]

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
> #+end_src
>
> Whereas:
>
> - \under{} gives the expected underscore symbol (_),
> - \vert{} gives  instead of the expected pipe symbol (|).

What is wrong with ? Doesn't Markdown accept HTML entities anyway?

Regards,

-- 
Nicolas Goaziou

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/)]

[Nicolas Goaziou]

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
>
> *Expected* behavior (note the *absence* of blank line after =Foo22=):
>
> #+NAME: test-ok.md
> #+begin_src markdown
> -   Foo 1
> -   Foo2:
> -   Foo21
> -   Foo22
> End of Foo2 item.
> #+end_src
>
> *Current* behavior (note the blank line after =Foo22=):
>
> #+NAME: test.md
> #+begin_src markdown
> -   Foo 1
> -   Foo2:
> -   Foo21
> -   Foo22
> 
> End of Foo2 item.
> #+end_src

Well, the rules governing blank lines in Mardown are mysterious to me.
They are also, AFAIK, totally undocumented.

Anyway, you are suggesting to remove any blank line before paragraphs
following a plain list, but only when they are already contained within
a list. In other words, both

  - Foo 1
  - Foo 2

  A paragraph

and

  - Foo 1
  - Foo 2:
- Foo 21
- Foo 22
End of Foo2 item.

are valid examples. Am I correct? 

Also, what about other block types, e.g., which one is valid:

  - Foo 1
  - Foo2:
- Foo 21
- Foo 22

#+begin_example
Some example
#+end_example

or

  - Foo 1
  - Foo2:
- Foo 21
- Foo 22
#+begin_example
Some example
#+end_example

?


Regards,

-- 
Nicolas Goaziou

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

[Joe Riel]

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

>From 5fd27a2ec60b5199d711995ca0ed5e9810a658e4 Mon Sep 17 00:00:00 2001
From: Joe Riel 
Date: Sat, 12 Sep 2015 14:23:42 -0700
Subject: [PATCH 3/3] doc/org.texi: elide duplicate phrase

* doc/org.texi (The export dispatcher):

The phrase "from which it is possible to select an export format and to toggle
export options." appeared both before and after the footnote.  Remove the
redundancy.

TINYCHANGE.
---
 doc/org.texi | 3 +--
 1 file changed, 1 insertion(+), 2 deletions(-)

diff --git a/doc/org.texi b/doc/org.texi
index c630c7a..8de8efc 100644
--- a/doc/org.texi
+++ b/doc/org.texi
@@ -10600,8 +10600,7 @@ toggle export options@footnote{It is also possible to use a less intrusive
 interface by setting @code{org-export-dispatch-use-expert-ui} to a
 non-@code{nil} value.  In that case, only a prompt is visible from the
 minibuffer.  From there one can still switch back to regular menu by pressing
-@key{?}.} from which it is possible to select an export format and to toggle
-export options.
+@key{?}.}.
 
 @table @asis
 @orgcmd{C-c C-e,org-export-dispatch}
-- 
2.1.4

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

[Joe Riel]

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 issue?
> 
> Thanks, I hadn't seen those patches.  Just reply to the mail with the
> patches and attach the patch with updated commit message.
> 
> Since your git email suggests that you are associated with a major
> software company, it's best if we follow the rules stringently.
> 
> Also, I believe there's a limit of 10 lines you can change without
> copyright assignment.  Though you have only changed documentation, which
> may or may not be within the same limit  Anyway, it's not an issue
> presently.  Hopefully somebody knows to what extend there's a difference
> between documentation and code, if at all.
> 
> Thanks for the patches and sorry to be a bother.

No problem.  I modified the commit messages.
Also sent an email to assign copyright to FSF.


-- 
Joe Riel

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

[Rasmus]

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 them to the correct place).
>
> The attached patches replace the previous.
> The patches are identical, these add TINYCHANGE to the
> commit messages.

Pushed.  Thanks.

-- 
However beautiful the theory, you should occasionally look at the evidence

Re: [O] Favorite way of syncing?

[Ramon Diaz-Uriarte]

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 this way,
>>> and also use it to send/receive the org files (with MobileOrg) to/from
>>
>> Thanks for the heads up on this.  The only thing I use Dropbox for is
>> MobileOrg and I would love to avoid using a proprietary *and* closed
>> system, especially as some of the content is sensitive.
>
> If the content is sensitive you can either encrypt the data yourself
> before it goes to Dropbox (see e.g. ecryptfs) or use a service that does
> this as part of its process (see e.g. spideroak).
>
> Not that I have anything against doing thing other ways - I'm just
> pointing out that privacy concerns don't, of themselves, mean you can't
> use Dropbox (or similar).


Sure, you are correct. However, if there are Android devices in the mix,
encrypting locally before sending to Dropbox becomes inconvenient (or at
least too inconvenient for me). I am not sure about spideroak's support for
android, and I recall having experienced problems (I no longer remember the
details) with Wuala.



Best,

R.


-- 
Ramon Diaz-Uriarte
Department of Biochemistry, Lab B-25
Facultad de Medicina
Universidad Autónoma de Madrid 
Arzobispo Morcillo, 4
28029 Madrid
Spain

Phone: +34-91-497-2412

Email: rdia...@gmail.com
   ramon.d...@iib.uam.es

http://ligarto.org/rdiaz

Re: [O] ob-lilypond test failures

[Nick Dokos]

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/org-mode/testing/examples/ob-lilypond-test.pdf:No such 
> file or directory
>
> For ob-lilypond/ly-attempt-to-play-midi:
>
> Test failed: ((should (equal "No midi file generated so can't
> play!" (org-babel-lilypond-attempt-to-play-midi midi-file))) :form
> (equal "No midi file generated so can't play!" "No midi file generated
> so can’t play!") :value nil :explanation (array-elt 29
> (different-atoms (39 "#x27" "?'") (8217 "#x2019" "?’"
>
> I don't know anything about lilypond.  I can make the tests not run when
> lilypond is not present, but as said, they don't even seem to work when
> lilypond is present.  I installed version 2.18.2.
>
> Thanks,
> Rasmus

I get passes:

,
|...
|passed   65/587  ob-lilypond/feature-provision
|passed   66/587  ob-lilypond/ly-arrange-mode
| No pdf file generated so can't display!
|passed   67/587  ob-lilypond/ly-attempt-to-open-pdf
| No midi file generated so can't play!
|passed   68/587  ob-lilypond/ly-attempt-to-play-midi
|passed   69/587  ob-lilypond/ly-check-for-compile-error
|...
`

but I didn't go any further to try to figure out who is producing
the messages.

I have lilypond installed.

Org-mode version 8.3.1 (release_8.3.1-234-g8c85c9 @
/home/nick/elisp/org-mode/lisp/)

-- 
Nick

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

[Nick Dokos]

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 the
error. It tells you how you got there.

See

  (info "(org) Feedback")

on how to enable it and produce a useful backtrace.

You read it from bottom to top: the bottom-most function has called
the next-to-bottom-most function, ..., which has called the top-most
function, which is in the middle of evaluating some expression when
the error occurred. The section on Debugging in the Emacs Lisp manual
contains more information.

Re: "master" and "maint" - I didn't know which version of org you were
using, so I tried it with both the master branch and the maint branch of
the git tree, as they were yesterday. I should probably have provided
more explicit versions but it was late and I was tired.

For the record, at the time that I was doing that:

"master" was Org-mode version 8.3.1 (release_8.3.1-234-g8c85c9 @
 /home/nick/elisp/org-mode/lisp/)
"maint"  was Org-mode version 8.3.1 (release_8.3.1-120-gbc322f @
 /home/nick/elisp/org-mode/lisp/)

HTH
-- 
Nick

Re: [O] Footnotes confused by brackets inside Latex

[Nicolas Goaziou]

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

> 2. Is there a workaround?

You can use non-inline footnotes.

Regards,

-- 
Nicolas Goaziou

Re: [O] Single outer smart quotes.

[Nicolas Goaziou]

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 apostrophes
> that occur on the outside of words, and I saw that it was updated
> again just last week to deal with some edge cases.

Correct.

> Do you think that there is an easy way to make it recognise single
> outer quotes without sacrificing the recent gains, or would it be
> better just to treat American style quoting as the standard for source
> files, and just add an en-gb entry to org-export-smart-quotes-alist
> that converts double quotes to single quotes and vice versa?

The latter. You can fix "en" entry in `org-export-smart-quotes-alist'
and add a new "us" entry, if needed.


Regards,

-- 
Nicolas Goaziou

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

[Joe Riel]

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-mode)?
> 
> 2. In function org-babel-execute:template functions first, second, third,
> etc are used to extract values from processed-params. However, such
> function are not defined in elisp, (nth N processed-params) should be used
> instead.  Is it correct?
> Also, it seems from other examples that the usual approach is to use assoc,
> e.g.,  (cdr (assoc ":session" params)). Are there enforced conventions that
> ensure the order in processed-params?

first, second, etc are macros in cl.el; nothing wrong with that.
However, there is a problem with the usage in the given template.
They are applied to processed-params, and that is not correct because
any variables in the block header are prepended to the list so first,
second, etc are wrong.  The template code should be rewritten.  The
better way to handle this appears to be

  (let ((vars (mapcar #'cdr (org-babel-get-header params :var
 ... )


> 3. In function org-babel-expand-body:template we assume that vars is a list
> of pairs.  However, it seems to me from some experiments that sometimes
> vars contains symbols. Am I wrong?

I don't know, but believe it should always contain pairs as vars are required
to have values.  Caveat: I just started playing with this so could be very 
wrong.

--
Joe Riel

Re: [O] Graphic files displayed in buffer?

[Thomas S . Dye]

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 document are
> displayed correctly as links.
>
> I'd like to have all the links displayed as links.  Any ideas how to fix
> this?

I think I've found a recently introduced bug.

The behavior I describe above can be triggered by a call to org-sbe,
which I have set up like this at the end of my Org mode file.

# Local Variables: 
# org-entities-user: nil
# eval: (and (fboundp 'org-sbe) (not (fboundp 'sbe)) (fset 'sbe 'org-sbe))
# eval: (sbe "user-entities")
# End:

If I omit the # eval: (sbe "user-entities") line, save the file, close
it, and re-open it then all is well.

If I add the line and refresh the setup, then the problem returns.

If I then delete the line, so there are no calls to org-sbe (or its
alias, sbe), and refresh the setup, then the problem persists.  If I
then save the file, kill its buffer, and re-open it, the problem is
gone.

I hope this makes sense.  It seems to me that org-sbe has recently begun
hosing something.  This is all code that I've been using regularly and
successfully for months or years.

All the best,
Tom

-- 
Thomas S. Dye
http://www.tsdye.com

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

[Rasmus]

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

Pushed thanks.

In general you don't have to write to long changelog entries.  You can
write it in the accompanying email if you want.

Also, the format is

 * file-changed.el (node/function): Capitalized and a period.

No line break and capitalized and finish with period.

I changed some minor things in the patches.

Thanks again.

Rasmus

-- 
When in doubt, do it!

Re: [O] Graphic files displayed in buffer?

[Rasmus]

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 all the links displayed as links.  Any ideas how to fix
>> this?
>
> I think I've found a recently introduced bug.
>
> The behavior I describe above can be triggered by a call to org-sbe,
> which I have set up like this at the end of my Org mode file.
>
> # Local Variables: 
> # org-entities-user: nil
> # eval: (and (fboundp 'org-sbe) (not (fboundp 'sbe)) (fset 'sbe 'org-sbe))
> # eval: (sbe "user-entities")
> # End:
>
> If I omit the # eval: (sbe "user-entities") line, save the file, close
> it, and re-open it then all is well.
>
> If I add the line and refresh the setup, then the problem returns.

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) (not (fboundp 'sbe)) (fset 'sbe 'org-sbe))
# eval: (sbe "user-entities")
# End: 

-- 
With monopolies the cake is a lie!

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

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:
>>
>> #+NAME: test.md
>> #+begin_src markdown
>> Foo |bar\_baz|
>>
>> Foo bar_baz
>> #+end_src
>>
>> Whereas:
>>
>> - \under{} gives the expected underscore symbol (_),
>> - \vert{} gives  instead of the expected pipe symbol (|).
>
> What is wrong with ? Doesn't Markdown accept HTML entities
> anyway?

The point is the following: the site where the .md file (exported from
the .org file) will be used has this (maybe current) feature to be able
to interpret strings such as:

|REP_TO_COMMENT|

Hence, I have to export "real" _ and |.

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 them \vert{}.  And that's the purpose
   of my bug report, \vert{} is exported as , not as "real" |.

In other words, I was happy with \under{} that exports real _ and, IMHO,
\vert{} should do the same with |.

Regards.
-- 
Denis

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/)]

[Nicolas Goaziou]

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 them \vert{}.  And that's the purpose
>of my bug report, \vert{} is exported as , not as "real" |.
>
> In other words, I was happy with \under{} that exports real _ and, IMHO,
> \vert{} should do the same with |.

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" entity with a new one that would do 1. So
 basically, this is 1 but on your machine only.
  3. Use a new entity that becomes | when used in HTML export.

WDYT?

Regards,

Re: [O] Graphic files displayed in buffer?

[Thomas S . Dye]

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) (not (fboundp 'sbe)) (fset 'sbe 'org-sbe))
> # eval: (sbe "user-entities")
> # End: 

Thanks for looking into this.  Your file works here, too.

I found that loading my file somehow sets this variable:

org-inline-image-overlays is a variable defined in `org.el'.
Its value is
(# # # # 
# # # # 
# # # # 
# # # # 
#)

Local in buffer anth_464_syllabus.org; global value is nil

Any idea how that might happen?  It is just one part of the file, the
rest is good (even though it contains lots of images).

Running org-remove-inline-images gets rid of the overlays.  If I save
after they are removed, kill the buffer, and then read it again I have
the same problem.

All the best,
Tom
-- 
Thomas S. Dye
http://www.tsdye.com

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/)]

[Charles C. Berry]

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" entity with a new one that would do 1. So
basically, this is 1 but on your machine only.
 3. Use a new entity that becomes | when used in HTML export.



If this creates a backend derived from 'md (and does not modify ox-md.el),
then fine. But, ...

It seem like there are flavors of Markdown that use verticals for varying 
purposes. For example, rmarkdown


http://rmarkdown.rstudio.com/authoring_pandoc_markdown.html

uses them as `line block' markers and to construct `table.el' style 
tables.


And I have seen verticals used to set off citations elsewhere.

And I am not even sure what Denis meant by using them to `interpret 
strings'.


Best,

Chuck

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

[Lawrence Bottorff]

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 see if it works. He also
seems to believe Scheme is a second-class citizen in babel-land.

On Sun, Sep 13, 2015 at 7:48 PM, Nick Dokos  wrote:

> 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 the
> error. It tells you how you got there.
>
> See
>
>   (info "(org) Feedback")
>
> on how to enable it and produce a useful backtrace.
>
> You read it from bottom to top: the bottom-most function has called
> the next-to-bottom-most function, ..., which has called the top-most
> function, which is in the middle of evaluating some expression when
> the error occurred. The section on Debugging in the Emacs Lisp manual
> contains more information.
>
> Re: "master" and "maint" - I didn't know which version of org you were
> using, so I tried it with both the master branch and the maint branch of
> the git tree, as they were yesterday. I should probably have provided
> more explicit versions but it was late and I was tired.
>
> For the record, at the time that I was doing that:
>
> "master" was Org-mode version 8.3.1 (release_8.3.1-234-g8c85c9 @
>  /home/nick/elisp/org-mode/lisp/)
> "maint"  was Org-mode version 8.3.1 (release_8.3.1-120-gbc322f @
>  /home/nick/elisp/org-mode/lisp/)
>
> HTH
> --
> Nick
>
>
>

Re: [O] Footnotes confused by brackets inside Latex

[Jarmo Hurri]

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