From: Ted Zlatanov <tzz@lifelogs.com>
To: emacs-devel@gnu.org
Subject: Re: OAuth2 implementation in Elisp
Date: Tue, 27 Sep 2011 15:20:11 -0500 [thread overview]
Message-ID: <8739fhvitg.fsf@lifelogs.com> (raw)
In-Reply-To: 87r532yzwo.fsf@keller.adm.naquadah.org
On Tue, 27 Sep 2011 13:42:47 +0200 Julien Danjou <julien@danjou.info> wrote:
JD> On Tue, Sep 27 2011, Ted Zlatanov wrote:
>> I've confirmed this is completely broken with w3m, at least. I can't
>> even use the "OK" button in the displayed screen because oauth2.el is
>> waiting for me in the minibuffer, and of course w3m can't process the
>> form because it doesn't store cookies by default (I didn't go further in
>> the testing). So please check that `browse-url' is not set to one of
>> the internal Emacs choices.
JD> This does not look like it should be oauth2.el work to add
JD> workaround on this.
Maybe, but it's the one that users will complain about :)
JD> Since it's likely that the Web page is a real web Page, what about
JD> providing an Emacs function like `browse-url-with-a-capable-browser'
JD> which would act like `browse-url' but will be defaulting to a capable
JD> browser and will indicate to the user that it should not set this to
JD> something that is not?
How about adding request capabilities, e.g.
(with-browse-url-requirements '(javascript css)
(browse-url the-url))
It could also be a browse-url argument I guess.
That would be a nice way to make it work for everyone...
Ted
next prev parent reply other threads:[~2011-09-27 20:20 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-22 21:55 OAuth2 implementation in Elisp Julien Danjou
2011-09-22 21:59 ` Deniz Dogan
2011-09-22 22:00 ` Deniz Dogan
2011-09-22 22:15 ` Julien Danjou
2011-09-25 11:25 ` Ted Zlatanov
2011-09-25 12:56 ` Julien Danjou
2011-09-25 13:31 ` Ted Zlatanov
2011-09-25 17:14 ` Karl Fogel
2011-09-25 20:50 ` Justin Lilly
2011-09-26 9:52 ` Julien Danjou
2011-09-26 14:36 ` Ted Zlatanov
2011-09-26 15:04 ` Julien Danjou
2011-09-26 15:15 ` Lars Magne Ingebrigtsen
2011-09-26 15:17 ` Julien Danjou
2011-09-26 16:24 ` Lars Magne Ingebrigtsen
2011-09-27 9:40 ` Julien Danjou
2011-09-27 23:25 ` Richard Stallman
2011-09-26 17:47 ` joakim
2011-09-26 19:09 ` Ted Zlatanov
2011-09-26 19:55 ` Tassilo Horn
2011-09-26 19:59 ` Lars Magne Ingebrigtsen
2011-09-26 20:29 ` Tassilo Horn
2011-09-26 20:31 ` Lars Magne Ingebrigtsen
2011-09-26 21:26 ` Ted Zlatanov
2011-09-27 9:43 ` Julien Danjou
2011-09-27 9:50 ` joakim
2011-09-27 10:14 ` Ted Zlatanov
2011-09-27 12:22 ` joakim
2011-09-27 20:17 ` Ted Zlatanov
2011-09-26 17:00 ` Ted Zlatanov
2011-09-28 3:35 ` Vijay Lakshminarayanan
2011-09-26 21:23 ` Ted Zlatanov
2011-09-27 10:18 ` Ted Zlatanov
2011-09-27 11:42 ` Julien Danjou
2011-09-27 20:20 ` Ted Zlatanov [this message]
2011-09-25 20:02 ` Deniz Dogan
2011-09-23 4:34 ` Stefan Monnier
2011-09-23 7:31 ` Julien Danjou
2011-09-23 8:23 ` Andreas Röhler
2011-09-23 8:48 ` Michael Albinus
2011-09-23 9:02 ` Julien Danjou
2011-09-23 9:32 ` Michael Albinus
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=8739fhvitg.fsf@lifelogs.com \
--to=tzz@lifelogs.com \
--cc=emacs-devel@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.