From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Ihor Radchenko Newsgroups: gmane.emacs.bugs Subject: bug#64696: 30.0.50; indent-to inherits preceding text properties, including 'invisible Date: Mon, 24 Jul 2023 08:18:54 +0000 Message-ID: <87edkx3eoh.fsf@localhost> References: <87fs5l3b3g.fsf@localhost> <83ilah79aq.fsf@gnu.org> <87jzux2zg8.fsf@localhost> <83351l74ci.fsf@gnu.org> <87a5vt2vx8.fsf@localhost> <831qh56vvz.fsf@gnu.org> <871qh52nlw.fsf@localhost> <83pm4p5er8.fsf@gnu.org> <874jm0mhgb.fsf@localhost> <831qh459sy.fsf@gnu.org> <87jzuvq785.fsf@localhost> <835y6ca1ah.fsf@gnu.org> <87zg3o8m2a.fsf@localhost> <83wmys8a2g.fsf@gnu.org> <87v8ecrqib.fsf@localhost> <83bkg481g5.fsf@gnu.org> <87bkg3rso5.fsf@localhost> <83wmyrt02d.fsf@gnu.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="29373"; mail-complaints-to="usenet@ciao.gmane.io" Cc: monnier@iro.umontreal.ca, 64696@debbugs.gnu.org To: Eli Zaretskii Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Mon Jul 24 10:19:34 2023 Return-path: Envelope-to: geb-bug-gnu-emacs@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 1qNqn0-0007Sc-49 for geb-bug-gnu-emacs@m.gmane-mx.org; Mon, 24 Jul 2023 10:19:34 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1qNqmZ-0000uB-2i; Mon, 24 Jul 2023 04:19:08 -0400 Original-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 1qNqmV-0000tK-8E for bug-gnu-emacs@gnu.org; Mon, 24 Jul 2023 04:19:04 -0400 Original-Received: from debbugs.gnu.org ([2001:470:142:5::43]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1qNqmU-0000kJ-Ox for bug-gnu-emacs@gnu.org; Mon, 24 Jul 2023 04:19:03 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1qNqmU-0008Sv-E9 for bug-gnu-emacs@gnu.org; Mon, 24 Jul 2023 04:19:02 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Ihor Radchenko Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Mon, 24 Jul 2023 08:19:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 64696 X-GNU-PR-Package: emacs Original-Received: via spool by 64696-submit@debbugs.gnu.org id=B64696.169018673932533 (code B ref 64696); Mon, 24 Jul 2023 08:19:02 +0000 Original-Received: (at 64696) by debbugs.gnu.org; 24 Jul 2023 08:18:59 +0000 Original-Received: from localhost ([127.0.0.1]:41709 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1qNqmR-0008Sf-BP for submit@debbugs.gnu.org; Mon, 24 Jul 2023 04:18:59 -0400 Original-Received: from mout01.posteo.de ([185.67.36.65]:50329) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1qNqmN-0008SN-PC for 64696@debbugs.gnu.org; Mon, 24 Jul 2023 04:18:58 -0400 Original-Received: from submission (posteo.de [185.67.36.169]) by mout01.posteo.de (Postfix) with ESMTPS id 93757240028 for <64696@debbugs.gnu.org>; Mon, 24 Jul 2023 10:18:49 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=posteo.net; s=2017; t=1690186729; bh=wCP3EfjV0iXEOj+b8QQhPJpTB78bULm2aSN8XfqJXBw=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version:From; b=ANwFpH9e23u8KUPOfNMkHNjxI+NzqbTXzmE1U6uBNSoE1w/mG87wG9/Mu1wBQs58t 5rgC2alBkUCgukWEbNIEPBf8PNy8pl+yTGb4hzIyyZlZmhLAuJ//uOhMbHxKrNc1OI bF3M1FERvZa1gkiswbimRE1CQIvPjoiXLGwYA0dB0eh6FBL8o7aEbS5X6T+h5h1agQ texhR6YTTiEvZwx3DGqAYp/Sds5W3O49hYr4f73kJULIvuDVVnsDFY1rOD+hmM4eJb t4toaO848lXsXMAUkyuQdYxikrKtlhNUcLhZtnX+gUfbNg/wRhguZRbGzEsuuZoJ47 uFayeixBNJbqA== Original-Received: from customer (localhost [127.0.0.1]) by submission (posteo.de) with ESMTPSA id 4R8Y2w3cjpz9ryt; Mon, 24 Jul 2023 10:18:48 +0200 (CEST) In-Reply-To: <83wmyrt02d.fsf@gnu.org> X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Original-Sender: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.bugs:265939 Archived-At: Eli Zaretskii writes: >> 1. Org mode is generally aiming for the produced Org files to be >> readable as unfontified plain text. So, quirks related to visual >> indentation generally tend to mess things up. > > "Unfontified"? AFAIK, Org files do use fontifications, don't they? > So what do you mean by "unfontified plain text" here? But that's an > aside, feel free to ignore. For example, consider an Org table like | *This* | is | some text | | more | | text | It looks aligned in Org buffers ("*" is invisible), but not when copied to message buffer. >> 2. Org mode uses indentation as part of the syntax. I had to get rid of >> using `current-column' and calculated "true textual indentation" >> manually to avoid breakage after `current-column' started to take >> into account invisibility. (bug#56837) > > This cannot be avoided. Emacs provides by default many features that > "mess up" this kind of "true textual indentation". Some of these > features include: > ... > (I'm probably missing some more.) Only the Lisp program knows which > of those are relevant to the particular application at hand. Sure, but how can an application, say, disable all the effects of visual representation without (1) searching and let-binding each specific toggle (and possibly adding more in future versions of Emacs); (2) re-implementing the existing indentation code (like what `org-current-text-column' does)? > We could introduce separate indentation/current-column knobs for each > of the above features, but it would make little sense to me, since > most, if not all, of them already have such knobs. For example, > character composition can be disabled by flipping a variable. It would help to list what contributes to indentation/columns in the documentation. > See above: you are actually opening a Pandora box, and any solution > will likely be based on existing variables. So I think we already > have what you want, it just might not be immediately obvious in each > case which of the knobs to use. The default behavior of > current-column can already be affected by disabling > auto-composition-mode, by tweaking the buffer's invisibility spec, and > by defining display properties whose values are conditional. Tab > expansion can also be controlled. What else would make sense? A toggle: disable all visual contributors. -- Ihor Radchenko // yantar92, Org mode contributor, Learn more about Org mode at . Support Org development at , or support my work at