all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Valentin Ignatev <valentignatev@gmail.com>
Cc: 34268@debbugs.gnu.org, sds@gnu.org,
	Augusto Stoffel <arstoffel@gmail.com>
Subject: bug#34268: 27.0.50; wrong indentation in python mode
Date: Wed, 22 Sep 2021 23:57:52 +0200	[thread overview]
Message-ID: <877df8qnmn.fsf_-_@gnus.org> (raw)
In-Reply-To: <CADXmXkg56TEF=GA0WQ4hdOGPpLv4ia2_8wZziLVtCUgX2atD0g@mail.gmail.com> (Valentin Ignatev's message of "Mon, 10 Jun 2019 00:24:28 +0300")

Valentin Ignatev <valentignatev@gmail.com> writes:

> Hey Sam, I've looked in the python.el code and it seems that it reuses
> python-indent-def-block-scale for calculating an indentation.
>
> The default value is 2 which is why inside-parens indent doubles. Setting its
> value to 1 fixes the issue.
>
> I also wonder why authors choose double indent for aligning function
> arguments. Is this some kind of an oldschool code style? :) 

(I'm going through old bug reports that unfortunately weren't resolved
at the time.)

If I understand correctly (and I may well not -- I don't write much
python), this is just a preference issue, and setting
`python-indent-def-block-scale' to 1 fixes the issue?

If that's what's recommended by the standards, should we flip the
default to 1?

I've added Augusto to the CCs; perhaps he has an opinion here.

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





  reply	other threads:[~2021-09-22 21:57 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-31 21:04 bug#34268: 27.0.50; wrong indentation in python mode Sam Steingold
2019-02-19 13:13 ` Bhavin Gandhi
2019-02-19 13:53   ` Sam Steingold
2019-06-09 21:24 ` bug#34268: Configuration option to fix the issue Valentin Ignatev
2021-09-22 21:57   ` Lars Ingebrigtsen [this message]
2021-09-23 12:37     ` bug#34268: 27.0.50; wrong indentation in python mode Andreas Röhler
2021-09-23 21:08     ` Augusto Stoffel
2021-09-23 22:01       ` 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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=877df8qnmn.fsf_-_@gnus.org \
    --to=larsi@gnus.org \
    --cc=34268@debbugs.gnu.org \
    --cc=arstoffel@gmail.com \
    --cc=sds@gnu.org \
    --cc=valentignatev@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 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.