all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: raman <raman@google.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: eww: call to eww-render looks incorrect
Date: Sun, 03 Sep 2017 10:50:35 -0700	[thread overview]
Message-ID: <p917exfbris.fsf@raman-glaptop2> (raw)
In-Reply-To: <8360czycfx.fsf@gnu.org> (Eli Zaretskii's message of "Sun, 03 Sep 2017 19:27:46 +0300")

Eli Zaretskii <eliz@gnu.org> writes:

thanks -- I was clearly confused.>> From: raman <raman@google.com>
>> Cc: emacs-devel@gnu.org
>> Date: Sun, 03 Sep 2017 08:52:20 -0700
>> 
>> Eli Zaretskii <eliz@gnu.org> writes:
>> 
>> I might be confused -- reading that signature I thought status should be
>> passed first, the call I see passes url first
>
> No, status is not included in the list of arguments.  The doc string
> says:
>
>   (url-retrieve URL CALLBACK &optional CBARGS SILENT INHIBIT-COOKIES)
>
>   Retrieve URL asynchronously and call CALLBACK with CBARGS when finished.
>   URL is either a string or a parsed URL.  If it is a string
>   containing characters that are not valid in a URI, those
>   characters are percent-encoded; see ‘url-encode-url’.
>
>   CALLBACK is called when the object has been completely retrieved, with
>   the current buffer containing the object, and any MIME headers associated
>   with it.  It is called as (apply CALLBACK STATUS CBARGS).
>   STATUS is a plist representing what happened during the request,
>
> As you see, only CBARGS are taken from the call to url-retrieve, the
> status is added when the callback is invoked.

-- 



      reply	other threads:[~2017-09-03 17:50 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-02 22:38 eww: call to eww-render looks incorrect raman
2017-09-03 14:56 ` Eli Zaretskii
2017-09-03 15:52   ` raman
2017-09-03 16:27     ` Eli Zaretskii
2017-09-03 17:50       ` raman [this message]

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=p917exfbris.fsf@raman-glaptop2 \
    --to=raman@google.com \
    --cc=eliz@gnu.org \
    --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.