From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Heime via "Bug reports for GNU Emacs, the Swiss army knife of text editors" Newsgroups: gmane.emacs.bugs Subject: bug#58804: Inconsistency between ruler-mode, fill-column and whitespace-mode Date: Thu, 27 Oct 2022 06:15:23 +0000 Message-ID: References: <83lep1n7w1.fsf@gnu.org> Reply-To: Heime 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="36587"; mail-complaints-to="usenet@ciao.gmane.io" Cc: 58804@debbugs.gnu.org To: Eli Zaretskii Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Thu Oct 27 08:17:32 2022 Return-path: Envelope-to: geb-bug-gnu-emacs@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 1onwCp-0009Is-8u for geb-bug-gnu-emacs@m.gmane-mx.org; Thu, 27 Oct 2022 08:17:31 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1onwBQ-0002SU-Ag; Thu, 27 Oct 2022 02:16:04 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1onwBO-00027h-Aa for bug-gnu-emacs@gnu.org; Thu, 27 Oct 2022 02:16:02 -0400 Original-Received: from debbugs.gnu.org ([209.51.188.43]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1onwBN-0000HK-Vc for bug-gnu-emacs@gnu.org; Thu, 27 Oct 2022 02:16:02 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1onwBN-00068q-JG for bug-gnu-emacs@gnu.org; Thu, 27 Oct 2022 02:16:01 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Heime Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Thu, 27 Oct 2022 06:16:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 58804 X-GNU-PR-Package: emacs Original-Received: via spool by 58804-submit@debbugs.gnu.org id=B58804.166685134223581 (code B ref 58804); Thu, 27 Oct 2022 06:16:01 +0000 Original-Received: (at 58804) by debbugs.gnu.org; 27 Oct 2022 06:15:42 +0000 Original-Received: from localhost ([127.0.0.1]:55973 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1onwB3-00068F-I9 for submit@debbugs.gnu.org; Thu, 27 Oct 2022 02:15:41 -0400 Original-Received: from mail-40141.protonmail.ch ([185.70.40.141]:21389) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1onwAx-00067z-TO for 58804@debbugs.gnu.org; Thu, 27 Oct 2022 02:15:39 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=protonmail.com; s=protonmail3; t=1666851329; x=1667110529; bh=x2kX2GGzjrh2Z8CosWEK6g8AA71FNHUdZFgIxZLM0Ag=; h=Date:To:From:Cc:Subject:Message-ID:In-Reply-To:References: Feedback-ID:From:To:Cc:Date:Subject:Reply-To:Feedback-ID: Message-ID:BIMI-Selector; b=gvVZOSRBF3nh5NJBpN8hIqFW5WydLKs2pAVDurDxjPVNuEwbikjha4K6/FT6TC+c0 1gWVMuvAJsvVGHi7jnTE5yrXOnOzTymLYNvf2cc+ckc5afB2BAZzV9l6Y5X1mZnF10 auzzPV3XuF1CjNGg4Xjhd+Q+a+R8I56GB15ev5iemxDLP+O1+R8NhFTV6w0FIg/1RU nmy4yWqBPUY584XKquPmdM2Dguumw8rPXJPFbpH6YDE4m6ajmpmPBfs+xqM69CGXrK Hiv4euCsyxORFEB+I+sOwCuxskVjNcNZbeB/fXRckCoFJzEdY78JpRmKBMKFB6EfjW Cw9CGtKKZylhA== In-Reply-To: <83lep1n7w1.fsf@gnu.org> Feedback-ID: 57735886:user:proton X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: "bug-gnu-emacs" Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.bugs:246273 Archived-At: ------- Original Message ------- On Thursday, October 27th, 2022 at 5:38 AM, Eli Zaretskii wr= ote: > > Date: Wed, 26 Oct 2022 20:22:37 +0000 > > From: Heime via "Bug reports for GNU Emacs, > > the Swiss army knife of text editors" bug-gnu-emacs@gnu.org > >=20 > > Having set both fill-column and whitespace-line-column to 72, I noticed= the following. > >=20 > > ruler-mode has the left end marker at column 72 >=20 >=20 > Do you mean "right end marker"? I see no end marker at the left part > of the display here, only the =C2=B6 marker at the right. Right End Marker actually. =20 > > but it should be at column 71 because column numbers start from 0. >=20 >=20 > I don't follow: ruler-mode counts columns starting from zero, as > everything in Emacs. If you move point to a column other than the > leftmost one, you will see "0" at the left edge of the ruler display. > So having the marker at column 72 is exactly right. When one is using a box cursor, it is very confusing. If one has=20 whitespace-style with 'lines-char, the column with the Right Ruler Marker= =20 gets highlighted. When users have a box cursor, it is convenient that the Right Ruler Marker is placed on the last column where it is acceptable to introduce a last character without exceeding line-column. Don't have users always having to remember to add or subtract 1 in their head, but=20 have use visual reference for the last valid column. Perhaps, you could introduce a new marker for that, and decide which one=20 to use? You could have an option to select the starting number, 0 or 1. Or you might have something better in mind that would work well visually. Particularly for those of us using box cursor. > Are you seeing this in "emacs -Q"? >=20 > > Here an improvement would be appreciated. That is, having > > the ability to show a ruler variant that starts from value 1. When one = uses a block cursor, > > the ruler left marker would then mark exactly column 72. The user will = knew that if he inputs > > the next character he would have reached the line limit and the ruler l= eft marker would coincide > > with that position. =20 > It sounds like you want column numbers that start from 1, not zero? > That should be a session-wide mode (if we want such an enhancement), > since otherwise there could be confusion. We currently support > one-based column only in the mode-line display under > column-number-mode. Maybe you have turned that on, which is why you > think there's a mismatch in ruler-mode? Yes, to start from 1, not zero - when one uses a "box cursor". And yes, I have both ruler-mode, whitespace-mode, and column-number-mode, all three enabled. I would appreciate if I could make the necessary customisations for all three to match.