all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Kevin Rodgers <kevin.d.rodgers@gmail.com>
To: 10613@debbugs.gnu.org
Subject: bug#10613: 24.0.92; Odd behavior of kill interspersed with suspend: document or change?
Date: Thu, 02 Feb 2012 01:10:53 -0700	[thread overview]
Message-ID: <jgdgcl$8q4$1@dough.gmane.org> (raw)
In-Reply-To: <87ehum32xg.fsf@sc3d.org>

On 1/26/12 8:21 AM, Reuben Thomas wrote:
> If a sequence of kill commands is interspersed with a suspend
> (suspend-emacs or suspend-frame, for example), then the kills are not
> treated as a contiguous sequence, and a following yank does not yank all
> the text killed.
>
> This feels a bit odd, as “suspend” is not a normal command: rather like
> suspending a computer, I expect that after resuming Emacs, it will be in
> the same state as when suspended. But this is not the case: if one
> suspends Emacs after a kill command, then on resumption a further kill
> will start a new kill-ring entry.

What is abnormal about the suspend-* commands, from Emacs' perspective?

> Is this behavior worth reconsidering? If not, is it worth documenting?
> (Presumably under suspend, rather than under killing, as I imagine this
> behavior changing has implications for things beyond the kill-ring.)
..

-- 
Kevin Rodgers
Denver, Colorado, USA






  reply	other threads:[~2012-02-02  8:10 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-26 15:21 bug#10613: 24.0.92; Odd behavior of kill interspersed with suspend: document or change? Reuben Thomas
2012-02-02  8:10 ` Kevin Rodgers [this message]
2018-02-13  0:32   ` Noam Postavsky
2018-02-13  9:19 ` bug#10613: Please consider this report again Reuben Thomas
2018-02-14 17:05   ` Eli Zaretskii
2018-02-15  1:51     ` Noam Postavsky
2018-02-15  2:00   ` Daniel Colascione

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='jgdgcl$8q4$1@dough.gmane.org' \
    --to=kevin.d.rodgers@gmail.com \
    --cc=10613@debbugs.gnu.org \
    /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.