GNU bug report logs - #5307
start of docs.google.com interface

Previous Next

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 5307 in the body.
You can then email your comments to 5307 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Pace Willisson <pace <at> alum.mit.edu>
To: bug-gnu-emacs <at> gnu.org
Subject: start of docs.google.com interface
Date: Sun, 3 Jan 2010 16:56:01 -0500

It would be neat to be able to access docs.google.com directly from
emacs, but there are many barriers.  I've taken a small step by
building out the core oauth stuff on top of
url-retrieve-synchronously:  I can do the authentication, get an xml
list of my documents, read the html contents of a file, and do a basic
translation of the file to an enriched text buffer.  I'm not going to
be able to work on it further for a good while, but perhaps someone is
interested in picking up from this point and taking the next steps.
Have a look at:

http://github.com/pacew/emacsg

(it's pretty messy now, but at least it demonstrates which key goes
where in the protocol)

Pace Willisson
pace <at> alum.mit.edu

Message #10 received at 5307 <at> debbugs.gnu.org (full text, mbox):

From: Lars Ingebrigtsen <larsi <at> gnus.org>
To: Pace Willisson <pace <at> alum.mit.edu>
Cc: 5307 <at> debbugs.gnu.org
Subject: Re: bug#5307: start of docs.google.com interface
Date: Tue, 01 Oct 2019 17:05:05 +0200

Pace Willisson <pace <at> alum.mit.edu> writes:

> It would be neat to be able to access docs.google.com directly from
> emacs, but there are many barriers.  I've taken a small step by
> building out the core oauth stuff on top of
> url-retrieve-synchronously:  I can do the authentication, get an xml
> list of my documents, read the html contents of a file, and do a basic
> translation of the file to an enriched text buffer.  I'm not going to
> be able to work on it further for a good while, but perhaps someone is
> interested in picking up from this point and taking the next steps.
> Have a look at:
>
> http://github.com/pacew/emacsg
>
> (it's pretty messy now, but at least it demonstrates which key goes
> where in the protocol)

(I'm going through old bug reports that unfortunately didn't get any
response at the time.)

This seems like a good idea for a (M)ELPA package, but it's probably
outside the scope of the Emacs bug tracker to proceed with.  So I'm
closing this bug report.

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no

Message #15 received at 5307 <at> debbugs.gnu.org (full text, mbox):

From: Richard Stallman <rms <at> gnu.org>
To: Lars Ingebrigtsen <larsi <at> gnus.org>
Cc: pace <at> alum.mit.edu, 5307 <at> debbugs.gnu.org
Subject: Re: bug#5307: start of docs.google.com interface
Date: Tue, 01 Oct 2019 18:11:56 -0400

[[[ To any NSA and FBI agents reading my email: please consider    ]]]
[[[ whether defending the US Constitution against all enemies,     ]]]
[[[ foreign or domestic, requires you to follow Snowden's example. ]]]

  > > It would be neat to be able to access docs.google.com directly from
  > > emacs, but there are many barriers.

It would be good _provided_ it doesn't involve running nonfree software
(in particular, Javascript code from Google itself).

Access to Google Docs which bypasses that Javascript code would
be a great step forward, worth celebrating.

-- 
Dr Richard Stallman
Founder, Free Software Foundation (https://gnu.org, https://fsf.org)
Internet Hall-of-Famer (https://internethalloffame.org)

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.