From mboxrd@z Thu Jan 1 00:00:00 1970 From: Bastien Subject: Re: [RFC] Org Minor Mode? Date: Fri, 30 May 2014 15:54:26 +0200 Message-ID: <87lhtj8j8t.fsf@bzg.ath.cx> References: <87ha61f4rk.fsf@gmail.com> <8738hlkn64.fsf@gmail.com> <87zjj9g87k.fsf@gmail.com> <877g5znrgl.fsf@bzg.ath.cx> <87y4xnzif9.fsf@gmail.com> <8738ft379k.fsf@bzg.ath.cx> <878uplim22.fsf@gmail.com> <87y4xl1mh5.fsf@bzg.ath.cx> <87zji0xysn.fsf@gmail.com> <87y4xks9a7.fsf@bzg.ath.cx> <87a99zlkbi.fsf@gmail.com> <87mwdzmplh.fsf@bzg.ath.cx> <878upjpeoc.fsf@gmail.com> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:46471) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WqNGf-0001IB-PR for emacs-orgmode@gnu.org; Fri, 30 May 2014 09:54:54 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1WqNGW-0005yc-PB for emacs-orgmode@gnu.org; Fri, 30 May 2014 09:54:45 -0400 Received: from mail-wi0-x231.google.com ([2a00:1450:400c:c05::231]:61837) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WqNGW-0005yO-GA for emacs-orgmode@gnu.org; Fri, 30 May 2014 09:54:36 -0400 Received: by mail-wi0-f177.google.com with SMTP id f8so1158282wiw.10 for ; Fri, 30 May 2014 06:54:33 -0700 (PDT) In-Reply-To: <878upjpeoc.fsf@gmail.com> (Thorsten Jolitz's message of "Fri, 30 May 2014 15:41:07 +0200") List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Thorsten Jolitz Cc: emacs-orgmode@gnu.org Hi Thorsten, Thorsten Jolitz writes: > I'm still not sure if this path isn't just the outorg path: copy a > subtree or a whole buffer into a temp-buffer, uncomment the comment > sections, enclose the source-code in source-blocks, and put the buffer > in Org-mode - only that the tmp buffer in this case is not for user > editing but for program execution. Yes -- that's the outorg path but transparent to the user, with no editing in the middle. > What will be copied to the temp-buffer? Only the comment-section at > point? The subtree at point? The (outcommented) element at point? Won't > some Org functions fail without the subtree/buffer context? What if text > is inserted as side-effect? E.g state change logs when going from TODO > to done, or even footnotes? Well, I don't know. Again, all this feels certainly dirty, but I'm trying to find something that will feel less awkward than making tons of Org regexps relative to their contexts, including the context for non-org-mode buffers... -- Bastien