From: Richard Riley <rileyrg@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: Blogging org entries using google command line.
Date: Thu, 09 Sep 2010 02:12:34 +0200 [thread overview]
Message-ID: <i698pk$5ma$1@dough.gmane.org> (raw)
In-Reply-To: 87vd6fj1cb.fsf@gmail.com
"Eric Schulte" <schulte.eric@gmail.com> writes:
> Hey Richard,
>
> That looks interesting. See the gdoc-write code block defined in the
> library-of-babel in the org repo at contrib/babel/library-of-babel.org
> which allows saving Org-mode data to google docs using the google
> command line.
>
> Maybe your function would be suitable for addition to the
> library-of-babel?
I'll clean it up, add customisation options etc and then repost. I'd
like to add calendar stuff too but its hard to find reasonable
documentation on how to specify specific date/ranges/times for some
reason.
regards
r.
>
> Cheers -- Eric
>
> Richard Riley <rileyrg@gmail.com> writes:
>
>> Using the google command line you can get some super access to all your
>> Google resources - including docs, calendars & blogs.
>>
>> http://code.google.com/p/googlecl/
>>
>> Once you have installed it and set up your OAUTH you can easily
>> manipulate/add/delete things in your google hosted data.
>>
>> While not polished and featuring hard coded blog name the following
>> function uses the google command line tool to blog the current
>> org-entry.
>>
>> (defun rgr/org-blog-entry ()
>> (interactive)
>> (save-excursion
>> (let ((tmpheading (org-get-heading)))
>> (goto-char (org-entry-beginning-position))
>> (set-mark (org-entry-end-position))
>> (let*((tmpfile (make-temp-file "org-blog-html-"))
>> (blog-command (concat "google blogger post --blog \"Open Sauce\" --title '" tmpheading "' " tmpfile )))
>> (org-export-as-html 1 nil nil (find-file-noselect tmpfile) t)
>> (with-current-buffer (get-file-buffer tmpfile) (save-buffer))
>> (start-process-shell-command "Google Blog" "*googlecl*" blog-command)))))
>>
>> At some point I'll try and make it more generic with customised options
>> if no one beats me to it ..
>>
>> regards
>>
>> r.
>
> _______________________________________________
> Emacs-orgmode mailing list
> Please use `Reply All' to send replies to the list.
> Emacs-orgmode@gnu.org
> http://lists.gnu.org/mailman/listinfo/emacs-orgmode
>
--
☘ http://www.shamrockirishbar.com, http://www.richardriley.net
"Learning French is trivial: the word for horse is 'cheval' and
everything follows thusly."
next prev parent reply other threads:[~2010-09-09 0:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-08 21:11 Blogging org entries using google command line Richard Riley
2010-09-08 22:32 ` Eric Schulte
2010-09-09 0:12 ` Richard Riley [this message]
2010-09-09 0:30 ` Tim Burt
2010-09-09 1:05 ` Richard Riley
2010-09-09 2:04 ` Tim Burt
2010-09-09 3:35 ` Richard Riley
2010-09-10 8:01 ` Yavuz Arkun
2010-09-10 17:00 ` Richard Riley
2010-09-12 16:40 ` David Maus
2010-09-12 16:57 ` Richard Riley
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='i698pk$5ma$1@dough.gmane.org' \
--to=rileyrg@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).