From: "François Allisson" <francois@allisson.co>
To: emacs-orgmode@gnu.org
Subject: [BUG] shell links broken
Date: Sun, 5 Aug 2012 11:21:18 +0200 [thread overview]
Message-ID: <20120805092118.GA12989@debian> (raw)
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)
------------------------------
next reply other threads:[~2012-08-05 9:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-05 9:21 François Allisson [this message]
2012-08-05 9:41 ` [BUG] shell links broken Bastien
2012-08-05 13:26 ` [BUG] [PATCH] " François Allisson
2012-08-05 14:29 ` Bastien
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20120805092118.GA12989@debian \
--to=francois@allisson.co \
--cc=emacs-orgmode@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).