From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.devel Subject: Re: Should indent-tabs-mode insert tabs only leading whitespace? Date: Fri, 17 Jul 2020 14:10:35 -0400 Message-ID: References: <0456f08d3ac9a2ee84ced480529ced00.squirrel@dancol.org> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="36283"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/28.0.50 (gnu/linux) Cc: emacs-devel@gnu.org To: "Daniel Colascione" Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Fri Jul 17 20:11:54 2020 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1jwUpt-0009Kx-W6 for ged-emacs-devel@m.gmane-mx.org; Fri, 17 Jul 2020 20:11:53 +0200 Original-Received: from localhost ([::1]:34048 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jwUpt-0007m1-1B for ged-emacs-devel@m.gmane-mx.org; Fri, 17 Jul 2020 14:11:53 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:35558) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1jwUon-0007Dh-Fq for emacs-devel@gnu.org; Fri, 17 Jul 2020 14:10:45 -0400 Original-Received: from mailscanner.iro.umontreal.ca ([132.204.25.50]:17910) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1jwUoh-00019e-8M for emacs-devel@gnu.org; Fri, 17 Jul 2020 14:10:44 -0400 Original-Received: from pmg3.iro.umontreal.ca (localhost [127.0.0.1]) by pmg3.iro.umontreal.ca (Proxmox) with ESMTP id C1E3E440318; Fri, 17 Jul 2020 14:10:37 -0400 (EDT) Original-Received: from mail01.iro.umontreal.ca (unknown [172.31.2.1]) by pmg3.iro.umontreal.ca (Proxmox) with ESMTP id 592544402D6; Fri, 17 Jul 2020 14:10:36 -0400 (EDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=iro.umontreal.ca; s=mail; t=1595009436; bh=vMBAtm6LpNJ2BCwYjBNGRWXGjGTou15HJ/Y6kVDzrQQ=; h=From:To:Cc:Subject:References:Date:In-Reply-To:From; b=LPH4mj8SoetppjYe2zXQQ9gRn/voegyXap9IyFyOWOTZj0jI10SZe01f/avwkUsYY 3AZodRUGSsJIvgHMGr+9DiUQ1mxZwbiS7TLae63Sz6ui4xECTsrq2M+TByAQMT5lUg B8fq8fQlM61LPFHxVqwUeTB1Ld+LCgz2faVO5bfl0oNQi67RXZnuduYOTBgY6eg1e3 omwtN90ETj3stT5ao7ZIMv5F3gVpuUaQ1X6r/5FkBteJSw4XksqdeQaDT+zD+VeWP4 8ERykBVlkvLGSsI9lN9ezvfQ9k/JWuIadIjo603AxBjunW7XAkgAJOKbCbMwpM+w04 /N4TqkCNYE0sA== Original-Received: from milanesa (76-10-180-175.dsl.teksavvy.com [76.10.180.175]) by mail01.iro.umontreal.ca (Postfix) with ESMTPSA id 1CA0C1209BC; Fri, 17 Jul 2020 14:10:36 -0400 (EDT) In-Reply-To: <0456f08d3ac9a2ee84ced480529ced00.squirrel@dancol.org> (Daniel Colascione's message of "Fri, 17 Jul 2020 10:52:20 -0700") Received-SPF: pass client-ip=132.204.25.50; envelope-from=monnier@iro.umontreal.ca; helo=mailscanner.iro.umontreal.ca X-detected-operating-system: by eggs.gnu.org: First seen = 2020/07/17 12:20:17 X-ACL-Warn: Detected OS = Linux 2.2.x-3.x [generic] X-Spam_score_int: -42 X-Spam_score: -4.3 X-Spam_bar: ---- X-Spam_report: (-4.3 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.io gmane.emacs.devel:253044 Archived-At: > There are lots of fixes for this problem, but the fundamental issue seems > to be that indent-to inserts tab characters for column alignment *after* > non-whitespace characters on a given line. What if indent-to always > inserted spaces when there were non-whitespace characters between BOL and > point? That whitespace manipulation isn't really indentation. AFAIK `indent-to` is a low-level function that is used for indentation indeed but is also used for alignment and many other purposes, so changing it as you suggested will likely lead to undesired behaviors in some cases. So I think this should be fixed elsewhere or at least be conditional on some new variable setting (e.g. `indent-tab-mode` set to `only-at-bol`). Stefan