From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: help-gnu-emacs@gnu.org
Subject: Re: contractor resources for emacs extension development
Date: Wed, 23 Oct 2013 09:31:11 +0800 [thread overview]
Message-ID: <87y55kixi8.fsf@ericabrahamsen.net> (raw)
In-Reply-To: 87bo2io72d.fsf@gmail.com
Thorsten Jolitz <tjolitz@gmail.com> writes:
> Alan Schmitt <alan.schmitt@polytechnique.org> writes:
>
>> Thorsten Jolitz <tjolitz@gmail.com> writes:
>>
>>> Did you set the hooks?
>>>
>>> In my .emacs I find e.g.
>>>
>>> ,-------------------------------------------------------------
>>> | (add-hook 'outline-minor-mode-hook 'outshine-hook-function))
>>> | (add-hook 'emacs-lisp-mode-hook 'outline-minor-mode)
>>> | (add-hook 'message-mode-hook 'outline-minor-mode))
>>> `-------------------------------------------------------------
>>>
>>> so whenever outline-minor-mode is activated, the
>>> `outshine-hook-function' is called for setting up things. For
>>> emacs-lisp-mode and message-mode (and others not listed) I then activate
>>> outline-minor-mode by default.
>>
>> I have them in my configuration file. Is it supposed to work if no
>> headling is present?
>
> Yes, because the trick I used is to temporarily convert this
> line:
>
> ,---------------------------
> | --text follows this line--
> `---------------------------
>
> into a first-level Org-mode heading to make outorg work.
>
> I assumed that this line is always present in message-mode between the
> header and the body, so there is always at least one heading (created
> in the background by outorg).
>
> Is that line present in your case?
A tiny, tiny compatibility trick: the "text follows this
line" line actually comes from the `mail-header-separator' variable. You
might search for the value of that, instead of a hard-coded string, just
in case it's been customized.
Eric
next prev parent reply other threads:[~2013-10-23 1:31 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-17 17:23 contractor resources for emacs extension development ckhan
2013-10-17 18:10 ` Pascal J. Bourguignon
2013-10-17 19:55 ` Marcin Borkowski
2013-10-17 20:01 ` Thorsten Jolitz
2013-10-18 6:08 ` Bastien
2013-10-18 8:00 ` Thorsten Jolitz
[not found] ` <mailman.4210.1382040123.10748.help-gnu-emacs@gnu.org>
2013-10-18 5:39 ` Eric Brown
2013-10-18 7:26 ` Thorsten Jolitz
[not found] ` <mailman.4237.1382081230.10748.help-gnu-emacs@gnu.org>
2013-10-18 11:25 ` Alan Schmitt
2013-10-18 12:06 ` Thorsten Jolitz
[not found] ` <mailman.4249.1382098046.10748.help-gnu-emacs@gnu.org>
2013-10-21 15:23 ` Alan Schmitt
2013-10-21 17:41 ` Thorsten Jolitz
2013-10-23 1:31 ` Eric Abrahamsen [this message]
2013-10-23 8:49 ` Thorsten Jolitz
[not found] ` <mailman.4412.1382377300.10748.help-gnu-emacs@gnu.org>
2013-10-22 11:57 ` Alan Schmitt
2013-10-22 12:05 ` outorg-edit-as-org and mu4e (Was: contractor resources for emacs extension development) Alan Schmitt
2013-10-22 16:41 ` outorg-edit-as-org and mu4e Thorsten Jolitz
[not found] ` <mailman.4479.1382460147.10748.help-gnu-emacs@gnu.org>
2013-10-23 9:54 ` Alan Schmitt
2013-10-23 10:37 ` Thorsten Jolitz
2013-10-18 6:03 ` contractor resources for emacs extension development Bastien
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.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87y55kixi8.fsf@ericabrahamsen.net \
--to=eric@ericabrahamsen.net \
--cc=help-gnu-emacs@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.
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).