[O] Repeated tasks

[N. Raghavendra]

Is there a way to specify the timestamp for a repeated task which has to
be done on the second Sunday of every month?  I'd like the todo state of
the task to go back to TODO after it has been marked DONE, as described
in the section on repeated tasks in the Org manual.

Thanks,
Raghu.

PS: I am sorry if you get multiple copies of this message.  I use Gmane
to read this list, and tried to post this message through Gmane, but
didn't get the confirmation message from the Gmane auto-authorizer.  So
I am posting it now directly to the list.  Does anyone else have
similar difficulties posting through Gmane?

-- 
N. Raghavendra , http://www.retrotexts.net/
Harish-Chandra Research Institute, http://www.hri.res.in/

Re: [O] Bug: Write file while editing babel code block doesn't work as expected [8.3.4 (release_8.3.4-778-g8127b3 @ /usr/local/share/emacs/site-lisp/org/)]

[Aaron Ecay]

Hi Nicolas,

2016ko maiatzak 11an, Nicolas Goaziou-ek idatzi zuen:

> I changed this in developement version. If you get any chance to test
> it, Please tell me if it behaves as expected. Thank you.

Is this a correct change?  Previously, C-x C-s in the org-src buffer
would save the underlying .org file, which was useful.  AFAICS this now
would not work.  I also wonder whether autosave will work correctly from
the org-src buffer.  I think the other suggestion in this thread (to use
write-region) is a better solution.

-- 
Aaron Ecay

Re: [O] [BUG] Noweb reference eval syntax does not work

[Aaron Ecay]

Hi Rasmus, hi all,

2016ko maiatzak 8an, Rasmus-ek idatzi zuen:

[...]

> As you mention, we’d loose the ability to chain together multiple blocks.
> I reckon they are meaningfully the same language, so I don’t see a loss.
> The example shown in the manual also does not convince me of the
> usefullness of this.

Ditto.

> 
>> It is redundant with #+NAME: keyword and slightly broken. Also it
>> induces hacks like `org-babel-use-quick-and-dirty-noweb-expansion' to
>> work-around its shortcomings. 
>> 
>> Besides, it doesn't make much sense to add the same parameters to
>> a bunch of blocks, so I find the syntax dubious.
>> 
>> I understand it can be a handy shortcut for inserting multiple blocks,
>> but, all in all, I tend to think it would be simpler to just remove the
>> feature, along with `:noweb-sep' and
>> `org-babel-use-quick-and-dirty-noweb-expansion'.
> 
> I’m happy to kill it off in Org-9.  I don’t know how widely the chaining
> of blocks is used, though, and whether the fix is always as simple as
> uniting the blocks.

I think that we can provide a replacement to noweb-ref as follows:

* Code blocks
:PROPERTIES:
:header-args: :noweb-ref foo
:END:

#+begin_src python
block 1
#+end_src

#+begin_src python
block 2
#+end_src

* Concat

The old way

#+begin_src python
<>
#+end_src

The new way:

#+begin_src python
<>
#+end_src

concat-blocks-of-lang-in-headline would have to be an elisp source block
implementing the appropriate behavior which is present in the document
or in the library of babel.

(And I think it would be good if the LoB contained some useful
predefined blocks like this one, in addition to those added by the
user.  A “standard library of babel” as it were.)

> 
>> What do you, and others, think? Is NAME enough for noweb syntax, or is
>> there a real need fo :noweb-ref?

To put it another way: it seems to me that the functionality of
:noweb-ref can be reimplemented in terms of other primitives.  And given
Nicolas’s comments about the complications and bugs it introduces, I’d
be in favor of deprecating and eventually removing it.

-- 
Aaron Ecay

[O] Disabling completion during capture

[Samuel W. Flint]

OK, so I have an issue with capture and completion.  On the following
template:

#+BEGIN_SRC org
* %^{Subject?}
:PROPERTIES:
:CREATED: %T
:END:

%?
#+END_SRC

When I go to capture, and I enter my value for the ~%^{Subject?}~
prompt, as soon as I hit "space", I get an window pop-up about "No
Completions".  As of now, the only way to put a space in as I enter it
is to use C-q.  What can I do to fix this.

Thanks,

Sam

--
Samuel W. Flint
4096R/266596F4
  (9477 D23E 389E 40C5 2F10  DE19 68E5 318E 2665 96F4)
(λs.s s) λs.s s

Re: [O] Bug: org -> org export ignores latex blocks [8.3.4 (8.3.4-50-g83e373-elpaplus @ /home/andrea/.emacs.d/elpa/org-plus-contrib-20160509/)]

[Andrea]

Okay, I have deleted the org one and left the org-contrib:
I can still use the new feature (probably org-contrib enables it).
Thanks for your explanation,

Andrea

Kaushal Modi  writes:

> On Thu, May 12, 2016 at 6:20 PM Andrea  wrote:
>
>> I think I saw that, but I did not read it carefully. And since the
>> autocompletion (I mean > not occur to me that may be the problem.
>>
>> By the way, I did not clone the git repo, so I should be on the master
>> published on ELPA.
>
>
> The versions published on ELPA are from the maint branch of org git.
>
>
>> When I give org-version in emacs I get:
>> Org-mode version 8.3.4 (8.3.4-50-g83e373-elpaplus @
>> /home/andrea/.emacs.d/elpa/org-plus-contrib-20160509/)
>>
>> On package-list-packages I have
>>
>>   org20160509  installed Outline-based
>> notes management and organizer
>>   org-plus-contrib   20160509  installed Outline-based
>> notes management and organizer
>>
>
> Correct, both are the exact same stable 8.3.x versions; just that
> org-plus-contrib has the packages in contrib/ folder which the other does
> not have.
>
> Also installing just org-plus-contrib should suffice. You do not need to
> install both. If you are not using any package from the contrib/ area (
> http://orgmode.org/cgit.cgi/org-mode.git/tree/contrib/lisp?h=maint ), you
> do not need org-plus-contrib, and you can use just the org package.
>
> But the mystery is still unresolved for me.. why did #+BEGIN_EXPORT syntax
> work for you .. May be someone else more knowledgeable can answer that.
> -- 

Re: [O] Bug: org -> org export ignores latex blocks [8.3.4 (8.3.4-50-g83e373-elpaplus @ /home/andrea/.emacs.d/elpa/org-plus-contrib-20160509/)]

[Kaushal Modi]

On Thu, May 12, 2016 at 6:20 PM Andrea  wrote:

> I think I saw that, but I did not read it carefully. And since the
> autocompletion (I mean  not occur to me that may be the problem.
>
> By the way, I did not clone the git repo, so I should be on the master
> published on ELPA.


The versions published on ELPA are from the maint branch of org git.


> When I give org-version in emacs I get:
> Org-mode version 8.3.4 (8.3.4-50-g83e373-elpaplus @
> /home/andrea/.emacs.d/elpa/org-plus-contrib-20160509/)
>
> On package-list-packages I have
>
>   org20160509  installed Outline-based
> notes management and organizer
>   org-plus-contrib   20160509  installed Outline-based
> notes management and organizer
>

Correct, both are the exact same stable 8.3.x versions; just that
org-plus-contrib has the packages in contrib/ folder which the other does
not have.

Also installing just org-plus-contrib should suffice. You do not need to
install both. If you are not using any package from the contrib/ area (
http://orgmode.org/cgit.cgi/org-mode.git/tree/contrib/lisp?h=maint ), you
do not need org-plus-contrib, and you can use just the org package.

But the mystery is still unresolved for me.. why did #+BEGIN_EXPORT syntax
work for you .. May be someone else more knowledgeable can answer that.
-- 

-- 
Kaushal Modi

Re: [O] Bug: org -> org export ignores latex blocks [8.3.4 (8.3.4-50-g83e373-elpaplus @ /home/andrea/.emacs.d/elpa/org-plus-contrib-20160509/)]

[Andrea]

I think I saw that, but I did not read it carefully. And since the
autocompletion (I mean  writes:

>
> But I am surprised that that fix applied to your org-plus-contrib version.
>
> It applies only to the version built from the master branch. Is
> org-plus-contrib the only version that you have installed? Or do you have
> multiple versions of org installed, including the one from org git?
> -- 

Re: [O] Bug: org -> org export ignores latex blocks [8.3.4 (8.3.4-50-g83e373-elpaplus @ /home/andrea/.emacs.d/elpa/org-plus-contrib-20160509/)]

[Kaushal Modi]

On Thu, May 12, 2016 at 5:38 PM Andrea  wrote:

> Hello,
>
> thanks for the fast reply. It actually works with the new syntax, thank
> you!
> There is a minor thing though: when I export a #+BEGIN_export latex to
> an org buffer, it exports to #+BEGIN_export (without the latex). Maybe
> this is a bug?
> Thanks,
>
> Andrea
>
> P.S: I did not know about these changes, I will look forward for them!
>


This was announced here on the list (
https://lists.gnu.org/archive/html/emacs-orgmode/2015-12/msg00525.html ).
It is also in ORG-NEWS for version 9.0 (
http://orgmode.org/cgit.cgi/org-mode.git/tree/etc/ORG-NEWS#n11 ).

But I am surprised that that fix applied to your org-plus-contrib version.

It applies only to the version built from the master branch. Is
org-plus-contrib the only version that you have installed? Or do you have
multiple versions of org installed, including the one from org git?
-- 

-- 
Kaushal Modi

Re: [O] Bug: org -> org export ignores latex blocks [8.3.4 (8.3.4-50-g83e373-elpaplus @ /home/andrea/.emacs.d/elpa/org-plus-contrib-20160509/)]

[Andrea]

Hello,

thanks for the fast reply. It actually works with the new syntax, thank
you!
There is a minor thing though: when I export a #+BEGIN_export latex to
an org buffer, it exports to #+BEGIN_export (without the latex). Maybe
this is a bug?
Thanks,

Andrea

P.S: I did not know about these changes, I will look forward for them!

John Hendy  writes:

> Ah. I always wondered about that since the change is reported for 9.0
> but it's in effect for me on:
>
> Org-mode version 8.3.4 (release_8.3.4-753-gda4db33 @ ~/.elisp/org/lisp/)
>
> But I've obviously built from git. Simple case would be for Andrea to
> just try it and let us know :) Other than that, I'd defer to Nicholas
> to say whether or not this should be going on.
>
>
> Thanks for the clarification,
> John
>
> On Thu, May 12, 2016 at 1:57 PM, Kaushal Modi  wrote:
>> On Thu, May 12, 2016 at 2:53 PM John Hendy  wrote:
>>>
>>> I believe this is due to the new syntax change for export blocks
>>> announced a bit back. See:
>>> - http://orgmode.org/cgit.cgi/org-mode.git/plain/etc/ORG-NEWS
>>>
>>> Try this instead:
>>>
>>> * Hello
>>> #+BEGIN_export latex
>>> hi I am latex
>>> #+END_export
>>
>>
>> I was going to say the same but then I saw that Andrea is using an
>> org-plus-contrib version. The new syntax would go in effect in org 9.0 or
>> for someone using org built from the master branch.
>>
>> It should not affect users using org from maint branch or
>> org/org-plus-contrib from Org Elpa.
>> --
>>
>> --
>> Kaushal Modi

Re: [O] No output from babel shell src block

[Thomas S. Dye]

John Hendy writes:

> There's no worg page for the shell language (surprised me!).

Several babel languages in core lack documentation on Worg in addition
to shell: calc, comint, coq, ebnf, emacs-lisp(!), forth, fortran,
haskell, io, java, javascript, objective caml, org(!!!), perl, plantuml,
processing, ruby, sass, scala, scheme, sed, and shen.

You've already contributed to the documentation effort (thanks!), but
potential volunteers might visit here for a documentation template:
http://orgmode.org/worg/org-contrib/babel/languages.html#develop

It's not such a big job to write the babel documentation, but it
certainly helps to understand the language being documented :-)

All the best,
Tom

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

Re: [O] No output from babel shell src block

[Ken Mankoff]

This is a known issue with diff, I think. Add a line containing ":" below, or 
"echo" or "diff foo bar | cat".

https://stackoverflow.com/questions/27304469/capturing-the-output-of-diff-with-org-babel

I have

(setq org-babel-default-header-args:sh
  '((:prologue . "exec 2>&1") (:epilogue . ":"))
)

so that stderr is always displayed in the RESULTS block.

  -k.
  
On 2016-05-12 at 15:24, John Hendy  wrote:
> Hello,
>
>
> I've not used shell in babel much, and am confused. I was trying to
> include diff output from a block in an analysis and it's not giving
> any output.
>
> As a test, I have a.txt which contains 1 and b.txt which contains 2,
> with boths in ~/Desktop.
>
> Manually:
> $ cd ~/Desktop
> $ diff a.txt b.txt
> 1c1
> < 1
> ---
>> 2
>
> Org:
> #+begin_src shell
>
> cd ~/Desktop
> diff a.txt b.txt
>
> #+end_src
>
> I get "Code block produced no output" with C-c C-c. If I replace the
> diff line with =pwd=, it puts the current directory in the results
> block (works as expected).
>
> I've tried replace, append, output, raw, and value for :results, as
> well as results and both for :exports. I've also tried using a #+name:
> which gives me a results block for the output, but it's empty.
>
> Am I missing something? Perhaps there's an analog for how some
> programs need a print() of some kind for the results to show up? Then
> again, I don't know why =pwd= works... There's no worg page for the
> shell language (surprised me!).
>
>
> Thanks,
> John

Re: [O] Bug: org -> org export ignores latex blocks [8.3.4 (8.3.4-50-g83e373-elpaplus @ /home/andrea/.emacs.d/elpa/org-plus-contrib-20160509/)]

[John Hendy]

On Thu, May 12, 2016 at 2:24 PM, Kaushal Modi  wrote:
>
> On Thu, May 12, 2016 at 3:16 PM John Hendy  wrote:
>>
>> Ah. I always wondered about that since the change is reported for 9.0
>> but it's in effect for me on:
>>
>> Org-mode version 8.3.4 (release_8.3.4-753-gda4db33 @ ~/.elisp/org/lisp/)
>>
>> But I've obviously built from git. Simple case would be for Andrea to
>> just try it and let us know :) Other than that, I'd defer to Nicholas
>> to say whether or not this should be going on.
>
>
> If you just git clone, you clone the bleeding-edge master branch with awesome 
> new features :) You are on master branch built recently.
>
>
> I agree that the version number is confusing for people building from the 
> master branch. It's figuratively 9.0+, but org-version still gives 
> 8.3.4-xxx-gxxx.

Indeed, I didn't know that. I agree, if it's basically a
9.0-prerelease analog, knowing that 9.0 features are building (via the
version number) would be nice to know. Or maybe that's common
knowledge other than in my head :)

Thanks,
John

>
> It would have been nice if the master branch built version showed a different 
> numerical version number than the one on the maint branch. Or probably some 
> prefix like dev/master? Nicolas?
> --
>
> --
> Kaushal Modi

[O] No output from babel shell src block

[John Hendy]

Hello,


I've not used shell in babel much, and am confused. I was trying to
include diff output from a block in an analysis and it's not giving
any output.

As a test, I have a.txt which contains 1 and b.txt which contains 2,
with boths in ~/Desktop.

Manually:
$ cd ~/Desktop
$ diff a.txt b.txt
1c1
< 1
---
> 2

Org:
#+begin_src shell

cd ~/Desktop
diff a.txt b.txt

#+end_src

I get "Code block produced no output" with C-c C-c. If I replace the
diff line with =pwd=, it puts the current directory in the results
block (works as expected).

I've tried replace, append, output, raw, and value for :results, as
well as results and both for :exports. I've also tried using a #+name:
which gives me a results block for the output, but it's empty.

Am I missing something? Perhaps there's an analog for how some
programs need a print() of some kind for the results to show up? Then
again, I don't know why =pwd= works... There's no worg page for the
shell language (surprised me!).


Thanks,
John

Re: [O] Bug: org -> org export ignores latex blocks [8.3.4 (8.3.4-50-g83e373-elpaplus @ /home/andrea/.emacs.d/elpa/org-plus-contrib-20160509/)]

[John Hendy]

Ah. I always wondered about that since the change is reported for 9.0
but it's in effect for me on:

Org-mode version 8.3.4 (release_8.3.4-753-gda4db33 @ ~/.elisp/org/lisp/)

But I've obviously built from git. Simple case would be for Andrea to
just try it and let us know :) Other than that, I'd defer to Nicholas
to say whether or not this should be going on.


Thanks for the clarification,
John

On Thu, May 12, 2016 at 1:57 PM, Kaushal Modi  wrote:
> On Thu, May 12, 2016 at 2:53 PM John Hendy  wrote:
>>
>> I believe this is due to the new syntax change for export blocks
>> announced a bit back. See:
>> - http://orgmode.org/cgit.cgi/org-mode.git/plain/etc/ORG-NEWS
>>
>> Try this instead:
>>
>> * Hello
>> #+BEGIN_export latex
>> hi I am latex
>> #+END_export
>
>
> I was going to say the same but then I saw that Andrea is using an
> org-plus-contrib version. The new syntax would go in effect in org 9.0 or
> for someone using org built from the master branch.
>
> It should not affect users using org from maint branch or
> org/org-plus-contrib from Org Elpa.
> --
>
> --
> Kaushal Modi

Re: [O] Bug: org -> org export ignores latex blocks [8.3.4 (8.3.4-50-g83e373-elpaplus @ /home/andrea/.emacs.d/elpa/org-plus-contrib-20160509/)]

[Kaushal Modi]

On Thu, May 12, 2016 at 2:53 PM John Hendy  wrote:

> I believe this is due to the new syntax change for export blocks
> announced a bit back. See:
> - http://orgmode.org/cgit.cgi/org-mode.git/plain/etc/ORG-NEWS
>
> Try this instead:
>
> * Hello
> #+BEGIN_export latex
> hi I am latex
> #+END_export
>

I was going to say the same but then I saw that Andrea is using an
org-plus-contrib version. The new syntax would go in effect in org 9.0 or
for someone using org built from the master branch.

It should not affect users using org from maint branch or
org/org-plus-contrib from Org Elpa.
-- 

-- 
Kaushal Modi

Re: [O] Bug: org -> org export ignores latex blocks [8.3.4 (8.3.4-50-g83e373-elpaplus @ /home/andrea/.emacs.d/elpa/org-plus-contrib-20160509/)]

[John Hendy]

On Thu, May 12, 2016 at 11:57 AM, Andrea  wrote:
>
> Remember to cover the basics, that is, what you expected to happen and
> what in fact did happen.  You don't know how to make a good report?  See
>
>  http://orgmode.org/manual/Feedback.html#Feedback
>
> Your bug report will be posted to the Org-mode mailing list.
> 
>
> Hello,
>
> I am a great fan of org mode, so thanks a lot for maintaining this wonder!
>
> The problem:
>
> when I try to export an org file to an org buffer/file, LaTex blocks are
> removed:
>
> the org file
> ---
> * Hello
> #+BEGIN_LaTeX
> hi I am latex
> #+END_LaTeX
> ---
> becomes
> ---
> # Created 2016-05-12 Thu 17:45
> #+TITLE:
> #+AUTHOR: Andrea
> * Hello
> ---

I believe this is due to the new syntax change for export blocks
announced a bit back. See:
- http://orgmode.org/cgit.cgi/org-mode.git/plain/etc/ORG-NEWS

Try this instead:

* Hello
#+BEGIN_export latex
hi I am latex
#+END_export

I get this in the resultant .tex:

\section{Hello}
\label{sec:org1f84eec}
hi I am latex
\end{document}


Best regards,
John

[O] Bug: org -> org export ignores latex blocks [8.3.4 (8.3.4-50-g83e373-elpaplus @ /home/andrea/.emacs.d/elpa/org-plus-contrib-20160509/)]

[Andrea]

Remember to cover the basics, that is, what you expected to happen and
what in fact did happen.  You don't know how to make a good report?  See

 http://orgmode.org/manual/Feedback.html#Feedback

Your bug report will be posted to the Org-mode mailing list.


Hello,

I am a great fan of org mode, so thanks a lot for maintaining this wonder!

The problem:

when I try to export an org file to an org buffer/file, LaTex blocks are
removed:

the org file
---
* Hello
#+BEGIN_LaTeX
hi I am latex
#+END_LaTeX
---
becomes
---
# Created 2016-05-12 Thu 17:45
#+TITLE: 
#+AUTHOR: Andrea
* Hello
---

The export to html deletes these blocks as well.
Packages as ox-pandoc and org-pandoc use this functionality,
and so fail the export as well.
Hope this can be solved easily.
Thanks,

Andrea

Emacs  : GNU Emacs 24.5.1 (x86_64-unknown-linux-gnu, GTK+ Version 3.20.3)
 of 2016-05-05 on arojas
Package: Org-mode version 8.3.4 (8.3.4-50-g83e373-elpaplus @ 
/home/andrea/.emacs.d/elpa/org-plus-contrib-20160509/)

current state:
==
(setq
 org-pandoc-epub-rights "Copyright 2016  <>"
 org-tab-first-hook '(org-hide-block-toggle-maybe 
org-babel-hide-result-toggle-maybe org-babel-header-arg-expand)
 org-speed-command-hook '(org-speed-command-default-hook 
org-babel-speed-command-hook)
 org-occur-hook '(org-first-headline-recenter)
 org-metaup-hook '(org-babel-load-in-session-maybe)
 org-html-format-drawer-function '(lambda (name contents) contents)
 org-log-done t
 org-latex-format-inlinetask-function 
'org-latex-format-inlinetask-default-function
 org-confirm-shell-link-function 'yes-or-no-p
 org-ascii-format-inlinetask-function 'org-ascii-format-inlinetask-default
 org-latex-pdf-process '("texi2dvi -p -b -V %f")
 org-latex-format-headline-function 'org-latex-format-headline-default-function
 org-default-notes-file "~/org/notes.org"
 org-after-todo-state-change-hook '(org-clock-out-if-current)
 org-latex-format-drawer-function '(lambda (name contents) contents)
 org-from-is-user-regexp nil
 org-loop-over-headlines-in-active-region 'start-level
 org-src-mode-hook '(org-src-babel-configure-edit-buffer 
org-src-mode-configure-edit-buffer)
 org-agenda-before-write-hook '(org-agenda-add-entry-text)
 org-babel-pre-tangle-hook '(save-buffer)
 org-mode-hook '(#[nil "\300\301\302\303\304$\207" [org-add-hook 
change-major-mode-hook org-show-block-all append local] 5]
 #[nil "\300\301\302\303\304$\207" [org-add-hook 
change-major-mode-hook org-babel-show-result-all append local]
   5]
 org-babel-result-hide-spec org-babel-hide-all-hashes 
turn-on-flyspell org-eldoc-load)
 org-archive-hook '(org-attach-archive-delete-maybe)
 org-ascii-format-drawer-function '(lambda (name contents width) contents)
 org-ctrl-c-ctrl-c-hook '(org-babel-hash-at-point 
org-babel-execute-safely-maybe)
 org-cycle-hook '(org-cycle-hide-archived-subtrees org-cycle-hide-drawers 
org-cycle-show-empty-lines
  org-optimize-window-after-visibility-change)
 org-plantuml-jar-path "/home/andrea/.emacs.d/plantuml.jar"
 org-babel-tangle-lang-exts '(("haskell" . "hs") ("ruby" . "rb") ("python" . 
"py") ("java" . "java") ("ocaml" . "ml")
  ("emacs-lisp" . "el") ("elisp" . "el"))
 org-confirm-elisp-link-function 'yes-or-no-p
 org-metadown-hook '(org-babel-pop-to-session-maybe)
 org-html-format-headline-function 'org-html-format-headline-default-function
 org-babel-load-languages '((ocaml . t) (java . t) (sh . t) (python . t) (ruby 
. t) (haskell . t) (plantuml . t))
 org-html-format-inlinetask-function 
'org-html-format-inlinetask-default-function
 org-agenda-files '("~/myTasks.org")
 org-clock-out-hook '(org-clock-remove-empty-clock-drawer)
 )

[O] Return header one level up

[Zach Sheffler]

I'm trying to dip my toes into the waters of customizing org-mode somewhat,
so I'm unsure as to where to look.

Is there an easy way to return the text of the parent header? In other
words, if I had this in the agenda prefix, and the agenda file read:

* One
** TODO Two

It would show in the agenda as

Todo: (One) Two

?

Re: [O] Buffer local value lost when exporting? (was Evaluate all org tables in file before exporting)

[Kaushal Modi]

Forgot to mention my emacs and org versions; here they are:

GNU Emacs 25.0.93.5 (x86_64-unknown-linux-gnu, GTK+ Version 2.24.23) of
2016-05-05

Org-mode version 8.3.4 (release_8.3.4-778-g8127b3 @
/home/kmodi/usr_local/apps/6/emacs/emacs-25/share/emacs/site-lisp/org/)

-- 

-- 
Kaushal Modi

[O] Buffer local value lost when exporting? (was Evaluate all org tables in file before exporting)

[Kaushal Modi]

Hi all,

I almost have a squeaky clean solution to this thanks to the hint provided
by someone on emacs.SE ( http://emacs.stackexchange.com/a/22215/115 ).

But in the process, I seem to have stumbled upon a bug.. the buffer local
value of variables are not respected at the time of exports.

To demonstrate that, please evaluate the elisp code at the end of this
email and do C-c C-e h o on the below MWE of org file:

As the buffer local value of modi/org-table-enable-buffer-wide-recalculation
var is nil, that table does not get recalculated when saving. But it always
gets recalculated when exporting (e.g. using C-c C-e h o).

= sample.org =
| N |
|---|
|   |
|   |
|   |
|   |
#+TBLFM: $1=@#-1

# Local Variables:
# modi/org-table-enable-buffer-wide-recalculation: nil
# End:
=

= auto-recalculate-org-tables.el =
;; Recalculate all org tables in the buffer when saving.
(defvar-local modi/org-table-enable-buffer-wide-recalculation t
  "When non-nil, all the org tables in the buffer will be recalculated when
saving the file or when exporting.
This variable is buffer local.")
;; Mark `modi/org-table-enable-buffer-wide-recalculation' as a safe local
;; variable as long as its value is t or nil. That way you are not prompted
;; to add that to `safe-local-variable-values' in custom.el.
(put 'modi/org-table-enable-buffer-wide-recalculation
 'safe-local-variable (lambda (val) (or (equal val nil) (equal val t

(defun modi/org-table-recalculate-buffer-tables ( args)
  "Wrapper function for `org-table-recalculate-buffer-tables' that runs
that function only if `modi/org-table-enable-buffer-wide-recalculation' is
non-nil.

Also, this function has ARGS as optional arguments that are needed for any
function that is added to the `org-export-before-processing-hook'."
  (message "modi/org-table-enable-buffer-wide-recalculation: %S"
   modi/org-table-enable-buffer-wide-recalculation)
  (when modi/org-table-enable-buffer-wide-recalculation
(org-table-recalculate-buffer-tables)))

(defun modi/org-table-recalculate-before-save ()
  "Recalculate all org tables in the buffer before saving."
  (add-hook 'before-save-hook #'modi/org-table-recalculate-buffer-tables
nil :local))
(add-hook 'org-mode-hook #'modi/org-table-recalculate-before-save)
;; FIXME: The buffer local value of
`modi/org-table-enable-buffer-wide-recalculation'
;; does not seem to be respected at the moment at the time of running
;; `org-export-before-processing-hook'. Investigating this ..
;; For now, as the default value of that variable is t, all org tables
;; in the buffer will always be recalculated at the time of export even
;; if the buffer local value of that var is nil.
(add-hook 'org-export-before-processing-hook
#'modi/org-table-recalculate-buffer-tables)
=

On Fri, May 6, 2016 at 10:58 AM Kaushal Modi  wrote:

> Hi folks,
>
> I am looking if anyone already has a solution (a function) that evaluates
> all the tables in the file/buffer. I should be then simply able to add that
> to local value of before-save-hook in org-mode, right?
>
> Currently, I need to remember to C-u C-c C-c on all the tables before
> exporting to ensure that all the calculated values are correct.
>
> Or am I missing some org variable, setting which should take care of this?
>
> Thanks.
> --
>
> --
> Kaushal Modi
>
-- 

-- 
Kaushal Modi

Re: [O] New Beamer environment selection problem

[Nicolas Goaziou]

Hello,

Julien Cubizolles  writes:

> I'm still experiencing this problem with the following example
>
> #+BEGIN_SRC elisp
>   (add-to-list 'load-path "~/git-repositories/org-mode/lisp")
>   (add-to-list 'load-path "~/git-repositories/org-mode/contrib/lisp")
> #+END_SRC
>
> #+RESULTS:
> : Successfully reloaded Org
> : Org-mode version 8.3.4 (release_8.3.4-695-gf07580 @ 
> /home/wilk/git-repositories/org-mode/lisp/)

This release is too old. You need to update Org.

Regards,

-- 
Nicolas Goaziou

Re: [O] New Beamer environment selection problem

[Julien Cubizolles]

Nicolas Goaziou  writes:


> Would the following patch solve the issue?

I'm still experiencing this problem with the following example

--8<---cut here---start->8---
#+BEGIN_SRC elisp
  (add-to-list 'load-path "~/git-repositories/org-mode/lisp")
  (add-to-list 'load-path "~/git-repositories/org-mode/contrib/lisp")
#+END_SRC

#+RESULTS:
: Successfully reloaded Org
: Org-mode version 8.3.4 (release_8.3.4-695-gf07580 @ 
/home/wilk/git-repositories/org-mode/lisp/)

* Entry
--8<---cut here---end--->8---

with emacs -Q evaluation the src
block, reloading org-mode, org-beamer-select-environment with point on
"Entry" fails with:

Debugger entered--Lisp error: (wrong-number-of-arguments max 0)
  max()
  apply(max nil)
  org-fast-tag-selection(nil nil nil nil)
  org-set-tags()
  org-beamer-select-environment()
  funcall-interactively(org-beamer-select-environment)
  call-interactively(org-beamer-select-environment nil nil)
  command-execute(org-beamer-select-environment)