From: Hsiu-Khuern Tang <email@example.com> To: "firstname.lastname@example.org" <email@example.com> Subject: Re: cannot edit two source code examples simultaneously Date: Mon, 18 May 2009 17:32:17 -0700 [thread overview] Message-ID: <20090519003216.GL13183@hplhtang1> (raw) In-Reply-To: <4FBDF50D-609C-4816-952C-54A83854F528@gmail.com> * On Sat 05:39PM +0000, 16 May 2009, Carsten Dominik (firstname.lastname@example.org) wrote: > Hi Hsiu-Khuern, > > On May 15, 2009, at 7:38 AM, Hsiu-Khuern Tang wrote: > > Hi Carsten, > > You recently changed org-edit-src-code to use a separate buffer instead of an > indirect buffer. One side effect of this is that I can no longer edit several > code examples at the same time: opening the second buffer will silently discard > any changes made in the first. I would prefer this behavior: when opening the > second edit source buffer, write any changes in the first buffer to the > originating Org buffer (but don't save it, of course). > > Another approach is to use different buffer names. > > I think the second idea is better, provided that a mechanism > ensures that not two editing instances of the same region > are created. This is what I have implemented now. Thank > you for your report. Thanks for implementing this and the subsequent refinements based on Dan's and Taru's inputs! -- Best, Hsiu-Khuern.
prev parent reply other threads:[~2009-05-19 0:34 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2009-05-15 5:38 Hsiu-Khuern Tang 2009-05-16 17:39 ` Carsten Dominik 2009-05-17 17:28 ` Dan Davison 2009-05-18 5:38 ` Taru Karttunen 2009-05-18 6:07 ` Dan Davison 2009-05-18 6:27 ` Taru Karttunen 2009-05-18 10:12 ` Carsten Dominik 2009-05-18 15:23 ` Carsten Dominik 2009-05-18 17:40 ` Dan Davison 2009-05-18 10:48 ` Carsten Dominik 2009-05-19 0:32 ` Hsiu-Khuern Tang [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 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=20090519003216.GL13183@hplhtang1 \ --email@example.com \ --firstname.lastname@example.org \ --subject='Re: cannot edit two source code examples simultaneously' \ /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
Code repositories for project(s) associated with this 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).