From: Lars Ingebrigtsen <larsi@gnus.org>
To: Dale Sedivec <dale@codefu.org>
Cc: swedebugia <swedebugia@riseup.net>, 42513@debbugs.gnu.org
Subject: bug#42513: Python indentation bug when using multi-line on an if-condition
Date: Thu, 28 Jan 2021 05:55:51 +0100 [thread overview]
Message-ID: <877dnx64o8.fsf@gnus.org> (raw)
In-Reply-To: <D38B8535-E681-4321-886E-68833F49036E@codefu.org> (Dale Sedivec's message of "Wed, 27 Jan 2021 12:20:32 -0600")
[-- Attachment #1: Type: text/plain, Size: 648 bytes --]
Dale Sedivec <dale@codefu.org> writes:
> If I use something other than a comment following the "if" statement
> line, I can reproduce the original behavior in a master build from
> yesterday. For example, replace "#do something" with "''" (an empty
> string) or just "bar".
Indeed:
def fun(arg):
if(
args.suppliername == "x"):
foo
else:
foo
def fun(arg):
if(
args.suppliername == "Messingschlager" or
args.suppliercodename == "MS"
):
foo
else:
foo
[-- Attachment #2: Type: image/png, Size: 56981 bytes --]
[-- Attachment #3: Type: text/plain, Size: 404 bytes --]
> (I am *guessing* the original reporter's code had at least one
> statement in the "if" block. It's not valid syntax otherwise.)
However, both these examples indent the same for me in Emacs 26.1 and
Emacs 28 (wrong in the same way), so I'm still not seeing what the
original reporter is seeing?
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
prev parent reply other threads:[~2021-01-28 4:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-24 9:40 bug#42513: Python indentation bug when using multi-line on an if-condition swedebugia
2020-09-15 23:25 ` bug#42513: Possible fix for Python indentation problem Dale Sedivec
2021-01-27 6:47 ` bug#42513: Python indentation bug when using multi-line on an if-condition Lars Ingebrigtsen
2021-01-27 18:20 ` Dale Sedivec
2021-01-28 4:55 ` Lars Ingebrigtsen [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=877dnx64o8.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=42513@debbugs.gnu.org \
--cc=dale@codefu.org \
--cc=swedebugia@riseup.net \
/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.