From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thorsten Jolitz Subject: Re: [RFC] Org Minor Mode? Date: Fri, 30 May 2014 15:41:07 +0200 Message-ID: <878upjpeoc.fsf@gmail.com> 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> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:41834) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WqN40-0000nX-8m for emacs-orgmode@gnu.org; Fri, 30 May 2014 09:41:46 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1WqN3u-0000Bj-CZ for emacs-orgmode@gnu.org; Fri, 30 May 2014 09:41:40 -0400 Received: from plane.gmane.org ([80.91.229.3]:56225) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WqN3u-0000BK-6B for emacs-orgmode@gnu.org; Fri, 30 May 2014 09:41:34 -0400 Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1WqN3m-0005uu-Oz for emacs-orgmode@gnu.org; Fri, 30 May 2014 15:41:26 +0200 Received: from g231233099.adsl.alicedsl.de ([92.231.233.99]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 30 May 2014 15:41:26 +0200 Received: from tjolitz by g231233099.adsl.alicedsl.de with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 30 May 2014 15:41:26 +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: emacs-orgmode@gnu.org Bastien writes: Hi Bastien, > Thorsten Jolitz writes: > >> One problem is that more and more Org functions seems to get redefined >> in terms of the new parser functionality, and obviously then can't be >> used anymore outside org-mode. > > That's not a problem if we follow the path I suggest: since the > tempoary buffer we operate in will be in org-mode at some point, the > parser will work there. 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. 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? -- cheers, Thorsten