From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp0 ([2001:41d0:2:bcc0::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms0.migadu.com with LMTPS id UCP8EgG00mCBsgAAgWs5BA (envelope-from ) for ; Wed, 23 Jun 2021 06:09:37 +0200 Received: from aspmx1.migadu.com ([2001:41d0:2:bcc0::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp0 with LMTPS id 8PW1DgG00mA2TAAA1q6Kng (envelope-from ) for ; Wed, 23 Jun 2021 04:09:37 +0000 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 19E86AB06 for ; Wed, 23 Jun 2021 06:09:36 +0200 (CEST) Received: from localhost ([::1]:40274 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1lvuCk-0006kD-7T for larch@yhetil.org; Wed, 23 Jun 2021 00:09:34 -0400 Received: from eggs.gnu.org ([2001:470:142:3::10]:40208) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1lvuC7-0006k5-01 for emacs-orgmode@gnu.org; Wed, 23 Jun 2021 00:08:55 -0400 Received: from relay-egress-host.us-east-2.a.mail.umich.edu ([18.219.209.13]:37762 helo=budding-arianrhow.relay-egress.a.mail.umich.edu) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1lvuC5-0003Qs-0v for emacs-orgmode@gnu.org; Wed, 23 Jun 2021 00:08:54 -0400 Received: from tricky-barghest.authn-relay.a.mail.umich.edu (ip-10-0-72-228.us-east-2.compute.internal [10.0.72.228]) by budding-arianrhow.relay-egress.a.mail.umich.edu with ESMTPS id 60D2B3D3.4C589.67C9BA13.1620871; Wed, 23 Jun 2021 00:08:51 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=umich.edu; s=relay-2018-08-29; t=1624421331; bh=U4CMSFE4xWt1vPP27b94v+CWtRkfhP4sJ65TgncZR0g=; h=From:To:cc:Subject:In-reply-to:Date; b=ilCgikSvyL80xgngbGFr8KfoJbLZXo6FmHFo3BxC67jcS208wI3UXpZ0nFEbY11jz +3KCJS52sYg9w/BjGFmaIC1bWeO/T3ZT4uWqD6PdTm/brds4UM/Vdt9mA7J3CgEt+t XrQMNh/q80P4yw/DTsZOdfazgdZD01s+4kmi8p5UUeFF6AQH1eYXaANbxS//bpG2gV zkNIEkGq7JVRyLZKvU1PxrQYzS7X3KUbdkX1D/N4jI6O31DvIByz8/yJ7yZGyMvhom EKZ0KFvyHSOIvEuX9KhSgrw1ETFfmTdPbS3AUNsXoEJfubrJtvE9XtqIwiO7u2pHB+ GreP1IShjvfwg== Received: from localhost (Mismatch [95.14.94.79]) by tricky-barghest.authn-relay.a.mail.umich.edu with ESMTPSA id 60D2B3D1.CC5C1.799ABEC6.1867170; Wed, 23 Jun 2021 00:08:50 -0400 From: Greg Minshall To: sebastien.miquel@posteo.eu Subject: Re: extra space at the end of lines in source In-reply-to: Your message of "Tue, 22 Jun 2021 21:00:03 +0000." <3a1162f9-1898-ceac-1aec-be17707c5982@posteo.eu> X-Mailer: MH-E 8.6+git; nmh 1.7.1; GNU Emacs 27.2 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Date: Wed, 23 Jun 2021 07:08:45 +0300 Message-ID: <2701993.1624421325@apollo2.minshall.org> Received-SPF: pass client-ip=18.219.209.13; envelope-from=minshall@umich.edu; helo=budding-arianrhow.relay-egress.a.mail.umich.edu X-Spam_score_int: -20 X-Spam_score: -2.1 X-Spam_bar: -- X-Spam_report: (-2.1 / 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_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: emacs-orgmode@gnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: org-mode-email Errors-To: emacs-orgmode-bounces+larch=yhetil.org@gnu.org Sender: "Emacs-orgmode" X-Migadu-Flow: FLOW_IN ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=yhetil.org; s=key1; t=1624421377; h=from:from:sender:sender: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:list-id:list-help:list-unsubscribe: list-subscribe:list-post:dkim-signature; bh=U4CMSFE4xWt1vPP27b94v+CWtRkfhP4sJ65TgncZR0g=; b=fyQFgjLPYUpPd2MaiLFN67JHdb5PrlFeFPpL/z38nPeoZNQpkCGS6jvOfPal+Dup2cXGe8 RuCEodBidOO4+jWrPUgr7rzhUJG68kCh/fEeCeznzMgQtf0/nFf/E1CY/DSHHvhYLSR6ap 9QV2EN1HiJrYr87DslwomFUte5x59U756wqfhk+b9jq8L2LxTxCt/jet9gjtk4H48wd9fi HL53ZwexOKoRMF0YDIDPGq1rtguhXULMXwoC6Gk0BnMYayOH8B0CcTE7zVOf17E9Kr3zOj IS7YcYFy4NQA+5G2qJ1QXS9eADIT2cY6Fhp4jtj0EbGSKpBVFs7RCfl0UAGovQ== ARC-Seal: i=1; s=key1; d=yhetil.org; t=1624421377; a=rsa-sha256; cv=none; b=H8cbsI6d7KdT6FnaF26EK8TiRRi4XJw8+BgiaZzmS4wrF3FAdYqaYG7IyWd5rOjCRFLjOI sB15HnaNVRpyetdl2CkRttxX7E/z8+Y7/W0Iyk22n5sxzLVtsBMSXKsqPjmAtXiYCH7TX6 UyQ64BghaNMckj5QpJBfUSwNuVHUwJuNQFbwdQ0lQ8x02OKKpFzcMB9TrP99rTCXjv1ZFe 6NRpBeZSVdG9B0x+g5RmdM+ONMqiKu6dDSeiCgAeGCuM1uY2q3NnB8pvE1eGK4RfOmZWfY iPECl5Gg7YXSoWXfJQow4pCOXvN5E0UsEWmx2xhXEsY7WR/8YLCu0MHHtnOsgA== ARC-Authentication-Results: i=1; aspmx1.migadu.com; dkim=pass header.d=umich.edu header.s=relay-2018-08-29 header.b=ilCgikSv; dmarc=pass (policy=none) header.from=umich.edu; spf=pass (aspmx1.migadu.com: domain of emacs-orgmode-bounces@gnu.org designates 209.51.188.17 as permitted sender) smtp.mailfrom=emacs-orgmode-bounces@gnu.org X-Migadu-Spam-Score: -1.62 Authentication-Results: aspmx1.migadu.com; dkim=pass header.d=umich.edu header.s=relay-2018-08-29 header.b=ilCgikSv; dmarc=pass (policy=none) header.from=umich.edu; spf=pass (aspmx1.migadu.com: domain of emacs-orgmode-bounces@gnu.org designates 209.51.188.17 as permitted sender) smtp.mailfrom=emacs-orgmode-bounces@gnu.org X-Migadu-Queue-Id: 19E86AB06 X-Spam-Score: -1.62 X-Migadu-Scanner: scn1.migadu.com X-TUID: 95nWZe/opnfu S=C3=A9bastien Miquel, thanks for the reply. > > it's long-term emacs behavior to eliminate spaces > > at the end of lines, at least in programming modes. (Tim -- i guess i should have said, "it's my long-term experience with emacs...".) > As for the `org-src--content-indentation' spaces, they are quite > peculiar. Note that they are removed when you call =3DC-c '=3D and when > you tangle (they should, but I haven't tested it), so strictly > speaking, they are removed in programming modes. What if your org > block itself is indented, do you also expect blank lines to be > entirely empty ? there are two "practical" issues, plus one aesthetic issue, for me: - because of the changes to source blocks i've edited, but not, in fact, tried to change, i'm getting loads of diffs when checking in a new version of the .org file - the next time i open the Org Src buffer, whatever lint-like process is running for that language may complain about extra spaces at the end of a line. (does that mean my experience is different from yours, or at least from your expectation?) - "aesthetically" (or, "conditioned", by years of some expected behavior), i find the thought that there may be lines like these in the file somewhat distressing. i'm resigned to the extra spaces when an org block is indented, so wouldn't find the existence of spaces there any more worrisome. (though, i would expect the spaces to be up to the indentation of the org block, not all the way up to "the programming level".) i do think the default should be to *not* add these spaces. if possible. cheers, Greg