From: Stefan <monnier@IRO.UMontreal.CA>
To: Alan Mackenzie <acm@muc.de>
Cc: emacs-devel@gnu.org
Subject: Re: [Emacs-diffs] trunk r116461: Connect electric-indent-mode up with CC Mode. Bug #15478.
Date: Sun, 23 Mar 2014 21:37:09 -0400 [thread overview]
Message-ID: <jwvior4iej0.fsf-monnier+emacsdiffs@gnu.org> (raw)
In-Reply-To: <20140322223454.GA3562@acm.acm> (Alan Mackenzie's message of "Sat, 22 Mar 2014 22:34:55 +0000")
> The actual definition of "electricity" is found in the Emacs manual, page
Use in other packages shows that people have understood the notion of
"electric" to mean many other things beside the very restricted
semantics you point to.
>> In Elisp, without electric-indent you have to use C-j or TAB if you
>> want your code indented. So whether the user hits C-j or RET is
>> relevant.
> No. To keep Elisp properly indented, you merely have to depress
> whichever key is bound to `newline-and-indent', whether that be RET, or
> C-j, or whatever.
"whichever key is bound to `newline-and-indent'" would be C-j and not
RET in all Emacsen released so far, so I see we violently agree.
> Electric indentation doesn't come into it.
Of course it does because electric-indent changes the behavior such that
RET can be (or has to be in 24.4) used instead of C-j. But you knew
that, obviously.
> Yes, but the point still stands. You open up a fresh line, by RET, and
> type code into it, but don't want to type RET/C-j at the end of it.
Fine. Feel free to provide a patch to make split-line auto-indent when
electric-indent is enabled.
> You'll want electric indentation on some other character you've just
> typed.
Indeed that's also good. But I don't know of any such character we
could use globally in electric-indent-chars, so it's up to each major
mode to specify which chars to use.
> No. If electric indentation has already happened after typing the
> semicolon/comma/brace, the alignment of the subsequent comment will
> remain undisturbed. If RET puts the alignment out, you're cursing it.
Then I misunderstood and don't know what you're talking about. Can you
give a scenario?
>> What would be more optimal?
> A mode-dependent or buffer-local dependent setting, as well as, rather
> than instead of.
We have that: electric-indent-local-mode and electric-indent-inhibit.
> Why can't we simply have RET bound to `newline-and-indent' and C-j
> bound to `newline' in programming modes, as discussed and, pretty much
> agreed on, in emacs-devel last autumn?
Lack of patch implementing this (supposed) simple change?
> Incidentally, in Emacs -Q, Text Mode and Fundamental Mode have gone back
> to the unwanted state of RET doing `newline-and-indent'. Should I raise
> another bug report?
You can, but it's not a bug. It's a feature (not sure what you mean by
"back" since it's been this way ever since I enabled
electric-indent-mode by default, AFAIK).
So make this bug report specific about a particular circumstance where
the behavior is undesirable, or about how hard it is to disable it.
Stefan
next prev parent reply other threads:[~2014-03-24 1:37 UTC|newest]
Thread overview: 64+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1WFSpO-0001e7-Gm@vcs.savannah.gnu.org>
2014-02-18 0:11 ` [Emacs-diffs] trunk r116461: Connect electric-indent-mode up with CC Mode. Bug #15478 Stefan Monnier
2014-02-22 18:27 ` Alan Mackenzie
2014-02-25 3:24 ` Stefan Monnier
2014-02-28 19:50 ` Alan Mackenzie
2014-03-01 15:57 ` Stefan Monnier
2014-03-02 11:51 ` Alan Mackenzie
2014-03-04 3:48 ` Stefan Monnier
2014-03-08 22:58 ` Alan Mackenzie
2014-03-09 1:57 ` Stefan Monnier
2014-03-09 12:37 ` Alan Mackenzie
2014-03-10 3:37 ` Stefan Monnier
2014-03-10 6:59 ` Glenn Morris
2014-03-10 12:24 ` João Távora
2014-03-10 18:30 ` Stefan Monnier
2014-03-16 22:35 ` Alan Mackenzie
2014-03-17 15:48 ` Stefan
2014-03-19 22:42 ` Alan Mackenzie
2014-03-20 1:46 ` Stefan
2014-03-20 8:35 ` Thien-Thi Nguyen
2014-03-21 8:24 ` João Távora
2014-03-22 13:13 ` Alan Mackenzie
2014-03-22 16:14 ` Stefan
2014-03-22 20:19 ` David Caldwell
2014-03-22 22:05 ` David Kastrup
2014-03-22 22:32 ` David Caldwell
2014-03-24 1:13 ` Stefan
2014-03-22 22:34 ` Alan Mackenzie
2014-03-24 1:37 ` Stefan [this message]
2014-03-24 22:40 ` Alan Mackenzie
2014-03-25 1:37 ` Dmitry Gutov
2014-03-26 20:53 ` Alan Mackenzie
2014-03-27 8:02 ` Dmitry Gutov
2014-03-30 14:57 ` Alan Mackenzie
2014-03-31 17:11 ` Dmitry Gutov
2014-04-03 21:53 ` Alan Mackenzie
2014-03-25 1:54 ` Stefan
2014-03-26 21:21 ` Alan Mackenzie
2014-03-27 14:49 ` Stefan Monnier
2014-03-30 11:37 ` Alan Mackenzie
2014-03-30 16:46 ` Stefan Monnier
2014-03-22 23:10 ` Alan Mackenzie
2014-03-24 1:39 ` Stefan
2014-03-24 6:59 ` Stephen J. Turnbull
2014-03-24 9:08 ` Dmitry Gutov
2014-03-24 17:19 ` Eli Zaretskii
2014-03-24 17:29 ` David Kastrup
2014-03-24 17:39 ` David Kastrup
2014-03-24 17:38 ` Dmitry Gutov
2014-03-24 17:52 ` Eli Zaretskii
2014-03-25 1:53 ` Dmitry Gutov
2014-03-25 3:49 ` Eli Zaretskii
2014-03-24 18:32 ` Stefan
2014-03-25 1:49 ` Dmitry Gutov
2014-03-25 7:44 ` Stephen J. Turnbull
2014-03-25 8:08 ` Steinar Bang
2014-03-25 16:49 ` Stephen J. Turnbull
2014-03-25 17:08 ` Steinar Bang
2014-03-25 17:31 ` Dmitry Gutov
2014-03-25 19:28 ` Steinar Bang
2014-03-25 19:49 ` David Kastrup
2014-03-25 19:54 ` Dmitry Gutov
2014-03-25 13:26 ` Stefan Monnier
2014-03-27 7:51 ` Stephen J. Turnbull
2014-03-24 21:12 ` Alan Mackenzie
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=jwvior4iej0.fsf-monnier+emacsdiffs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=acm@muc.de \
--cc=emacs-devel@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 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).