From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Abdul-Lateef Haji-Ali Newsgroups: gmane.emacs.bugs Subject: bug#59141: 28.1.90; Face :extend when all the line but trailing \n is invisible Date: Fri, 11 Nov 2022 19:47:45 +0000 Message-ID: References: <871qqcdfvr.fsf@localhost> <83h6z5psqe.fsf@gnu.org> <83bkpdpf92.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="33627"; mail-complaints-to="usenet@ciao.gmane.io" Cc: 59141@debbugs.gnu.org, yantar92@posteo.net, juri@linkov.net, kevin.legouguec@gmail.com To: Eli Zaretskii Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Fri Nov 11 20:51:18 2022 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 1ota3Z-0008Xc-UO for geb-bug-gnu-emacs@m.gmane-mx.org; Fri, 11 Nov 2022 20:51:17 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1ota3L-0006sS-JK; Fri, 11 Nov 2022 14:51:03 -0500 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 1ota3K-0006sJ-BW for bug-gnu-emacs@gnu.org; Fri, 11 Nov 2022 14:51:02 -0500 Original-Received: from debbugs.gnu.org ([209.51.188.43]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1ota3K-00087X-3p for bug-gnu-emacs@gnu.org; Fri, 11 Nov 2022 14:51:02 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1ota3J-0000D5-WA for bug-gnu-emacs@gnu.org; Fri, 11 Nov 2022 14:51:02 -0500 X-Loop: help-debbugs@gnu.org Resent-From: Abdul-Lateef Haji-Ali Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Fri, 11 Nov 2022 19:51:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 59141 X-GNU-PR-Package: emacs Original-Received: via spool by 59141-submit@debbugs.gnu.org id=B59141.1668196212738 (code B ref 59141); Fri, 11 Nov 2022 19:51:01 +0000 Original-Received: (at 59141) by debbugs.gnu.org; 11 Nov 2022 19:50:12 +0000 Original-Received: from localhost ([127.0.0.1]:46793 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1ota2V-0000Bo-OZ for submit@debbugs.gnu.org; Fri, 11 Nov 2022 14:50:12 -0500 Original-Received: from mail-wm1-f51.google.com ([209.85.128.51]:50943) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1ota2U-0000Bb-JJ for 59141@debbugs.gnu.org; Fri, 11 Nov 2022 14:50:11 -0500 Original-Received: by mail-wm1-f51.google.com with SMTP id v7so3500795wmn.0 for <59141@debbugs.gnu.org>; Fri, 11 Nov 2022 11:50:10 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:message-id:date:references:in-reply-to:subject:cc:to :from:from:to:cc:subject:date:message-id:reply-to; bh=yFsTJTaIjjVszuwlOAwAH5Fe0q/1KchJbyJUPF9D5JE=; b=DImsVqS8BD/yYUNrslKPV8+DBZ63PvsAGqLn1StszZRRGKJD+tlLWnJfCOl3O5reVs TQ0M8p3UxcVlaYXMOzGWLlE976Pbeieezj3NZc81xxGFynOFf/J1KkNF2LU0UoiJj2uR mp5yO+Fj9VtjBXcNmcDxxkkjllg3namCHTRjkRmLx/DwRfYOVjHvcXqVWj2x/BcGONEx EvoAQvP8LpJM6KSonRq3abIZwWhhKzQQOnoUu09ePi0E7ad2ZTt51x93bcIMj4Occqw9 MIzEzPa70ctrw7yqbx/wNNaMJ6a5W/3dO2Qw5CNrguzIAOmQlbtQpfnjfJF5Rh+swpws ODEw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=mime-version:message-id:date:references:in-reply-to:subject:cc:to :from:x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=yFsTJTaIjjVszuwlOAwAH5Fe0q/1KchJbyJUPF9D5JE=; b=sUFzhSgatpGnf0TavD4GXO0xpanNtVLO0IYOei2k8mvZYlhq4oYqlpGG2ZAdrmMltS apKJfxR+QQyiyNmOee138zC5MDA0MOTWArojvVZUlg5vruJbyinAm73qIDB/ukfokfAX Lh+l5qd1mS1ylFelS9yC3yJLa0/GcE2Cb/zdWOpYrIdeLiCjKh1YJAstxwtWJ1RaIiBi rxOQioCX3nAms0Gd/KlTwwZtsJOFq5YiJccGyDhS5I4oPnKEa6rZpZGYjqFjvOLreFnK BW5THfw2U1EUw/UDyW+dTOuz31fNw9qOeyc2NM9lTTcW4V7s4JVSGiAy2IbCuUzVlsyM HJIA== X-Gm-Message-State: ANoB5pl9arqto3w1bu7mM6bHjicDSAiTI4DkzEVcuviSeJL/CQS7S6vB rdIkYnYanNAJ+CmmZypCLP8= X-Google-Smtp-Source: AA0mqf5EbEemKS/D0PZQTsAnmtG6DdkrhOGuZ+77LoGnihRJPAh0G96bd8laCESC+7t2OzMkbCg1dg== X-Received: by 2002:a05:600c:1d1e:b0:3cd:3422:62f3 with SMTP id l30-20020a05600c1d1e00b003cd342262f3mr2325680wms.26.1668196204463; Fri, 11 Nov 2022 11:50:04 -0800 (PST) Original-Received: from localhost (sgyl-45-b2-v4wan-165314-cust948.vm6.cable.virginm.net. [92.236.87.181]) by smtp.gmail.com with ESMTPSA id co19-20020a0560000a1300b0022e66749437sm2684655wrb.93.2022.11.11.11.50.03 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Fri, 11 Nov 2022 11:50:04 -0800 (PST) In-Reply-To: <83bkpdpf92.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:247615 Archived-At: On 11/11/2022, Eli Zaretskii wrote: > I don't think I understand the question. What do you mean by "overlay > rendering"? An overlay can produce text only if it has a > before-string or after-string property, so what do you mean by > "arbitrary text"? I might be using the wrong terms here, but I think the idea is straightforward. According to `buffer-invisibility-spec` docs ,---- | If the (ATOM . ELLIPSIS) form is used, and ELLIPSIS is non-nil, an | ellipsis will be displayed after the invisible characters. `---- so I am wondering if a new form like `(ATOM . STRING)` can be supported so that STRING can be displayed after the invisible characters instead of ellipses. >> More to the point, what do people think about the making the extent of an outline of an entry include a new line? Is that more or less logical than the current behaviour? > > How would that help? The display engine is blissfully unaware of Org > headings and entries, it just sees text in a buffer. The question was indeed directed to org users rather than to display engine developers. The suggested solution is have an outline entry include the new line character (so that the whole extended lines is hidden). The displayed text after the invisible text would then be "...\n". The final output is behaviour to the current one except for two things: 1. The entry would contain "\n'", logically speaking. 2. The extended line would be hidden as part of the entry. I hope this clarifies my point.