From: Paul Davis <paul.dangersalad@gmail.com>
To: Nicolas Goaziou <mail@nicolasgoaziou.fr>
Cc: emacs-orgmode@gnu.org
Subject: Re: Bug: Editing src blocks: user-error: Cannot modify an area being edited in a dedicated buffer [9.1.4 (9.1.4-2-g118753-elpaplus @ /home/paul/.emacs.d/elpa/org-plus-contrib-20171211/)]
Date: Thu, 21 Dec 2017 22:39:33 +0000 [thread overview]
Message-ID: <CAPvM=sT=QepB-qb0NFjP1DX4+CsOa84EyDFWg3zfwTHhpRARFg@mail.gmail.com> (raw)
In-Reply-To: <87o9mwkvtq.fsf@nicolasgoaziou.fr>
[-- Attachment #1: Type: text/plain, Size: 915 bytes --]
Turns out that the issue was caused by trying to disable a flycheck checker
using the org edit src hook
On Mon, Dec 18, 2017, 6:30 AM Nicolas Goaziou <mail@nicolasgoaziou.fr>
wrote:
> Hello,
>
> Paul Davis <paul.dangersalad@gmail.com> writes:
>
> > Using ~C-c '~ to edit a src block works as expected, but if I make
> > changes and use ~C-c '~ again, I get the error ~Cannot modify an area
> > being edited in a dedicated buffer~
>
> I need more information. Where do you make changes? In the newly created
> buffer? Where do you call ~C-c '~?
>
> For example, I created the following buffer
>
> #+begin_src emacs-lisp
> (+ 1 2)
> #+end_src
>
> moved on the source block, used C-c '. Then, in the new buffer,
> I replaced 2 with 3 and pressed C-c ' again, without any error?
>
> IOW, could you provide a precise recipe demonstrating the issue?
>
> Thank you.
>
> Regards,
>
> --
> Nicolas Goaziou
>
[-- Attachment #2: Type: text/html, Size: 1356 bytes --]
next prev parent reply other threads:[~2017-12-21 22:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-17 19:11 Bug: Editing src blocks: user-error: Cannot modify an area being edited in a dedicated buffer [9.1.4 (9.1.4-2-g118753-elpaplus @ /home/paul/.emacs.d/elpa/org-plus-contrib-20171211/)] Paul Davis
2017-12-18 13:30 ` Nicolas Goaziou
2017-12-21 22:39 ` Paul Davis [this message]
2017-12-22 10:24 ` stardiviner
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='CAPvM=sT=QepB-qb0NFjP1DX4+CsOa84EyDFWg3zfwTHhpRARFg@mail.gmail.com' \
--to=paul.dangersalad@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=mail@nicolasgoaziou.fr \
/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).