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: Sun, 27 Jul 2014 17:55:23 +0300 [thread overview]
Message-ID: <831tt6j1gk.fsf@gnu.org> (raw)
In-Reply-To: <53D50029.9020802@gmx.at>
> Date: Sun, 27 Jul 2014 15:35:37 +0200
> From: martin rudalics <rudalics@gmx.at>
>
> > (It's amazing what one 99%-correct line of Lisp can do.)
>
> Indeed. Thanks for fixing my 1% blindness.
You're welcome.
As long as I have your attention: how about adding some comments
and/or text to respective doc strings to explain what exactly the
following functions do, and why/when are they needed?
window-normal-size
window-new-total
window-new-normal
window-new-pixel
and the corresponding set-* functions. Their doc strings are just
tautological repetition of their names, which isn't helpful. And the
ELisp manual doesn't say a word about them, so the doc strings need to
do a better job, IMO.
next prev parent reply other threads:[~2014-07-27 14:55 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 [this message]
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
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
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=831tt6j1gk.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 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).