From: Eric Schulte <schulte.eric@gmail.com>
To: Andy Moreton <andrewjmoreton@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Bug: source code editing using C-c ' (org-edit-special) eats characters
Date: Thu, 08 Nov 2012 10:27:16 -0700 [thread overview]
Message-ID: <87625gj98r.fsf@gmail.com> (raw)
In-Reply-To: <509BADF5.6020006@gmail.com> (Andy Moreton's message of "Thu, 08 Nov 2012 13:04:53 +0000")
Andy Moreton <andrewjmoreton@gmail.com> writes:
> On 07/11/2012 23:02, Eric S Fraga wrote:
>> Andy Moreton <andrewjmoreton@gmail.com> writes:
>>> I'm seeing a similar problem in emacs trunk (r110821) where "C-c '" in
>>> the *Org Src* buffer closes the source edit window and discards the
>>> entire contents of the source block.
>>>
>>> Should I raise an emacs bug for this ?
>>>
>>> AndyM
>>
>> I've seen this happen recently as well, specifically where I have added
>> comment lines to the source, e.g. lines starting with # in sh src code
>> blocks. I was in a rush to get something done so didn't stop to try to
>> figure out what was happening or to generate a minimal example. I also
>> don't know if it's still happening -- this happened to me late last
>> week, IRC. I also don't know if the problem was dependent on the
>> version of Emacs as I use three systems daily (long story).
>
> This problem does seem difficult to reproduce consistently.
> Editing this to add new source discarded all edits:
>
> #+begin_src c
> #+end_src
>
> Changing it to use "C" made it keep the edits:
>
> #+begin_src C
> #+end_src
>
> However after changing the source block back to using "c", the problem did not
> return.
>
> I've seen problems more consistently with shell script blocks:
>
> #+begin_src shell-script
> #+end_src
>
> I'll try to produce a recipe that can consistently show this problem.
>
I have a similar and possibly related problem which I can consistently
reproduce.
In any Org-mode buffer create and enter an empty code block, I like to
do this with "<s TAB sh DOWNARROW" resulting in the following with the
cursor at C
#+begin_src sh
C
#+end_src
Then "C-'" into edit mode type "foo bar" do *not* type enter, and then
do a "C-'" again to go back to the Org-mode buffer. You are left with
the following in the Org-mode buffer, which is not valid Org.
#+begin_src sh
foo bar#+end_src
This is a relatively new problem which I only begun to notice in the
last month or so.
Best,
>
> AndyM
>
>
--
Eric Schulte
http://cs.unm.edu/~eschulte
next prev parent reply other threads:[~2012-11-08 17:26 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-23 18:03 Bug: source code editing using C-c ' (org-edit-special) eats characters Hsiu-Khuern Tang
2012-10-23 20:07 ` Myles English
2012-10-23 20:31 ` Nick Dokos
2012-10-23 21:04 ` myles english
2012-10-23 21:16 ` Hsiu-Khuern Tang
2012-10-25 8:53 ` Bastien
2012-10-30 17:20 ` Hsiu-Khuern Tang
2012-11-07 13:38 ` Andy Moreton
2012-11-07 23:02 ` Eric S Fraga
2012-11-08 3:20 ` Eric S Fraga
2012-11-08 13:04 ` Andy Moreton
2012-11-08 17:27 ` Eric Schulte [this message]
2012-11-09 3:19 ` Eric Fraga
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=87625gj98r.fsf@gmail.com \
--to=schulte.eric@gmail.com \
--cc=andrewjmoreton@gmail.com \
--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).