unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Carlos Pita <carlosjosepita@gmail.com>
Cc: Noam Postavsky <npostavs@gmail.com>, 37726@debbugs.gnu.org
Subject: bug#37726:
Date: Sun, 09 Aug 2020 23:54:26 +0200	[thread overview]
Message-ID: <874kpba3jh.fsf@gnus.org> (raw)
In-Reply-To: <CAELgYhdUR1AOz+QEEtR1zK9NiE7MeDHfqjUEkX0S6Hb3BXJbCg@mail.gmail.com> (Carlos Pita's message of "Sat, 19 Oct 2019 05:32:03 -0300")

Carlos Pita <carlosjosepita@gmail.com> writes:

> This new patch:
>
> * Removes accidentally introduced blank line.
> * Improves commit message.
>

If you have a string like:

multiline = '''
bunch
of
lines
'''

After the patch, and if you hit TAB at the start of the lines, you'll
end up with:

multiline = '''
            bunch
            of
            lines
            '''

But that's a different string, isn't it?  The leading spaces are part of
the string itself, which isn't what we want.

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no





  parent reply	other threads:[~2020-08-09 21:54 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-13  4:29 bug#37726: [PATCH] Indent python multiline strings to start and previous levels Carlos Pita
2019-10-13  5:04 ` bug#37726: Carlos Pita
2019-10-13 18:35   ` bug#37726: Carlos Pita
2019-10-13 19:06     ` bug#37726: Carlos Pita
2019-10-19  8:32       ` bug#37726: Carlos Pita
2019-10-23  0:25         ` bug#37726: [PATCH] Indent python multiline strings to start and previous levels Noam Postavsky
2020-08-09 18:46         ` bug#37726: Lars Ingebrigtsen
2020-08-09 21:44           ` bug#37726: Glenn Morris
2020-08-09 21:50             ` bug#37726: Lars Ingebrigtsen
2020-08-09 21:54         ` Lars Ingebrigtsen [this message]
2020-10-13  3:56           ` bug#37726: Lars Ingebrigtsen
2019-10-23  0:34       ` bug#37726: [PATCH] Indent python multiline strings to start and previous levels Noam Postavsky

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=874kpba3jh.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=37726@debbugs.gnu.org \
    --cc=carlosjosepita@gmail.com \
    --cc=npostavs@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).