From: Emanuel Berg <embe8573@student.uu.se>
To: help-gnu-emacs@gnu.org
Subject: Re: how to add button to emacs that play a elisp code
Date: Tue, 16 Sep 2014 00:45:12 +0200 [thread overview]
Message-ID: <877g148pvr.fsf@debian.uxu> (raw)
In-Reply-To: mailman.8874.1410760111.1147.help-gnu-emacs@gnu.org
Alex Kost <alezost@gmail.com> writes:
> A comment to your hint.
>
> As you are using Gnus, you may just attach your elisp
> file (or buffer) to make it be highlighted inline:
> "C-c RET f" (or "C-c RET b") and choose
> "application/emacs-lisp" type.
I'm using Gnus - but I'm not the one reading the post.
How will that make it look for people not using Gnus?
I like to have my posts totally client-agnostic. But if
it doesn't bloat the post with too much
incomprehensible metadata for the non-Gnuser, I'll
consider it - why not encourage people to switch to
Gnus?
OK - here is the attached Elisp:
Wait - `C-c RET' is undefined, it says.
Do you mean I (or any Gnuser reading such messages)
should use your keystrokes in message-mode to get the
highlight? But there, `C-c RET' is `gnus-article-mail'!
What are the names of the commands?
> Another way is including org source blocks.
You mean like this:
#+BEGIN_SRC emacs-lisp
(defun org-xor (a b)
"Exclusive or."
(if a (not b) b))
#+END_SRC
Org manual example from:
http://orgmode.org/manual/Working-With-Source-Code.html
I have the same concerns for that method, but let's see
how that works, as well.
--
underground experts united
next prev parent reply other threads:[~2014-09-15 22:45 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-11 7:44 how to add button to emacs that play a elisp code Renato Pontefice
2014-09-11 8:08 ` Gian Uberto Lauri
2014-09-11 8:40 ` Gian Uberto Lauri
2014-09-11 12:17 ` Stefan Monnier
2014-09-11 12:22 ` Gian Uberto Lauri
2014-09-11 12:35 ` Stefan Monnier
2014-09-11 12:46 ` Gian Uberto Lauri
[not found] ` <mailman.8685.1410439222.1147.help-gnu-emacs@gnu.org>
2014-09-11 21:15 ` Emanuel Berg
2014-09-11 23:42 ` Pascal J. Bourguignon
2014-09-12 0:05 ` Emanuel Berg
2014-09-12 0:23 ` Michael Heerdegen
[not found] ` <mailman.8717.1410481417.1147.help-gnu-emacs@gnu.org>
2014-09-12 0:50 ` Emanuel Berg
2014-09-12 1:19 ` Michael Heerdegen
2014-09-12 14:52 ` Drew Adams
[not found] ` <mailman.8719.1410484774.1147.help-gnu-emacs@gnu.org>
2014-09-12 2:07 ` Emanuel Berg
2014-09-12 7:44 ` Renato Pontefice
2014-09-12 10:15 ` Renato Pontefice
2014-09-12 19:33 ` Emanuel Berg
2014-09-13 21:28 ` Pascal J. Bourguignon
2014-09-14 2:30 ` Rusi
2014-09-14 4:18 ` Rusi
2014-09-14 18:16 ` Emanuel Berg
2014-09-14 18:11 ` Emanuel Berg
2014-09-15 5:48 ` Alex Kost
[not found] ` <mailman.8874.1410760111.1147.help-gnu-emacs@gnu.org>
2014-09-15 22:45 ` Emanuel Berg [this message]
2014-09-16 4:55 ` Alex Kost
[not found] ` <mailman.8956.1410843332.1147.help-gnu-emacs@gnu.org>
2014-09-16 22:27 ` Emanuel Berg
[not found] ` <mailman.8671.1410424828.1147.help-gnu-emacs@gnu.org>
2014-09-11 21:06 ` Emanuel Berg
[not found] ` <mailman.8670.1410422963.1147.help-gnu-emacs@gnu.org>
2014-09-11 8:24 ` Renato Pontefice
2014-09-11 16:00 ` Pascal J. Bourguignon
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=877g148pvr.fsf@debian.uxu \
--to=embe8573@student.uu.se \
--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).