From: Eli Zaretskii <eliz@gnu.org>
To: martin rudalics <rudalics@gmx.at>
Cc: mvoteiza@udel.edu, 18112@debbugs.gnu.org
Subject: bug#18112: 24.4.50; emacs --daemon infinite loop in find_interval
Date: Sat, 09 Aug 2014 18:37:17 +0300 [thread overview]
Message-ID: <83fvh5lln6.fsf@gnu.org> (raw)
In-Reply-To: <53E60287.9070301@gmx.at>
> Date: Sat, 09 Aug 2014 13:14:15 +0200
> From: martin rudalics <rudalics@gmx.at>
> CC: 18112@debbugs.gnu.org, mvoteiza@udel.edu
>
> > I see no improvement for the "total" size. The additions to the doc
> > strings point to window-total-size, but that function's doc string
> > does not explain what is the semantics of "total" in this respect.
> > (The doc string of window-total-size references window-total-width and
> > window-total-height, which do say something about that, but having to
> > traverse more than 1 hyperlink to find the information is not a good
> > idea, IMO.)
> >
> > Also, the way you document the *-new-* functions could be improved.
> > You say something like
> >
> > The new pixel size of WINDOW is used by `window-resize-apply' and, if
> > that function succeeds, will be subsequently returned by the functions
> > `window-pixel-height' and `window-pixel-width'.
> >
> > I suggest instead to say something that describes the effect, but not
> > how the effect is achieved (which is low-level information that
> > obscures and obfuscates what the reader would like to know):
> >
> > The new pixel size of WINDOW, if it is valid, will be shortly
> > installed as WINDOW's size.
>
> I've tried to follow your advices. Please have another look.
Thanks, the *-new-* functions are now clearly documented.
The issue with window-total-size is still there, though.
next prev parent reply other threads:[~2014-08-09 15:37 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-25 23:08 bug#18112: 24.4.50; emacs --daemon infinite loop in find_interval Mark Oteiza
2014-07-26 6:42 ` Eli Zaretskii
2014-07-26 7:55 ` Eli Zaretskii
2014-07-26 8:06 ` Andreas Schwab
2014-07-26 8:15 ` Andreas Schwab
2014-07-26 8:22 ` Eli Zaretskii
2014-07-26 9:04 ` Eli Zaretskii
2014-07-26 9:33 ` Eli Zaretskii
2014-07-27 13:05 ` Eli Zaretskii
2014-07-27 13:35 ` martin rudalics
2014-07-27 14:55 ` Eli Zaretskii
2014-07-27 18:15 ` martin rudalics
2014-08-08 10:10 ` martin rudalics
2014-08-08 10:40 ` Eli Zaretskii
2014-08-09 11:14 ` martin rudalics
2014-08-09 15:37 ` Eli Zaretskii [this message]
2014-08-09 15:56 ` martin rudalics
2014-08-09 16:29 ` Eli Zaretskii
2014-08-10 10:42 ` martin rudalics
2014-08-10 14:04 ` Eli Zaretskii
2014-07-26 9:17 ` Andreas Schwab
2014-07-26 9:44 ` Andreas Schwab
2014-07-26 11:07 ` Eli Zaretskii
2014-07-26 11:27 ` Andreas Schwab
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=83fvh5lln6.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=18112@debbugs.gnu.org \
--cc=mvoteiza@udel.edu \
--cc=rudalics@gmx.at \
/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.