From: phillip.lord@newcastle.ac.uk (Phillip Lord)
To: "Andreas Röhler" <andreas.roehler@easy-emacs.de>
Cc: Nicolas Richard <theonewiththeevillook@yahoo.fr>, help-gnu-emacs@gnu.org
Subject: Re: indirect-buffers and text-properties
Date: Fri, 31 Jan 2014 09:46:00 +0000 [thread overview]
Message-ID: <87eh3ocwmf.fsf@newcastle.ac.uk> (raw)
In-Reply-To: <52EA8135.8060105@easy-emacs.de> ("Andreas \=\?utf-8\?Q\?R\=C3\=B6h\?\= \=\?utf-8\?Q\?ler\=22's\?\= message of "Thu, 30 Jan 2014 17:43:33 +0100")
Andreas Röhler <andreas.roehler@easy-emacs.de> writes:
> Am 30.01.2014 16:36, schrieb Nicolas Richard:
>> Andreas Röhler <andreas.roehler@easy-emacs.de> writes:
>>> M-x org-edit-src-code
>>> uses an indirect buffer, but fontifies correctly.
>>
>> It is not an indirect buffer in my version, it uses generate-new-buffer.
>>
>
> Ah, thanks. When having a look into again, seems it's not used for languages,
> while `org-tree-to-indirect-buffer' has it.
It's also not quite what I want. With org-edit-src-code when you edit
the code, it pops up a buffer in the correct mode, then you edit but
only in this buffer -- the org mode buffer is unchanged, then it is
"commited" back to org.
I really want to see the two parts simultaneously, for the entire
buffer, but in two modes.
Phil
prev parent reply other threads:[~2014-01-31 9:46 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-30 12:29 indirect-buffers and text-properties Phillip Lord
2014-01-30 13:27 ` Stefan Monnier
2014-01-30 14:13 ` Phillip Lord
2014-01-30 15:03 ` Stefan Monnier
2014-01-30 15:45 ` Phillip Lord
2014-01-30 16:17 ` Stefan Monnier
2014-01-31 9:52 ` Phillip Lord
2014-01-31 13:35 ` Stefan Monnier
2014-01-31 16:12 ` Phillip Lord
2014-01-30 15:33 ` Andreas Röhler
2014-01-30 15:36 ` Nicolas Richard
2014-01-30 16:43 ` Andreas Röhler
2014-01-31 9:46 ` Phillip Lord [this message]
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=87eh3ocwmf.fsf@newcastle.ac.uk \
--to=phillip.lord@newcastle.ac.uk \
--cc=andreas.roehler@easy-emacs.de \
--cc=help-gnu-emacs@gnu.org \
--cc=theonewiththeevillook@yahoo.fr \
/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.