From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp10.migadu.com ([2001:41d0:2:4a6f::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms9.migadu.com with LMTPS id mF+cIAePkmTregAASxT56A (envelope-from ) for ; Wed, 21 Jun 2023 07:47:51 +0200 Received: from aspmx1.migadu.com ([2001:41d0:2:4a6f::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp10.migadu.com with LMTPS id SFPCHwePkmRMVwEAG6o9tA (envelope-from ) for ; Wed, 21 Jun 2023 07:47:51 +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 971EDD8B4 for ; Wed, 21 Jun 2023 07:47:50 +0200 (CEST) Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1qBqg5-0007op-Uv; Wed, 21 Jun 2023 01:46:50 -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 1qBqg3-0007og-KE for emacs-orgmode@gnu.org; Wed, 21 Jun 2023 01:46:47 -0400 Received: from mout01.posteo.de ([185.67.36.65]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1qBqg0-000862-SX for emacs-orgmode@gnu.org; Wed, 21 Jun 2023 01:46:47 -0400 Received: from submission (posteo.de [185.67.36.169]) by mout01.posteo.de (Postfix) with ESMTPS id 4911A240027 for ; Wed, 21 Jun 2023 07:46:41 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=posteo.eu; s=2017; t=1687326401; bh=yTZ4xe75CZUy+wE9oQDi9RnvQ3jBv1D+K8AhITXj6/I=; h=Message-ID:Date:MIME-Version:Reply-To:Subject:To:Cc:From: Content-Transfer-Encoding:From; b=YPol4qFTEcX9Dn09xhuLd+Z5gb/FpDfwUu0M+/MJm5CLF0I5iap7qTx4LbP9BQAxl /xP2tTwD+PqB8kW7hP5DlC2vSa1J9nr1IBU60LXzRjELMW0FSUxDRtYpZLZ8tAv2OF 4yK1djR52Om4t9YCw5zm2B5KSWjgwtSODUtZpThgVFs4OiHe4fmv0FjSZHnIuBRW+0 ZFQYYalYq+oOKT8wvDXlueUIy/aRI/kNzFi1ZfkJ5k36/1DWW+92EEfdhc4+RdsThY DXVmgL/wNPg8Ieg123sJHKb6c99DLW0e6K6hnCixOTgvm05MQLNxQnof0upVuPmZ7s LIB4VPEJltZ7g== Received: from customer (localhost [127.0.0.1]) by submission (posteo.de) with ESMTPSA id 4QmCDc5CNPz6trs; Wed, 21 Jun 2023 07:46:40 +0200 (CEST) Message-ID: Date: Wed, 21 Jun 2023 05:46:41 +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> From: =?UTF-8?Q?S=c3=a9bastien_Miquel?= In-Reply-To: <87sfamsb7m.fsf@localhost> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Received-SPF: pass client-ip=185.67.36.65; envelope-from=sebastien.miquel@posteo.eu; helo=mout01.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-Seal: i=1; s=key1; d=yhetil.org; t=1687326471; a=rsa-sha256; cv=none; b=eCw6JsF/RVG8B0RYd8xGFN/dLZDRo32+WpLx8y7MB5unmmeiEwWn84wMv4Oxl1DPkdG47g zj0rfvrG948mNgsXCE3W64daCxiA0Uot4KlBrsIX4BvgOcqG0KZGCocl6U912KRNOsBqXm unrzF2bVAnO646vkjFFdUDEeLa3+UF/KRY79MKqQdP4K70bqF28o7pfDyTGOzJ+fPs+jsX fRc9aNy3IWGNd/BpxWQooQaoDWuMsG6fHM0qAmexbbCartGsdAnZlwQ2erni2NNBpPIomb z0RunM5k4zB/YmEIv3XzuZAd3+UfFIELVE8BZM9Xbx+EuCYyye2gVHT9JEi7Jw== ARC-Authentication-Results: i=1; aspmx1.migadu.com; dkim=pass header.d=posteo.eu header.s=2017 header.b=YPol4qFT; 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-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=yhetil.org; s=key1; t=1687326471; 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=xTx0LG4EzWvSXdPZsgsPSkF7bEGm+zE4Kv85ARoJas0=; b=Y/TuYcgE3UmLl8b4uGvSlHLVCnb5rcqYUhMBqCSJXtvOR4sJ3lHYuEDskSAMQrBnVDWyFB u0zvn/iRPFfkIO9QdWkzW3PKmlBAN3IcThPf4NNrw9HkfZZiAT6PCNQmwOyNXDTdcKfYI3 s+RzDvulmScTwoi5bJKEi43Ow2j5ZvXCvXx7Pfa7yiJn/sz1sxWhCWkHHYyouUDJndQjvO V0l8zXu/psXFZQh0Tfs1yfp/lQBWWyqJepLc9HYmLksLW4dZJbozKDI1ZXEVkJI0fIR38w J5BjI78ft34cBYixSanj8tYkxrkAIeFJ+cGgic2jl8D7FZszL8C+Q50lg5d9QQ== Authentication-Results: aspmx1.migadu.com; dkim=pass header.d=posteo.eu header.s=2017 header.b=YPol4qFT; 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-Scanner: scn0.migadu.com X-Migadu-Spam-Score: -12.06 X-Spam-Score: -12.06 X-Migadu-Queue-Id: 971EDD8B4 X-TUID: pj1uoSMWi961 Ihor Radchenko writes: >> ...But I guess >> what you propose amounts to >> ... > You are right. I'll try to write a patch, this week-end. >>>> I was not aware of how we treated inline src blocks, but I don't think >>>> so. LaTeX fragments, in particular $$…$$ fragments, can have >>>> significant (for the user) newlines. >>> May you provide an example? >>> AFAIK, LaTeX usually treats newlines as whitespace, same with " ". >> When I say significant, I don't mean for compilation. When editing an >> array of equations for example, one might want to keep one equation >> per line in the buffer. > Then, may latex-fragment-specific logic be moved to > `org-edit-latex-fragment'? It already provides WRITE-BACK in > the `org-src--edit-element' call. We may as well take care about > clearing up indentation of the first line and other things there. Looks like it could, yes : call the WRITE-BACK after indentation. This doesn't seem to conflict for other org elements. -- Sébastien Miquel