From: Thorsten Jolitz <tjolitz@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: [RFC] Org Minor Mode?
Date: Sat, 19 Apr 2014 12:11:41 +0200 [thread overview]
Message-ID: <87d2gdtyqq.fsf@gmail.com> (raw)
In-Reply-To: 87ioq5hoze.fsf@bzg.ath.cx
Bastien <bzg@gnu.org> writes:
Hi Bastien,
> Thorsten Jolitz <tjolitz@gmail.com> writes:
>
>> The real value and innovation of a true
>> org-minor-mode would be to introduce Org's intelligent headlines and all
>> the related functionality into the world of outcommented text in
>> programming modes.
>
> Yes. We could have `orgstruct-comment-prefix-regexp' along with
> `orgstruct-heading-prefix-regexp'. I'll check this, thanks for
> the idea!
As long as there are hardcoded regexp searches all over the place in
org.el, org-agenda.el, orgtbl.el, and to a minor extends almost all
other Org libraries, I don't think just another outline-regexp can do
the trick - the called functions will fail when trying to match
,--------
| "^foo$"
`--------
but looking at
,---------------------------------------------------------------
| "^<<comment-starter-syntax>>foo<<maybe-comment-end-syntax>>$"
`---------------------------------------------------------------
Furthermore calling Org functions modifies the buffer, sometimes
inserting new lines, sometimes not. An Org minor-mode would need to
detect all newly inserted lines after a command call and outcomment them
with the programming major-mode's comment syntax.
I already found a way to do that using external calls to diff, its
implemented in omm.el (needs to be debugged though, I stopped working on
it because it seemed the idea of an Org Minor Mode was a bit unpopular).
In summary, its about:
1. generalize the regexp constants and vars (allow for comment-syntax,
when org-minor-mode)
2. deal with hardcoded regexp-snippets in functions (my proposoal:
replace "^" with org-BOL, "$" with org-EOL, "\\*" with org-STAR)
3. outcomment new lines after calls to Org commands.
All the other stuff should be already there in orgstruct and outshine.
--
cheers,
Thorsten
next prev parent reply other threads:[~2014-04-19 10:10 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 [this message]
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
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=87d2gdtyqq.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).