From: Damian Nadales <damian.nadales@asml.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Glenn Morris <rgm@gnu.org>,
"19887@debbugs.gnu.org" <19887@debbugs.gnu.org>
Subject: bug#19887: 24.4; Cannot kill buffer; Wrong type argument: overlayp, nil
Date: Fri, 20 Feb 2015 12:17:15 +0000 [thread overview]
Message-ID: <A91BE6AD3859A64BB2074A8F81DF08790317EBEF@NLVDHX735.sn-eu.asml.com> (raw)
In-Reply-To: <83k2zclvgm.fsf@gnu.org>
Hi Eli,
> > [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.
>
[Damian Nadales]
No, it wasn't. Sorry for that.
I replied to Glenn Morris yesterday, mentioning these extra details.
> What is the full recipe to reproduce the problem, please?
[Damian Nadales]
So the recipe full recipe is:
- launch emacs -Q
- Create a buffer ``myorgfile.org``
- Insert the following text:
#+BEGIN_SRC C++
#+END_SRC
- Position the cursor in the source code block (between the BEGIN and END directives)
- Press C-c ' (this will open a new buffer)
- Perform M-x c++-mode in the new buffer
- C-x k (kill the newly created buffer)
- You should see the error message now.
Let me know if there is anything else I could do.
Sorry for the vagueness in my first instructions.
Best regards,
Damian.
-- The information contained in this communication and any attachments is confidential and may be privileged, and is for the sole use of the intended recipient(s). Any unauthorized review, use, disclosure or distribution is prohibited. Unless explicitly stated otherwise in the body of this communication or the attachment thereto (if any), the information is provided on an AS-IS basis without any express or implied warranties or liabilities. To the extent you are relying on this information, you are doing so at your own risk. If you are not the intended recipient, please notify the sender immediately by replying to this message and destroy all copies of this message and any attachments. The sender nor the company/group of companies he or she represents shall be liable for the proper and complete transmission of the information contained in this communication, or for any delay in its receipt.
prev parent reply other threads:[~2015-02-20 12:18 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 ` bug#19887: 24.4; Cannot kill buffer; Wrong type argument: overlayp, nil Alexis
2015-02-18 1:12 ` 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 [this message]
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=A91BE6AD3859A64BB2074A8F81DF08790317EBEF@NLVDHX735.sn-eu.asml.com \
--to=damian.nadales@asml.com \
--cc=19887@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=rgm@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).