unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Boruch Baum <boruch_baum@gmx.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 45582@debbugs.gnu.org
Subject: bug#45582: 28: auto-fill final line of indented paragraph
Date: Fri, 1 Jan 2021 07:25:21 -0500	[thread overview]
Message-ID: <20210101122521.uzqz2o6nug6bow4y@E15-2016.optimum.net> (raw)
In-Reply-To: <83a6ttgmgo.fsf@gnu.org>

n 2021-01-01 09:12, Eli Zaretskii wrote:
> > Date: Thu, 31 Dec 2020 18:23:25 -0500
> > From: Boruch Baum <boruch_baum@gmx.com>
>
> You are in Lisp Interaction mode, which has its own indentation rules.
> Try this in Fundamental mode, and you will see the behavior you
> expect, I think.
>
> IOW, I don't think there's a bug here. But if there is a bug, please
> tell what behavior you expected and why.

The default contents of the scratch buffer read: "This buffer is for
text that is not saved ..." so any newcomer to emacs gets the indication
that _text_ typed here will be treated as text (and yes lisp typed here
will be treated as lisp), and people expect text paragraphs not to have
their final line be out-dented *after* completion. Any newcomer to emacs
will clearly consider this a bug. I also do consider it a bug.

> To investigate this further, note that electric-indent-mode is ON

That speaks to the choice of how to classify the bug, not whether it is
a bug. Maybe you'll consider it a bug in that mode, or in auto-fill
mode, or in lisp-interaction-mode, or in the setup of the scratch
buffer, or in the relationship between those three modes, or in the
default comment of that buffer, or in something else. I don't have a
suggestion either way, only the observation that the behavior is
unexpected, counter-intuitive, and annoying.

--
hkp://keys.gnupg.net
CA45 09B5 5351 7C11 A9D1  7286 0036 9E45 1595 8BC0





  reply	other threads:[~2021-01-01 12:25 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-31 23:23 bug#45582: 28: auto-fill final line of indented paragraph Boruch Baum
2021-01-01  7:12 ` Eli Zaretskii
2021-01-01 12:25   ` Boruch Baum [this message]
2021-01-11 15:48     ` Lars Ingebrigtsen

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=20210101122521.uzqz2o6nug6bow4y@E15-2016.optimum.net \
    --to=boruch_baum@gmx.com \
    --cc=45582@debbugs.gnu.org \
    --cc=eliz@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).