From: "Drew Adams" <drew.adams@oracle.com>
To: <lennart.borgman@gmail.com>
Cc: 7296@debbugs.gnu.org
Subject: bug#7296: display-pixel-height not enough
Date: Tue, 2 Nov 2010 11:24:15 -0700 [thread overview]
Message-ID: <1886CEE3C5E349D2A645454175C010DE@us.oracle.com> (raw)
In-Reply-To: <AANLkTik7A0FPXOy=HeM_f+yzTn8JfFHE+AShrjuQ3SAT@mail.gmail.com>
For some reason, it seems this message never made it to the BUGS list. Sending
again.
-----Original Message-----
From: Drew Adams Sent: Monday, November 01, 2010 11:36 AM
To: 'Lennart Borgman' Cc: 'YAMAMOTO Mitsuharu'; '7296@debbugs.gnu.org'
> > It's not that one or the other is better; it's that they
> > are different. If you change the meaning and return value
> > of an existing function then you break existing code. If
> > you want to add an additional function that returns some
> > other value that you find more useful, that's one thing.
> > Proposing to change the existing function is something else again.
>
> There is no clear description of what display-pixel-height currently
> returns. So how do we know how it is currently used?
I know how I currently use it (and I pointed you to the code). And my code has
been been used by others as well (it is included in Aquamacs, AFAIK). It seems
to DTRT.
How did I find out what `display-pixel-height' returns? Well, I tried it out,
for one thing. And I read the doc string, which I found clear enough.
You cannot change the behavior of something radically just because you feel the
doc is not precise enough. Imprecise doc is not a license to change up to down
or whole to part.
These functions have been around quite a while. If you want something
incompatibly different then create a new function. Do not try to turn the
existing functions upside down.
> It looks like it is difficult to get this information, but as I said
> the current return value must be documented. I suggest that we just
> change the doc string and says that it returns value for the total
> display.
I'm all for clear doc. But in this case I don't see the difference. If I tell
you that function `foobar' returns the diameter of its input circle, is that
different from telling you that it returns the "total" diameter?
Is the length of your bicycle different from the length of your whole bicycle?
With no qualifier I think that the entire display is understood implicitly.
> And in addition to that it would probably be good to have the
> "opposite" function too. At least I need it.
It is in the doc of your new, partial-height function that you would state that
it returns the height of only part of the (total) display.
In sum, you are looking for a different behavior from what
`display-pixel-height' provides. For that you should be asking for a different
function - exactly as you would do if you wanted to change the return units from
pixels to lines.
This is not a doc issue IMO, and IMO it is not a problem with
`display-pixel-height'. What you are asking for is (or should be) a new,
additional function.
next prev parent reply other threads:[~2010-11-02 18:24 UTC|newest]
Thread overview: 70+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-28 10:11 bug#7296: display-pixel-height not enough Lennart Borgman
2010-10-28 18:01 ` Eli Zaretskii
2010-10-28 20:39 ` Lennart Borgman
2010-10-29 7:59 ` Eli Zaretskii
2010-10-29 8:03 ` Lennart Borgman
2010-10-29 10:12 ` Eli Zaretskii
2010-10-29 8:42 ` Lennart Borgman
2010-10-29 10:13 ` Jan Djärv
2010-10-29 10:57 ` Eli Zaretskii
2010-10-29 12:28 ` Lennart Borgman
2010-10-29 13:15 ` Jan D.
2010-10-29 13:38 ` Lennart Borgman
2010-10-29 14:51 ` Drew Adams
2010-10-29 16:53 ` Jan Djärv
2010-10-29 17:37 ` Stefan Monnier
2010-10-29 19:27 ` Lennart Borgman
2010-10-29 19:59 ` Jan D.
2010-10-29 16:24 ` Stefan Monnier
2010-10-29 19:57 ` Jan D.
2010-10-29 20:05 ` Lennart Borgman
2010-10-30 7:28 ` Jan Djärv
2010-10-30 9:25 ` Lennart Borgman
2010-10-30 10:45 ` Jan Djärv
2010-10-30 14:05 ` Lennart Borgman
2010-10-30 15:06 ` Drew Adams
2010-10-30 15:14 ` Lennart Borgman
2010-10-30 17:27 ` Jan Djärv
2010-10-30 17:41 ` Lennart Borgman
2010-10-30 18:30 ` Jan Djärv
2010-10-30 18:59 ` Lennart Borgman
2010-10-31 10:51 ` Jan Djärv
2010-10-31 12:46 ` Lennart Borgman
2010-11-01 11:37 ` Jan Djärv
2010-11-01 12:00 ` Lennart Borgman
2010-11-01 19:38 ` Jan Djärv
2010-11-01 20:26 ` Eli Zaretskii
2010-11-01 20:35 ` Lennart Borgman
2010-11-01 21:11 ` Jan Djärv
2010-11-01 21:40 ` Eli Zaretskii
2010-11-02 1:09 ` Jason Rumney
2010-11-02 4:01 ` Eli Zaretskii
2010-11-02 13:25 ` Jan D.
2010-11-02 14:53 ` Eli Zaretskii
2010-11-02 16:10 ` Lennart Borgman
2010-11-02 17:48 ` Drew Adams
2010-11-02 17:54 ` Jan Djärv
2010-10-31 3:47 ` Stefan Monnier
2010-10-31 4:13 ` YAMAMOTO Mitsuharu
2010-10-31 10:46 ` Lennart Borgman
2010-11-01 0:10 ` YAMAMOTO Mitsuharu
2010-11-01 0:24 ` Lennart Borgman
2010-11-01 0:56 ` YAMAMOTO Mitsuharu
2010-11-01 1:26 ` Lennart Borgman
2010-11-01 2:46 ` YAMAMOTO Mitsuharu
2010-11-01 10:20 ` Lennart Borgman
2010-11-01 11:40 ` Jan Djärv
2010-11-01 12:04 ` Lennart Borgman
2010-11-01 19:40 ` Jan Djärv
2010-11-02 3:45 ` YAMAMOTO Mitsuharu
2010-11-01 7:44 ` Jason Rumney
2010-11-01 10:12 ` Lennart Borgman
2010-11-01 15:09 ` Drew Adams
2010-11-01 18:08 ` Lennart Borgman
2010-11-02 14:24 ` Stefan Monnier
2010-11-02 15:24 ` Lennart Borgman
2010-11-02 17:17 ` Stefan Monnier
2010-10-31 10:53 ` Jan Djärv
2010-11-02 18:24 ` Drew Adams [this message]
2015-01-03 18:46 ` martin rudalics
2015-02-13 18:29 ` martin rudalics
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1886CEE3C5E349D2A645454175C010DE@us.oracle.com \
--to=drew.adams@oracle.com \
--cc=7296@debbugs.gnu.org \
--cc=lennart.borgman@gmail.com \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).