From mboxrd@z Thu Jan 1 00:00:00 1970 From: Bastien Subject: Re: [RFC] Org Minor Mode? Date: Thu, 29 May 2014 02:01:58 +0200 Message-ID: <87y4xl1mh5.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> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:45766) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WpnnR-0001CJ-6N for emacs-orgmode@gnu.org; Wed, 28 May 2014 20:02:22 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1WpnnI-0003WO-1d for emacs-orgmode@gnu.org; Wed, 28 May 2014 20:02:13 -0400 Received: from mail-we0-x230.google.com ([2a00:1450:400c:c03::230]:40677) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WpnnH-0003WG-QU for emacs-orgmode@gnu.org; Wed, 28 May 2014 20:02:03 -0400 Received: by mail-we0-f176.google.com with SMTP id q59so12226342wes.35 for ; Wed, 28 May 2014 17:02:03 -0700 (PDT) In-Reply-To: <878uplim22.fsf@gmail.com> (Thorsten Jolitz's message of "Thu, 29 May 2014 00:19:01 +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: > Thats currently possible with outorg.el, M-# M-# on a outshine subtree > or buffer is just the reverse of C-c ' on a source-block - it offers the > subtree of buffer in a temporary *outorg-edit-buffer* in full Org-mode > with the comment-section converted to text and the source-code enclosed > in source-blocks. (Did you look at `org-open-at-point' and the way it handles link in comments? I don't think M-# M-# does the same.) > So this works quite well already. But as outshine evolves, me and others > would like to have it more powerful and even more similar to > Org-mode. Then I start reimplementing features based on outline and > extensions, knowing that they are already there in Org-mode, > sophisticated and well tested. Thats a bit frustrating, especially since > it seems that its just a few chars in the regexps that inhibit using > Org-mode functions outside of org-mode. This would be easy to fix in a > small library, but since Org-mode is so big, this is really a political > thing since changing the regexps would cause more than 600 changes in > the sources and then require a (slightly) different approach to writing > regexps in the future. There is definitely a cost, but the gain would be > considerable too ... This is not about the number of lines to be edited or the man-hour we need to spend on this. Rather about performance and maintainability. -- Bastien