From mboxrd@z Thu Jan 1 00:00:00 1970 From: Alan Parker Lue Subject: org-agenda-quit Kills Visible Buffers Date: Thu, 24 Dec 2015 15:09:48 -0800 Message-ID: Mime-Version: 1.0 Content-Type: multipart/alternative; boundary=001a113ecd447371820527acefcf Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:36386) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aCF14-00086L-8T for emacs-orgmode@gnu.org; Thu, 24 Dec 2015 18:09:50 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1aCF13-0003ji-EV for emacs-orgmode@gnu.org; Thu, 24 Dec 2015 18:09:50 -0500 Received: from mail-io0-x232.google.com ([2607:f8b0:4001:c06::232]:36109) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aCF13-0003jd-75 for emacs-orgmode@gnu.org; Thu, 24 Dec 2015 18:09:49 -0500 Received: by mail-io0-x232.google.com with SMTP id o67so250904344iof.3 for ; Thu, 24 Dec 2015 15:09:49 -0800 (PST) List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: emacs-orgmode@gnu.org --001a113ecd447371820527acefcf Content-Type: text/plain; charset=UTF-8 After upgrading org-mode recently, I find that hitting "q" for (org-agenda-quit) while viewing an agenda kills the buffer that was active when I created the agenda. I'm on org-mode v8.3.2. To reproduce: - Activate a buffer, call it =active_buf.txt= - C-c a for (org-agenda) - a for "Agenda for current week or day" - q for (org-agenda-quit) I find that =active_buf.txt= has now been killed. Same thing happens with "x" for (org-agenda-exit). Also happens after completely doing away with my init.el, so I don't believe this is the result of a setting. What is going on? Alan --001a113ecd447371820527acefcf Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
After upgrading org-mode recently, I find that hitting &qu= ot;q" for (org-agenda-quit) while viewing an agenda kills the buffer t= hat was active when I created the agenda.

I'm on org= -mode v8.3.2. To reproduce:
  • Activate a buffer, call it = =3Dactive_buf.txt=3D
  • C-c a for (org-agenda)
  • a for "Age= nda for current week or day"
  • q for (org-agenda-quit)
=
I find that =3Dactive_buf.txt=3D has now been killed.
=
Same thing happens with "x" for (org-agenda-exit).= Also happens after completely doing away with my init.el, so I don't b= elieve this is the result of a setting.

What is go= ing on?

Alan

--001a113ecd447371820527acefcf--