From: Alan Mackenzie <acm@muc.de>
To: Glenn Morris <rgm@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: key-binding for cycle-spacing
Date: Thu, 30 Jan 2014 06:11:44 +0000 [thread overview]
Message-ID: <20140130061144.GA2801@acm.acm> (raw)
In-Reply-To: <id8utyurdb.fsf@fencepost.gnu.org>
Hi, Glenn.
On Wed, Jan 29, 2014 at 09:37:36PM -0500, Glenn Morris wrote:
> Alan Mackenzie wrote:
> >> If you have not used it, the first time you call it in a consecutive
> >> sequence, it acts like `just-one-space'.
> > Not quite. It's more complicated than that.
> Please say how (were you referring to Johan's point?), otherwise this is
> not helpful.
If you type M-9 M-SPC, with `just-one-space' you'll end up with 9 spaces.
With `cycle-spacing', you'll usually get 9, sometime you'll get zero.
> > `cycle-spacing' has lots of complicated edge cases.
> Could you give say two examples of such cases?
One is above. A second one is what happens if you give a different
argument on the second invocation from the first. A third one is what
happens when there's just a tab in the buffer, which occupies one visible
space.
> You could avoid all the extra functionality by simply not using the
> command more than once in a row (a no-op for just-one-space).
Not quite. The first time round, `cycle-spacing''s behaviour is
different according to how much space is already there.
> > It seems to violate the KISS principle.
> So do many things. cc-bytecomp is a favourite of mine.
Yes, there are many things in CC Mode which are complicated, and believe
me, I suffer because of it. But `cycle-spacing' is complicated at the
basic user level and doesn't seem to have any utility.
> > Please keep M-SPC bound to `just-one-space'.
> For ever, or for now?
For ever. :-)
--
Alan Mackenzie (Nuremberg, Germany).
next prev parent reply other threads:[~2014-01-30 6:11 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-29 17:15 key-binding for cycle-spacing Glenn Morris
2014-01-29 17:21 ` Bastien
2014-01-29 17:44 ` Eli Zaretskii
2014-01-29 18:35 ` Glenn Morris
2014-01-29 18:46 ` Glenn Morris
2014-01-29 18:49 ` Eli Zaretskii
2014-01-30 2:33 ` Glenn Morris
2014-01-31 22:36 ` Tassilo Horn
2014-01-29 19:18 ` Teemu Likonen
2014-01-29 19:53 ` David Kastrup
2014-01-29 20:28 ` Alan Mackenzie
2014-01-30 2:37 ` Glenn Morris
2014-01-30 6:11 ` Alan Mackenzie [this message]
2014-01-31 22:40 ` Tassilo Horn
2014-01-31 22:55 ` Alan Mackenzie
2014-01-31 23:35 ` Tassilo Horn
2014-02-10 13:45 ` Michal Nazarewicz
2014-02-10 12:19 ` [PATCH] Make `cycle-spacing' behave more like `just-one-space' if called once Michal Nazarewicz
2014-03-27 14:27 ` Stefan Monnier
2014-03-28 16:29 ` Michal Nazarewicz
2014-01-29 20:30 ` key-binding for cycle-spacing Johan Bockgård
2014-01-30 2:32 ` Glenn Morris
2014-01-30 14:09 ` Richard Stallman
2014-01-30 15:21 ` Stefan Monnier
2014-01-30 23:23 ` Richard Stallman
2014-02-10 13:09 ` Michal Nazarewicz
2014-02-10 13:06 ` [PATCH] Make `cycle-spacing' behave more like `just-one-space' if colled once Michal Nazarewicz
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=20140130061144.GA2801@acm.acm \
--to=acm@muc.de \
--cc=emacs-devel@gnu.org \
--cc=rgm@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.