emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Samuel Wales <samologist@gmail.com>
To: "Tom Breton (Tehom)" <tehom@panix.com>
Cc: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: Blogging from org-mode
Date: Mon, 17 Jan 2011 12:39:48 -0700	[thread overview]
Message-ID: <AANLkTinkdKVb26iXgxJdU9ORY=qiyDuSEZBiPgqRePV8@mail.gmail.com> (raw)
In-Reply-To: <cdb2d2bc94946df471bdbe73be73575e.squirrel@mail.panix.com>

On 2011-01-16, Tom Breton (Tehom) <tehom@panix.com> wrote:
> Feel free to play with org2blog/atom, and there's a "mob" user on the repo
> if you feel like contributing.

Sounds great.  However. I am not likely to be able to do much with it,
such as tweaking it.  I don't know if it will work with 22.[1]

IMO ideally, we would have one tool that does everything your solution
does and everything mine does (on my list, such as subtrees, except
perhaps curl and xsltproc), and have it in contrib.  I guess g-client
would go there too by analogy with htmlize.

Then again, I suppose my solution only needs an API call if the
dependencies work.

> Please let me know if you have any trouble obtaining the g-client version
> that supports this.

Cannot go searching and testing now.[1]  But I like the idea of using
Atom very much and I hope your project gets some interest.

Samuel

[1] I would have to try it, which I can almost never do because all
computer use is physically painful.  Most people wouldn't notice the
difference but I find from experience that debugging, backporting,
testing, and installing are even more of a problem than email,
requiring more repetition than predicted and often being fruitless
despite being physically painful .  This is one reason why most of my
contributions to org are ideas not code.  I am very fortunate that
they often get implemented -- I think it's a sign of a really healthy
open source community that I can still contribute with ideas without
having to code.

-- 
The Kafka Pandemic: http://thekafkapandemic.blogspot.com
I support WPI: http://www.wpinstitute.org/xmrv/index.html -- PLEASE DONATE
===
I want to see the original (pre-hold) Lo et al. 2010 NIH/FDA/Harvard MLV paper.

  reply	other threads:[~2011-01-17 19:39 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-16 20:57 Blogging from org-mode Tom Breton (Tehom)
2011-01-16 22:59 ` Samuel Wales
2011-01-17  2:25   ` Tom Breton (Tehom)
2011-01-17 19:39     ` Samuel Wales [this message]
2011-01-17 19:13 ` Juan Reyero
2011-01-17 20:03   ` Erik Iverson
2011-01-17 21:02     ` Samuel Wales
2011-01-17 21:28       ` Erik Iverson
2011-01-18  3:46         ` Samuel Wales
  -- strict thread matches above, loose matches on Subject: below --
2008-03-17  6:06 blogging " Cezar Halmagean
2008-03-18 23:27 ` Bastien Guerry
2008-03-19 18:05   ` Cezar Halmagean
2008-03-20 10:04     ` Bastien
2008-03-20 16:47       ` Cezar Halmagean
2008-03-20 18:20         ` Bastien Guerry
2008-03-20 18:52           ` Cezar Halmagean

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='AANLkTinkdKVb26iXgxJdU9ORY=qiyDuSEZBiPgqRePV8@mail.gmail.com' \
    --to=samologist@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=tehom@panix.com \
    /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).