From: Thorsten Jolitz <tjolitz@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: [RFC] Org Minor Mode?
Date: Tue, 27 May 2014 11:20:58 +0200 [thread overview]
Message-ID: <87y4xnzif9.fsf@gmail.com> (raw)
In-Reply-To: 877g5znrgl.fsf@bzg.ath.cx
Bastien <bzg@gnu.org> writes:
Hi Bastien,
> Thorsten Jolitz <tjolitz@gmail.com> writes:
>
>> So I would rather have a clear picture of the 'political situation' wrt
>> to org-minor-mode and some technical discussion first. But anyway, I
>> will not have time to work on this again before June.
>
> I for one need to have a clearer picture of what such a minor mode
> would really do, without getting prematurily lost in the details of
> possible implementations.
Its just a better and smarter outshine-mode (major-mode agnostic "Org
look&feel" for programming modes).
> Once we have a clear goal, let's build a small list of steps, then
> submit a patch for the first step. (We can then work on a separate
> branch for the whole feature, and spend months on this branch.)
The goal for org-minor-mode would be the same like for outshine - give
programming mode buffers the same look&feel like Org-mode buffers. This
works already quite good with outshine, I structure all my elisp,
picolisp, R, CSS (etc etc) files like Org files, and when I switch between
them and Org-files I hardly notice a difference wrt navigation, folding,
structure editing, fontification etc.
But the backend for outshine is outline-(minor)-mode. Org-mode does some
things better than outline-mode, and tons of things outline-mode can't
do.
> If the change is relying on too many external libraries, it is not
> very likely to happen.
It should end up as one new library (e.g. omm.el) that is part of
Org-mode, replacing both orgstruct-mode and outshine.
> The feature seems to bring interest, but let's refrain from spending
> our enthusiasm in early and lengthy discussions that nobody can fully
> follow, especially if you won't have time to hack something before
> June...
outshine, outorg and navi-mode are all in the mid-range of popular melpa
packages, so there seems to be some real demand ...
> So I really don't want to play the cold fish here, but let's move
> with code and small steps rather than discussions and big goals.
I started with code (https://github.com/tj64/omm), but faced the
fundamental problem of hardcoded regexps (^, $, and \\*) all over the
Org sources that make Org functions fail on outcommented headers and in
outcommented text sections in general.
The goals, ideas and even implementations (outshine, orgstruct) are
already there, a first intent to merge them into one library exists
(omm.el), but what to do about this core problem?
--
cheers,
Thorsten
next prev parent reply other threads:[~2014-05-27 9:21 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 [this message]
2014-05-28 21:47 ` Bastien
2014-05-28 22:19 ` Thorsten Jolitz
2014-05-29 0:01 ` Bastien
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=87y4xnzif9.fsf@gmail.com \
--to=tjolitz@gmail.com \
--cc=emacs-orgmode@gnu.org \
/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).