unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Gustaf Waldemarson <gustaf.waldemarson@gmail.com>
To: kobarity <kobarity@gmail.com>
Cc: 62696@debbugs.gnu.org
Subject: bug#62696: python.el: Extra indentation for conditionals
Date: Sun, 16 Apr 2023 17:49:26 +0200	[thread overview]
Message-ID: <CABehr5ewQt6-Lhba802YSDRL1rcBuJc59evy1ZDEzbf-aWcY2A@mail.gmail.com> (raw)
In-Reply-To: <eke7fs90j6ya.wl-kobarity@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1660 bytes --]

Hello,

I think that's a really good idea actually. It might also be a good idea to
add a
negative example (i.e., the black-indentation style you mentioned earlier),
or
a reference to one (maybe to the tests?)

Best regards,
Gustaf

Den sön 16 apr. 2023 kl 15:24 skrev kobarity <kobarity@gmail.com>:

>
> kobarity wrote:
> > Gustaf Waldemarson wrote:
> > > "Increase indentation inside parens of a block.
> > > When this variable is set to non-nil and the contents of a block
> > > inside parens are indented to the same level as outside the same
> > > block, increase the indentation of the line."
> >
> > Thank you for your suggestion.  I think this is more readable and
> > would like to make changes in this direction.
>
> I have concluded that it's better to include an example in the
> docstring of `python-indent-block-paren-deeper'.  How about the
> following?  I also attached the updated patch.
>
> "Increase indentation inside parens of a block.
> If non-nil, increase the indentation of the lines inside parens
> in a header of a block when they are indented to the same level
> as the body of the block:
>
>     if (some_expression
>             and another_expression):
>         do_something()
>
> instead of:
>
>     if (some_expression
>         and another_expression):
>         do_something()
>
> This variable only works if the opening paren is followed by
> non-whitespace characters on the same line.  Modify
> `python-indent-def-block-scale' to customize the case where
> non-whitespace character does not follow the opening paren on the
> same line."
>
> Best regards,
> kobarity
>

[-- Attachment #2: Type: text/html, Size: 2206 bytes --]

  reply	other threads:[~2023-04-16 15:49 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-06 12:47 bug#62696: python.el: Extra indentation for conditionals Gustaf Waldemarson
2023-04-09 12:11 ` kobarity
2023-04-10 11:11   ` Gustaf Waldemarson
2023-04-10 15:21     ` kobarity
2023-04-11 11:11       ` Gustaf Waldemarson
2023-04-12 15:26         ` kobarity
2023-04-16 13:24           ` kobarity
2023-04-16 15:49             ` Gustaf Waldemarson [this message]
2023-04-18 14:23               ` kobarity
2023-04-20  8:22                 ` Eli Zaretskii
2023-04-20 13:40                   ` Gustaf Waldemarson
2023-04-20 14:19                     ` kobarity
2023-04-20 17:44                       ` Gustaf Waldemarson
2023-04-22  9:33                       ` Eli Zaretskii

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=CABehr5ewQt6-Lhba802YSDRL1rcBuJc59evy1ZDEzbf-aWcY2A@mail.gmail.com \
    --to=gustaf.waldemarson@gmail.com \
    --cc=62696@debbugs.gnu.org \
    --cc=kobarity@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).