public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Ulrich Mueller <ulm@gentoo.org>
To: Paul Zander <negril.nx+gentoo@gmail.com>
Cc: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] [PATCH 3/3] [QA] drop indent_size
Date: Sun, 05 May 2024 19:53:14 +0200	[thread overview]
Message-ID: <ujzk8f8mt@gentoo.org> (raw)
In-Reply-To: <20240505155038.24810-1-negril.nx+gentoo@gmail.com> (Paul Zander's message of "Sun, 5 May 2024 17:50:38 +0200")

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

>>>>> On Sun, 05 May 2024, Paul Zander wrote:

> indent_size is the width in spaces, we use tabs.
> tab_width would be the tab width in spaces, but there is no reason to
> force this.

The Devmanual says that "each tab represents four spaces" [1,2], and
ebuild-mode implements it so [3]. Maybe it would be good to stay
consistent for different editors?

[1] https://devmanual.gentoo.org/quickstart/index.html#basic-format
[2] https://devmanual.gentoo.org/ebuild-writing/file-format/index.html#indenting-and-whitespace
[3] https://gitweb.gentoo.org/proj/ebuild-mode.git/tree/ebuild-mode.el#n416

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 507 bytes --]

  reply	other threads:[~2024-05-05 17:53 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-05 14:45 [gentoo-dev] [PATCH 1/3] [QA] fix .editorconfig Paul Zander
2024-05-05 15:48 ` [gentoo-dev] [PATCH 2/3] [QA] allow overriding settings Paul Zander
2024-05-05 15:50   ` [gentoo-dev] [PATCH 3/3] [QA] drop indent_size Paul Zander
2024-05-05 17:53     ` Ulrich Mueller [this message]
2024-05-05 18:56     ` Eli Schwartz
2024-05-05 19:04   ` [gentoo-dev] [PATCH 2/3] [QA] allow overriding settings Eli Schwartz
2024-05-05 17:45 ` [gentoo-dev] [PATCH 1/3] [QA] fix .editorconfig Ulrich Mueller
2024-09-19  7:24 ` Sam James

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=ujzk8f8mt@gentoo.org \
    --to=ulm@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    --cc=negril.nx+gentoo@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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox