From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Sebastien Vauban" Subject: Re: [BUG] in Release 8.2 - editing code in indirect buffer Date: Tue, 24 Sep 2013 18:53:33 +0200 Message-ID: <86vc1qupo2.fsf@somewhere.org> References: <8F09B93E-FC4D-48B8-A9AB-3EDC0D81EEEF@gmail.com> <220E3767-24DA-494B-9512-9C4DA30CEA43@gmail.com> <86zjr2urcg.fsf@somewhere.org> <578DF849-8046-47A6-879C-FC5874BE591B@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: <578DF849-8046-47A6-879C-FC5874BE591B-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> (Carsten Dominik's message of "Tue, 24 Sep 2013 18:35:22 +0200") 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-mXXj517/zsQ@public.gmane.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org-mXXj517/zsQ@public.gmane.org To: Carsten Dominik Cc: emacs-orgmode-mXXj517/zsQ@public.gmane.org Hi Carsten, Carsten Dominik wrote: > On 24.9.2013, at 18:17, Sebastien Vauban wrote: >> Carsten Dominik wrote: >>> On 23.9.2013, at 09:40, Rainer M Krug wrote: >>>>=20 >>>> When starting to edit a code block via C-c ' everything works as expec= ted >>>> and the code block is highlighted and an indirect buffer is opened. >>>>=20 >>>> When I click into the highlighted block, I an "send" to the indirect b= uffer. >>>> This behavior changes, after saving with C-s, even when nothing has be= en >>>> edited: the area in the original org file looses its magic, and looks = normal >>>> again and can also be edited! >>>>=20 >>>> The indirect buffer stays functional and, upon close via C-c ' saves t= he >>>> changes into the original buffer and *overwrites* changes done in this= block >>>> in the org document. >>>=20 >>> This is a bug which is difficult to fix in all generality. What should = really >>> happen is that the text in the original buffer is made read-only. But s= o far >>> this does not happen in our implementation (due to Dan Davison IIRC). T= he >>> reason for this is that read-only text properties left by accident in a >>> buffer are difficult to get rid of. >>>=20 >>> There are many things the user could go back and screw up the original. >>> That's why Org choses to protect with highlighting with an overlay. Not= e that >>> this is not a protection against editing, but it is a visual warning. >>=20 >> I never knew that "your" goal was to make the code block read-only in th= e Org >> buffer. Note that I would be really opposed to such a change. Editing co= de in >> the prose would really become a pain to me -- please know that I NEVER u= se the >> indirect buffer. > > I only mean while there is a special buffer also editing this block! Pfff! I'm relieved -- I should have understood it=C2=A0;-) Best regards, Seb --=20 Sebastien Vauban