emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Ista Zahn <istazahn@gmail.com>
To: Rainer M Krug <Rainer@krugs.de>
Cc: emacs-orgmode Mailinglist <emacs-orgmode@gnu.org>
Subject: Re: BUG?: BABEL - Release 8.2
Date: Sat, 21 Sep 2013 11:25:54 -0400	[thread overview]
Message-ID: <CA+vqiLHt2RvK+az8t32L9Pb-dZW+gw7edymMmWfd3Ernek1GhQ@mail.gmail.com> (raw)
In-Reply-To: <m2siwynuuy.fsf@krugs.de>

I observe the same behavior with org installed from
elpa/org-plus-contrib-20130916.

Best,
Ista

On Sat, Sep 21, 2013 at 9:54 AM, Rainer M Krug <Rainer@krugs.de> wrote:
> 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 <Rainer@krugs.de> writes:
>
>> Carsten Dominik <carsten.dominik@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>
>
> --
> Rainer M. Krug
>
> email: RMKrug<at>gmail<dot>com
>
>

  parent reply	other threads:[~2013-09-21 15:26 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-19 20:27 Release 8.2 Carsten Dominik
2013-09-20  4:32 ` Mehul Sanghvi
2013-09-20  5:07   ` Carsten Dominik
2013-09-20  9:40 ` Alexander Baier
2013-09-20 10:01   ` Carsten Dominik
2013-09-20 11:06 ` BUG?: BABEL - " Rainer M Krug
2013-09-20 11:06 ` Rainer M Krug
2013-09-21 13:54   ` Rainer M Krug
2013-09-21 15:02     ` BUG?: Org-src " Eric Schulte
2013-09-21 15:25     ` Ista Zahn [this message]
2013-09-20 11:17 ` Suvayu Ali
2013-09-23  7:40 ` [BUG] in Release 8.2 - editing code in indirect buffer Rainer M Krug
2013-09-24 14:01   ` Rainer M Krug
2013-09-24 16:02   ` Carsten Dominik
2013-09-24 16:17     ` Sebastien Vauban
2013-09-24 16:35       ` Carsten Dominik
     [not found]         ` <578DF849-8046-47A6-879C-FC5874BE591B-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2013-09-24 16:53           ` Sebastien Vauban
2013-09-25  6:53             ` Rainer M Krug
2013-09-25  7:09               ` Carsten Dominik
2013-09-25  7:38                 ` Rainer M Krug
2013-09-25 13:13                   ` Eric Schulte
2013-09-25 14:00                     ` Rainer M Krug
2013-09-25 19:39                     ` Andreas Leha
2013-09-26  8:11                       ` Rainer M Krug
2013-09-25  6:48     ` Rainer M Krug
2013-09-25  7:15       ` Carsten Dominik
2013-09-25  7:29         ` Rainer M Krug
2013-10-02 22:55 ` Release 8.2 Mike McLean

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=CA+vqiLHt2RvK+az8t32L9Pb-dZW+gw7edymMmWfd3Ernek1GhQ@mail.gmail.com \
    --to=istazahn@gmail.com \
    --cc=Rainer@krugs.de \
    --cc=emacs-orgmode@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).