From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Reuben Thomas Newsgroups: gmane.emacs.bugs Subject: bug#10613: Please consider this report again Date: Tue, 13 Feb 2018 09:19:04 +0000 Message-ID: References: <87ehum32xg.fsf@sc3d.org> NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="001a113e4cf26e2ce80565147c6c" X-Trace: blaine.gmane.org 1518513505 17017 195.159.176.226 (13 Feb 2018 09:18:25 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Tue, 13 Feb 2018 09:18:25 +0000 (UTC) To: 10613@debbugs.gnu.org Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Tue Feb 13 10:18:21 2018 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1elWjA-0003oZ-4D for geb-bug-gnu-emacs@m.gmane.org; Tue, 13 Feb 2018 10:18:16 +0100 Original-Received: from localhost ([::1]:60092 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1elWlB-0007r4-Oo for geb-bug-gnu-emacs@m.gmane.org; Tue, 13 Feb 2018 04:20:21 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:50228) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1elWkx-0007kV-QH for bug-gnu-emacs@gnu.org; Tue, 13 Feb 2018 04:20:13 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1elWks-0005vr-Sm for bug-gnu-emacs@gnu.org; Tue, 13 Feb 2018 04:20:07 -0500 Original-Received: from debbugs.gnu.org ([208.118.235.43]:60745) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1elWks-0005v8-N9 for bug-gnu-emacs@gnu.org; Tue, 13 Feb 2018 04:20:02 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1elWks-0000Mp-Co for bug-gnu-emacs@gnu.org; Tue, 13 Feb 2018 04:20:02 -0500 X-Loop: help-debbugs@gnu.org In-Reply-To: <87ehum32xg.fsf@sc3d.org> Resent-From: Reuben Thomas Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Tue, 13 Feb 2018 09:20:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 10613 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: notabug Original-Received: via spool by 10613-submit@debbugs.gnu.org id=B10613.15185135531347 (code B ref 10613); Tue, 13 Feb 2018 09:20:02 +0000 Original-Received: (at 10613) by debbugs.gnu.org; 13 Feb 2018 09:19:13 +0000 Original-Received: from localhost ([127.0.0.1]:40409 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1elWk4-0000Lf-V8 for submit@debbugs.gnu.org; Tue, 13 Feb 2018 04:19:13 -0500 Original-Received: from mail-ot0-f172.google.com ([74.125.82.172]:39585) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1elWk3-0000LR-5Q for 10613@debbugs.gnu.org; Tue, 13 Feb 2018 04:19:11 -0500 Original-Received: by mail-ot0-f172.google.com with SMTP id f18so16699485otf.6 for <10613@debbugs.gnu.org>; Tue, 13 Feb 2018 01:19:11 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sc3d.org; s=google; h=mime-version:from:date:message-id:subject:to; bh=e2w4+7qPjJEVswqTXio+24Bn6lGVY33xIYw8OnLdQn8=; b=DwAy3AbYnFADhuSMppCTGG7j8/jOFTnJv4pDBdIps0haOP9w3xTBvbsyg1qviTCUMe 7txUiFShZWXSXE6BsW9FJKMxpy54XdTCabuBhnWnVUmPQQGPOIO5mq6jXzaDB7Fvqp3p uA0yhZpU94CCchgIFsdBAEoaEoXml8d439Kqo= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=e2w4+7qPjJEVswqTXio+24Bn6lGVY33xIYw8OnLdQn8=; b=s0eRwJG6YaBYrxK4sf/V0Dcw3ArsH1jKV2+Ek6092YlMOeZHxkCONYnFHOblXAj/l5 VgVQRQz06DlY/yhTNBvOjIvlcuKIxNrULCi45ErrffVTKN4+/ygtpP9gnOIQjb8DAvtR lgupoivMjxz92wioqe+YXRXSgE5jZ9q2R3iCE3YnI/IZf93cNvYkF3Es1LHKXvJOwmoF M6DuL1ztzMFkkaN8V9veUdn3ZA2RKzQlZrOH5DHetTmpy9IxRnq+oZ2dFaxdke2tAMSz a19U1XnlIYmtSOOzsqUYNnw6dxbqz3ZLKA0xQ+Qpk73nlPdZEY+XmtFxxzncgIxdK9Qm R/ug== X-Gm-Message-State: APf1xPAR377Tz3pi/WkUxufmtKq54i77CS9qXThFhczUXRGWdoF/bwOR 0W8UH65yV+HK19uVVgAxDYe4lsNQvFAAfiT229e8AqBo X-Google-Smtp-Source: AH8x224LNAjNyiGvDjY/Mh4UF/uYuN48PH4cijreWsOaKh/Y/acRQvBWj0qEBSSYYs8OReqRS/HsQK8ELzGtACbEQ5Q= X-Received: by 10.157.47.200 with SMTP id b8mr402696otd.194.1518513544893; Tue, 13 Feb 2018 01:19:04 -0800 (PST) Original-Received: by 10.157.12.180 with HTTP; Tue, 13 Feb 2018 01:19:04 -0800 (PST) X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 208.118.235.43 X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Original-Sender: "bug-gnu-emacs" Xref: news.gmane.org gmane.emacs.bugs:143245 Archived-At: --001a113e4cf26e2ce80565147c6c Content-Type: text/plain; charset="UTF-8" Unfortunately the two responses to my report seem to have focussed on just one word, which I probably chose badly. Sorry about that. But I think the report remains valid: suspending Emacs is not a movement, not an editing command, so why should it affect the behaviour of the next kill? Consider: if I suspend the computer on which I am running Emacs, then it does not affect the behaviour of Emacs in any way (or shouldn't!). When I resume, Emacs will behave exactly as if nothing had happened in the interim (other than time having passed). So from Emacs's perspective, why should "suspend-emacs" behave differently? -- https://rrt.sc3d.org --001a113e4cf26e2ce80565147c6c Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Unfortunately the two responses to my= report seem to have focussed on just one word, which I probably chose badl= y. Sorry about that.

But I think the repo= rt remains valid: suspending Emacs is not a movement, not an editing comman= d, so why should it affect the behaviour of the next kill?

Consider: if I suspend the computer on which I am running= Emacs, then it does not affect the behaviour of Emacs in any way (or shoul= dn't!). When I resume, Emacs will behave exactly as if nothing had happ= ened in the interim (other than time having passed).

So from Emacs's perspective, why should "suspend-emacs= " behave differently?

--
=
--001a113e4cf26e2ce80565147c6c--