From mboxrd@z Thu Jan 1 00:00:00 1970 From: Eli Zaretskii Subject: bug#19887: 24.4; Cannot kill buffer; Wrong type argument: overlayp, nil Date: Fri, 20 Feb 2015 13:22:27 +0200 Message-ID: <83fva0lte4.fsf@gnu.org> References: <83vbix3nqf.fsf@gnu.org> <83k2zclvgm.fsf@gnu.org> <87h9ugg780.fsf@yahoo.fr> Reply-To: Eli Zaretskii Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:39979) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YOlfm-0002Rb-RH for emacs-orgmode@gnu.org; Fri, 20 Feb 2015 06:23:07 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1YOlfi-0001vM-O4 for emacs-orgmode@gnu.org; Fri, 20 Feb 2015 06:23:06 -0500 Received: from debbugs.gnu.org ([140.186.70.43]:57947) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YOlfi-0001vI-KZ for emacs-orgmode@gnu.org; Fri, 20 Feb 2015 06:23:02 -0500 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.80) (envelope-from ) id 1YOlfi-0005p3-Cw for emacs-orgmode@gnu.org; Fri, 20 Feb 2015 06:23:02 -0500 Sender: "Debbugs-submit" Resent-Message-ID: In-reply-to: <87h9ugg780.fsf@yahoo.fr> 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: Nicolas Richard Cc: damian.nadales@asml.com, 19887@debbugs.gnu.org, mail@nicolasgoaziou.fr > From: Nicolas Richard > Cc: Damian Nadales , 19887@debbugs.gnu.org, Nicolas Goaziou > Date: Fri, 20 Feb 2015 12:20:15 +0100 > > Eli Zaretskii writes: > >> From: Damian Nadales > >> That's weird. Which buffer are you killing, the Org buffer, or the > >> new buffer that is created when pressing C-c ' inside the source > >> block? Is the latter the one I cannot kill. > > > > There was no "C-c '" in the recipe you posted. > > > > What is the full recipe to reproduce the problem, please? > > PMJI, but at , > Nicolas Goaziou said "This should be fixed." > > Perhaps this bug report can simply be closed then ? If it's fixed, please close it.