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: Fri, 18 Mar 2022 10:29:30 +0100 Message-ID: <877d8rlhtw.fsf@wavexx.thregr.org> References: <87sfrhu6et.fsf@wavexx.thregr.org> <87h77xpgg6.fsf@yahoo.com> <87wngtf2hb.fsf@wavexx.thregr.org> <83mthpgfao.fsf@gnu.org> <87sfrhklob.fsf@wavexx.thregr.org> <83lex9gc3y.fsf@gnu.org> <87o824lwy7.fsf@wavexx.thregr.org> <83k0cshh43.fsf@gnu.org> <87fsngl0ue.fsf@wavexx.thregr.org> <83ee2zhjai.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="7166"; 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 Fri Mar 18 10:42:00 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 1nV97P-0001fj-Mz for ged-emacs-devel@m.gmane-mx.org; Fri, 18 Mar 2022 10:41:59 +0100 Original-Received: from localhost ([::1]:36818 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1nV97O-0006wb-0d for ged-emacs-devel@m.gmane-mx.org; Fri, 18 Mar 2022 05:41:58 -0400 Original-Received: from eggs.gnu.org ([209.51.188.92]:60346) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1nV95p-0005uX-6Q for emacs-devel@gnu.org; Fri, 18 Mar 2022 05:40:21 -0400 Original-Received: from erc.thregr.org ([46.43.2.63]:52220) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1nV95n-0005We-9R; Fri, 18 Mar 2022 05:40:20 -0400 Original-Received: from [37.163.157.63] (helo=localhost) by erc.thregr.org with esmtpsa (TLS1.3:ECDHE_SECP256R1__RSA_PSS_RSAE_SHA256__AES_256_GCM:256) id 1nV95g-0005dU-8U (envelope-from ); Fri, 18 Mar 2022 10:40:12 +0100 In-reply-to: <83ee2zhjai.fsf@gnu.org> Received-SPF: pass client-ip=46.43.2.63; envelope-from=wavexx@thregr.org; helo=erc.thregr.org X-Spam_score_int: -18 X-Spam_score: -1.9 X-Spam_bar: - X-Spam_report: (-1.9 / 5.0 requ) BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01 autolearn=ham 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:287271 Archived-At: On Fri, Mar 18 2022, Eli Zaretskii wrote: >> First/last column reserved when the "tty fringe" is on. On one hand, >> potentially more wasteful than the overlay-arrow. On the other, it >> would >> be guaranteed to be a single-character only (and any character there >> wouldn't overlap - making it clearly distinct). > > How many hours will pass before someone requests a capability to use > more than just a single column? We already use two with "=>", so > going down to one with something like ">" will probably be considered > a regression by some. > > So I think the current situation is better on balance. I don't expect so. While searching randomly online for bigger fringe bitmaps I've seen several people asking whether it would be possible to put a character in there instead of hardcoding some pixels. It is undoubtedly restrictive when you consider ascii, but unicode expands that space massively. That 2-character arrow can fit in a single glyph and look actually like a double-arrow. That's certainly my reasoning: for most of the bullet/arrow requirements, we would be pretty much set. What I would expect to happen with such a feature on graphical displays instead is the possibility to use an independent family for just one symbol. Because we already have plenty of families designed for iconography, such as fontawesome, but those families are not intended to be interchangeable/generic. They're just repositories of glyphs.