From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: [PATCH] Support "\n" in icomplete-separator Date: Fri, 13 Nov 2020 15:02:46 +0200 Message-ID: <83tuttwgsp.fsf@gnu.org> References: <20201105235735.oxouuek66ehu5o45@Ergus> <20201106151541.dpgep7borlja25su@Ergus> <837dqv5huk.fsf@gnu.org> <83mtzp2qj0.fsf@gnu.org> <83r1p11369.fsf@gnu.org> <834klv26vu.fsf@gnu.org> <835z69y7kc.fsf@gnu.org> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="22261"; mail-complaints-to="usenet@ciao.gmane.io" Cc: spacibba@aol.com, monnier@iro.umontreal.ca, andreyk.mad@gmail.com, emacs-devel@gnu.org To: Gregory Heytings Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Fri Nov 13 14:05:41 2020 Return-path: Envelope-to: ged-emacs-devel@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 1kdYlp-0005c3-0A for ged-emacs-devel@m.gmane-mx.org; Fri, 13 Nov 2020 14:05:41 +0100 Original-Received: from localhost ([::1]:38768 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1kdYlo-0001pl-0V for ged-emacs-devel@m.gmane-mx.org; Fri, 13 Nov 2020 08:05:40 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:45810) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1kdYjL-00009Q-GM for emacs-devel@gnu.org; Fri, 13 Nov 2020 08:03:10 -0500 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:57558) by eggs.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1kdYjK-0005Op-B6; Fri, 13 Nov 2020 08:03:06 -0500 Original-Received: from [176.228.60.248] (port=3273 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1kdYjF-0007TS-Mv; Fri, 13 Nov 2020 08:03:03 -0500 In-Reply-To: (message from Gregory Heytings on Fri, 13 Nov 2020 12:56:12 +0000) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.io gmane.emacs.devel:259133 Archived-At: > Date: Fri, 13 Nov 2020 12:56:12 +0000 > From: Gregory Heytings > cc: Andrii Kolomoiets , spacibba@aol.com, > monnier@iro.umontreal.ca, emacs-devel@gnu.org > > > We can do that, but I don't think it would be TRT, because the current > > strategy does work in many use cases. I thin a better way is to let > > applications control this aspect of the behavior, because we will never > > be able to find a solution that always works, what with all the > > different settings and kinds of display in the mini-window. > > I fully agree with you. And the question is again: given that the > solution I offered doesn't please you, how should that be done? As mentioned in the original discussion: with a special text property or overlay property on the first character of the text to be shown in the mini-window. The display engine will see that and heed it.