From: Eli Zaretskii <eliz@gnu.org>
To: Michal Nazarewicz <mina86@mina86.com>
Cc: dak@gnu.org, rms@gnu.org, 23787@debbugs.gnu.org, bojohan@gnu.org,
tsdh@gnu.org, acm@muc.de, tlikonen@iki.fi
Subject: bug#23787: [PATCH] * lisp/bindings.el: create binding for ‘cycle-spacing’
Date: Fri, 17 Jun 2016 23:22:34 +0300 [thread overview]
Message-ID: <83inx7bm5x.fsf@gnu.org> (raw)
In-Reply-To: <1466194336-23967-1-git-send-email-mina86@mina86.com> (message from Michal Nazarewicz on Fri, 17 Jun 2016 22:12:16 +0200)
> From: Michal Nazarewicz <mina86@mina86.com>
> Cc: Glenn Morris <rgm@gnu.org>,
> Richard Stallman <rms@gnu.org>,
> Eli Zaretskii <eliz@gnu.org>,
> David Kastrup <dak@gnu.org>,
> Tassilo Horn <tsdh@gnu.org>,
> Teemu Likonen <tlikonen@iki.fi>,
> Alan Mackenzie <acm@muc.de>,
> Johan Bockgård <bojohan@gnu.org>
> Date: Fri, 17 Jun 2016 22:12:16 +0200
>
> ‘cycle-spacing’ behaves like ‘just-one-space’ when invoked once so
> binding it to M-SPC should not be (very) destructive to users.
>
> When this change has been propesed back in 2014¹, the main concern
> was that back then the function behaved a bit differently from the
> old one in certain situations. This has since been changed by a
> [687e0e1: “Make ‘cycle-spacing’ behave more like ‘just-one-space’
> if colled once.”] commit.
That's not the only concern that was brought up back then. It was
suggested to poll users.
next prev parent reply other threads:[~2016-06-17 20:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-17 20:12 bug#23787: [PATCH] * lisp/bindings.el: create binding for ‘cycle-spacing’ Michal Nazarewicz
2016-06-17 20:22 ` Eli Zaretskii [this message]
2016-06-17 21:13 ` Michal Nazarewicz
2016-06-17 22:06 ` Glenn Morris
2016-06-17 22:16 ` David Kastrup
2016-06-20 13:30 ` Michal Nazarewicz
2016-06-24 22:14 ` 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=83inx7bm5x.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=23787@debbugs.gnu.org \
--cc=acm@muc.de \
--cc=bojohan@gnu.org \
--cc=dak@gnu.org \
--cc=mina86@mina86.com \
--cc=rms@gnu.org \
--cc=tlikonen@iki.fi \
--cc=tsdh@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.