From: Luke Amdor <luke.amdor@gmail.com>
To: org-mode Mode <emacs-orgmode@gnu.org>
Subject: [PATCH] TINYCHANGE - fix Fix use of org-open-at-point with shell and midnight cleaning
Date: Wed, 29 Apr 2015 13:42:36 +0000 [thread overview]
Message-ID: <CAO_=w4_Dvbze_yefewwqKBv9Qa-m69jq5ZdFvPr9tOgBu55nYQ@mail.gmail.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 136 bytes --]
Patch is attached. I was running into this when I'd run a shell script
through an org link and later a clean-buffers would run. Thanks!
[-- Attachment #1.2: Type: text/html, Size: 161 bytes --]
[-- Attachment #2: 0001-org.el-Fix-use-of-org-open-at-point-with-shell-and-m.patch --]
[-- Type: application/octet-stream, Size: 933 bytes --]
From 6a9dce8de4f8f14f3ffa482e64fb08fe6519d87e Mon Sep 17 00:00:00 2001
From: Luke Amdor <luke.amdor@gmail.com>
Date: Tue, 28 Apr 2015 17:44:17 -0500
Subject: [PATCH] org.el: Fix use of org-open-at-point with shell and midnight
cleaning
* lisp/org.el (org-open-at-point): Make sure org shell output buffer is a string of buffer name before appending to `clean-buffer-list-kill-buffer-names' for cleaning later.
TINYCHANGE
---
lisp/org.el | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/lisp/org.el b/lisp/org.el
index 4635ee8..e2d1724 100755
--- a/lisp/org.el
+++ b/lisp/org.el
@@ -10836,7 +10836,7 @@ link in a property drawer line."
(shell-command cmd buf)
(when (featurep 'midnight)
(setq clean-buffer-list-kill-buffer-names
- (cons buf
+ (cons (buffer-name buf)
clean-buffer-list-kill-buffer-names))))
(user-error "Abort"))))
((equal type "elisp")
--
2.3.5
next reply other threads:[~2015-04-29 13:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-29 13:42 Luke Amdor [this message]
2015-04-29 21:41 ` [PATCH] TINYCHANGE - fix Fix use of org-open-at-point with shell and midnight cleaning Nicolas Goaziou
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='CAO_=w4_Dvbze_yefewwqKBv9Qa-m69jq5ZdFvPr9tOgBu55nYQ@mail.gmail.com' \
--to=luke.amdor@gmail.com \
--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).