all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Glenn Morris <rgm@gnu.org>
To: Carlos Pita <carlosjosepita@gmail.com>
Cc: 32120@debbugs.gnu.org, Robert Pluim <rpluim@gmail.com>
Subject: bug#32120: 26.1; In python.el tab-width should default to 4
Date: Wed, 11 Jul 2018 13:19:26 -0400	[thread overview]
Message-ID: <0mo9fdvgf5.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <CAELgYhcbhRkLWG0Obf2JmyJRef7bgSHCqcQPNHhVK4xA5hePXw@mail.gmail.com> (Carlos Pita's message of "Wed, 11 Jul 2018 10:50:39 -0300")

Carlos Pita wrote:

> When you do rigid indentation, say C-x Tab and then S-Right, you get
> 8-spaces tab steps with that configuration.

Right. What is your justification for wanting this to be 4?
Python generally discourages tabs, but when they are present, seems to
follow the historical convention mapping them to 8 spaces. Eg

https://docs.python.org/3/reference/lexical_analysis.html#indentation

    Tabs are replaced (from left to right) by one to eight spaces such
    that the total number of characters up to and including the
    replacement is a multiple of eight (this is intended to be the same
    rule as used by Unix).





  reply	other threads:[~2018-07-11 17:19 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-10 22:05 bug#32120: 26.1; In python.el tab-width should default to 4 Carlos Pita
2018-07-11  9:33 ` Robert Pluim
2018-07-11 13:50   ` Carlos Pita
2018-07-11 17:19     ` Glenn Morris [this message]
2018-07-11 17:25       ` Carlos Pita
2018-07-11 20:15         ` Glenn Morris
2018-07-11 20:23           ` Carlos Pita
2019-03-30  3:17         ` Noam Postavsky
2019-03-30  3:25           ` Carlos Pita
2019-03-30 12:52             ` Noam Postavsky
2019-03-30 13:33               ` Carlos Pita
2019-03-30 13:37                 ` Carlos Pita
2019-01-07  3:13 ` bug#32120: Carlos Pita
2019-09-13 11:03 ` bug#32120: 26.1; In python.el tab-width should default to 4 Stefan Kangas

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=0mo9fdvgf5.fsf@fencepost.gnu.org \
    --to=rgm@gnu.org \
    --cc=32120@debbugs.gnu.org \
    --cc=carlosjosepita@gmail.com \
    --cc=rpluim@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.