From: Eli Zaretskii <eliz@gnu.org>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: eggert@cs.ucla.edu, 25606@debbugs.gnu.org
Subject: bug#25606: [DRAFT PATCH 2/2] Signal list cycles in ‘length’ etc.
Date: Thu, 02 Feb 2017 19:28:19 +0200 [thread overview]
Message-ID: <83wpd8v6x8.fsf@gnu.org> (raw)
In-Reply-To: <20170201235622.30836-2-eggert@cs.ucla.edu> (message from Paul Eggert on Wed, 1 Feb 2017 15:56:22 -0800)
> From: Paul Eggert <eggert@cs.ucla.edu>
> Date: Wed, 1 Feb 2017 15:56:22 -0800
> Cc: Paul Eggert <eggert@cs.ucla.edu>
>
> Use macros like FOR_EACH_TAIL instead of maybe_quit to
> catch list cycles automatically instead of relying on the
> user becoming impatient and typing C-g.
I don't think this is a good idea. We don't know when the user will
become impatient, and on busy systems the counter could be very low by
that time. I think we shouldn't second-guess users this way, and
should always leave them the possibility of interrupting a possibly
prolonged calculation.
Also, could we please have tests for these functions?
Thanks.
next prev parent reply other threads:[~2017-02-02 17:28 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-01 23:56 bug#25605: [DRAFT PATCH 1/2] Simplify use of FOR_EACH_TAIL Paul Eggert
2017-02-01 23:56 ` bug#25606: [DRAFT PATCH 2/2] Signal list cycles in ‘length’ etc Paul Eggert
2017-02-02 17:28 ` Eli Zaretskii [this message]
2017-02-02 23:01 ` Paul Eggert
2017-02-03 7:55 ` Eli Zaretskii
2017-02-03 20:29 ` Paul Eggert
2017-02-04 9:05 ` Eli Zaretskii
2017-02-04 19:11 ` Paul Eggert
2017-02-04 19:52 ` Eli Zaretskii
2017-02-04 21:45 ` Paul Eggert
2017-02-05 18:45 ` Eli Zaretskii
2017-02-05 21:17 ` Paul Eggert
2017-02-02 17:29 ` bug#25605: [DRAFT PATCH 1/2] Simplify use of FOR_EACH_TAIL Eli Zaretskii
2017-02-05 21:30 ` bug#25605: patches installed for 25605, 25606 Paul Eggert
2017-02-06 16:04 ` bug#25605: bug#25606: " Eli Zaretskii
2017-02-07 6:53 ` Paul Eggert
2017-02-07 12:47 ` Philipp Stephani
2017-02-07 16:32 ` bug#25605: " Paul Eggert
2017-02-07 21:47 ` Philipp Stephani
2017-02-07 22:20 ` Paul Eggert
2017-02-07 22:55 ` Philipp Stephani
2017-02-10 9:59 ` bug#25605: " Eli Zaretskii
2017-02-12 8:31 ` Paul Eggert
2017-02-12 16:13 ` bug#25605: " Eli Zaretskii
2017-02-12 18:55 ` Paul Eggert
2017-02-12 19:33 ` Eli Zaretskii
2017-02-12 19:41 ` bug#25605: " Lars Ingebrigtsen
2017-02-12 19:49 ` bug#25606: " Lars Ingebrigtsen
2017-02-12 20:22 ` Eli Zaretskii
2017-02-12 19:43 ` Paul Eggert
2017-02-13 9:11 ` Michael Albinus
2017-02-13 14:37 ` Eli Zaretskii
2017-02-12 19:41 ` Eli Zaretskii
2017-02-12 20:57 ` bug#25605: " Paul Eggert
2017-02-13 5:37 ` Eli Zaretskii
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=83wpd8v6x8.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=25606@debbugs.gnu.org \
--cc=eggert@cs.ucla.edu \
/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.