From: Thorsten Jolitz <tjolitz@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: Re: outorg-edit-as-org and mu4e
Date: Tue, 22 Oct 2013 18:41:58 +0200 [thread overview]
Message-ID: <874n89feax.fsf@gmail.com> (raw)
In-Reply-To: m2eh7dqzmh.fsf_-_@polytechnique.org
Alan Schmitt <alan.schmitt@polytechnique.org> writes:
> Alan Schmitt <alan.schmitt@polytechnique.org> writes:
>
>> I think I found the problem, looking at the code for
>> outorg-edit-as-org. It seems that you explicitly check for
>> message-mode, but I write my email using mu4e, and then the major mode
>> is mu4e-compose-mode. Is there a way to apply
>> 'outorg-prepare-message-mode-buffer-for-editing' for other modes than
>> message mode? (Editing the code seems to be the only way I see.)
>
> Sorry to reply to myself, but how about replacing
>
> #+begin_src emacs-lisp
> (and (eq major-mode 'message-mode)
> (outorg-prepare-message-mode-buffer-for-editing))
> #+end_src
>
> on lines 719-720 of outorg.el by
>
> #+begin_src emacs-lisp
> (and (derived-mode-p 'message-mode)
> (outorg-prepare-message-mode-buffer-for-editing))
> #+end_src
>
> I think it would work with mu4e-compose-mode.
Ok, then its not a bug but just a (slightly) different use case.
I don't use mu4e, actually I never heard of it (is it good?). Could you
test these changes and let me know if it works for you? Then I'm happy
to apply them to outorg, no matter if this version:
#+begin_src emacs-lisp
(and (derived-mode-p 'message-mode)
(outorg-prepare-message-mode-buffer-for-editing))
#+end_src
or something like this (untested):
#+begin_src emacs-lisp
(and
(or (eq major-mode 'message-mode)
(eq major-mode 'mu4e-compose-mode))
(outorg-prepare-message-mode-buffer-for-editing))
#+end_src
--
cheers,
Thorsten
next prev parent reply other threads:[~2013-10-22 16:41 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
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 ` Thorsten Jolitz [this message]
[not found] ` <mailman.4479.1382460147.10748.help-gnu-emacs@gnu.org>
2013-10-23 9:54 ` outorg-edit-as-org and mu4e 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=874n89feax.fsf@gmail.com \
--to=tjolitz@gmail.com \
--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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.