From: Robert Pluim <rpluim@gmail.com>
To: ding@gnus.org
Subject: Re: browse-url-url-encode-chars,
Date: Thu, 23 Sep 2010 10:19:30 +0200 [thread overview]
Message-ID: <pknsk10c1nx.fsf@gmail.com> (raw)
In-Reply-To: <b4mwrqdgrkn.fsf@jpl.org>
Katsumi Yamaoka <yamaoka@jpl.org> writes:
> Julien Danjou <julien@danjou.info> wrote:
>> commit aa7ce8bb58e3ab3881192ab7864bf430ca07c21d
>> Author: Julien Danjou <julien@danjou.info>
>> Date: Wed Sep 22 15:40:49 2010 +0200
> [...]
>> +(defun gnus-html-encode-url (url)
>> + "Encode URL."
>> + (browse-url-url-encode-chars url "[)$ ]"))
>
> Julien Danjou <julien@danjou.info> wrote:
>> commit 55ffb35736a85abc8c91df2498074e70461ef502
>> Author: Julien Danjou <julien@danjou.info>
>> Date: Wed Sep 22 18:22:19 2010 +0200
> [...]
>> - (edges (window-pixel-edges (get-buffer-window (current-buffer))))
>> + (edges (window-inside-pixel-edges (get-buffer-window (current-buffer))))
>
> `browse-url-url-encode-chars' is not available in Emacs 22 and
> XEmacs. `window-inside-pixel-edges' is not available in XEmacs.
>
> Maybe it's easy to implement `gnus-browse-url-url-encode-chars',
> however the latter doesn't seem to be. Any idea?
Hmm, there's
`window-text-area-pixel-edges' is a built-in function
-- loaded from "/build/xemacs-edge/src/window.c"
(window-text-area-pixel-edges &optional WINDOW)
Documentation:
Return a list of the pixel edge coordinates of the text area of WINDOW.
The returned list is of the form (LEFT TOP RIGHT BOTTOM),
all relative to 0, 0 at the top left corner of the total area allocated
to the window, which includes the scrollbars.
but I'm not 100% that does exactly what you want.
Robert
next prev parent reply other threads:[~2010-09-23 8:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1OyQQw-0000mC-00@quimby.gnus.org>
2010-09-23 1:46 ` browse-url-url-encode-chars, Katsumi Yamaoka
2010-09-23 8:19 ` Robert Pluim [this message]
2010-09-23 15:58 ` browse-url-url-encode-chars, Lars Magne Ingebrigtsen
2010-09-23 17:40 ` browse-url-url-encode-chars, Julien Danjou
2010-09-23 17:45 ` browse-url-url-encode-chars, Lars Magne Ingebrigtsen
2010-09-23 18:01 ` browse-url-url-encode-chars, Julien Danjou
2010-09-23 23:18 ` browse-url-url-encode-chars, Katsumi Yamaoka
2010-09-24 7:20 ` browse-url-url-encode-chars, Julien Danjou
2010-09-24 7:27 ` browse-url-url-encode-chars, Katsumi Yamaoka
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=pknsk10c1nx.fsf@gmail.com \
--to=rpluim@gmail.com \
--cc=ding@gnus.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.
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).