emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Bastien <bzg@gnu.org>
To: Thorsten Jolitz <tjolitz@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: [RFC] Org Minor Mode?
Date: Thu, 29 May 2014 02:01:58 +0200	[thread overview]
Message-ID: <87y4xl1mh5.fsf@bzg.ath.cx> (raw)
In-Reply-To: <878uplim22.fsf@gmail.com> (Thorsten Jolitz's message of "Thu, 29 May 2014 00:19:01 +0200")

Hi Thorsten

Thorsten Jolitz <tjolitz@gmail.com> 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

  reply	other threads:[~2014-05-29  0:02 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-10 17:55 [RFC] Org Minor Mode? Thorsten Jolitz
2014-04-10 19:19 ` Nicolas Goaziou
2014-04-11 10:07   ` Bastien
2014-04-11 17:22     ` Richard Lawrence
2014-04-13 16:28       ` Thorsten Jolitz
2014-04-19  5:37       ` Samuel Wales
2014-04-19 10:25         ` Thorsten Jolitz
2014-04-13 16:07     ` Thorsten Jolitz
2014-04-18 13:27       ` Bastien
2014-04-13 16:00   ` Thorsten Jolitz
2014-04-18 13:29     ` Bastien
2014-04-18 15:54       ` Thorsten Jolitz
2014-04-19  5:23         ` Bastien
2014-04-19 10:11           ` Thorsten Jolitz
2014-04-19 12:57             ` Bastien
2014-04-24 21:06               ` Ilya Shlyakhter
2014-04-25  8:00                 ` Thorsten Jolitz
2014-04-29 12:24                 ` Bastien
2014-04-29 18:44                   ` Ilya Shlyakhter
2014-05-06  9:06                     ` Bastien
2014-04-24 21:16   ` Ilya Shlyakhter
2014-04-25  7:49     ` Thorsten Jolitz
2014-05-06  9:20       ` Bastien
2014-05-27  9:20         ` Thorsten Jolitz
2014-05-28 21:47           ` Bastien
2014-05-28 22:19             ` Thorsten Jolitz
2014-05-29  0:01               ` Bastien [this message]
2014-05-29 17:47                 ` Thorsten Jolitz
2014-05-29 18:57                   ` Bastien
2014-05-30  8:52                     ` Thorsten Jolitz
2014-05-30 12:13                       ` Bastien
2014-05-30 13:41                         ` Thorsten Jolitz
2014-05-30 13:54                           ` Bastien
2014-05-30 14:15                             ` Thorsten Jolitz
2014-05-30 14:22                               ` Bastien
2014-05-30 14:38                                 ` Thorsten Jolitz

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=87y4xl1mh5.fsf@bzg.ath.cx \
    --to=bzg@gnu.org \
    --cc=emacs-orgmode@gnu.org \
    --cc=tjolitz@gmail.com \
    /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 public 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).