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: Bigger fringe bitmaps Date: Thu, 17 Mar 2022 14:57:00 +0200 Message-ID: <83k0cshh43.fsf@gnu.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> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="40847"; mail-complaints-to="usenet@ciao.gmane.io" Cc: emacs-devel@gnu.org To: Yuri D'Elia Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Thu Mar 17 14:00:02 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 1nUpjW-000AUO-4y for ged-emacs-devel@m.gmane-mx.org; Thu, 17 Mar 2022 14:00:02 +0100 Original-Received: from localhost ([::1]:51260 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1nUpjV-0006Zm-3d for ged-emacs-devel@m.gmane-mx.org; Thu, 17 Mar 2022 09:00:01 -0400 Original-Received: from eggs.gnu.org ([209.51.188.92]:41214) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1nUpgh-0003Z4-3S for emacs-devel@gnu.org; Thu, 17 Mar 2022 08:57:07 -0400 Original-Received: from [2001:470:142:3::e] (port=55094 helo=fencepost.gnu.org) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1nUpgg-0002VZ-9I; Thu, 17 Mar 2022 08:57:06 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=References:Subject:In-Reply-To:To:From:Date: mime-version; bh=+Cnmjifm6/Mr23T8RzNgxKWxt8btRiX3J62UGJ3dU9s=; b=hMf5lDb8Bb6j fILF5tu1GapUxW2Ev/df7VIACJxWfy+hcMeyR+8lRju6HF6M7O3ZbhL+kkW4cbV4y8Tm2/Fi0TRvs ocC0R9J3xUtFm9namYOmBBQLG8NH2biH5IoNc/D3qtmdQcFv28orkjCLDjXHcxp2bxzuOT5FUM3a1 fl1BiPL7ODYEEQMmTGOCP3yy3VReXIUMsgeO4XLbSlRX9WuTB3koKKIUvCgCAefpL1t2H2j3CMArP uph4eoAj0qDTSKgzM36oPEK0tBH/UP1NyInVcQMpvTNcLPtkShd474SiTQn7MQSb35zsp551mH4TL 4CDkZD2TzO89Ttdi0lxkHg==; Original-Received: from [87.69.77.57] (port=3417 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1nUpgf-0005Bq-KK; Thu, 17 Mar 2022 08:57:05 -0400 In-Reply-To: <87o824lwy7.fsf@wavexx.thregr.org> (message from Yuri D'Elia on Thu, 17 Mar 2022 10:44:54 +0100) 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:287256 Archived-At: > From: Yuri D'Elia > Cc: emacs-devel@gnu.org > Date: Thu, 17 Mar 2022 10:44:54 +0100 > > > Emacs doesn't know how to scale a font at display time. The font is > > "scaled" (or, rather, selected) when the face using the font is > > defined. So dynamically changing the font of a face when the user > > plays with fringe-style would be another complication that needs to be > > taken care of. > > Mhh, I'm not sure if we added some sort of connection between the fringe > sizes and fringe face, which one would prevail? Setting the fringe size > (which right now is just a fixed pixel size) could implicitly set the > fringe face size being used, and/or vice-versa. I didn't say it's impossible, I said it needed to be taken care of. Changing a face means recomputing all the faces on the frame as well, and currently setting a fringe style does nothing of the kind. > > How is this different from what overlay-arrow already does? It is > > even more flexible, as it is not limited to a single column. > <...> > > In what way does it not behave the same? > > I agree it's more powerful, but the overlay-arrow shares the same space > with the buffer, so it can hide existing information. I like the fact > that the fringe is a minimal, non-shared, space. How would you go about not sharing the screen space with the buffer, when the display is a TTY? What else is there that we could use instead? > The node does say: > > On a graphical display the contents of the string are ignored; instead > a glyph is displayed in the fringe area to the left of the display area. > > Maybe it should be: > > On a graphical display, or when the left fringe is disabled, the > contents of the string are ignored; instead a glyph is displayed in the > fringe area to the left of the display area. You mean, when left fringe is enabled, right? I made the text there more accurate, thanks.