[O] open link in source code block

2019-01-04 Thread Win Treese
I suspect that this has come up before, but I couldn’t find anything about it 
in the mailing list archives.

Suppose I have the following Org file contents:

* test
#+BEGIN_SRC emacs-lisp
(setq yyy 3)
;; See https://www.gnu.org
#+END_SRC

The URL for gnu.org is highlighted as a clickable link. But if I click it, the 
source block is evaluated. This seems rather unexpected, especially since my 
intention was to open the link.

I don’t know if this is a bug or if it’s the intended behavior. Or if there is 
a setting I have missed.

Version information: Aquamacs 3.5 on Mac OS 10.13.6, based on Emacs 25.3.50.1, 
Org version 9.2. Started Aquamacs with -q, then ran (package-initialize) so 
that it would find the current MELPA version of Org. No other configuration 
code was run.

Thanks for any insight.

Win Treese
tre...@acm.org






Re: [O] org-ref exports nicely to html but not to odt

2019-01-04 Thread Uwe Brauer
>>> "Ken" == Ken Mankoff  writes:

   > On 2019-01-04 at 22:37 +0100, Uwe Brauer  wrote:
   >> I exported the org file in question to latex (I could also start
   >> directly with latex for that matter.)

   > Yes.

   >> Could I stick with bibtex?

   > Yes. No need to use biber + biblatex, you can stick with bibtex.

   > I only run that command because my massive 3000+ bib file contains
   > things that pandoc has trouble with (accents? Not sure). That command
   > extracts the bibtex entries used in the current document.

   > As I write this I realize this means you don't even need to compile
   > the PDF and/or run bibtex. If you have a TeX file and an appropriate
   > accompanying BiBTeX file, that should work.

   >> pandoc -f latex -t docx -o test.docx --bibliography 
/home/oub/texmf/bibtex/bib/bibgraf.bib  test.tex
   >> 
   >> /home/oub/texmf/bibtex/bib/bibgraf.bib is my main bibtex date base.
   >> 
   >> But this did not work pandoc gets frozen.
   >> 
   >> What do I miss.

   > I don't know. Try with a small bib file with 1 entry (and a TeX file
   > that only cites that one entry). Does that work? Then maybe your
   > bibgraf.bib has the same problem mine does (although I recall pandoc
   > issuing an error and crashing, not just freezing).


I tried that and it did not work neither, I might need to write the
pandoc list.


smime.p7s
Description: S/MIME cryptographic signature


Re: [O] org-ref exports nicely to html but not to odt

2019-01-04 Thread Ken Mankoff


On 2019-01-04 at 22:37 +0100, Uwe Brauer  wrote:
> I exported the org file in question to latex (I could also start
> directly with latex for that matter.)

Yes.

> Could I stick with bibtex?

Yes. No need to use biber + biblatex, you can stick with bibtex.

I only run that command because my massive 3000+ bib file contains things that 
pandoc has trouble with (accents? Not sure). That command extracts the bibtex 
entries used in the current document.

As I write this I realize this means you don't even need to compile the PDF 
and/or run bibtex. If you have a TeX file and an appropriate accompanying 
BiBTeX file, that should work.

> pandoc -f latex -t docx -o test.docx --bibliography 
> /home/oub/texmf/bibtex/bib/bibgraf.bib  test.tex
>
> /home/oub/texmf/bibtex/bib/bibgraf.bib is my main bibtex date base.
>
> But this did not work pandoc gets frozen.
>
> What do I miss.

I don't know. Try with a small bib file with 1 entry (and a TeX file that only 
cites that one entry). Does that work? Then maybe your bibgraf.bib has the same 
problem mine does (although I recall pandoc issuing an error and crashing, not 
just freezing).

If this method works with a MWE, then the issue my be your full bib file. In 
this case you need to extract the entries used in this document (e.g. my 
method). Presumably this subset does not cause the pandoc issue. I also find 
extracting the entries useful for archiving a project.

You can extract entries as I showed, or "bibexport .aux" (requires a 
compiled PDF), or 
http://korrekt.org/page/Note:How_to_Extract_Used_Entries_From_BibTeX_Files or 
other methods...

  -k.



Re: [O] org-ref exports nicely to html but not to odt

2019-01-04 Thread John Kitchin
I have used pandoc a little a while ago.   See
http://kitchingroup.cheme.cmu.edu/blog/2015/01/29/Export-org-mode-to-docx-with-citations-via-pandoc/

If you search pandoc on my blog you may find some more.

On Fri, Jan 4, 2019 at 5:28 PM Uwe Brauer  wrote:

> >>> "Ken" == Ken Mankoff  writes:
>
>> On 2019-01-04 at 22:37 +0100, Uwe Brauer  wrote:
>>> I exported the org file in question to latex (I could also start
>>> directly with latex for that matter.)
>
>> Yes.
>
>>> Could I stick with bibtex?
>
>> Yes. No need to use biber + biblatex, you can stick with bibtex.
>
>> I only run that command because my massive 3000+ bib file contains
>> things that pandoc has trouble with (accents? Not sure). That command
>> extracts the bibtex entries used in the current document.
>
>> As I write this I realize this means you don't even need to compile
>> the PDF and/or run bibtex. If you have a TeX file and an appropriate
>> accompanying BiBTeX file, that should work.
>
>>> pandoc -f latex -t docx -o test.docx --bibliography
> /home/oub/texmf/bibtex/bib/bibgraf.bib  test.tex
>>>
>>> /home/oub/texmf/bibtex/bib/bibgraf.bib is my main bibtex date base.
>>>
>>> But this did not work pandoc gets frozen.
>>>
>>> What do I miss.
>
>> I don't know. Try with a small bib file with 1 entry (and a TeX file
>> that only cites that one entry). Does that work? Then maybe your
>> bibgraf.bib has the same problem mine does (although I recall pandoc
>> issuing an error and crashing, not just freezing).
>
>
> I tried that and it did not work neither, I might need to write the
> pandoc list.
>
-- 
John

---
Professor John Kitchin
Doherty Hall A207F
Department of Chemical Engineering
Carnegie Mellon University
Pittsburgh, PA 15213
412-268-7803
@johnkitchin
http://kitchingroup.cheme.cmu.edu


Re: [O] Change in order of tag collation from #+filetags plus heading tags [Regression 9.1 -> 9.2]

2019-01-04 Thread Kaushal Modi
On Fri, Jan 4, 2019 at 8:15 AM Nicolas Goaziou 
wrote:

>
> The order of tags is unspecified, either in the docstring, in the
> manual, or in the syntax. So it doesn't really matter.
>

This regression was caught by one of the ox-hugo tests. I'd to like to fix
it to the former tag order because I think it makes sense to have the
#+filetags tags in the very beginning instead of embedding it between the
parent heading tags and local tags.


> Feel free to provide a patch if it bothers you.
>

Here is the proposed rough patch; locally I also have a test ready that
tests this regression.

=
diff --git a/lisp/org.el b/lisp/org.el
index 2273a6997..15744704a 100644
--- a/lisp/org.el
+++ b/lisp/org.el
@@ -14607,11 +14607,11 @@ Inherited tags have the `inherited' text
property."
 (org-back-to-heading t)
 (let ((ltags (org--get-local-tags)) itags)
   (if (or local (not org-use-tag-inheritance)) ltags
-(setq itags org-file-tags)
 (while (org-up-heading-safe)
   (setq itags (append (mapcar #'org-add-prop-inherited
   (org--get-local-tags))
   itags)))
+(setq itags (append org-file-tags itags))
 (delete-dups
  (append (org-remove-uninherited-tags itags) ltags
=

I am also copying Matt Lundin as I believe that this commit[1] caused this
regression.

If above looks good, I will go ahead the commit this patch with test,
proper commit log, etc.

Thanks for reviewing.

[1]:
https://code.orgmode.org/bzg/org-mode/commit/5e27b2fd326810e4ed876b094df852338909c1f8


Re: [O] org-ref exports nicely to html but not to odt

2019-01-04 Thread Uwe Brauer
>>> "Ken" == Ken Mankoff  writes:

   > On 2019-01-04 at 18:08 +0100, Uwe Brauer  wrote:
   >> When I export it to html, the bibliography comes out nice. When I
   >> export it to odt, the resulting odt files contains a lot of rubbish.
   >> 
   >> A kludge is to export it to html and then open it with LO/OO and copy
   >> it in an empty odt file, but is there any other solution?

   > I find the best ODT comes from LaTeX -> pandoc -> ODT. I have the
   > following section at the bottom of my default Org template
   > workbook.


That sounds very promising. But I am a bit confused.

I exported the org file in question to latex (I could also start
directly with latex for that matter.)

Now I can run without a problem bibtex on that file and several times
latex. But you propose to use biber which I have never used.

So when I run in the command line 
biber test.tex --output_format bibtex
INFO - This is Biber 2.4
INFO - Logfile is 'test.tex.blg'
ERROR - Cannot find control file 'test.tex.bcf'! - did you pass the 
"backend=biber" option to BibLaTeX?
INFO - ERRORS: 1


Could I stick with bibtex?

Now suppse I can then 
I tried 

pandoc -f latex -t docx -o test.docx --bibliography 
/home/oub/texmf/bibtex/bib/bibgraf.bib  test.tex

/home/oub/texmf/bibtex/bib/bibgraf.bib is my main bibtex date base.

But this did not work 
pandoc gets frozen.

What do I miss.

Thanks

Uwe 


smime.p7s
Description: S/MIME cryptographic signature


Re: [O] org-ref exports nicely to html but not to odt

2019-01-04 Thread Ken Mankoff


On 2019-01-04 at 18:08 +0100, Uwe Brauer  wrote:
> When I export it to html, the bibliography comes out nice. When I
> export it to odt, the resulting odt files contains a lot of rubbish.
>
> A kludge is to export it to html and then open it with LO/OO and copy
> it in an empty odt file, but is there any other solution?

I find the best ODT comes from LaTeX -> pandoc -> ODT. I have the following 
section at the bottom of my default Org template workbook.

  -k.



* DOCX  :noexport:

Exporting to DOCX by using pandoc to convert the LaTeX export to DOCX seems to 
work much better than using Org directly. This means you need to export to 
LaTeX, properly compile the latex (to get the references correct), then run the 
BibTeX code block below 1x (and re-run each time you update any references), 
then run the Pandoc code block to convert the TeX file to DOCX.

** BibTeX   :noexport:
#+BEGIN_SRC sh :results verbatim :var fn=(file-name-sans-extension 
(buffer-name))
biber ${fn} --output_format bibtex
#+END_SRC
#+RESULTS:

** Pandoc
#+BEGIN_SRC sh :results verbatim :var fn=(file-name-sans-extension 
(buffer-name))
pandoc -f latex -t docx -o ${fn}.docx --bibliography ./${fn}_biber.bib ${fn}.tex
#+END_SRC
#+RESULTS:



Re: [O] org-ref exports nicely to html but not to odt

2019-01-04 Thread John Kitchin
It is identical to the html output, it just that odt doesn't render the
html tags. You can just customize that variable to get rid of the html
markers, and then it will look better. I don't know how to get bold/italics
in odt though.

John

---
Professor John Kitchin
Doherty Hall A207F
Department of Chemical Engineering
Carnegie Mellon University
Pittsburgh, PA 15213
412-268-7803
@johnkitchin
http://kitchingroup.cheme.cmu.edu



On Fri, Jan 4, 2019 at 3:43 PM Uwe Brauer  wrote:

> >>> "John" == John Kitchin  writes:
>
>> Export to backends other than LaTeX have pretty limited support.
>> I assume by a lot of rubbish you mean there is a lot of html markers
> in
>> the bibliography.
>
> Right.
>
>> You can customize how these are formatted to some extent in the
>> variable: org-ref-bibliography-entry-format
>
>> This is not a citation preprocessor though, so it will not do things
>> like numbered references, or handle markup in the bibtex entries.
>
> I would be happy if the odt output were similar or identical to the
> html output.
>
>
>> You might check out https://github.com/andras-simonyi/citeproc-org,
> it
>> might have more capability along those lines.
>
> Thanks
>
>


Re: [O] org-ref exports nicely to html but not to odt

2019-01-04 Thread Uwe Brauer
>>> "John" == John Kitchin  writes:

   > Export to backends other than LaTeX have pretty limited support.
   > I assume by a lot of rubbish you mean there is a lot of html markers in
   > the bibliography.

Right.

   > You can customize how these are formatted to some extent in the
   > variable: org-ref-bibliography-entry-format

   > This is not a citation preprocessor though, so it will not do things
   > like numbered references, or handle markup in the bibtex entries.

I would be happy if the odt output were similar or identical to the
html output.


   > You might check out https://github.com/andras-simonyi/citeproc-org, it
   > might have more capability along those lines.

Thanks



smime.p7s
Description: S/MIME cryptographic signature


Re: [O] org-ref exports nicely to html but not to odt

2019-01-04 Thread John Kitchin
Export to backends other than LaTeX have pretty limited support.

I assume by a lot of rubbish you mean there is a lot of html markers in
the bibliography.

You can customize how these are formatted to some extent in the
variable: org-ref-bibliography-entry-format

This is not a citation preprocessor though, so it will not do things
like numbered references, or handle markup in the bibtex entries.

You might check out https://github.com/andras-simonyi/citeproc-org, it
might have more capability along those lines.

Uwe Brauer  writes:

> Hi
>
> Please look at the following example
>
> #+begin_example
> *  Bibliography
>
> citep:tao08:_global
>
> bibliographystyle:plain
> bibliography:test.bib
>
> #+end_example
>
> When I export it to html, the bibliography comes out nice.
> When I export it to odt, the resulting odt files contains a lot of
> rubbish.
>
> A kludge is to export it to html and then open it with LO/OO and copy
> it in an empty odt file, but is there any other solution?
>
> regards
>
> Uwe Brauer


--
Professor John Kitchin
Doherty Hall A207F
Department of Chemical Engineering
Carnegie Mellon University
Pittsburgh, PA 15213
412-268-7803
@johnkitchin
http://kitchingroup.cheme.cmu.edu



Re: [O] how using TexLive on a website like in org-mode?

2019-01-04 Thread Joseph Vidal-Rosset
Many thanks Eric, I am going to have a look on section 13 of the manual.

Best wishes,

Jo.

Le ven. 4 janv. 2019 à 18:53, Eric S Fraga  a écrit :

> On Friday,  4 Jan 2019 at 18:17, Joseph Vidal-Rosset wrote:
> > I have a dedicated server for a personal website and I wonder how it is
> > possible to use texlive as most as possible into html webpages, in the
> > same way that we export via org-mode.
>
> I am not entirely sure I understand your question but could you
> "publish" the files using org?  See section 13 of the manual.
> --
> Eric S Fraga via Emacs 27.0.50, Org release_9.1.14-1035-gfeb442
>


Re: [O] how using TexLive on a website like in org-mode?

2019-01-04 Thread Eric S Fraga
On Friday,  4 Jan 2019 at 18:17, Joseph Vidal-Rosset wrote:
> I have a dedicated server for a personal website and I wonder how it is
> possible to use texlive as most as possible into html webpages, in the
> same way that we export via org-mode.

I am not entirely sure I understand your question but could you
"publish" the files using org?  See section 13 of the manual.
-- 
Eric S Fraga via Emacs 27.0.50, Org release_9.1.14-1035-gfeb442



[O] how using TexLive on a website like in org-mode?

2019-01-04 Thread Joseph Vidal-Rosset
Hello the list,

Happy New Year to everybody!

I have a dedicated server for a  personal website and I wonder how it is
possible to use  texlive as most as possible into  html webpages, in the
same way that we export via org-mode.

I would be glad  for example to use the proof.sty  package to import png
images like in this email, to get for example the image of this formal
derivation 

\[
\infer[^{L\lnot {\rm \mathit{def}}}]{\lnot \lnot P \Rightarrow P}{
  \infer[^{L\lnot {\rm \mathit{def}}}]{\lnot P \supset \bot \Rightarrow P}{
\infer[^{L\supset\supset}]{(P \supset \bot) \supset \bot \Rightarrow P}{
  \infer[^{{\rm \mathit{Ax_{c]{\bot \supset \bot, P \Rightarrow \bot, 
P}{}
  &
  \infer[^{L\bot}]{\bot \Rightarrow P}{}
}
  }
}
\]

in a html webpage easily. But I do  not know how to do. The CMS that I
am   using  is   /not/  WordPress,   but  SPIP
[[https://www.spip.net/en_rubrique25.html]]

Help would be very welcome.

Again, happy 2019 to everybody!

-- 
Jo. 

[O] org-ref exports nicely to html but not to odt

2019-01-04 Thread Uwe Brauer
Hi

Please look at the following example 

#+begin_example
*  Bibliography

citep:tao08:_global

bibliographystyle:plain
bibliography:test.bib

#+end_example

When I export it to html, the bibliography comes out nice.
When I export it to odt, the resulting odt files contains a lot of
rubbish.

A kludge is to export it to html and then open it with LO/OO and copy
it in an empty odt file, but is there any other solution?

regards

Uwe Brauer

@Article{tao08:_global,
  author   = {Tao, Terence},
  fjournal = {Current Developments in Mathematics},
  journal  = {Current Developments in Mathematics},
  pages= {255-340},
  publisher= {International Press of Boston},
  title= {Global behaviour of nonlinear dispersive and wave
  equations},
  url  = {https://projecteuclid.org:443/euclid.cdm/1223654544},
  volume   = 2006,
  year = 2008
}


Re: [O] Fix C-u C-c C-q (align all tags in visible buffer)

2019-01-04 Thread Nicolas Goaziou
Kaushal Modi  writes:

> Commited to maint, merged to master, with a test.

Great. Thank you!



Re: [O] Fix C-u C-c C-q (align all tags in visible buffer)

2019-01-04 Thread Kaushal Modi
Hello Nicolas,

On Fri, Jan 4, 2019 at 8:17 AM Nicolas Goaziou 
wrote:

> Hello,
>
>
> > If this looks good, I can commit this to maint and master.
>
> Sure. Please also provide a regression test for it.
>

Thank you.

Commited to maint, merged to master, with a test.

https://code.orgmode.org/bzg/org-mode/commit/539091799b370a1c452fe4952e8074d7dfe8656f


[O] TODO cycle in agenda column view clears the line.

2019-01-04 Thread Robert Mosher
When in agenda view with column view enabled hitting 't' clears the current
line so it displays as a blank line. There is no text there, so it is not a
font color issue.

Though it does actually cycle the TODO value of the line. In fact, you can
hit 't' again on the blank line and it will continue to update the TODO
state. So it is only a display issue, and not functional.

Refreshing the agenda will display that line again.

-Rob


Re: [O] [Patch] [Feature request] Add option to natively fontify latex snippets and environment

2019-01-04 Thread Nicolas Goaziou
Hello,

Carlos Pita  writes:

> I've improved the commit message to better align org mode conventions
> and also added a note to ORG-NEWS about the new feature.

Applied. Thank you.

Regards,

-- 
Nicolas Goaziou



Re: [O] Bug: Latex preview fg color w/tikz (known problem, fix suggested) [9.1.9 (release_9.1.9-65-g5e4542 @ /home/carlos/local/stow/emacs-26/share/emacs/26.1.90/lisp/org/)]

2019-01-04 Thread Nicolas Goaziou
Hello,

Carlos Pita  writes:

> I've improved the commit message to better fit org mode conventions
> and also added a note to ORG-NEWS about the new feature. Let me know
> if there still is something I should change or feel free to amend it
> to your liking.

Applied. Thank you!

> One question for future patches: is it ok to add a link to the mailing
> list thread where the issue was discussed in the commit message?

I usually do that for bugfixes, indeed.

Regards,

-- 
Nicolas Goaziou



Re: [O] Bug: Inconsistent usage of org-capture-get [9.2 (release_9.2 @ /Users/xristos/code/elisp/third-party/org-mode/lisp/)]

2019-01-04 Thread Nicolas Goaziou
Hello,

xristos  writes:

> At some point, the optional argument LOCAL was added to org-capture-get:
>
> (org-capture-get PROP  LOCAL)
>
> "When LOCAL is set, use the local variable ‘org-capture-current-plist’,
> this is necessary after initialization of the capture process,
> to avoid conflicts with other active capture processes."
>
> A lot of the org-capture-get calls in org-capture.el do not set LOCAL
> and suffer from aforementioned conflicts. The calls inside function 
> org-capture
> are exempt from this, but the calls inside org-capture-finalize that do not
> set LOCAL are obviously erroneous. There are more org-capture-get calls in
> other functions that have to be reviewed.

Do you want to provide a patch for that?

Regards,

-- 
Nicolas Goaziou



Re: [O] Fix C-u C-c C-q (align all tags in visible buffer)

2019-01-04 Thread Nicolas Goaziou
Hello,

Kaushal Modi  writes:

> This minor bug had been bothering me for a while and I eventually got to
> looking into the source code for it.
>
> As of current master, C-u C-c C-q doesn't work as in the doc-string i.e.
> "When optional argument ALL is non-nil, align all tags in the visible part
> of the buffer.".
>
> Here's an example Org buffer:
>
> =
> * Foo :abc:
> ** Bar :def:
> =
>
> - With point on Foo heading, C-u C-c C-q aligns only :def: tag (tags from
> *next* heading onwards).
> - So when point is on Bar, no tags get aligned.
>
> Though I remember that C-u C-c C-q worked quite some time back.
>
> A commit in Apr 28, 2018 broke that behavior in
> https://code.orgmode.org/bzg/org-mode/commit/1615261cdc5da6dbe50176d7958c775d6d54411e#diff-f9a90d66b3053f60bd4e8d63f214273067d0d28L14288
> .
>
> While I don't understand that entire commit, this simple fix brings back
> the true C-u C-c C-q behavior:
>
> diff --git a/lisp/org.el b/lisp/org.el
> index db3c11b5f..b8daa3bfc 100644
> --- a/lisp/org.el
> +++ b/lisp/org.el
> @@ -14203,8 +14203,10 @@ visible part of the buffer."
>  (org--align-tags-here (funcall get-indent-column))
>(save-excursion
>  (if all
> +(progn
> +  (goto-char (point-min))
>(while (re-search-forward org-tag-line-re nil t)
> -  (org--align-tags-here (funcall get-indent-column)))
> +(org--align-tags-here (funcall get-indent-column
>(org-back-to-heading t)
>(org--align-tags-here (funcall get-indent-column)))
>
>
> If this looks good, I can commit this to maint and master.

Sure. Please also provide a regression test for it.

Thank you.

Regards,

-- 
Nicolas Goaziou



Re: [O] Change in order of tag collation from #+filetags plus heading tags [Regression 9.1 -> 9.2]

2019-01-04 Thread Nicolas Goaziou
Hello,

Kaushal Modi  writes:

> I have noticed a minor regression in the order in which Org collects the
> "ALLTAGS" tags at point.
>
> Here is a simple Org file to reproduce that issue:
>
> =
>
> #+filetags: a
>
> * Level 1
> :b:
> ** Level 2
> :c:
> *** Level 3
> :d:
>
> =
>
> With point anywhere under ~* Level 3~ heading, evaluate:
>
> M-: (org-entry-get (point) "ALLTAGS")
>
>
> In Org 9.1.x, the order of tags returned was ":a:b:c:d:".
> But in Org 9.2, the order becomes ":b:c:a:d:".
>
> So, earlier (Org 9.1.x) the order was:
> 1. tags from filetags
> 2. tags from parent headings in order
> 3. current heading tags
>
> In Org 9.2, the order is:
> 1. *tags from parent headings in order*
> 2. *tags from filetags*
> 3. current heading tags
>
> Is this switch of order expected?

The order of tags is unspecified, either in the docstring, in the
manual, or in the syntax. So it doesn't really matter.

Feel free to provide a patch if it bothers you.

Regards,

-- 
Nicolas Goaziou



Re: [O] FW: [RFC] Link-type for attachments, more attach options

2019-01-04 Thread Feng Shu
Gustav Wikström  writes:


I like this feature very much!




> Hi,
>
>  
>
> I’ve attached a patch with some suggested additions to org-attach. Patch 
> comments below. Please review.
>
>  
>
> Kind regards
>
> Gustav
>
> ___
>
> Patch comments:
>
> * Add new linktype "attached" for attachments
>
>  
>
> A new linktype "attached" is added in order to reduce link-duplication
>
> when wanting to link to files in attached folders of nodes. This works
>
> for both ID-based attachments and ATTACH_DIR.  Inline images will
>
> trigger also for attachments, as well as search-decorations in the
>
> links.  The goal is to make the functionality for attached-links
>
> mirror file-links.
>
>  
>
> * Add further options for ATTACH_DIR
>
>  
>
> When working with ATTACH_DIR there are now a couple of new options available:
>
> - org-attach-dir-inherit-by-default
>
> - org-attach-dir-create-if-not-exist
>
> - org-attach-dir-relative
>
>  
>
> Descriptions of them can be found in the commit for each new customization.
>
>  
>
> * Documentation in org-manual
>
>  
>
> Org-manual is updated with the new link-type as well as some minor
>
> cleanup in the documentation related to external links and attachments.
>

-- 




[O] [feature] org table formula filters

2019-01-04 Thread Tobias Zawada
Hi,

The part "More complicated but very general solution" of the answer 
https://emacs.stackexchange.com/a/46862/2370 on Emacs SE defines input and 
output filters for table formulas.
The input filter filters the arguments before construction of the calc equation.
The output filter filters the calc result before printing it into the target 
cell.
In the SE answer the filters are used to convert between the calc duration 
syntax h@ m' s" and the duration syntax hh:mm:ss.
The filters could be a useful extension of org table formula modes.

Best regards,
Tobias