unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Toomas Rosin <toomas@rosin.ee>
Cc: 15821@debbugs.gnu.org
Subject: bug#15821: a better M-SPC
Date: Sat, 16 Nov 2013 16:42:24 -0500	[thread overview]
Message-ID: <jwvy54o6nli.fsf-monnier+emacsbugs@gnu.org> (raw)
In-Reply-To: <2866409.xsAelUrJXd@toomas>

> I hope this is the right place for the following suggestion.

It is.

> My version of M-SPC is an improvement over the original Emacs one in
> two respects: it operates both horizontally and vertically, and it
> takes a numeric argument.  See the docstring for details.

I don't myself use M-SPC much and have never used its numeric argument,
so I'd like to hear what other users have to say about your suggestion.

Reading your docstring, I see the following changes:
1- On a non-empty blank line, leave exactly ARG spaces on it (without
   ARG, make it empty).

2- On an empty line, delete all blank lines above and below it, leaving
   ARG empty lines.

3- At the beginning or end of a non-blank line, delete all leading
   resp. trailing whitespace, leaving ARG (by default, zero) spaces.

4- Don't treat a negative ARG as meaning to also delete newlines.

Point 4 sounds like an oversight (you don't yourself use that "negative
ARG" feature, so you didn't bother to implement it), right?

For points 1 to 3, the main issue I see with them is that some people
apparently tend to like M-SPC so much that they hit M-SPC when they just
want to insert a SPC (Richard mentioned doing that, recently), so
changing M-SPC so that it sometimes finishes with no space at point can
be an annoyance.


        Stefan





  reply	other threads:[~2013-11-16 21:42 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-06  9:36 bug#15821: a better M-SPC Toomas Rosin
2013-11-16 21:42 ` Stefan Monnier [this message]
2020-01-21  1:20   ` Stefan Kangas
2020-01-21  9:24     ` Andreas Schwab
2020-01-22  3:13     ` Richard Stallman
2020-02-28 23:21     ` Stefan Kangas

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=jwvy54o6nli.fsf-monnier+emacsbugs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=15821@debbugs.gnu.org \
    --cc=toomas@rosin.ee \
    /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).