[O] [BUG] shell links broken

2012-08-05 Thread François Allisson
Hello list,

Since last update of org this morning, I cannot open shell links any
longer. Instead, I get the message void-variable
clean-buffer-list-kill-buffer-names in the mini-buffer.

Commit 96551f3dd8885dee6972c70ce06888fd3d5f4dd4
(http://orgmode.org/w/?p=org-mode.git;a=commit;h=96551f3dd8885dee6972c70ce06888fd3d5f4dd4)
seems to be responsible. I don't understand the idea behind this huge
commit (I just started to read the elisp intro, since all my e-life is
in org now, it's time to start understanding the tool I use ;-)
hopefully I'll be more useful in some time for these kind of stuffs).

Anyway, below are potentially useful stuffs to reproduce the bug.

Best,
François


Versions:
Org-mode version 7.8.11 (release_7.8.11-366-g6f571d @ 
/usr/local/share/emacs/24.1.50/site-lisp/org/)
GNU Emacs 24.1.50.1 (i686-pc-linux-gnu, GTK+ Version 2.24.10) of 2012-08-02 on 
debian

-*ecm.org*
* An eshell link
[[shell:echo 'Hello!'][My shell is polite.]]


-*Backtrace*--
Debugger entered--Lisp error: (void-variable 
clean-buffer-list-kill-buffer-names)
  org-open-at-point(nil)
  call-interactively(org-open-at-point nil nil)
--

-*minimal-org.el*-
(setq debug-on-error t
  debug-on-signal nil
  debug-on-quit nil) 
(add-to-list 'load-path (expand-file-name 
/usr/local/share/emacs/24.1.50/site-lisp/org))
(require 'org-install)
--



Re: [O] [BUG] shell links broken

2012-08-05 Thread Bastien
Hi François,

François Allisson franc...@allisson.co writes:

 Since last update of org this morning, I cannot open shell links any
 longer. Instead, I get the message void-variable
 clean-buffer-list-kill-buffer-names in the mini-buffer.

Fixed, thanks.

 Commit 96551f3dd8885dee6972c70ce06888fd3d5f4dd4
 (http://orgmode.org/w/?p=org-mode.git;a=commit;h=96551f3dd8885dee6972c70ce06888fd3d5f4dd4)
 seems to be responsible. I don't understand the idea behind this huge
 commit (I just started to read the elisp intro, since all my e-life is
 in org now, it's time to start understanding the tool I use ;-)
 hopefully I'll be more useful in some time for these kind of stuffs).

This is not from this commit.

 Anyway, below are potentially useful stuffs to reproduce the bug.

Thanks for the detailed recipe!

All best,

-- 
 Bastien