From: Alexis <flexibeast@gmail.com>
To: 19887@debbugs.gnu.org
Subject: bug#19887: 24.4; Cannot kill buffer; Wrong type argument: overlayp, nil
Date: Wed, 18 Feb 2015 11:35:24 +1100 [thread overview]
Message-ID: <87k2zgm4z7.fsf@gmail.com> (raw)
In-Reply-To: <bnh9uk2vcq.fsf@fencepost.gnu.org>
On 2015-02-18T06:25:57+1100, Glenn Morris said:
GM> Damian Nadales wrote:
>> - Run emacs -Q
>>
>> - Create an org-mode file (i.e. ``myorgfile.org``)
>>
>> - Insert the following text:
>>
>> o #+BEGIN_SRC C++
>>
>> #+END_SRC
>>
>> - Edit the source block by placing the cursor inside the SRC
>> block.
>>
>> - Start C++ mode (c++-mode)
>>
>> - Try to kill the buffer.
GM> Please do
GM> M-x toggle-debug-on-error
GM> repeat the problem, and post the resulting backtrace. (I
can't GM> reproduce it.)
Running a manually compiled Emacs 24.4.1 on Debian
Wheezy(+updates) x86_64, and following the above steps, i can't
reproduce this either.
From the above description, i assume by the "Start C++ mode" line,
you're not moving the cursor inside the source block and then
doing:
C-c '
(i.e. `org-edit-special`) in order to open a c++-mode buffer for
editing the block contents?
Alexis.
next parent reply other threads:[~2015-02-18 0:36 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <A91BE6AD3859A64BB2074A8F81DF08790317E812@NLVDHX735.sn-eu.asml.com>
[not found] ` <bnh9uk2vcq.fsf@fencepost.gnu.org>
2015-02-18 0:35 ` Alexis [this message]
2015-02-18 1:12 ` bug#19887: 24.4; Cannot kill buffer; Wrong type argument: overlayp, nil Nicolas Goaziou
2015-02-18 9:06 ` Damian Nadales
2015-02-19 15:49 ` Eli Zaretskii
2015-02-20 7:32 ` Damian Nadales
2015-02-20 8:52 ` Alexis
2015-02-20 10:37 ` Eli Zaretskii
2015-02-20 11:20 ` Nicolas Richard
2015-02-20 11:22 ` Eli Zaretskii
2015-02-20 12:56 ` Damian Nadales
2017-12-01 19:02 ` Nicolas Goaziou
2015-02-20 12:17 ` Damian Nadales
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=87k2zgm4z7.fsf@gmail.com \
--to=flexibeast@gmail.com \
--cc=19887@debbugs.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).