GNU bug report logs - #39427
26.3; whitespace-mode doesn't track fill-column changes

Previous Next

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 39427 in the body.
You can then email your comments to 39427 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Trey Harris <treyharris <at> gmail.com>
To: bug-gnu-emacs <at> gnu.org
Subject: 26.3; whitespace-mode doesn't track fill-column changes
Date: Tue, 04 Feb 2020 15:50:15 -0500

1. In *scratch*, toggle whitespace-mode (M-x whitespace-mode RET)

2. Do (C-u 65 x) to get 65 characters, then continue typing into the
line. When you reach 70 (or the value of fill-column), the line will
change face to the long line variant.

3. Do set-fill-column (C-x f) and accept the current value matching 
point's current column. Then type "some more".

**Expected behavior:** the long-line face variant should go away when you
increase fill-column, until you begin typing "some-more".

**Actual behaviOor:** the face does not change.

4. Toggle whitespace-mode off and back on (M-x whitespace-mode RET M-xx
whitespace-mode RET)u

5. Delete "some-more" and press DEL again to get the line under a width
of fill-column. Note that the face changes, as a toggle of
whitespace-mode caused it to re-read fill-column's value.

When whitespace-mode is enabled and whitespace-line-column is set to nil
(meaning track fill-column,) it should track changes to fill-column.

But in fact, whitespace-mode doesn't even track changes to
whitespace-line-column; if you set it to, say, 200 at step 3 above, the
line does not re-face without toggling whitespace-mode, either.
---

In GNU Emacs 26.3 (build 2, x86_64-pc-linux-gnu, GTK+ Version 3.22.30)
 of 2019-09-16 built on lcy01-amd64-030
System Description:	Ubuntu 18.04.3 LTS

Recent messages:
No MH variant found on the system
Creating group...
Creating group entries...done
Creating customization items ...done
Resetting customization items...done
Creating customization setup...done
Mark saved where search started
Quit
Saving file /home/trey/.emacs.d/custom.el...
Wrote /home/trey/.emacs.d/custom.el [2 times]

Configured using:
 'configure --build=x86_64-linux-gnu --prefix=/usr
 '--includedir=${prefix}/include' '--mandir=${prefix}/share/man'
 '--infodir=${prefix}/share/info' --sysconfdir=/etc --localstatedir=/var
 --disable-silent-rules '--libdir=${prefix}/lib/x86_64-linux-gnu'
 '--libexecdir=${prefix}/lib/x86_64-linux-gnu' --disable-maintainer-mode
 --disable-dependency-tracking --prefix=/usr --sharedstatedir=/var/lib
 --program-suffix=26 --with-modules --with-file-notification=inotify
 --with-mailutils --with-x=yes --with-x-toolkit=gtk3 --with-xwidgets
 --with-lcms2 'CFLAGS=-g -O2
 -fdebug-prefix-map=/build/emacs26-TP6iDo/emacs26-26.3~1.git96dd019=. -fstack-protector-strong
 -Wformat -Werror=format-security -no-pie' 'CPPFLAGS=-Wdate-time
 -D_FORTIFY_SOURCE=2' 'LDFLAGS=-Wl,-Bsymbolic-functions -Wl,-z,relro
 -no-pie''

Configured features:
XPM JPEG TIFF GIF PNG RSVG IMAGEMAGICK SOUND GPM DBUS GSETTINGS GLIB
NOTIFY LIBSELINUX GNUTLS LIBXML2 FREETYPE M17N_FLT LIBOTF XFT ZLIB
TOOLKIT_SCROLL_BARS GTK3 X11 XDBE XIM MODULES THREADS XWIDGETS
LIBSYSTEMD LCMS2

Important settings:
  value of $LC_COLLATE: POSIX
  value of $LANG: en_US.UTF-8
  locale-coding-system: utf-8-unix

Major mode: Lisp Interaction

Minor modes in effect:
  global-magit-file-mode: t
  direnv-mode: t
  savehist-mode: t
  csv-field-index-mode: t
  paredit-mode: t
  rainbow-delimiters-mode: t
  elmacro-mode: t
  ws-butler-global-mode: t
  ws-butler-mode: t
  pcre-mode: t
  helm-mode: t
  helm--remap-mouse-mode: t
  yas-global-mode: t
  yas-minor-mode: t
  desktop-save-mode: t
  xterm-mouse-mode: t
  show-paren-mode: t
  recentf-mode: t
  rcirc-track-minor-mode: t
  other-frame-window-mode: t
  magit-wip-initial-backup-mode: t
  magit-wip-before-change-mode: t
  magit-wip-after-apply-mode: t
  magit-wip-after-save-mode: t
  magit-wip-mode: t
  diff-auto-refine-mode: t
  global-git-commit-mode: t
  magit-auto-revert-mode: t
  async-bytecomp-package-mode: t
  shell-dirtrack-mode: t
  electric-pair-mode: t
  display-time-mode: t
  override-global-mode: t
  cl-old-struct-compat-mode: t
  tooltip-mode: t
  global-eldoc-mode: t
  eldoc-mode: t
  electric-indent-mode: t
  mouse-wheel-mode: t
  menu-bar-mode: t
  file-name-shadow-mode: t
  global-font-lock-mode: t
  font-lock-mode: t
  auto-composition-mode: t
  auto-encryption-mode: t
  auto-compression-mode: t
  size-indication-mode: t
  column-number-mode: t
  line-number-mode: t
  transient-mark-mode: t

Load-path shadows:
[snip]

Features:
[snip]

Memory information:
((conses 16 6740696 666979)
 (symbols 48 101039 1)
 (miscs 40 16055 9728)
 (strings 32 773826 62430)
 (string-bytes 1 44503375)
 (vectors 16 183288)
 (vector-slots 8 4279365 137664)
 (floats 8 843 2525)
 (intervals 56 663386 40618)
 (buffers 992 466))

Message #10 received at 39427 <at> debbugs.gnu.org (full text, mbox):

From: Štěpán Němec <stepnem <at> gmail.com>
To: Eli Zaretskii <eliz <at> gnu.org>, Noam Postavsky <npostavs <at> gmail.com>
Cc: tastytea <at> tastytea.de, 39427 <at> debbugs.gnu.org, 36837 <at> debbugs.gnu.org
Subject: Re: bug#36837: 26.2; whitespace-mode: whitespace-line-column is not
 set to local fill-column
Date: Fri, 28 Feb 2020 09:14:11 +0100

On Fri, 28 Feb 2020 07:01:18 +0200
Eli Zaretskii wrote:

>> From: Noam Postavsky <npostavs <at> gmail.com>

>> I've been somewhat out of things as well, but I believe emacs-27 is
>> still open for bug fixes.  And I would classify this as a bug fix, so no
>> NEWS needed.
>
> I won't argue if this is a bug fix or not, but why is it urgent to
> have this in Emacs 27?

I find that question hard to address (isn't the "bug fix or not", and of
course _your_ and other maintainers' personal definition of "bug fix"
and "urgent" precisely the crucial factors for answering it?).

Personally I don't see any reason not to consider behaviours observed in
both bug reports bugs, but "urgent" certainly sounds more dramatic than
I feel about it. IOW, I don't feel strongly about having to have this in
27, especially in case of any doubts on maintainers' part.

-- 
Štěpán

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.