[O] Lack of availability

[Bastien]

Dear all,

I'm sorry for my current lack of availability.  I wanted
to hack back since late august but I was not able to.

I'm going through hard times since the summer and I need
to focus on securing a basic environment for my daily life.

I hope I can sort this out soon enough.

I'm thankful to everyone who actively contribute with bug
fixes, questions and answers.  It's great to see this.

All best,

-- 
 Bastien

Re: [O] Lack of availability

[Glyn Millington]

Bastien b...@gnu.org writes:

 Dear all,

 I'm sorry for my current lack of availability.  I wanted
 to hack back since late august but I was not able to.

 I'm going through hard times since the summer and I need
 to focus on securing a basic environment for my daily life.

 I hope I can sort this out soon enough.

 I'm thankful to everyone who actively contribute with bug
 fixes, questions and answers.  It's great to see this.


I hope life stabilises for you soon! 

with best wishes



Glyn

Re: [O] [PATCH] WAS Re: Bug: problem w/ R code blocks [8.3beta (release_8.3beta-362-ga92789 at /usr/local/share/emacs/site-lisp/org/)]

[Rainer M Krug]

Charles Berry ccbe...@ucsd.edu writes:

 Charles Berry ccberry at ucsd.edu writes:

 
 Rainer M Krug Rainer at krugs.de writes:
 
  
  Thanks - you came before me. I get the same error but managed to work 
  around.
  
  This is likely caused by the upgrade of ess, 
 
 Likely.
 
 But it may not be an ESS problem per se. 
 
 M-x R starts a process that runs asynchronously. In interactive use there 
 is no issue (barring something in .First() that slows the startup for
 a very long time).
 
 But, ...
 
 If the  (rename-buffer ...) in org-babel-R-initiate-session
 runs before all the setup that ESS performs in the process buffer is 
 complete, chaos can result.
 
 Not sure what the best way is to fix this.


 OK. Looks like (ess-wait-for-process) fixes this. Here is a patch.

Thanks.

Haven't tried it yet, but I can't imagine any downside of this
patch. Could this be committed?

Rainer


 Chuck
 ==

 From 89472012d80ce9ad4c8722f304c0d29327efa1fc Mon Sep 17 00:00:00 2001
 From: chasberry ccbe...@ucsd.edu
 Date: Tue, 16 Sep 2014 19:57:59 -0700
 Subject: [PATCH] lisp/ob-R.el: use `ess-wait-for-process' to assure clean
  session startup

 * lisp/ob-R.el (org-babel-R-initiate-session): Make sure that (R) has
 finished before `rename-buffer' is run.

 TINYCHANGE
 ---
  lisp/ob-R.el | 3 +++
  1 file changed, 3 insertions(+)

 diff --git a/lisp/ob-R.el b/lisp/ob-R.el
 index 41b943c..7575acf 100644
 --- a/lisp/ob-R.el
 +++ b/lisp/ob-R.el
 @@ -35,6 +35,8 @@
  (declare-function inferior-ess-send-input ext:ess-inf ())
  (declare-function ess-make-buffer-current ext:ess-inf ())
  (declare-function ess-eval-buffer ext:ess-inf (vis))
 +(declare-function ess-wait-for-process ext:ess-inf 
 +   (optional proc sec-prompt wait force-redisplay))
  (declare-function org-number-sequence org-compat (from optional to inc))
  (declare-function org-remove-if-not org (predicate seq))
  (declare-function org-every org (pred seq))
 @@ -262,6 +264,7 @@ This function is called by `org-babel-execute-src-block'.
   ;; Session buffer exists, but with dead process
   (set-buffer session))
 (require 'ess) (R)
 +   (ess-wait-for-process)
 (rename-buffer
  (if (bufferp session)
  (buffer-name session)

-- 
Rainer M. Krug
email: Raineratkrugsdotde
PGP: 0x0F52F982


pgpnuTGfJgstT.pgp
Description: PGP signature

Re: [O] [PATCH] WAS Re: Bug: problem w/ R code blocks [8.3beta (release_8.3beta-362-ga92789 at /usr/local/share/emacs/site-lisp/org/)]

[Rainer M Krug]

Rainer M Krug rai...@krugs.de writes:

Using it, error is gone.

Rainer

 Charles Berry ccbe...@ucsd.edu writes:

 Charles Berry ccberry at ucsd.edu writes:

 
 Rainer M Krug Rainer at krugs.de writes:
 
  
  Thanks - you came before me. I get the same error but managed to work 
  around.
  
  This is likely caused by the upgrade of ess, 
 
 Likely.
 
 But it may not be an ESS problem per se. 
 
 M-x R starts a process that runs asynchronously. In interactive use there 
 is no issue (barring something in .First() that slows the startup for
 a very long time).
 
 But, ...
 
 If the  (rename-buffer ...) in org-babel-R-initiate-session
 runs before all the setup that ESS performs in the process buffer is 
 complete, chaos can result.
 
 Not sure what the best way is to fix this.


 OK. Looks like (ess-wait-for-process) fixes this. Here is a patch.

 Thanks.

 Haven't tried it yet, but I can't imagine any downside of this
 patch. Could this be committed?

 Rainer


 Chuck
 ==

 From 89472012d80ce9ad4c8722f304c0d29327efa1fc Mon Sep 17 00:00:00 2001
 From: chasberry ccbe...@ucsd.edu
 Date: Tue, 16 Sep 2014 19:57:59 -0700
 Subject: [PATCH] lisp/ob-R.el: use `ess-wait-for-process' to assure clean
  session startup

 * lisp/ob-R.el (org-babel-R-initiate-session): Make sure that (R) has
 finished before `rename-buffer' is run.

 TINYCHANGE
 ---
  lisp/ob-R.el | 3 +++
  1 file changed, 3 insertions(+)

 diff --git a/lisp/ob-R.el b/lisp/ob-R.el
 index 41b943c..7575acf 100644
 --- a/lisp/ob-R.el
 +++ b/lisp/ob-R.el
 @@ -35,6 +35,8 @@
  (declare-function inferior-ess-send-input ext:ess-inf ())
  (declare-function ess-make-buffer-current ext:ess-inf ())
  (declare-function ess-eval-buffer ext:ess-inf (vis))
 +(declare-function ess-wait-for-process ext:ess-inf 
 +  (optional proc sec-prompt wait force-redisplay))
  (declare-function org-number-sequence org-compat (from optional to inc))
  (declare-function org-remove-if-not org (predicate seq))
  (declare-function org-every org (pred seq))
 @@ -262,6 +264,7 @@ This function is called by 
 `org-babel-execute-src-block'.
  ;; Session buffer exists, but with dead process
  (set-buffer session))
(require 'ess) (R)
 +  (ess-wait-for-process)
(rename-buffer
 (if (bufferp session)
 (buffer-name session)

-- 
Rainer M. Krug
email: Raineratkrugsdotde
PGP: 0x0F52F982


pgp_LdElBmteT.pgp
Description: PGP signature

[O] Emacs server and org-protocol

[Gonzalo Camarillo]

Hi,

I am using org-protocol to have my firefox browser talk to my emacs (to
capture stuff).

I am using Windows 7. So, I cannot use the --daemon flag to simply start
a sever (it is not supported under Windows). Instead, I have added a
(server-start) line to my .emacs file (init.el).

When I run emacs for the first time, everything works correctly (i.e.,
the server starts and I can connect to it from firefox). However, when I
open a second instance of emacs, it processes again the .emacs file and,
thus, I get the following error:

 Warning (server): Unable to start the Emacs server.
 There is an existing Emacs server, named server.
 To start the server in this Emacs process, stop the existing
 server or call `M-x server-force-delete' to forcibly disconnect it.

Does anybody know a workaround so that the server is only started
once?... maybe in connection to opening a particular .org file?

Thanks,

Gonzalo

Re: [O] Emacs server and org-protocol

[Paul Rudin]

Gonzalo Camarillo gcama...@gmail.com writes:


 Does anybody know a workaround so that the server is only started
 once?... 

Does the function server-running-p work on windows? If so then you can
replace (server-start) with (unless (server-running-p) (server-start)).

[O] State-of-the-art in linking org items to places in source files?

[Thorsten Jolitz]

Hi List, 

I remember extensive discussions on this list of how to associate
org-files and source files by links, but I don't find them anymore and I
don't remember what is the State-of-the-art in this area.

It was about 'outsourcing' commentsplanning-info from a programming-mode
file to an associated org-mode file and the ability to jump back and
forth seamlessly between the two files (or rather between the right
places in both files).

Wasn't there even a library to support this kind of workflow?
I would appreciate any hint that updates me on this topic. 

-- 
cheers,
Thorsten

Re: [O] Emacs server and org-protocol

[Fabrice Popineau]

What is the purpose of opening a second instance of emacs ?
I precisely tend to avoid it.

If the emacs server is running, why not using emacsclient(w) instead of a
new instance ?

Fabrice

2014-09-17 9:26 GMT+02:00 Gonzalo Camarillo gcama...@gmail.com:

 Hi,

 I am using org-protocol to have my firefox browser talk to my emacs (to
 capture stuff).

 I am using Windows 7. So, I cannot use the --daemon flag to simply start
 a sever (it is not supported under Windows). Instead, I have added a
 (server-start) line to my .emacs file (init.el).

 When I run emacs for the first time, everything works correctly (i.e.,
 the server starts and I can connect to it from firefox). However, when I
 open a second instance of emacs, it processes again the .emacs file and,
 thus, I get the following error:

  Warning (server): Unable to start the Emacs server.
  There is an existing Emacs server, named server.
  To start the server in this Emacs process, stop the existing
  server or call `M-x server-force-delete' to forcibly disconnect it.

 Does anybody know a workaround so that the server is only started
 once?... maybe in connection to opening a particular .org file?

 Thanks,

 Gonzalo





-- 
Fabrice Popineau
-
SUPELEC
Département Informatique
3, rue Joliot Curie
91192 Gif/Yvette Cedex
Tel direct : +33 (0) 169851950
Standard : +33 (0) 169851212
--

Re: [O] Emacs server and org-protocol

[Paul Rudin]

Fabrice Popineau fabrice.popin...@supelec.fr writes:

 What is the purpose of opening a second instance of emacs ? 
 I precisely tend to avoid it.

There are situations where it can be useful - e.g. using emacs as
a news or mail client where the whole process can block for a few
seconds.

Re: [O] Emacs server and org-protocol

[Thorsten Jolitz]

Fabrice Popineau fabrice.popin...@supelec.fr writes:

 What is the purpose of opening a second instance of emacs ? 
 I precisely tend to avoid it.

 If the emacs server is running, why not using emacsclient(w) instead
 of a new instance ?

I had that setup for quite some time - starting one Emacs server on the
console, and then several emacsclients as parts of tmux and stumpwm
window configurations. 

But it crashed too often - and it was just too painful to recover all
the emacsclients in all the window-configurations. 

So nowadays I have one (non-server) Emacs instance for doing the real
work, and another server instance which I use for the convenience of
getting emacsclients everywhere for some quick adhoc stuff, without
caring much when it crashes.

-- 
cheers,
Thorsten

Re: [O] Emacs server and org-protocol

[Gonzalo Camarillo]

Hi Paul,

yes, adding (require 'server) makes the function available. That is exactly
what I was looking for. Thanks for the quick response!

Cheers,

Gonzalo


On Wed, Sep 17, 2014 at 9:36 AM, Paul Rudin p...@rudin.co.uk wrote:

 Gonzalo Camarillo gcama...@gmail.com writes:


  Does anybody know a workaround so that the server is only started
  once?...

 Does the function server-running-p work on windows? If so then you can
 replace (server-start) with (unless (server-running-p) (server-start)).

[O] Bug (regression) in org-replace-disputed-keys. Bisected.

[Teika Kazura]

Hello, org-list. I experience a regression in org-replace-disputed-keys, and I 
git-bisect'ed it.

* Symptom: org-replace-disputed-keys doesn't work for me.
Emacs version: GNU Emacs 24.3.1 (x86_64-pc-linux-gnu, GTK+ Version 3.0.12)

* How to reproduce it:
1. Put the org to /tmp/org-mode
2. Save the following lisp to minimal-org.el
---
(progn
  (setq org-replace-disputed-keys t)
  (setq org-disputed-keys
'(([(shift up)] . [(ctrl up)])
  ([(shift down)] . [(ctrl down)])
  ([(shift left)] . [(ctrl left)])
  ([(shift right)] . [(ctrl right)])
  ([(shift meta right)] . [(shift control right)])
  ([(shift meta left)] . [(shift control left)])
  ([(shift meta up)] . [(shift control up)])
  ([(shift meta down)] . [(shift control down)])
  ([(shift control right)] . [(shift meta right)])
  ([(shift control left)] . [(shift meta left)]))
)
  (add-to-list 'load-path (expand-file-name /tmp/org-mode/lisp))
  (pop-to-buffer *scratch*)
  (insert *  (org-version)  ( (org-git-version) )\n )
  (require 'org)
  (org-mode))

3. Run emacs with 
  $ emacs -Q -l minimal-org.el
4. M-x org-schedule, and press ctrl+cursor.

Shift+cursor should be replaced with ctrl+cursor, but they aren't. For 
example `describe-key' for C-down says:

C-down runs the command forward-paragraph, which is an interactive
compiled Lisp function in `paragraphs.el'

* The bad commit
The exact bad commit can't be tracked (org fails to initialize), but I narrowed 
it down to 6 commits. It was done between 
9a0e84fbd7b0e25cf49613e787d572f3c71723dc and 
8ad6f534f9b24f273b7699199df34c0f44f9059f .
I here show the diff for org.el in that period. The last 2 hunks looks 
relevant:

diff --git a/lisp/org.el b/lisp/org.el
index aebf58f..7f0717e 100644
--- a/lisp/org.el
+++ b/lisp/org.el
@@ -6897,7 +6897,7 @@ of the first headline in the buffer.  This is important, 
because if the
 first headline is not level one, then (hide-sublevels 1) gives confusing
 results.
   (interactive)
-  (let ((l (org-current-line))
+  (let ((pos (point))
(level (save-excursion
 (goto-char (point-min))
 (if (re-search-forward (concat ^ outline-regexp) nil t)
@@ -6906,7 +6906,7 @@ results.
   (funcall outline-level))
 (and level (hide-sublevels level))
 (recenter '(4))
-(org-goto-line l)))
+(goto-char pos)))
 
 (defun org-content (optional arg)
   Show all headlines in the buffer, like a table of contents.
@@ -14050,10 +14050,19 @@ See also `org-scan-tags'.
minus tag mm
tagsmatch todomatch tagsmatcher todomatcher kwd matcher
orterms term orlist re-p str-p level-p level-op time-p
-   prop-p pn pv po gv rest)
+   prop-p pn pv po gv rest (start 0) (ss 0))
 ;; Expand group tags
 (setq match (org-tags-expand match))
-(if (string-match /+ match)
+
+;; Check if there is a TODO part of this match, which would be the
+;; part after a /.  TO make sure that this slash is not part of
+;; a property value to be matched against, we also check that there
+;; is no  after that slash.
+;; First, find the last slash
+(while (string-match /+ match ss)
+  (setq start (match-beginning 0) ss (match-end 0)))
+(if (and (string-match /+ match start)
+(not (save-match-data (string-match \ match start
;; match contains also a todo-matching request
(progn
  (setq tagsmatch (substring match 0 (match-beginning 0))
@@ -16126,7 +16135,8 @@ So these are more for recording a certain time/date.
 (defvar org-read-date-inactive)
 
 (defvar org-read-date-minibuffer-local-map
-  (let ((map (make-sparse-keymap)))
+  (let* ((org-replace-disputed-keys nil)
+(map (make-sparse-keymap)))
 (set-keymap-parent map minibuffer-local-map)
 (org-defkey map (kbd .)
 (lambda () (interactive)
@@ -16286,7 +16296,6 @@ user.
  (calendar-current-date
(org-eval-in-calendar nil t)
(let* ((old-map (current-local-map))
-  (org-replace-disputed-keys nil)
   (map (copy-keymap calendar-mode-map))
   (minibuffer-local-map
(copy-keymap org-read-date-minibuffer-local-map)))


Thank you very much for developing org-mode.

Kind regards,
Teika (Teika kazura)

# Hey, it was almost exacly a year ago. Only few use this feature? ;]

Re: [O] Emacs server and org-protocol

[Fabrice Popineau]

2014-09-17 9:56 GMT+02:00 Paul Rudin p...@rudin.co.uk:

 Fabrice Popineau fabrice.popin...@supelec.fr writes:

  What is the purpose of opening a second instance of emacs ?
  I precisely tend to avoid it.

 There are situations where it can be useful - e.g. using emacs as
 a news or mail client where the whole process can block for a few
 seconds.


Yes seconds or even much more.
This is the reason I don't use Emacs to read my mail/news anymore :-/

-- 
Fabrice

Re: [O] Emacs server and org-protocol

[Alexis]

Fabrice Popineau writes:

 Yes seconds or even much more.
 This is the reason I don't use Emacs to read my mail/news anymore :-/

If i may ask, which email front-end were you using? (Gnus, perhaps?) i
used to use notmuch.el, and currently use mu4e, and basically don't have
this issue 


Alexis.

[O] [PATCH][BUG] org-capture-templates checkitem not working as expected

[Ohad Kammar]

Dear Org users,

There's a bug with the checkitem type org-capture-templates.

To reproduce:

1) Choose an org file with the headline Test list, e.g., execute:
   $ cat  ~/org-capture-bugreport.org
   * Test list [/]
   ^C
2) Add the following two templates to your org-capture-templates:
 (b Demonstrate a bug in capture templates checkitem (file
~/org-capture-bugreport.org Test list)
  there should be '[ ]' at the beginning of this item,
but there isn't. :immediate-finish t)
 (v Demonstrate a bug in capture templates checkitem (file
~/org-capture-bugreport.org Test list)
  [ ] This is how it should behave :immediate-finish t)
3) org-capture b and org-capture v

I expected the 'b' option to add a checkbox item under Test list,
but instead it only adds an item. The 'v' option behaves as I expect
from 'b', but I had to add the checkbox manually.

Below is a patch fixing this issue. (This is my first patch to Org, I'm
happy to fix any mistakes.

Yours,
Ohad.


From 8a09dd1e6aea78551d2958beebf88156ce54e774 Mon Sep 17 00:00:00 2001
From: Ohad Kammar ohad.kam...@cl.cam.ac.uk
Date: Wed, 17 Sep 2014 09:43:45 +0100
Subject: [PATCH] org-capture.el: Implemented checkitem capture type

org-capture.el (org-capture-place-item): Add check-box if appropriate.

Pre-patch, the checkitem and item types behave exactly the same,
rather than inserting a checkbox.

Fix by Simon Castellan and Ohad Kammar.

TINYCHANGE
---
 lisp/org-capture.el |2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/lisp/org-capture.el b/lisp/org-capture.el
index 9e33d25..365d7c5 100644
--- a/lisp/org-capture.el
+++ b/lisp/org-capture.el
@@ -1094,7 +1094,7 @@ may have been stored before.
 (setq txt (org-remove-indentation txt))
 ;; Make sure this is indeed an item
 (unless (string-match (concat \\` (org-item-re)) txt)
-  (setq txt (concat - 
+  (setq txt (concat -  (if (eq (org-capture-get :type)
'checkitem) [ ]  )
 (mapconcat 'identity (split-string txt \n)
\n  
 ;; Set the correct indentation, depending on context
-- 
1.7.9.5

[O] Bug: LaTeX export produces no output; clobbering keybindings [8.2.7c (8.2.7c-64-g01f736-elpa @/home/tbg/.emacs.d/elpa/org-20140915/)]

[Tobias Getzner]

Hello,

When using LaTeX-based export targets that produce a .tex file as output
(export to LaTeX file, PDF, PDF and open), I receive the message «Buffer
foo.tex modified; kill anyway?». Irrespective of whether I answer y/n,
no .tex file is produced, and «latexmk» fails with «no such file».

Exporting to a LaTeX buffers seems to work.

Both after issuing the file-producing exports, and when issuing
exports to buffer only (export to LaTeX buffer), the keybindings in the
original org-mode buffer become garbled; e. g., issuing another «C-c
C-e» after attempting a LaTeX export no longer invokes the export menu,
but is now bound to the command «LaTeX-enviroment». Actions such as
«fill-paragraph» also no longer work the way they usually work in
org-mode. The mode-line still reports «Org» as the major mode, though.
To get the expected commands back, I have to invoke «M-x org-mode».

I’ve also tested exporting to HTML, and this seems to work as usual. I
haven’t been using the LaTeX exporter in a while, so I’m not sure since
when this issue has been present.

I’d welcome any suggestions as to what might be the problem.

Best regards,
Tobias



Emacs  : GNU Emacs 24.3.1 (x86_64-unknown-linux-gnu, GTK+ Version 3.12.2)
 of 2014-06-11 on var-lib-archbuild-staging-x86_64-jgc
Package: Org-mode version 8.2.7c (8.2.7c-64-g01f736-elpa @ 
/home/tbg/.emacs.d/elpa/org-20140915/)

current state:
==
(setq
 org-tab-first-hook '(org-hide-block-toggle-maybe 
org-src-native-tab-command-maybe
  org-babel-hide-result-toggle-maybe 
org-babel-header-arg-expand)
 org-latex-classes '((sr-article
  \\documentclass[11pt]{article}\n
[DEFAULT-PACKAGES]\n[PACKAGES]\n[EXTRA]
  (\\section{%s} . \\section*{%s})
  (\\subsection{%s} . \\subsection*{%s})
  (\\paragraph{%s} . \\paragraph*{%s})
  (\\subparagraph{%s} . \\subparagraph*{%s}))
 (article \\documentclass[11pt]{article}
  (\\section{%s} . \\section*{%s})
  (\\subsection{%s} . \\subsection*{%s})
  (\\subsubsection{%s} . \\subsubsection*{%s})
  (\\paragraph{%s} . \\paragraph*{%s})
  (\\subparagraph{%s} . \\subparagraph*{%s}))
 (report \\documentclass[11pt]{report}
  (\\part{%s} . \\part*{%s}) (\\chapter{%s} . 
\\chapter*{%s})
  (\\section{%s} . \\section*{%s})
  (\\subsection{%s} . \\subsection*{%s})
  (\\subsubsection{%s} . \\subsubsection*{%s}))
 (book \\documentclass[11pt]{book} (\\part{%s} . 
\\part*{%s})
  (\\chapter{%s} . \\chapter*{%s})
  (\\section{%s} . \\section*{%s})
  (\\subsection{%s} . \\subsection*{%s})
  (\\subsubsection{%s} . \\subsubsection*{%s}))
 )
 org-speed-command-hook '(org-speed-command-default-hook 
org-babel-speed-command-hook)
 org-ellipsis  ▼
 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 'ignore
 org-confirm-shell-link-function 'yes-or-no-p
 org-image-actual-width '(500)
 org-ascii-format-inlinetask-function 'org-ascii-format-inlinetask-default
 org-startup-folded nil
 org-latex-pdf-process '(latexmk -pdf %f latexmk -c %f)
 org-file-apps '((auto-mode . emacs) (.* . xdg-open %s))
 org-special-ctrl-a/e t
 org-shiftleft-hook '((lambda nil (org-ref-swap-citation-link -1)))
 org-latex-format-headline-function 'org-latex-format-headline-default-function
 org-startup-indented t
 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-src-mode-hook '(org-src-babel-configure-edit-buffer
 org-src-mode-configure-edit-buffer)
 org-tags-column 0
 org-agenda-before-write-hook '(org-agenda-add-entry-text)
 org-babel-pre-tangle-hook '(save-buffer)
 org-mode-hook '(org-mode-reftex-setup my-org-mode-hook (lambda nil 
(org-bullets-mode 1))
 #[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
 org-ac/setup-current-buffer)
 org-outline-path-complete-in-steps nil
 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)
 

Re: [O] Emacs server and org-protocol

[Alexis]

Eric S Fraga writes:

 The issue is not the email front-end per se but the email servers (IMAP,
 POP, whatever).  A couple of years ago, I ended up having to use an
 email server that would take many seconds, often minutes, to access,
 even just to query to find out if there was any new email.

Well, i run getmail+procmail to fetch and sort my mail, so if a server
is running slowly, that doesn't affect Emacs. Emacs is only affected by
e.g. mu indexing newly-arrived emails, which is fast enough that i don't
notice it.


Alexis.

Re: [O] Emacs server and org-protocol

[Eric S Fraga]

On Wednesday, 17 Sep 2014 at 18:54, Alexis wrote:

[...]

 If i may ask, which email front-end were you using? (Gnus, perhaps?) i
 used to use notmuch.el, and currently use mu4e, and basically don't have
 this issue 

The issue is not the email front-end per se but the email servers (IMAP,
POP, whatever).  A couple of years ago, I ended up having to use an
email server that would take many seconds, often minutes, to access,
even just to query to find out if there was any new email.

The easiest solution, for me, was to get into the habit of starting two
emacs instances.  The first for all my work (org, writing, coding, etc.)
and a second just for email.  The first starts the emacs server so
emacsclient always goes to the non-email instance.  I've been doing this
for two years now and it has become second nature for me.

Obviously, the real fix is to have proper multi-threading in Emacs and,
as in nuclear fusion, this will be with us *soon* ;-)

-- 
: Eric S Fraga, GnuPG: 0xFFFCF67D
: in Emacs 24.4.50.1 + Ma Gnus v0.12 + evil-git-0469bee
: BBDB version 3.1.2 (2014-05-06 11:45:08 -0500)


signature.asc
Description: PGP signature

Re: [O] Emacs server and org-protocol

[Fabrice Popineau]

2014-09-17 11:06 GMT+02:00 Eric S Fraga e.fr...@ucl.ac.uk:

 On Wednesday, 17 Sep 2014 at 18:54, Alexis wrote:

 [...]

  If i may ask, which email front-end were you using? (Gnus, perhaps?) i
  used to use notmuch.el, and currently use mu4e, and basically don't have
  this issue 

 The issue is not the email front-end per se but the email servers (IMAP,
 POP, whatever).  A couple of years ago, I ended up having to use an
 email server that would take many seconds, often minutes, to access,
 even just to query to find out if there was any new email.

 The easiest solution, for me, was to get into the habit of starting two
 emacs instances.  The first for all my work (org, writing, coding, etc.)
 and a second just for email.  The first starts the emacs server so
 emacsclient always goes to the non-email instance.  I've been doing this
 for two years now and it has become second nature for me.

 Obviously, the real fix is to have proper multi-threading in Emacs and,
 as in nuclear fusion, this will be with us *soon* ;-)


I disagree on this. The problem is less servers than the sheer slowness of
elisp.
And Gnus offers so many fancy opportunities to process your mail that it is
easy to
overuse it.

Emacs won't become any more efficient without switching its own elisp
implementation to something with a true compiler (or jit).

Threading would gain some responsiveness, but that may not be so obvious
nor so easy to implement.
http://www.emacswiki.org/emacs/ConcurrentEmacs
http://www.emacswiki.org/emacs/NoThreading

Fabrice

Re: [O] Bug: LaTeX export produces no output; clobbering keybindings [8.2.7c (8.2.7c-64-g01f736-elpa@/home/tbg/.emacs.d/elpa/org-20140915/)]

[Tobias Getzner]

On Wed, 17 Sep 2014 08:27:21 +, Tobias Getzner wrote:

 When using LaTeX-based export targets that produce a .tex file as output
 (export to LaTeX file, PDF, PDF and open), I receive the message «Buffer
 foo.tex modified; kill anyway?». Irrespective of whether I answer y/n,
 no .tex file is produced, and «latexmk» fails with «no such file».
 
 Both after issuing the file-producing exports, and when issuing
 exports to buffer only (export to LaTeX buffer), the keybindings in the
 original org-mode buffer become garbled; e. g., issuing another «C-c
 C-e» after attempting a LaTeX export no longer invokes the export menu,
 but is now bound to the command «LaTeX-enviroment». 

I seem to have located the trigger. Inter alia, my TeX-mode-hook invokes 
«(TeX-source-correlate-mode)» which sets a variable so that synctex files 
are generated when running AucTeX commands. When this command is removed, 
exporting to .tex files appears to work again and the keybindings remain 
unchanged after export. Is this a bug, or is some configuration required 
to make org-mode not trip over the TeX-mode hook?

Best regards,
T.

Re: [O] Emacs server and org-protocol

[Eric S Fraga]

On Wednesday, 17 Sep 2014 at 11:41, Fabrice Popineau wrote:

[...]

 I disagree on this. The problem is less servers than the sheer slowness of
 elisp.

Sure, elisp is not fast but I it seems to be perfectly fast enough for
me for gnus, even on my little OpenPandora.  In my case, the limiting
factor is the email server and not elisp.  YMMV, of course!

-- 
: Eric S Fraga, GnuPG: 0xFFFCF67D
: in Emacs 24.4.50.1 + Ma Gnus v0.12 + evil-git-0469bee
: BBDB version 3.1.2 (2014-05-06 11:45:08 -0500)


signature.asc
Description: PGP signature

Re: [O] TODO items in lists (not headings)

[Gary Oberbrunner]

On Tue, Sep 16, 2014 at 11:48 PM, Thomas S. Dye t...@tsdye.com wrote:

 Aloha Gary,

 Gary Oberbrunner ga...@oberbrunner.com writes:

  Gary:
My reason for not using TODO is just that it'd be ugly and confusing to
  put a heading in the middle of a list.
 
Compare this:
  * Meeting report
  ** Meeting 1
- a thing that happened
- another thing that happened
- TODO: email everyone about all the things
- some more things that happened
 
to this:
  * Meeting report
  ** Meeting 1
- a thing that happened
- another thing that happened
  ***TODO: email everyone about all the things
- some more things that happened

 One solution is to use a capture template for TODO items and then refile
 them.  I picked this up from Bernt Hansen and like it a lot:

 http://doc.norang.ca/org-mode.html#Capture


Wow, that guy is serious!  I don't think his setup solves what I'm looking
for, but there is so much great stuff in there it'll take me weeks to check
it all out.

-- 
Gary

Re: [O] Lack of availability

[Rasmus]

Bastien b...@gnu.org writes:

 I'm sorry for my current lack of availability.  I wanted
 to hack back since late august but I was not able to.

 I'm going through hard times since the summer and I need
 to focus on securing a basic environment for my daily life.

 I hope I can sort this out soon enough.

 I'm thankful to everyone who actively contribute with bug
 fixes, questions and answers.  It's great to see this.

I'm hope things will be in your corner of the world soon.  Best of
luck!

—Rasmus

-- 
Bang bang

Re: [O] Emacs server and org-protocol

[Stefan Huchler]

I dont really get what the problem is here, email servers checkup is
fast enough, and rss u can use that:

nnrss-use-local to ‘t’ and use ‘nnrss-generate-download-script

Re: [O] Emacs server and org-protocol

[Rainer M Krug]

Stefan Huchler stefan.huch...@mail.de writes:

 I dont really get what the problem is here, email servers checkup is

Not necessarily - depends which mail server (e.g. gmail or local), if
you have one or many folders / tags, your network connection, ...

Often used solution:

mail server (e.g. gmail) - offlineimap - local imap server - gnus -
the user

So offlineimap runs in the background and the local email server check
is fast enough.

I have two instances running, because of longer calculation in my second
(non-email) emacs instance...

Cheers,

Rainer


 fast enough, and rss u can use that:

 nnrss-use-local to ‘t’ and use ‘nnrss-generate-download-script





-- 
Rainer M. Krug
email: Raineratkrugsdotde
PGP: 0x0F52F982


pgpSiQ7VoGtAL.pgp
Description: PGP signature

[O] Changed behaviours of LaTeX exporter in version 8.0+

[Kyeong Soo (Joseph) Kim]

I recently upgraded my org-mode from 7.x to 8.2.7c (bundled with a Windows
Emacs package for ESS) and have been struggling with changed behaviours of
LaTeX exporter since.

Below is the list of those changes:


1. Double backslashes (for line break) embedded in a string for #+AUTHOR:

With version 7.x, the following line

#+AUTHOR: Joseph Kim\\Department of Electrical and Electronic
Engineering\\Example University

is exported to

\author{Joseph Kim\\Department of Electrical and Electronic
Engineering\\Example University}


With version 8.2.7c, however, the same line is exported to

\author{Joseph Kim$\backslash$\Department of Electrical and Electronic
Engineering$\backslash$\Example University}

which results in LaTeX compilation error.


2. Accessing the value of #+KEYWORDS: and change of cases in
org-special-blocks

For keywords section in IEEE papers, I used to have the following settings:

#+KEYWORDS: AAA, BBB, CCC
...
#+BEGIN_IEEEkeywords
{{{KEYWORDS}}}.
#+END_IEEEkeywords

which turns into

\begin{IEEEkeywords}
AAA, BBB, CCC.
\end{IEEEkeywords}


Version 8.2.7c, however, produces the following from the same settings:

\begin{ieeekeywords}
.
\end{ieeekeywords}


Because the keyword environment in IEEE LaTeX class is case-sensitive,
again it results in LaTeX compilation error.


Now I wonder whether I should go back to 7.x or not in spite of many
improvements in the new version.

Any advice or help would be greatly appreciated in this regard.

Regards,
Joseph

[O] async export not working for me

[Julien Cubizolles]

I'm running org-mode 8.3beta from org-plus-contrib in melpa. I must have
missed something obvious cause I could never get async export working.

Here is what I do:
--8---cut here---start-8---
emacs -Q
(require 'package)
(package-initialize) ;; since org is installed by package
--8---cut here---end---8---


create a test.org file with only

--8---cut here---start-8---
* First Heading
* Second Heading
--8---cut here---end---8---

run 

--8---cut here---start-8---
C-c
C-a ;; in the export dispatcher
l
p
--8---cut here---end---8---

I get:

--8---cut here---start-8---
Initializing asynchronous export process
org-export-to-file: Wrong type argument: stringp, nil
--8---cut here---end---8---

the synchronous export works fine.

If I run emacs with my regular config files, I get:
--8---cut here---start-8---
Initializing asynchronous export process
Process 'org-export-process' exited abnormally
--8---cut here---end---8---

different error message but still not ok.

What could possibly go wrong ?

Julien.

Re: [O] async export not working for me

[Rasmus]

Hi Julien,

Julien Cubizolles j.cubizol...@free.fr writes:

 I'm running org-mode 8.3beta from org-plus-contrib in melpa. I must have
 missed something obvious cause I could never get async export working.

 Here is what I do:
 emacs -Q
 (require 'package)
 (package-initialize) ;; since org is installed by package


 create a test.org file with only

 * First Heading
 * Second Heading

 run 

 C-c
 C-a ;; in the export dispatcher
 l
 p

 I get:

 Initializing asynchronous export process
 org-export-to-file: Wrong type argument: stringp, nil

 the synchronous export works fine.

 If I run emacs with my regular config files, I get:
 Initializing asynchronous export process
 Process 'org-export-process' exited abnormally

 different error message but still not ok.

 What could possibly go wrong ?

Probably you are somehow not loading settings correctly.  In your
normal init file you need to set `org-export-async-init-file'.  In
that file you then need to make sure everything is working as
expected.  On way to debug is to start from emacs -q, load
`org-export-async-init-file' and see what error you expect.

I set `org-export-async-init-file' like the following snippet.  It's
complicated because my init-org-async.el loads a subset of my init
file.

(eval-after-load 'ox ;; shouldn't be byte compiled.
  '(when (and user-init-file (buffer-file-name)) ;; don't do it in async
 (setq org-export-async-init-file
   (expand-file-name init-org-async.el (file-name-directory 
user-init-file)

Here's my init file for async export.  Perhaps you will find a trick
that makes your files export async there.

;; initialization file for org async.

;; Note that in my init.el I use
;; orgstruct with headlines like:
;;   ;;* PRE
;;   ...
;;   ;;* ORG 
;;   ...

(defun read-between-headlines (start optional end file)
  Read a part of the init file.  Give a START regexp to find the
start point and optionally an end regexp.
  (save-match-data
(let ((file (or file
(expand-file-name init.el user-emacs-directory)))
  (end (or end  ^;+ ?\\*\\*? ?[A_Za-z0-9]+))
  (case-fold-search t)
  m1 m2)
  (with-temp-buffer
(insert-file file)
(goto-char (point-min))
(search-forward-regexp start)
(setq m1 (point))
(search-forward-regexp ^;+ ?\\*\\*? ?[A_Za-z0-9]+)
(setq m2 (point))
(eval-region m1 m2)

(mapc (lambda (x) (add-to-list 'load-path x))
  `(/usr/share/emacs/site-lisp/org
/usr/share/emacs/site-lisp/org_contrib/lisp
,(expand-file-name lisp user-emacs-directory)))

(setq user-full-name Rasmus)
(setq user-mail-address ras...@gmx.us)
(require 'org) ;; loads from site lisp
(require 'ox)
(require 'cl)  ;; stupid bug in one of the org-packages? 
(setq org-export-async-debug nil)

(mapc (lambda (x) (read-between-headlines (concat ;+ ?\\*+ ? x))) '(PRE 
ORG))

;; from http://sachachua.com/notebook/emacs/dotemacs.el
(defun ask-user-about-lock (file opponent) Always steal lock. t)

Hope it helps,
Rasmus

-- 
Lasciate ogni speranza o voi che entrate: siete nella mani di'machellaio

Re: [O] async export not working for me

[Nicolas Goaziou]

Hello,

Julien Cubizolles j.cubizol...@free.fr writes:

 I'm running org-mode 8.3beta from org-plus-contrib in melpa. I must have
 missed something obvious cause I could never get async export working.

[...]

 What could possibly go wrong ?

No idea. You may want to set `org-export-async-debug' to a non-nil
value and report the error.


Regards,

-- 
Nicolas Goaziou

Re: [O] Changed behaviours of LaTeX exporter in version 8.0+

[Nicolas Goaziou]

Hello,

Kyeong Soo (Joseph) Kim kyeongsoo@gmail.com writes:

 1. Double backslashes (for line break) embedded in a string for #+AUTHOR:

 With version 7.x, the following line

 #+AUTHOR: Joseph Kim\\Department of Electrical and Electronic
 Engineering\\Example University


[...]

 With version 8.2.7c, however, the same line is exported to

 \author{Joseph Kim$\backslash$\Department of Electrical and Electronic
 Engineering$\backslash$\Example University}

 which results in LaTeX compilation error.

AUTHOR, like TITLE, and DATE, now expect Org syntax, not LaTeX code. You
can insert raw LaTeX using an export snippet: @@latex:\\@@. Your author
line would then be


  #+AUTHOR: Joseph Kim@@latex:\\@@Department of Electrical and Electronic 
Engineering@@latex:\\@@Example University

Note that you can shorten this with a macro.

 2. Accessing the value of #+KEYWORDS: and change of cases in
 org-special-blocks

 For keywords section in IEEE papers, I used to have the following settings:

 #+KEYWORDS: AAA, BBB, CCC
 ...
 #+BEGIN_IEEEkeywords
 {{{KEYWORDS}}}.
 #+END_IEEEkeywords

[...]

 Version 8.2.7c, however, produces the following from the same settings:

 \begin{ieeekeywords}
 .
 \end{ieeekeywords}

I'm surprised {{{KEYWORDS}}} even worked as, AFAIK, it wasn't
documented.  Indeed, there is no such macro in Org 8.0.  However, you
can define your own

#+MACRO: keywords AAA, BBB, CCC

and then use

#+BEGIN_IEEEkeywords
{{{keywords}}}.
#+END_IEEEkeywords

 Because the keyword environment in IEEE LaTeX class is case-sensitive,
 again it results in LaTeX compilation error.

I fixed it in master. It will land in Org 8.3. Meanwhile, you can use
a filter to upcase IEEE in your special blocks.


Regards,

-- 
Nicolas Goaziou

Re: [O] async export not working for me

[Julien Cubizolles]

Rasmus ras...@gmx.us writes:

 Hi Julien,

 Probably you are somehow not loading settings correctly.  In your
 normal init file you need to set `org-export-async-init-file'.

I completely missed this part... I feel stupid now. Maybe org should
complain when this variable is not set and someone like me tries to
export async ?

I will pick what is necessary for export in my normal init file
(basically all org and latex related stuff) and give it a try.

Thanks for pointing that out. I'll have a look at your setup too.


Julien.

Re: [O] Emacs server and org-protocol

[Brett Viren]

Alexis flexibe...@gmail.com writes:

 If i may ask, which email front-end were you using? (Gnus, perhaps?) i
 used to use notmuch.el, and currently use mu4e, and basically don't have
 this issue 

My GNUS + IMAP subprocess + Maildir used to lead to long wait times when
updating for new mail (g in Groups).  Things have now vastly improved
since moving my Maildirs to a SSD.

-Brett.


pgpdCvvL5sXuj.pgp
Description: PGP signature

Re: [O] Emacs server and org-protocol

[Stefan Huchler]

Rainer M Krug rai...@krugs.de writes:

 Stefan Huchler stefan.huch...@mail.de writes:

 I dont really get what the problem is here, email servers checkup is

 Not necessarily - depends which mail server (e.g. gmail or local), if
 you have one or many folders / tags, your network connection, ...

I just did setup the nnrss-download thing and yes mail still takes a bit
longer. I dont even see the big problem in waithing here 2 seks or so,
dont have to check my mails every 10 mins.

What I have more a problem with is that it often hangs have to cancel it
at least every seond time.

And btw is there a way to update my rss things in emacs every 10 mins
automaticly? because if it automaticly downloads every 10 mins the xml
files it would make sense taht in gnus u see the new entries automaticly
after that.

and yes a local email (offline-email-server) would be the solution for
mail, but I am to lazy to setup and backup all that data :)

[O] emacs stackexchange beta site

[Ian Kelling]

Just wanted to share, and bring this up for discussion. I'm cross posting to
a few emacs mailing lists.

http://area51.stackexchange.com/proposals/76571/emacs

And some discussion going on here:
http://discuss.area51.stackexchange.com/questions/17923/what-to-expect-in-the-emacs-private-beta

Which I replied to here http://discuss.area51.stackexchange.com/a/17944/115173

Re: [O] [PATCH] WAS Re: Bug: problem w/ R code blocks [8.3beta (release_8.3beta-362-ga92789 at /usr/local/share/emacs/site-lisp/org/)]

[Cook, Malcolm]

Hiya,

Likewise - same problem here is fixed with injection of patch.  

Thanks!

~ malcolm_cook


 -Original Message-
 From: emacs-orgmode-bounces+mec=stowers@gnu.org 
 [mailto:emacs-orgmode-bounces+mec=stowers@gnu.org] On
 Behalf Of Rainer M Krug
 Sent: Wednesday, September 17, 2014 2:26 AM
 To: Charles Berry
 Cc: emacs-orgmode@gnu.org
 Subject: Re: [O] [PATCH] WAS Re: Bug: problem w/ R code blocks [8.3beta 
 (release_8.3beta-362-ga92789 at
 /usr/local/share/emacs/site-lisp/org/)]
 
 Rainer M Krug rai...@krugs.de writes:
 
 Using it, error is gone.
 
 Rainer
 
  Charles Berry ccbe...@ucsd.edu writes:
 
  Charles Berry ccberry at ucsd.edu writes:
 
 
  Rainer M Krug Rainer at krugs.de writes:
 
  
   Thanks - you came before me. I get the same error but managed to work
   around.
  
   This is likely caused by the upgrade of ess,
 
  Likely.
 
  But it may not be an ESS problem per se.
 
  M-x R starts a process that runs asynchronously. In interactive use there
  is no issue (barring something in .First() that slows the startup for
  a very long time).
 
  But, ...
 
  If the  (rename-buffer ...) in org-babel-R-initiate-session
  runs before all the setup that ESS performs in the process buffer is
  complete, chaos can result.
 
  Not sure what the best way is to fix this.
 
 
  OK. Looks like (ess-wait-for-process) fixes this. Here is a patch.
 
  Thanks.
 
  Haven't tried it yet, but I can't imagine any downside of this
  patch. Could this be committed?
 
  Rainer
 
 
  Chuck
  ==
 
  From 89472012d80ce9ad4c8722f304c0d29327efa1fc Mon Sep 17 00:00:00 2001
  From: chasberry ccbe...@ucsd.edu
  Date: Tue, 16 Sep 2014 19:57:59 -0700
  Subject: [PATCH] lisp/ob-R.el: use `ess-wait-for-process' to assure clean
   session startup
 
  * lisp/ob-R.el (org-babel-R-initiate-session): Make sure that (R) has
  finished before `rename-buffer' is run.
 
  TINYCHANGE
  ---
   lisp/ob-R.el | 3 +++
   1 file changed, 3 insertions(+)
 
  diff --git a/lisp/ob-R.el b/lisp/ob-R.el
  index 41b943c..7575acf 100644
  --- a/lisp/ob-R.el
  +++ b/lisp/ob-R.el
  @@ -35,6 +35,8 @@
   (declare-function inferior-ess-send-input ext:ess-inf ())
   (declare-function ess-make-buffer-current ext:ess-inf ())
   (declare-function ess-eval-buffer ext:ess-inf (vis))
  +(declare-function ess-wait-for-process ext:ess-inf
  +(optional proc sec-prompt wait force-redisplay))
   (declare-function org-number-sequence org-compat (from optional to 
  inc))
   (declare-function org-remove-if-not org (predicate seq))
   (declare-function org-every org (pred seq))
  @@ -262,6 +264,7 @@ This function is called by 
  `org-babel-execute-src-block'.
 ;; Session buffer exists, but with dead process
 (set-buffer session))
   (require 'ess) (R)
  +(ess-wait-for-process)
   (rename-buffer
(if (bufferp session)
(buffer-name session)
 
 --
 Rainer M. Krug
 email: Raineratkrugsdotde
 PGP: 0x0F52F982

Re: [O] TODO items in lists (not headings)

[Nick Dokos]

Gary Oberbrunner ga...@oberbrunner.com writes:

 On Tue, Sep 16, 2014 at 11:48 PM, Thomas S. Dye t...@tsdye.com wrote:

 Aloha Gary,

 Gary Oberbrunner ga...@oberbrunner.com writes:

  Gary:
    My reason for not using TODO is just that it'd be ugly and confusing 
 to
  put a heading in the middle of a list.
 
    Compare this:
  * Meeting report
  ** Meeting 1
    - a thing that happened
    - another thing that happened
    - TODO: email everyone about all the things
    - some more things that happened
 
    to this:
  * Meeting report
  ** Meeting 1
    - a thing that happened
    - another thing that happened
  ***TODO: email everyone about all the things
    - some more things that happened

 One solution is to use a capture template for TODO items and then refile
 them.  I picked this up from Bernt Hansen and like it a lot:

 http://doc.norang.ca/org-mode.html#Capture

 Wow, that guy is serious!  I don't think his setup solves what I'm looking 
 for, but there is so much great stuff in there it'll take me weeks to check 
 it all out.

Indeed - Bernt's writeup has been the source of inspiration for lots of
people on this list.

On your question:

I don't think you can have list items carrying TODO keywords. Why can't
you make the list items third-level headlines instead?

-- 
Nick

Re: [O] Emacs server and org-protocol

[Alexis]

Stefan Huchler writes:

 What I have more a problem with is that it often hangs have to cancel
 it at least every seond time.

Sounds like something that might need to be reported as a bug?


Alexis.

Re: [O] [PATCH] WAS Re: Bug: problem w/ R code blocks [8.3beta (release_8.3beta-362-ga92789 at /usr/local/share/emacs/site-lisp/org/)]

[Aaron Ecay]

Hi all,

I have pushed the patch to the master branch, thanks to Chuck and to
Rainer and Malcom for testing it.

Chuck, it looks like you have already provided another “preliminary
patch” for org back in 2012 (commit 578a7f5a).  If it’s possible for
you, it might be good to do the copyright assignment described at
http://orgmode.org/worg/org-contribute.html#sec-2 before you run
out of lifetime eligibility for TINYCHANGEs (which is ultimately
controlled by the emacs core developers and/or FSF’s lawyers, but
it’s widely taken to be 15 lines or fewer).

-- 
Aaron Ecay

Re: [O] Difference :header-args: and :header-args+:?

[Aaron Ecay]

Hi Achim,

2014ko irailak 9an, Achim Gratz-ek idatzi zuen:
 
 Aaron Ecay writes:
 Can you say more about the corner cases?
 
 It's been quite some time since I looked at this, but inline calls were
 quirky for instance since their point of call is ill-defined.

Surely the point of call is just where they are written in the buffer?
In any case, I’ll just take your word for it that there are unspecified
difficulties.


[...]

 Most computer languages with which I’m familiar (Python, R,
 C, Scheme/Lisp, ...) use lexical scoping by default, and elisp has been
 slowly but steadily moving in that direction for years.  Thus this new
 suggested dynamic-type behavior for header args is surprising to me.
 
 There isn't even an execution model for Babel, so this discussion is
 going nowhere. Anyway, the idea was that when you look at a Babel
 invocation, you should be able to figure out the default header args at
 that point without actually having to trace the execution all the way
 down to the last recursion level.  

That’s one point of view.  The other is that you should be able to
specify a babel block’s behavior fully (i.e. including header args) and
know that it will have that behavior no matter where it is called from.
I think this system better promotes writing modular babel documents.

 That's also important for caching since the cache signature for results
 doesn't take default headers into account.  

But this issue is orthogonal to how the default headers are calculated,
isn’t it?


[...]

 
 No, it doesn't demonstrate this.  Try to accumulate something to the
 commenr property via comment+ at the lower level and convince yourself it
 fails in exactly the same way: only the lowest level is returned as the
 value of the property.
 
 That looks like a bug in the property API.  When getting the property it
 determines that the property is defined at the lowest level and then
 doesn't ascend into the upper ones.  But even the examples in the manual
 show that the entry should add to the higher level definition of the
 property if the +-variant is used.  The problem is that
 org-entry-get-with-inheritance uses org-entry-get (with the inheritance
 parameter set to nil), but has no provision to check for the + on the
 property.

OK, I see.  With this bug fixed, the new system probably has similar
power to the old one indeed.  (Modulo the point of definition vs. point
of call issue.)


[...]

 It looks like it is trying to demonstrate
 inheritance and overriding of :var header args.  I can’t figure out
 why the #+call in “Overwrite” gets go1, but the addition of “var+ to1”
 in “Accumulate” causes this to shift, not to “to1”, but to “ge1”.
 
 The most specific layer is ge1.  While go1 is shadowed by to1 in the
 same layer, this is then again shadowed by ge1 (the more specific
 layer).  Shadowing only happens in the same layer, which are overlaid
 only just before the invocation.  Add :var+: to3 and remove the
 t3=th3 definition to see this in action.

Sorry, I still don’t get it.  I guess this is just a wart of the
interaction between the two systems; let’s hope it disappears as soon as
possible.

-- 
Aaron Ecay

Re: [O] async export not working for me

[Julien Cubizolles]

Julien Cubizolles j.cubizol...@free.fr writes:

 Rasmus ras...@gmx.us writes:

 Hi Julien,

 Probably you are somehow not loading settings correctly.  In your
 normal init file you need to set `org-export-async-init-file'.

I could get it to work at last, thank you a lot. I noticed something
though: when I run org-latex-export-to-pdf async on a very simple test
org file, the *Org Export Stack* buffer displays

--8---cut here---start-8---
 latex0:07   /home/wilk/tmp/test.pdf
--8---cut here---end---8---

and the minibuffer indicates that the process completed.


When I publish a complex project, the line in this buffer is

--8---cut here---start-8---
  exit   *Org Export Process*6
--8---cut here---end---8---

same as if there had been a problem. There is no success message in the
minibuffer, but no error message in the *Org Export Process* buffer.

Julien.

Re: [O] Changed behaviours of LaTeX exporter in version 8.0+

[Kyeong Soo (Joseph) Kim]

Hello Nicolas,

Great thanks for the detailed instructions with clear explanations for the
problems.

I have addressed all those issues per your suggestions, but put some
comments embedded below.


Again, many thanks for your great help!

Joseph


On Thu, Sep 18, 2014 at 3:01 AM, Nicolas Goaziou m...@nicolasgoaziou.fr
wrote:

- snip -


  2. Accessing the value of #+KEYWORDS: and change of cases in
  org-special-blocks
 
  For keywords section in IEEE papers, I used to have the following
 settings:
 
  #+KEYWORDS: AAA, BBB, CCC
  ...
  #+BEGIN_IEEEkeywords
  {{{KEYWORDS}}}.
  #+END_IEEEkeywords

 [...]

  Version 8.2.7c, however, produces the following from the same settings:
 
  \begin{ieeekeywords}
  .
  \end{ieeekeywords}

 I'm surprised {{{KEYWORDS}}} even worked as, AFAIK, it wasn't
 documented.  Indeed, there is no such macro in Org 8.0.  However, you
 can define your own


'{{{KEYWORDS}}}' worked without any issues in previous versions, which in
fact was suggested by someone in the mailing list or stackoverflow
(unfortunately, I couldn't find that via Google any longer).

By the way, in Sec. 12.3 of the Org manual (ver. 8.2.7c), 'KEYWORDS' is
listed together with 'AUTHOR', 'TITLE' and so on as export keywords. Also,
according to Sec. 11.6, those predefined keywords (e.g.,  #+TITLE:,
#+AUTHOR:) can be accessed by {{{title}}} and {{{author}}} like
user-defined macros.

It seems that there is some inconsistency between the actual behavior and
the corresponding manual in export engine of org-mode ver. 8.2.7c.

- snip -