Re: [O] [bug] inserting footnotes via org-footnote-action command

[Nicolas Goaziou]

Hello,

Martin Carlé  writes:

> Well, I wrapped the exporter mechanism into some advice functions that
> allow for many different exports from a single file in such a manner that
> multiple exports are not restricted to subtrees.

Not sure to understand this.

> This extended export mechanism collects sections as marked by tags.
> This is why, I need to tag the org-footnote-section as well.

Why don't you also collect systematically the footnote section?

Regards,

-- 
Nicolas Goaziou

Re: [O] * [[shell:cat ~/tmp | grep "asdf :: "]] does not work.

[Nicolas Goaziou]

Hello,

Josef Atmin  writes:

> Well, one could also say [[shell:cat ~/tmp | grep "asdf :: "]] is link
> syntax, no matter how you look at it.  It is a question of precedence.

Of course. I'm just telling you how Org sees it.

> I think it is more obvious to interpret
>
>* [[ ... :: ... ]] 
>
> as a link syntax rather than a descrition list entry.

It's less interesting because it implies backtracking. Anyway, as said
previously, just put your link on the line below, and the problem is
solved.

> But even if the *  :: syntax takes precedence, then the folowing
> should work, I think, but it does not.
>
>* test :: [[shell:cat ~/tmp | grep "asdf :: "]]
>
> If I klick on the link, I still get the errror message "No link
> found".

This is because tag matches to the last "::" in the line. Without that,
you cannot have "::" in a tag.

Regards,

-- 
Nicolas Goaziou

[O] How do I format numbers to an exported table to latex, produced by a code block?

[Diogo Ramos]

I have the following org file:

--8<---cut here---start->8---
#+BEGIN_SRC python :exports both
  import numpy as np

  return np.matrix([[.123456789, 2], [3, 4]])
#+END_SRC

#+RESULTS:
| 0.12345679 | 2 |
|  3 | 4 |
--8<---cut here---end--->8---

I want to export it to latex to produce a pdf but I want to format the
numbers of the table so I get, say

| 123.456e-3 | 2.000 |
|  3.000 | 4.000 |

on the exported pdf.

How can I do it?

Re: [O] issues with org-contacts

[Andreas Reuleaux]

Nicolas Goaziou  writes:

> It looks like a lexical binding problem. We switched "org.el" to lexical
> binding in development version. You may be having a mixed installation,
> somehow.
>
> Regards,

Ah, OK, thanks a lot (and as already answered in private e-mail):
I will take a closer look at my installation in terms of lexical
binding then.

-Andreas

Re: [O] Org-mode: How to render latex inside ~code~

[Lawrence Bottorff]

Got it set

(custom-set-variables ... '(org-pretty-entities t) ...

but nothing changed. ~> (cons 1 nil) \to (1)~ still outputs the raw \to
even though in the buffer it changes.

On Sat, Feb 27, 2016 at 8:41 PM, Thomas S. Dye  wrote:

> Aloha Lawrence,
>
> Lawrence Bottorff writes:
>
> > This seems a catch-22: I want to render code in an org-mode export (html
> or
> > latex pdf) where the snippet below done as a ~code block
> >
> >> (cons 1 nil) \to (1)
> >
> > actually renders \to as a proper right arrow (yields). Of course if I do
> the
> > snippet as inline latex
> >
> > $> (cons 1 nil) \to (1)$
> >
> > I get the properly rendered right arrow, but now it's not in the sans
> mono code
> > font. What can I do to have my cake and eat it too?
>
> \to is defined in org-entities.  Do you get what you want by setting
> org-pretty-entities non nil?
>
> All the best,
> Tom
>
> --
> Thomas S. Dye
> http://www.tsdye.com
>

Re: [O] Org-mode: How to render latex inside ~code~

[Thomas S . Dye]

Aloha Lawrence,

Lawrence Bottorff writes:

> This seems a catch-22: I want to render code in an org-mode export (html or
> latex pdf) where the snippet below done as a ~code block
>
>> (cons 1 nil) \to (1)
>
> actually renders \to as a proper right arrow (yields). Of course if I do the
> snippet as inline latex
>
> $> (cons 1 nil) \to (1)$
>
> I get the properly rendered right arrow, but now it's not in the sans mono 
> code
> font. What can I do to have my cake and eat it too?

\to is defined in org-entities.  Do you get what you want by setting
org-pretty-entities non nil?

All the best,
Tom

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

[O] Org-mode: How to render latex inside ~code~

[Lawrence Bottorff]

This seems a catch-22: I want to render code in an org-mode export (html or
latex pdf) where the snippet below done as a ~code block

> (cons 1 nil) \to (1)

actually renders \to as a proper right arrow (yields). Of course if I do
the snippet as inline latex

$> (cons 1 nil) \to (1)$

I get the properly rendered right arrow, but now it's not in the sans mono
code font. What can I do to have my cake and eat it too?

LB

Re: [O] non-standard link errors

[Skip Collins]

Nicolas Goaziou  wrote:
> Skip Collins  writes:
> > Org throws an error when I export html with a link type that it does
> > not know about. I would like it to simply add the link to the exported
> > document without checking its validity. For example, I have a link
> > that, when tapped on an iPhone, will open a particular app. I would
> > like the html to look something like:
> > Connect using FaceTime
> >
> > The link works on an iPhone. But Org won't generate the html. Other
> > apps uses x-callback-url links formatted like this:
> > x-appname://x-callback-url/import?=Open%20Mail.app.
> >
> > These also do not work. Short of adding every type I might want to use
> > with org-add-link-type, is it possible to disable the export error and
> > just pass links through as written?
>
> It is possible in development version, where a variable controlling how
> link errors should be handled was introduced.

I added this line to the top of my org file:
#+OPTIONS: broken-links:t

But that eliminates both the link and its description from the export.
Changing it from 't' to 'mark' puts a BROKEN LINK message in the
output. I suggest adding a new option 'pass' that would simply pass
"broken" links verbatim into the output.

Re: [O] Possible bug in LaTeX export of special blocks

[Thomas S . Dye]

Aloha Nicolas,

Nicolas Goaziou writes:
>>
>> The blank line after \label{orgspecialblock1} causes the equation number
>> to be set on the following line, rather than to the right of the
>> equation.  My expectation is there is no blank line after the \label,
>> which yields the desired behavior.
>
> Fixed in maint. Thank you.

Perfect.  Thanks!

All the best,
Tom

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

Re: [O] [bug] inserting footnotes via org-footnote-action command

[Martin Carlé]

Thanks for inviting me to elaborate.

Well, I wrapped the exporter mechanism into some advice functions that
allow for many different exports from a single file in such a manner that
multiple exports are not restricted to subtrees.

This extended export mechanism collects sections as marked by tags.
This is why, I need to tag the org-footnote-section as well.

Best regards,
mc


On 2016-02-27 Sat 10:16, Nicolas Goaziou wrote:

> Hello,
>
> Martin Carlé  writes:
>
>> Keeping the tags is actually crucial to my practice, since I run some
>> filters during export based on tags.
>>
>> Couldn't the algorithm be adopted to check for tags assigned to the
>> org-footnote-section and then re-create them as well?
>
> Footnote section is special, so, in a sense, is a tag on its own.
> Besides, export process completely ignores this section. So, I'm not
> sure about what you want to achieve with tagging it. Would you want to
> elaborate a bit?
>
>
> Regards,


-- 
Fetch my gnupg key:
gpg --keyserver pgp.mit.edu --recv-keys 7E3CA33F


smime.p7s
Description: S/MIME cryptographic signature

Re: [O] * [[shell:cat ~/tmp | grep "asdf :: "]] does not work.

[Josef Atmin]

Dear Nicolas!

On Wed, Feb 24, 2016 at 06:38:09PM +0100, Nicolas Goaziou wrote:
> Hello,
> 
> Josef Atmin  writes:
> 
> >> when a shell command in an unnumbered list includes '::', it is not 
> >> recognized as a shell
> >> command anymore.
> >> 
> >> To reproduce the bug, paste the following two lines in file 'tmp'
> >> 
> >>   asdf :: asdf
> >>   asdf :: qwer
> >> 
> >> and add the following shell commands to an org file
> >> 
> >>* [[shell:cat ~/tmp | grep "asdf :"]]
> >>* [[shell:cat ~/tmp | grep "asdf ::"]]
> >>* [[shell:cat ~/tmp | grep "asdf :: "]]
> >> 
> >> If you klick on them you will probably find that the first two work while 
> >> the last one
> >> does not, presumably because it is interpreted as a description list entry.
> >> Interestingly, if you use a numbered list
> >> 
> >>1. [[shell:cat ~/tmp | grep "asdf :"]]
> >>2. [[shell:cat ~/tmp | grep "asdf ::"]]
> >>3. [[shell:cat ~/tmp | grep "asdf :: "]]
> >> 
> >> then all three work.
> 
> This is not a bug. -  :: *is* description list syntax, no matter how
> you look at it. You can easily work around this, e.g., by starting the
> link on the next line.

Well, one could also say [[shell:cat ~/tmp | grep "asdf :: "]] is link
syntax, no matter how you look at it.  It is a question of precedence.
I think it is more obvious to interpret

   * [[ ... :: ... ]] 

as a link syntax rather than a descrition list entry.

But even if the *  :: syntax takes precedence, then the folowing
should work, I think, but it does not.

   * test :: [[shell:cat ~/tmp | grep "asdf :: "]]

If I klick on the link, I still get the errror message "No link found".

Best regards,

Josef.

Re: [O] Bug: HTML export fails to set source IDs correctly [8.3.4 (8.3.4-elpa @ /Users/aaron/.emacs.d/elpa/org-20160222/)]

[Nicolas Goaziou]

Hello,

Aaron Miller  writes:

> Can you provide some insight on why the behavior was changed?

You needed to conform your labels to the target language, i.e, make sure
the label didn't contain any forbidden characters, which you were
expected to know.

`org-latex-prefer-user-labels' explains it very well. It is for `latex'
back-end only, however.


Regards,

-- 
Nicolas Goaziou

Re: [O] issues with org-contacts

[Nicolas Goaziou]

Hello,

Andreas Reuleaux  writes:

> I have been using Julien Danjou's org-contacts for a while now,
> cf
>
>   http://orgmode.org/worg/org-contrib/
>   org-contacts.el – manage contacts
>  Written by Julien Danjou. Link to raw file.
>   https://julien.danjou.info/projects/emacs-packages#org-contacts
>
> and happily so far, ie. I haven't changed my config.
>
> I would eg. type
>
> st+ in my To: field of a message, that I am composing
>
>   To: st+
>
> hit tab, and the contact address would be completed from my
> (list of) org-contacts-files (find an address matching st...)
>
> When I do so (hit tab ie.) in my current environment: emacs (24.5.1) / org 
> (8.2.10,
> the one that comes with emacs, as I understand), on debian testing ie., I get:
>
>   org-make-tags-matcher: `org-make-tags-matcher' expects todo-only to be 
> scoped in
>  
> I get the same error message, when I use a newer org version (8.3.3),
> install the debian package org-mode ie.
>
> I did contact Julien about this issue, but he pointed me to the org mailing
> list instead, as he isn't maintaining the code any more.
>
> Can anyone first: confirm my issue, and then: point me in the right
> direction, please?

It looks like a lexical binding problem. We switched "org.el" to lexical
binding in development version. You may be having a mixed installation,
somehow.

Regards,

-- 
Nicolas Goaziou

Re: [O] Possible bug in LaTeX export of special blocks

[Nicolas Goaziou]

Hello,

Thomas S. Dye  writes:

> Exporting these two special blocks to LaTeX
>
> ,--
> | #+name: eq:foobar
> | #+begin_equation 
> | foo = bar
> | #+end_equation   
> |  
> | #+begin_equation 
> | bar = baz
> | #+end_equation   
> `--
>
> yields this in the tex file
>
> ,-
> | \begin{equation}
> | foo = bar   
> | \label{orgspecialblock1}
> | 
> | \end{equation}  
> | 
> | \begin{equation}
> | bar = baz   
> | \end{equation}  
> `-
>
> The blank line after \label{orgspecialblock1} causes the equation number
> to be set on the following line, rather than to the right of the
> equation.  My expectation is there is no blank line after the \label,
> which yields the desired behavior.

Fixed in maint. Thank you.

Regards,

-- 
Nicolas Goaziou

Re: [O] Renaming ITEM in column view causes problems

[Nicolas Goaziou]

Hello,

David Jacobs  writes:

> The following example shows how renaming the ITEM column in column view 
> causes the parent heading to show up. Anyone know how to fix this?
>
> ** Bad Summary
> #+BEGIN: columnview :skip-empty-rows t :id "bad"
> | Name   | Nick |
> |+--|
> | ** Contact Information |  |
> | *** John Doe   | Jon  |
> #+END
>
> ** Contact Information
> :PROPERTIES:
> :ID:  bad 
> :COLUMNS: %20ITEM(Name) %Nick
> :END:
> *** John Doe
> :PROPERTIES:
> :Nick: Jon
> :END:
>  
>   
> ** Good Summary
> #+BEGIN: columnview :skip-empty-rows t :id "good"
> | ITEM | Nick |
> |--+--|
> | *** John Doe | Jon  |
> #+END
>
> ** Contact Information
> :PROPERTIES:
> :ID:  good 
> :COLUMNS: %20ITEM %Nick
> :END:
> *** John Doe
> :PROPERTIES:
> :Nick: Jon
> :END:

This was fixed, along with other issues related to Column view, in
development version.

Regards,

-- 
Nicolas Goaziou