From: Rainer M Krug <Rainer@krugs.de>
To: Carsten Dominik <carsten.dominik@gmail.com>
Cc: emacs-orgmode@gnu.org, Eric Schulte <eschulte@cs.unm.edu>
Subject: Re: [BUG] in Release 8.2 - editing code in indirect buffer
Date: Wed, 25 Sep 2013 09:38:41 +0200 [thread overview]
Message-ID: <m2siwt8i66.fsf@krugs.de> (raw)
In-Reply-To: <4B85FCE2-E97D-429F-87C2-A553025F1D96@gmail.com> (Carsten Dominik's message of "Wed, 25 Sep 2013 09:09:52 +0200")
[-- Attachment #1: Type: text/plain, Size: 3597 bytes --]
Carsten Dominik <carsten.dominik@gmail.com> writes:
> On 25.9.2013, at 08:53, Rainer M Krug <Rainer@krugs.de> wrote:
>
>> "Sebastien Vauban" <sva-news@mygooglest.com>
>> writes:
>>
>>> Hi Carsten,
>>>
>>> Carsten Dominik wrote:
>>>> On 24.9.2013, at 18:17, Sebastien Vauban <sva-news@mygooglest.com> wrote:
>>>>> Carsten Dominik wrote:
>>>>>> On 23.9.2013, at 09:40, Rainer M Krug <Rainer@krugs.de> wrote:
>>>>>>>
>>>>>>> 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!
>>>>>>>
>>>>>>> The indirect buffer stays functional and, upon close via C-c ' saves the
>>>>>>> changes into the original buffer and *overwrites* changes done in this block
>>>>>>> in the org document.
>>>>>>
>>>>>> 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 so far
>>>>>> this does not happen in our implementation (due to Dan Davison IIRC). The
>>>>>> reason for this is that read-only text properties left by accident in a
>>>>>> buffer are difficult to get rid of.
>>>>>>
>>>>>> 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. Note that
>>>>>> this is not a protection against editing, but it is a visual warning.
>>>>>
>>>>> I never knew that "your" goal was to make the code block read-only in the Org
>>>>> buffer. Note that I would be really opposed to such a change. Editing code in
>>>>> the prose would really become a pain to me -- please know that I NEVER use 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 ;-)
>>
>> While we are at editing code blocks inline (I also do this quite often).
>>
>> This might have been asked before, but in code blocks we have
>>
>> - syntax highlighting
>> - indenting using the code block language settings
>>
>> but would it be possible to have, when the cursor is in a code block,
>> the menus and shortcuts for the language mode enabled, i.e. complete
>> support for editing the code block language, as in the special buffer,
>> but inline in org? Evaluationg single lines of code directly from the
>> code block in org would be *brilliant*.
>
> This is very complicated, because such functionality needs
> the entire environment of a mode. I think there are some solutions
> which allow multiple major modes - but I don't think we will go
> there with Org.
This is definitely not an easy task, but which I think would be an very
useful feature, making the work-flow of using embedded code much faster.
>
> However, I think this is really a question to Eric Schulte (in CC).
Would be great, if there is would be a way of implementing this in the
medium future.
Cheers,
Rainer
>
> - Carsten
>
>>
>> Cheers,
>>
>> Rainer
>>
>>>
>>> Best regards,
>>> Seb
>> <#secure method=pgpmime mode=sign>
>>
>> --
>> Rainer M. Krug
>>
>> email: RMKrug<at>gmail<dot>com
>>
>>
>
--
Rainer M. Krug
email: RMKrug<at>gmail<dot>com
[-- Attachment #2: Type: application/pgp-signature, Size: 486 bytes --]
next prev parent reply other threads:[~2013-09-25 7:39 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 ` BUG?: BABEL " Ista Zahn
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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m2siwt8i66.fsf@krugs.de \
--to=rainer@krugs.de \
--cc=carsten.dominik@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=eschulte@cs.unm.edu \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.