From: Stefan Monnier <monnier@IRO.UMontreal.CA>
To: dieter@duenenhof-wilhelm.de (H. Dieter Wilhelm)
Cc: 18847@debbugs.gnu.org
Subject: bug#18847: 24.4; Inconsistent behaviour of M-h with negative arguments
Date: Thu, 30 Oct 2014 12:35:00 -0400 [thread overview]
Message-ID: <jwvioj1a5ei.fsf-monnier+emacsbugs@gnu.org> (raw)
In-Reply-To: <87oasvq1ja.fsf@vsl28t2g.ww011> (H. Dieter Wilhelm's message of "Tue, 28 Oct 2014 23:20:41 +0100")
[ Be careful to keep 18847@debbugs.gnu.org in the Cc, please. ]
> 1) The sole real bug - in my opinion - is that M-h doesn't retain the
> "marking direction" from a negative argument when repeating.
OK, I agree with this, it's a plain bug.
> 2) When applying M-h (or any other marking command) at the end of a
> buffer (at least interactively, I failed to address this), the right
> thing to do is marking (a) previous element(s). I would like to know
> if you find this a good idea.
I have no opinion on this, I never use M-h myself.
> 3) M-h (C-M-h and C-x C-p ) differ from C-@ and C-M-@ that they are
> always marking (a) whole element(s). I wanted to clarify in the
> documentation string that a marking from point is also achievable
> with M-h.
So this part is just a docstring change, right?
> 4) M-h does signal an error applying zero as an argument, the other
> marking commands just ignore zero, so I thought a message might be a
> good compromise to the current state...
I have no opinion on this one either. It doesn't seem terribly
important, so reducing discrepancies in this case might be the
dominating factor.
Stefan
next prev parent reply other threads:[~2014-10-30 16:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-26 23:27 bug#18847: 24.4; Inconsistent behaviour of M-h with negative arguments H. Dieter Wilhelm
2014-10-27 7:37 ` H. Dieter Wilhelm
2014-10-28 17:04 ` Stefan Monnier
[not found] ` <87oasvq1ja.fsf@vsl28t2g.ww011>
2014-10-30 16:35 ` Stefan Monnier [this message]
2014-11-03 17:56 ` H. Dieter Wilhelm
2014-11-15 19:13 ` H. Dieter Wilhelm
2020-08-13 9:51 ` Lars Ingebrigtsen
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=jwvioj1a5ei.fsf-monnier+emacsbugs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=18847@debbugs.gnu.org \
--cc=dieter@duenenhof-wilhelm.de \
/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).