all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Ken Olum <kdo@cosmos.phy.tufts.edu>
Cc: 17560@debbugs.gnu.org
Subject: bug#17560: 24.4.50; wrong type argument if rmail-delete-after-output set
Date: Fri, 23 May 2014 20:37:48 +0300	[thread overview]
Message-ID: <83k39cl7kj.fsf@gnu.org> (raw)
In-Reply-To: <q5261kwlcik.fsf@cosmos.phy.tufts.edu>

> From: Ken Olum <kdo@cosmos.phy.tufts.edu>
> Cc: 17560@debbugs.gnu.org
> Date: Fri, 23 May 2014 11:50:59 -0400
> 
> I'd put
> 
> (if (not count) (setq count 1))
> 
> in rmail-delete-forward and for consistency make the argument of
> rmail-delete-backward optional and add the same code there.
> 
> Unfortunately, that is not consistent with rmail-next-message, for
> example.  The alternative would be to make the argument not optional and
> change all callers to say (rmail-delete-forward 1).

The alternative is what I had in mind, yes.

> Unfortunately, in previous versions of emacs this would mean to move
> backward, so new calls would be incompatible with the old
> definition, which I think argues against this plan.

I don't think this problem should bother us, as the change in
rmail-delete-forward is backward-incompatible anyway.  Which reminds
me: could you also make a suitable entry in NEWS?

TIA





  reply	other threads:[~2014-05-23 17:37 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-23 15:02 bug#17560: 24.4.50; wrong type argument if rmail-delete-after-output set Ken Olum
2014-05-23 15:31 ` Eli Zaretskii
2014-05-23 15:50   ` Ken Olum
2014-05-23 17:37     ` Eli Zaretskii [this message]
2014-05-23 18:48       ` Ken Olum
2014-05-23 19:53         ` Eli Zaretskii
2014-05-23 20:04           ` Ken Olum
2014-05-24  6:54             ` Eli Zaretskii
2014-05-27 15:08               ` Ken Olum
2014-05-30  9:35                 ` 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=83k39cl7kj.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=17560@debbugs.gnu.org \
    --cc=kdo@cosmos.phy.tufts.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.