From: John Floren <john@jfloren.net>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: [9fans] Google command line client
Date: Thu, 29 Mar 2012 14:36:38 -0700 [thread overview]
Message-ID: <CAL4LZyh6dYo6MaJUHssZbddQd1Sp6=HNQ0vcTgEXga5jHckCYA@mail.gmail.com> (raw)
Turns out Google command line client
(http://code.google.com/p/googlecl/) works on Plan 9 just fine. All
you need is python (from fgb's contrib, or if you want to risk
potentially out-of-date code I've got a tarball at
http://jfloren.net/contrib/packages/lang/python/root.tgz, just untar
it and copy the files under root/ to the appropriate places)
First, download the gdata client library version 2.0.14
(http://gdata-python-client.googlecode.com/files/gdata-2.0.14.tar.gz).
This is an older version, but it's needed for compatibility reasons.
Untar it, then run "python setup.py install".
Next, download the actual command line client
(http://googlecl.googlecode.com/files/googlecl-0.9.13.tar.gz as of
today), untar it, and once again run "python setup.py install".
You can then run /sys/lib/python/bin/google, which will give you a
prompt. For kicks, you can enter something like 'docs edit --title
"testing" --editor sam' to make and edit a quick text document. The
first time, it will prompt you for an account name and then give you a
link to authorize the client. I couldn't get the authorization link to
work in abaco, I had to enter it in Firefox, but there may be a way to
get abaco to work.
You can also do something like '/sys/lib/python/bin/google calendar
list' from an rc prompt, so whipping up a guide file for Acme will be
very easy.
John
next reply other threads:[~2012-03-29 21:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-29 21:36 John Floren [this message]
2012-03-29 22:39 ` steve
2012-03-30 0:35 ` erik quanstrom
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAL4LZyh6dYo6MaJUHssZbddQd1Sp6=HNQ0vcTgEXga5jHckCYA@mail.gmail.com' \
--to=john@jfloren.net \
--cc=9fans@9fans.net \
/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 NNTP newsgroup(s).