emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "François Pinard" <pinard@iro.umontreal.ca>
To: emacs-orgmode@gnu.org
Subject: Re: gnus: link annoyance
Date: Tue, 07 Jan 2014 10:02:09 -0500	[thread overview]
Message-ID: <871u0jesy6.fsf@iro.umontreal.ca> (raw)
In-Reply-To: <8738kzgbv4.fsf@crunchbang.i-did-not-set--mail-host-address--so-tickle-me> (Joseph Vidal-Rosset's message of "Tue, 07 Jan 2014 14:28:15 +0100")

Joseph Vidal-Rosset <joseph.vidal.rosset@gmail.com> writes:

> Org uses Gnus, is it possible of making uses of Org via Gnus?  [...]
> Is it already possible to do that with Org and Gnus, or not?  If it is
> not possible at the moment, would it be possible?

Gnus and Org are both open source and very capable systems, both in
themselves and when it comes to extensibility.  The main problem is
acquiring enough familiarity with their internals to find out the
correct, short, compact way of doing about anything one wants. :-)

> I mean that it would be great to write a letter with for example the
> letter class in a file letter.org .  After that you can export your
> letter.org to a letter.html as well as to letter.pdf via letter.tex,
> and with Gnus, thanks to the link system, you can send your nice
> letter.html to your colleague with letter.pdf as attachment.

Many years ago, the message composition has been fairly decoupled from
Gnus and brought back into Emacs for other mailers to use.  So, I guess
you are seeking some machinery between Org and Message, more than
between Org and Gnus.

I'm far from being sure, but if I wanted to use Org as a mean to write
HTML or PDF as message attachments, I would think it could be done with
a very moderate amount of Emacs Lisp customization.  Unless mistaken,
the Org editor to HTML might yield its output in a temporary Emacs
buffer, (for PDF, maybe not) and I would be fairly surprised if message
composition does not have facilities to receive attachments from
buffers.  And even if one would have to go through an external file, the
extra overhead might be negligible in practice.  Putting all the pieces
together might require some work, but maybe not that much.

François

  reply	other threads:[~2014-01-07 15:02 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-06 13:48 gnus: link annoyance François Pinard
2014-01-06 16:39 ` Nick Dokos
2014-01-07  5:14   ` François Pinard
2014-01-07 12:07     ` Nick Dokos
2014-01-07 15:28       ` François Pinard
2014-01-07 19:06         ` Achim Gratz
2014-01-08  1:37           ` François Pinard
2014-01-08 15:15             ` Bastien
2014-01-06 17:05 ` Rasmus
2014-01-07  5:36   ` François Pinard
2014-01-07  9:00     ` Bastien
2014-01-07 14:13       ` François Pinard
2014-01-07 13:01     ` Rasmus
2014-01-07 14:34       ` François Pinard
2014-01-07 13:28     ` Joseph Vidal-Rosset
2014-01-07 15:02       ` François Pinard [this message]
2014-01-07 17:09         ` Joseph Vidal-Rosset
2014-01-07 17:43           ` Nick Dokos

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=871u0jesy6.fsf@iro.umontreal.ca \
    --to=pinard@iro.umontreal.ca \
    --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).