From: Richard Stallman <rms@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: rgm@gnu.org, johnw@gnu.org, 22564@debbugs.gnu.org,
monnier@iro.umontreal.ca, acm@muc.de, larsi@gnus.org
Subject: bug#22564: Fundamental mode isn't fundamental enough.
Date: Sat, 07 May 2022 19:08:36 -0400 [thread overview]
Message-ID: <E1nnTXQ-0003um-44@fencepost.gnu.org> (raw)
In-Reply-To: <83ilqhzwfd.fsf@gnu.org> (message from Eli Zaretskii on Sat, 07 May 2022 09:30:46 +0300)
[[[ To any NSA and FBI agents reading my email: please consider ]]]
[[[ whether defending the US Constitution against all enemies, ]]]
[[[ foreign or domestic, requires you to follow Snowden's example. ]]]
> > As far as I could see, it did not change anything.
> > So I tried again in emacs -Q, and I saw it indented the
> > following line.
> Are you customizing the command bound to RET in your init files?
I can't see any sign that it does that, but I guess it does something
pertinent though I can't tell what.
Anyway, the thing to document is the emacs -Q behavior.
> Indenting the following line is the expected default behavior, yes.
I think the documentation of Electric Indent mode should say that that
is what it does in modes that don't alter the behavior. That's explicit.
Why not?
> > Maybe. But I do think the term "reindent" needs to be explined
> > somewhere in the Emacs manual.
> If all we need to say is that reindent means to remove any indentation
> and then indent the line according to context and major mode's rules,
> that's simple enough.
I think that's correct.
--
Dr Richard Stallman (https://stallman.org)
Chief GNUisance of the GNU Project (https://gnu.org)
Founder, Free Software Foundation (https://fsf.org)
Internet Hall-of-Famer (https://internethalloffame.org)
next prev parent reply other threads:[~2022-05-07 23:08 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-05 12:55 bug#22564: Fundamental mode isn't fundamental enough Alan Mackenzie
2016-02-05 14:46 ` Eli Zaretskii
2016-02-05 15:13 ` Alan Mackenzie
2016-02-05 15:34 ` Mark Oteiza
2016-02-05 15:38 ` Drew Adams
2016-02-05 17:57 ` Marcin Borkowski
2016-02-05 19:59 ` Drew Adams
2016-02-05 19:26 ` Eli Zaretskii
2016-02-05 20:18 ` Marcin Borkowski
2016-02-06 19:48 ` Richard Stallman
2016-02-05 20:23 ` Glenn Morris
2016-02-05 21:43 ` Glenn Morris
2016-02-05 21:53 ` Alan Mackenzie
2016-02-17 2:50 ` John Wiegley
2022-04-27 14:39 ` Lars Ingebrigtsen
2022-05-01 1:53 ` Richard Stallman
2022-05-01 6:16 ` Eli Zaretskii
2022-05-02 23:47 ` Richard Stallman
2022-05-03 7:03 ` Andreas Röhler
2022-05-03 14:28 ` Drew Adams
2022-05-03 17:00 ` Eli Zaretskii
2022-05-04 22:49 ` Richard Stallman
2022-05-05 5:43 ` Eli Zaretskii
2022-05-05 11:02 ` Andreas Röhler
2022-05-05 16:17 ` Eli Zaretskii
2022-05-05 18:34 ` Andreas Röhler
2022-05-06 23:20 ` Richard Stallman
2022-05-07 6:30 ` Eli Zaretskii
2022-05-07 23:08 ` Richard Stallman [this message]
[not found] ` <mailman.3748.1454702408.843.bug-gnu-emacs@gnu.org>
2016-02-06 11:06 ` Alan Mackenzie
2016-02-07 18:33 ` Richard Stallman
[not found] ` <mailman.3712.1454686507.843.bug-gnu-emacs@gnu.org>
2016-02-06 11:21 ` Alan Mackenzie
2016-02-06 14:36 ` Mark Oteiza
2016-02-06 16:59 ` Achim Gratz
2016-02-07 19:09 ` Eli Zaretskii
2016-02-07 21:02 ` Achim Gratz
2016-02-07 21:08 ` Eli Zaretskii
2016-02-08 19:39 ` Achim Gratz
2016-02-08 20:05 ` Eli Zaretskii
2016-02-08 20:18 ` Achim Gratz
2016-02-08 20:53 ` Eli Zaretskii
2016-02-08 21:01 ` Achim Gratz
2016-02-09 3:31 ` Eli Zaretskii
[not found] <<20160205125559.GC7727@acm.fritz.box>
[not found] ` <<834mdnusem.fsf@gnu.org>
2016-02-05 15:36 ` Drew Adams
[not found] <<mailman.3748.1454702408.843.bug-gnu-emacs@gnu.org>
[not found] ` <<20160206110601.6095.qmail@mail.muc.de>
2016-02-06 15:57 ` Drew Adams
[not found] ` <<E1aSU9T-0002aS-5O@fencepost.gnu.org>
2016-02-07 19:43 ` Drew Adams
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=E1nnTXQ-0003um-44@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=22564@debbugs.gnu.org \
--cc=acm@muc.de \
--cc=eliz@gnu.org \
--cc=johnw@gnu.org \
--cc=larsi@gnus.org \
--cc=monnier@iro.umontreal.ca \
--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.