One possible reason for a lack of reply is the miss-tagging with "babel"
in the subject line.  This doesn't have anything to do with code block
execution, so I've re-tagged the subject and hopefully someone with
knowledge of this portion of the code will reply.

Cheers,

Rainer M Krug <rai...@krugs.de> writes:

> Just to reiterate - is this only me or others as well? I consider this
> as a serious problem, as it can result in loss of data.
>
> If it is only me, I have to dig deeper into my config.
>
> Cheers,
>
> Rainer 
>
> Rainer M Krug <rai...@krugs.de> writes:
>
>> Carsten Dominik <carsten.domi...@gmail.com> writes:
>>
>>>     
>>> Hi everyone,
>>>
>>> I have just released version 8.2 of Org mode.  This is rather a minor 
>>> release,
>>> mainly designed to do some stabilization and cleanup before the merge
>>> into Emacs.  Bastien will do this next week (?).
>>
>> Just upgraded, to 8.2 and I found a bug:
>>
>> When starting to edit a code block via C-c ' everything works as expected
>> and the code block is highlighted and an indirect buffer is opened.
>>
>> When I click into the highlighted block, I an "send" to the indirect
>> buffer. This behavior changes, after saving with C-s, even when nothing
>> has been edited: the area in the original org file looses its magic, and
>> looks normal again and can also be edited! 
>>
>> he indirect buffer stays functional and, upon close vie C-c ' saves the
>> changes into the original buffer and overwrites changes done in this block.
>>
>> Can somebody please confirm?
>>
>> Rainer
> <#secure method=pgpmime mode=sign>
>

-- 
Eric Schulte
https://cs.unm.edu/~eschulte
PGP: 0x614CA05D

Reply via email to