From: jorge.a.alfaro@gmail.com (Jorge A. Alfaro-Murillo)
To: emacs-orgmode@gnu.org
Subject: org-edit-src-code outside of org
Date: Tue, 13 May 2014 16:49:57 -0400 [thread overview]
Message-ID: <87y4y55rpm.fsf@gmail.com> (raw)
Hi, I would like to use org-edit-src-code outside of org, I think it
would be very handy in Message mode, to send messages that contain code
and edit that code in the proper mode.
I put something like this
#+BEGIN_SRC emacs-lisp
(defun mm-org-try-structure-completion ()
(interactive)
(if (not (org-try-structure-completion))
(message-tab)))
(eval-after-load "message"
'(progn
(define-key message-mode-map (kbd "<tab>")
'mm-org-try-structure-completion)))
#+END_SRC
which allows me now to do <'a letter' and hit <tab> and get a the proper
source block just as in org.
I can enter the editing of the source block without problems with
org-edit-src-code (which I plan to bind to C-c ', just as in org),
however when I am want to close the editing and go back to the message
buffer it fails, specifically the part of org-edit-src-exit that says:
#+BEGIN_SRC emacs-lisp
(unless (org-bound-and-true-p org-edit-src-from-org-mode)
(error "This is not a sub-editing buffer, something is wrong"))
#+END_SRC
Is there a particular reason why the code has to check to see if it is
coming from org-mode? Shouldn't it be enough that already the
org-in-block-p was passed?
If I evaluate the function definition of org-edit-src-exit without the
last part everything works as expect, I can exit with C-c ' and the code
is there. Even doing C-x C-s before exiting works as well.
Best,
Jorge.
PS: What is the alternative when you write messages with code, do you
guys first write it in org and then copy and yank it?
next reply other threads:[~2014-05-13 20:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-13 20:49 Jorge A. Alfaro-Murillo [this message]
2014-05-13 20:58 ` org-edit-src-code outside of org Ken Mankoff
2014-05-13 21:12 ` Jorge A. Alfaro-Murillo
2014-05-14 13:44 ` Hubert Chathi
2014-05-17 6:33 ` Jorge A. Alfaro-Murillo
2014-05-17 8:23 ` Alexander Baier
2014-05-27 8:32 ` 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=87y4y55rpm.fsf@gmail.com \
--to=jorge.a.alfaro@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).