From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: Fill column indicator functionality Date: Fri, 15 Mar 2019 17:43:22 +0200 Message-ID: <83sgvoywh1.fsf@gnu.org> References: <20190309132207.w2ho3j6p5on6fyzw@Ergus> <838sxo87gc.fsf@gnu.org> <20190311104814.kp2nv6arv47hcykz@Ergus> <83y35l4ee0.fsf@gnu.org> <20190312152928.73o4b5fk4paz7wm5@Ergus> <834l883w15.fsf@gnu.org> <20190312192017.fkfd4h5gsbdue5q3@Ergus> <83imwm3fxf.fsf@gnu.org> <20190313200225.dpqrw7xthkj47fqw@Ergus> <83bm2e35a1.fsf@gnu.org> <20190314030224.l5zseslncw3xc5ox@Ergus> <835zsm2c2s.fsf@gnu.org> <303612d8-e691-f753-84c9-f462d88262b6@gmail.com> <83d0ms1to4.fsf@gnu.org> <83zhpwz1i6.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Injection-Info: blaine.gmane.org; posting-host="blaine.gmane.org:195.159.176.226"; logging-data="122446"; mail-complaints-to="usenet@blaine.gmane.org" Cc: emacs-devel@gnu.org To: Alp Aker Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri Mar 15 16:46:08 2019 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([209.51.188.17]) by blaine.gmane.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1h4p23-000VcM-1L for ged-emacs-devel@m.gmane.org; Fri, 15 Mar 2019 16:46:03 +0100 Original-Received: from localhost ([127.0.0.1]:57592 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1h4p21-000387-HL for ged-emacs-devel@m.gmane.org; Fri, 15 Mar 2019 11:46:01 -0400 Original-Received: from eggs.gnu.org ([209.51.188.92]:34075) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1h4ozo-0001xo-IV for emacs-devel@gnu.org; Fri, 15 Mar 2019 11:43:45 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:42660) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1h4ozo-0001ai-Bp; Fri, 15 Mar 2019 11:43:44 -0400 Original-Received: from [176.228.60.248] (port=2787 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1h4ozn-0000ui-9I; Fri, 15 Mar 2019 11:43:43 -0400 In-reply-to: (message from Alp Aker on Fri, 15 Mar 2019 10:19:04 -0400) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.21 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.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.org gmane.emacs.devel:234171 Archived-At: > Cc: emacs-devel@gnu.org > From: Alp Aker > Date: Fri, 15 Mar 2019 10:19:04 -0400 > > I did not have a dynamically sized images in mind, only fixed-height > images.  They offer a way of achieving the graphical effect that some > people in this thread have requested that would involve, as you point > out, only a trivial extension of what Ergus has already done. Right. > Would lack of support for variable line heights be an issue? I hope not, at least not initially. But Clément seems to think otherwise. > I can only offer my experience here as the author of > fill-column-indicator.  Among the many issues that package has, lack > of support for variable line heights in a window hasn't been one of > them.  It just isn't something users have requested. This is Emacs: as soon as you offer a feature that solves N problems users always wanted solved, someone will come up and argue that solution for the N+1th problem is an absolute must to have ;-) > A choice between image and character was what I had in mind.  (If a > buffer is displayed on both GUI and TTY frames, you can even use both at > the same time, which is what fci-mode does.) > > I wouldn't expect end users to create their own images.  Again, I can > only offer my own experience, but the only customization requests I've > received have been for (a) color, (b) thickness, and (c) dashed vs. > solid.  Those can be offered as simple customization options.  Arbitrary > user defined images are possible on this scheme, but wouldn't be the > basic mode of customization. Sounds like we are in violent agreement, then. Thanks for your comments, the experience of fci-mode is, of course, something we should learn from when we design the customization facilities of this new implementation.