emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Thorsten Jolitz <tjolitz@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: [RFC] Org Minor Mode?
Date: Fri, 25 Apr 2014 10:00:46 +0200	[thread overview]
Message-ID: <87vbtxg7o1.fsf@gmail.com> (raw)
In-Reply-To: ljbudl$ppc$1@ger.gmane.org

Ilya Shlyakhter <ilya_shl@alum.mit.edu> writes:

> On 4/19/2014 8:57 AM, Bastien wrote:
>> Hi Thorsten,
>>
>> Thorsten Jolitz <tjolitz@gmail.com> writes:
>>
>>> 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.
>>
>> I still think there is a simpler way, I'll explore this and
>> I'll let you know.
>>
>
> What about using advice on regexp functions to transform the regexps
> (when invoked in org-minor-mode buffers) so that $ is replaced with ";
> $" etc?

Its definitely one option, but its always said in the manuals that, if
possible, one should rather modify the sources than using advices, and
since Org-mode is not abandon-ware at all, I thought I ask first how
chances are for such modifications. 

> One other issue is the use of the number of stars to determine outline
> level.

Since outshine should bring the look&feel of Org-mode to programming
language buffers, using other language elements (like e.g. functions) as
outline items is not only a technical problem, but a conceptual problem
too. In Org-mode, functions are stored in src-blocks, they are not
headlines. Thus they should be treated in outshine rather like plain
lists or drawers or other elements that change visibility but are no
headline. 

-- 
cheers,
Thorsten

  reply	other threads:[~2014-04-25  8:01 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 [this message]
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=87vbtxg7o1.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).