From: Paul Eggert <eggert@cs.ucla.edu>
To: Eli Zaretskii <eliz@gnu.org>, Karl Fogel <kfogel@red-bean.com>
Cc: bruce.connor.am@gmail.com, emacs-devel@gnu.org
Subject: Re: Questioning the new behavior of `open-line'.
Date: Wed, 11 Nov 2015 11:20:58 -0800 [thread overview]
Message-ID: <5643951A.8040602@cs.ucla.edu> (raw)
In-Reply-To: <83vb98jqwp.fsf@gnu.org>
Eli Zaretskii wrote:
> People who don't like electric-indent-mode can just turn it off, can't
> they? Why argue about defaults when they can be so easily changed?
I think we're discussing the default behavior when electric-indent-mode is on,
which it often is by default.
I too was taken aback and annoyed by the new behavior of C-o. For example, I
visited src/lisp.h and typed this:
C-s xnmalloc C-a C-o
The resulting buffer looked like this:
extern void *xrealloc (void *, size_t) ATTRIBUTE_ALLOC_SIZE ((2));
extern void xfree (void *);
X
extern void *xnmalloc (ptrdiff_t, ptrdiff_t)
ATTRIBUTE_MALLOC_SIZE ((1,2));
extern void *xnrealloc (void *, ptrdiff_t, ptrdiff_t)
ATTRIBUTE_ALLOC_SIZE ((2,3));
(where the cursor is marked with "X"), i.e., the "xnmalloc" line was greatly
indented, which is not what I wanted. With old Emacs it would look like this:
extern void *xrealloc (void *, size_t) ATTRIBUTE_ALLOC_SIZE ((2));
extern void xfree (void *);
X
extern void *xnmalloc (ptrdiff_t, ptrdiff_t) ATTRIBUTE_MALLOC_SIZE ((1,2));
extern void *xnrealloc (void *, ptrdiff_t, ptrdiff_t)
ATTRIBUTE_ALLOC_SIZE ((2,3));
which is what I wanted: a new blank line with the cursor at the start, and with
no change to the next line.
next prev parent reply other threads:[~2015-11-11 19:20 UTC|newest]
Thread overview: 65+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-11 18:08 Questioning the new behavior of `open-line' Karl Fogel
2015-11-11 18:51 ` John Wiegley
2015-11-11 18:58 ` Karl Fogel
2015-11-11 19:07 ` Eli Zaretskii
2015-11-11 19:13 ` John Wiegley
2015-11-11 19:39 ` Karl Fogel
2015-11-11 20:11 ` Eli Zaretskii
2015-11-11 20:17 ` John Wiegley
2015-11-11 20:33 ` Karl Fogel
2015-11-11 20:37 ` Alan Mackenzie
2015-11-11 20:46 ` Eli Zaretskii
2015-11-11 20:58 ` John Wiegley
2015-11-11 21:08 ` Karl Fogel
2015-11-11 21:13 ` John Wiegley
2015-11-12 7:59 ` Karl Fogel
2015-11-11 21:53 ` David Kastrup
2015-11-11 21:52 ` David Kastrup
2015-11-12 0:08 ` Rasmus
2015-11-12 8:06 ` Karl Fogel
2015-11-12 10:00 ` Artur Malabarba
2015-11-12 11:08 ` Rasmus
2015-11-12 11:18 ` Andreas Schwab
2015-11-12 13:11 ` Artur Malabarba
2015-11-12 14:16 ` Rasmus
2015-11-12 14:44 ` Yuri Khan
2015-11-12 14:52 ` Rasmus
2015-11-12 14:54 ` Yuri Khan
2015-11-12 15:38 ` David Kastrup
2015-11-12 16:20 ` Karl Fogel
2015-11-12 16:33 ` Pierpaolo Bernardi
[not found] ` <CAAdUY-LVoXm-c+Cv8Gx6h+d40YDoK4rJp1U6Tw+Gc+yCOVee=g@mail.gmail.com>
2015-11-13 1:17 ` Artur Malabarba
2015-11-13 6:04 ` Pierpaolo Bernardi
2015-11-14 12:34 ` Artur Malabarba
2015-11-14 19:39 ` David Kastrup
2015-11-17 0:42 ` Karl Fogel
2015-11-17 0:53 ` Karl Fogel
2015-11-17 3:46 ` John Wiegley
2015-11-17 22:57 ` Richard Stallman
2015-11-17 23:16 ` John Wiegley
2015-11-18 17:25 ` Andreas Röhler
2015-11-17 23:20 ` Artur Malabarba
2015-11-18 20:32 ` Karl Fogel
2015-11-18 21:03 ` Artur Malabarba
2015-11-19 23:34 ` Karl Fogel
2015-11-19 23:57 ` Artur Malabarba
2015-11-14 21:59 ` Karl Fogel
2015-11-12 14:57 ` David Kastrup
2015-11-12 16:09 ` Artur Malabarba
2015-11-12 15:26 ` Rasmus
2015-11-11 20:15 ` Eli Zaretskii
2015-11-11 20:28 ` John Wiegley
2015-11-11 20:55 ` Eli Zaretskii
2015-11-11 21:00 ` John Wiegley
2015-11-11 21:16 ` Eli Zaretskii
2015-11-11 21:17 ` Alan Mackenzie
2015-11-11 21:30 ` John Wiegley
2015-11-11 22:40 ` Artur Malabarba
2015-11-11 19:20 ` Paul Eggert [this message]
2015-11-11 19:25 ` John Wiegley
2015-11-11 20:13 ` Eli Zaretskii
2015-11-11 21:50 ` David Kastrup
2015-11-11 22:24 ` Artur Malabarba
2015-11-11 21:31 ` John Wiegley
2015-11-11 21:46 ` Karl Fogel
2015-11-12 7:38 ` Andreas Röhler
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=5643951A.8040602@cs.ucla.edu \
--to=eggert@cs.ucla.edu \
--cc=bruce.connor.am@gmail.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=kfogel@red-bean.com \
/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.