Gnus development mailing list
 help / color / mirror / Atom feed
From: Julien Danjou <julien@danjou.info>
To: ding@gnus.org
Subject: Re: browse-url-url-encode-chars,
Date: Thu, 23 Sep 2010 19:40:41 +0200	[thread overview]
Message-ID: <87r5gkcq92.fsf@keller.adm.naquadah.org> (raw)
In-Reply-To: <m3aan8xxha.fsf@quimbies.gnus.org> (Lars Magne Ingebrigtsen's message of "Thu, 23 Sep 2010 17:58:57 +0200")

[-- Attachment #1: Type: text/plain, Size: 653 bytes --]

On Thu, Sep 23 2010, Lars Magne Ingebrigtsen wrote:

>> Maybe it's easy to implement `gnus-browse-url-url-encode-chars',
>> however the latter doesn't seem to be.  Any idea?
>
> While `window-inside-pixel-edges' gives a more accurate number for our
> purposes, I think `window-pixel-edges' is sufficient.  I mean, we only
> need a rough ballpark number, don't we?
>
> Julien, perhaps this should be changed back, unless there are any other
> effects I'm not aware of?

I'm neither aware of any other effect. This was just to be more precise,
as you point out.

-- 
Julien Danjou
// ᐰ <julien@danjou.info>   http://julien.danjou.info

[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]

  reply	other threads:[~2010-09-23 17:40 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   ` browse-url-url-encode-chars, Robert Pluim
2010-09-23 15:58   ` browse-url-url-encode-chars, Lars Magne Ingebrigtsen
2010-09-23 17:40     ` Julien Danjou [this message]
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=87r5gkcq92.fsf@keller.adm.naquadah.org \
    --to=julien@danjou.info \
    --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).