From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Yuri D'Elia Newsgroups: gmane.emacs.devel Subject: Re: Bigger fringe bitmaps Date: Thu, 17 Mar 2022 09:34:08 +0100 Message-ID: <87sfrhklob.fsf@wavexx.thregr.org> References: <87sfrhu6et.fsf@wavexx.thregr.org> <87h77xpgg6.fsf@yahoo.com> <87wngtf2hb.fsf@wavexx.thregr.org> <83mthpgfao.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="19735"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: mu4e 1.7.9; emacs 29.0.50 Cc: emacs-devel@gnu.org To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Thu Mar 17 09:51:15 2022 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 1nUlqk-0004wt-Lt for ged-emacs-devel@m.gmane-mx.org; Thu, 17 Mar 2022 09:51:14 +0100 Original-Received: from localhost ([::1]:43284 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1nUlqj-0007Kz-7b for ged-emacs-devel@m.gmane-mx.org; Thu, 17 Mar 2022 04:51:13 -0400 Original-Received: from eggs.gnu.org ([209.51.188.92]:60362) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1nUlpr-0006fP-RW for emacs-devel@gnu.org; Thu, 17 Mar 2022 04:50:19 -0400 Original-Received: from [2001:41c9:1:41f::63] (port=59470 helo=erc.thregr.org) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1nUlpp-00018s-RP; Thu, 17 Mar 2022 04:50:19 -0400 Original-Received: from [37.160.141.214] (helo=localhost) by erc.thregr.org with esmtpsa (TLS1.3:ECDHE_SECP256R1__RSA_PSS_RSAE_SHA256__AES_256_GCM:256) id 1nUlpi-000Wlv-Kd (envelope-from ); Thu, 17 Mar 2022 09:50:10 +0100 In-reply-to: <83mthpgfao.fsf@gnu.org> X-Host-Lookup-Failed: Reverse DNS lookup failed for 2001:41c9:1:41f::63 (failed) Received-SPF: pass client-ip=2001:41c9:1:41f::63; envelope-from=wavexx@thregr.org; helo=erc.thregr.org X-Spam_score_int: -10 X-Spam_score: -1.1 X-Spam_bar: - X-Spam_report: (-1.1 / 5.0 requ) BAYES_00=-1.9, RDNS_NONE=0.793, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01 autolearn=no autolearn_force=no X-Spam_action: no action X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.29 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:287251 Archived-At: On Thu, Mar 17 2022, Eli Zaretskii wrote: > I did comment on that. To repeat: it could be a useful new feature, > but I don't think it should be _the_ solution for showing stuff on the > fringes on hidpi terminals; we should be able to produce legible > display of the bitmaps on those terminals. Seen it, I was just prompting for more feedback on the idea and discuss if this could be a good and/or bad idea. >> I like the idea of using =F0=9F=A2=B1 (or =E2=A4=B6=E2=A4=B7) for wrappe= d text, =F0=9F=AE=97 as a >> end-of-buffer, and so on. Easily scaled, and nicely antialiased. > > You disregard the issue of which fonts support what characters in the > relevant Unicode blocks. Definitely. > Solving this in the limited fringe screen estate will need some > non-trivial ideas. And what about 'half-width' or 'minimal' > fringe-styles? I mentally imagine this as just scaling the font smaller to fit the fringe width, centering each character vertically. >> Especially the fact that this would potentially mean an usable fringe >> mode on character displays that can be toggled, so that you don't need >> to provide an alternate signaling mechanism if you rely on the fringe to >> show makers (like gud). > > I don't think I follow. Emacs doesn't support fringes on TTY > displays, so what do you mean by "usable fringe mode on character > displays"? That would be part of the advantage of allowing a character to be used in lieu of a bitmap (either as a feature or as a fallback). On a TTY we could just reserve the first/last column for the "fringe" and display the lowest-common-denominator format available. > This is already supported, see overlay-arrow-string. Or do you mean > something else? Yes, but it doesn't behave exactly in the same way as the fringe does. (and I also as I just discovered, if I disable the fringe on a graphical display I do not get the overlay arrows as a fallback -- or did I miss some variable to control this behavior?)