unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Monnier via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: Акимжанчег <zelenaruta@gmail.com>, 45922@debbugs.gnu.org
Subject: bug#45922: 27.1; Better auto-fill for strings in python-mode
Date: Sat, 07 May 2022 13:28:15 -0400	[thread overview]
Message-ID: <jwvr1551cga.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <87h761l1rg.fsf@gnus.org> (Lars Ingebrigtsen's message of "Sat, 07 May 2022 18:56:51 +0200")

> But this reminds me that auto-fill-mode in programming modes is a bad
> idea in general:

Or at least, it needs to be custom-tailored (as in `smie-auto-fill` or
things along these lines).

In many/most programming languages the only real trouble is
inserting/adding newlines inside strings or newline-terminated comments.

> So I think the answer to this bug report is really -- don't use
> auto-fill in python-mode, and I'm closing it as a wontfix.

Yup, in python-mode (and other programming modes where LF is not always
treated as whitespace) it does need a lot more care.


        Stefan






      reply	other threads:[~2022-05-07 17:28 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-16 21:49 bug#45922: 27.1; Better auto-fill for strings in python-mode Акимжанчег
2021-01-17 11:58 ` Tomas Nordin
     [not found]   ` <CAJBTzO=rE4n4iZdBNv2HE=zi+_O1r=bqwFdsCku1-3VZOgqOWg@mail.gmail.com>
2021-01-17 20:18     ` Tomas Nordin
2022-05-07 15:51 ` Lars Ingebrigtsen
2022-05-07 16:25   ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-05-07 16:56     ` Lars Ingebrigtsen
2022-05-07 17:28       ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]

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=jwvr1551cga.fsf-monnier+emacs@gnu.org \
    --to=bug-gnu-emacs@gnu.org \
    --cc=45922@debbugs.gnu.org \
    --cc=larsi@gnus.org \
    --cc=monnier@iro.umontreal.ca \
    --cc=zelenaruta@gmail.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 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).