From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp11.migadu.com ([2001:41d0:2:bcc0::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms9.migadu.com with LMTPS id oCHlA62BmWTTDAEASxT56A (envelope-from ) for ; Mon, 26 Jun 2023 14:16:45 +0200 Received: from aspmx1.migadu.com ([2001:41d0:2:bcc0::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp11.migadu.com with LMTPS id 6L60A62BmWTGMwAA9RJhRA (envelope-from ) for ; Mon, 26 Jun 2023 14:16:45 +0200 Received: from lists.gnu.org (lists.gnu.org [209.51.188.17]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by aspmx1.migadu.com (Postfix) with ESMTPS id C48743BDD0 for ; Mon, 26 Jun 2023 14:16:44 +0200 (CEST) Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1qDl7v-0002rs-VZ; Mon, 26 Jun 2023 08:15:28 -0400 Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1qDl7r-0002r4-Tn for emacs-orgmode@gnu.org; Mon, 26 Jun 2023 08:15:25 -0400 Received: from mout02.posteo.de ([185.67.36.66]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1qDl7p-0007zo-5p for emacs-orgmode@gnu.org; Mon, 26 Jun 2023 08:15:23 -0400 Received: from submission (posteo.de [185.67.36.169]) by mout02.posteo.de (Postfix) with ESMTPS id DAC63240101 for ; Mon, 26 Jun 2023 14:15:17 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=posteo.eu; s=2017; t=1687781717; bh=mLIh2YAWMSxrjmBKRTg5I1gFGlKbCmy41QtRT6IHcMM=; h=Message-ID:Date:MIME-Version:Reply-To:Subject:To:Cc:From: Content-Transfer-Encoding:From; b=o7jCgrg6hflyw2E5f3hgl1XxToTiavzEwFuS39iuW1dDx+BRf3hMT8gJx7vM27UBg NLeYBiKSqCWTRNtgSjyveXEMEhspLX4eAvYmGnYlsaAKlwwW+7EedomnL61+a6BUCK O6QTrAZJUl4nCDpcu2H4SJnsfwKux53omDiJ2uwBvIU5TqZmoMhFvnYKF0S3dai1o0 7VSpXy3AyhU7F59QiFbzL0LCBQIC+jz3I4VR+B0qrEcIPD7vK/NWWDfor3GwhJVCe9 tXBl8TSzFkmRXv5gupVSZgddNF39gl5ocwvj2V5IMwjSYZdAc2VaPR1rW7EqKZb9vd BA/lLUSoicz8g== Received: from customer (localhost [127.0.0.1]) by submission (posteo.de) with ESMTPSA id 4QqRcj1N9Vz6tvx; Mon, 26 Jun 2023 14:15:17 +0200 (CEST) Message-ID: <1a97917c-bbab-4d7f-b629-0c84807448f2@posteo.eu> Date: Mon, 26 Jun 2023 12:15:16 +0000 MIME-Version: 1.0 Subject: Re: [BUG] Source block indentation does not work properly for yaml-mode [9.6.6 ( @ /home/user/.emacs.d/elpa/org-9.6.6/)] Content-Language: fr To: Ihor Radchenko Cc: wolf , emacs-orgmode@gnu.org References: <87ttva8chx.fsf@localhost> <8d8642c9-ced3-b254-0f49-f7b9c06311ff@posteo.eu> <87352p9g13.fsf@localhost> <87zg4vsof6.fsf@localhost> <37d86bbf-c0e2-6337-efc2-cdf63dbf4580@posteo.eu> <87sfamsb7m.fsf@localhost> <274bbd61-790d-8e19-d3a0-0793126c3bb0@posteo.eu> <87cz1itp8k.fsf@localhost> From: =?UTF-8?Q?S=c3=a9bastien_Miquel?= In-Reply-To: <87cz1itp8k.fsf@localhost> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Received-SPF: pass client-ip=185.67.36.66; envelope-from=sebastien.miquel@posteo.eu; helo=mout02.posteo.de X-Spam_score_int: -43 X-Spam_score: -4.4 X-Spam_bar: ---- X-Spam_report: (-4.4 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H5=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: emacs-orgmode@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Reply-To: sebastien.miquel@posteo.eu Errors-To: emacs-orgmode-bounces+larch=yhetil.org@gnu.org Sender: emacs-orgmode-bounces+larch=yhetil.org@gnu.org X-Migadu-Country: US X-Migadu-Flow: FLOW_IN ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=yhetil.org; s=key1; t=1687781804; h=from:from:sender:sender:reply-to:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc:mime-version:mime-version: content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references:list-id:list-help: list-unsubscribe:list-subscribe:list-post:dkim-signature; bh=twIcYwgOZ0klusx4y6bVbuwo63rExTllEWLh3vn4RTU=; b=hMRVzHpsxluBQlurYMzblyCdyEOY5WU9913DOn1kmnBtjuEanmsbprCRcrpJkDbtHCMnTT KG3Sy49GBBsN/V7NYk7veJLznc1WYDgNJA0tkXnMf/wBQMM78cto3P+1nT7wxFqk/Ga2WJ NZGpcOkCgg30bSZg3PJX2iDHl8C6bPJHGTnf045KdyC8OGyxzLznfOx1F0n0wDvx2HzjSN rziAVpqI5BAkQSMfFSddcKta4rLSIpC2VnTf6XvlzlR9SbdO+VxPibYDP2SKnNWQp/2/TJ LwYHlwlE56DjTfKsBf5gSmbuJ0w2V+ZeJX5+pNLLqos5LdLnn2MqkaMmuzVXvw== ARC-Authentication-Results: i=1; aspmx1.migadu.com; dkim=pass header.d=posteo.eu header.s=2017 header.b=o7jCgrg6; dmarc=pass (policy=none) header.from=posteo.eu; spf=pass (aspmx1.migadu.com: domain of "emacs-orgmode-bounces+larch=yhetil.org@gnu.org" designates 209.51.188.17 as permitted sender) smtp.mailfrom="emacs-orgmode-bounces+larch=yhetil.org@gnu.org" ARC-Seal: i=1; s=key1; d=yhetil.org; t=1687781804; a=rsa-sha256; cv=none; b=HfQFHgh2hj6nk025l5pG/aimYzUrZ4lMsY67DFyMCSzavrpMDU1g18tcDBxqpY4TNMGvX/ Vvl7OcirgumdJpM/uldaF4okCoH+zlEC7XuL5bcUAFkE2eBHG8d1uX90edxTeXCYdI4aHK TRGQdL2kfr4shDa+BHZ7UZ4kKPwglIAkGrI+qasZt5/Mi4bd5b9xMUCbkbPmEfjEOz+Gk/ lOXvx5ju2ihSjN0idfugeCQe5RH0sTiZiVOZnLMmhu/7vRn/lyC1y6sDl/4fnKTdjuPeZn AUePpFnHtiV/wUrKJy9UbDFYwBn8HhPCAbkhYnCw6IjljwqarhsKGuZiJfPsJA== X-Migadu-Scanner: scn1.migadu.com X-Migadu-Spam-Score: -6.55 Authentication-Results: aspmx1.migadu.com; dkim=pass header.d=posteo.eu header.s=2017 header.b=o7jCgrg6; dmarc=pass (policy=none) header.from=posteo.eu; spf=pass (aspmx1.migadu.com: domain of "emacs-orgmode-bounces+larch=yhetil.org@gnu.org" designates 209.51.188.17 as permitted sender) smtp.mailfrom="emacs-orgmode-bounces+larch=yhetil.org@gnu.org" X-Migadu-Queue-Id: C48743BDD0 X-Spam-Score: -6.55 X-TUID: jRppJMrzxprF Ihor Radchenko writes: > May you please provide an example for such breakage? > From my point of view, alignment is far lesser concern compared to > indentation breaking code execution/tangling/other functional parts of Org. Let's say tab-width is 8 and elisp-mode uses tabs for indentation. In the following snippet, arg2 should be indented with a tab. #+BEGIN_SRC emacs-lisp (some-f arg1 arg2) ;; arg2 is indented at column 8 #+END_SRC If I add two spaces at the beginning of the block. It should visually look like this: #+BEGIN_SRC emacs-lisp (some-f arg1 arg2) ;; arg2 is indented at column 8 #+END_SRC Calling =indent-to= would rather put the two spaces after the tab character. But then we lose this idea of clean separation between the org indentation and the native indentation, and we will need to convert the indent of every line on subsequent edits (org -> elisp), as well as for tangling, or code execution. If we have to do this, we might as well just respect the org buffer =indent-tabs-mode=, and redo every indentation with each conversion. This could possibly be costly when tangling a large buffer. The visual breakage would be much more common than those more serious issues, which had gone unnoticed so far. -- Sébastien Miquel