From 72fc7258bf328b48bb032f607778ce81316276d4 Mon Sep 17 00:00:00 2001 From: Stefan Kangas Date: Fri, 12 Aug 2022 17:48:30 +0200 Subject: [PATCH] Delete references to deleted library hilit19.el * doc/misc/gnus.texi (Compatibility): * lisp/progmodes/f90.el: * lisp/ps-print.el: * lisp/vc/ediff.el: Delete references to hilit19.el. --- doc/misc/gnus.texi | 10 ---------- lisp/progmodes/f90.el | 7 +++---- lisp/ps-print.el | 10 +++++----- lisp/vc/ediff.el | 11 +++++------ 4 files changed, 13 insertions(+), 25 deletions(-) diff --git a/doc/misc/gnus.texi b/doc/misc/gnus.texi index d608f3113fd..9f7403ae8f5 100644 --- a/doc/misc/gnus.texi +++ b/doc/misc/gnus.texi @@ -27021,16 +27021,6 @@ maintains a hash table that points to the entries in this alist (which speeds up many functions), and changing the alist directly will lead to peculiar results. -@cindex hilit19 -@cindex highlighting -Old hilit19 code does not work at all. In fact, you should probably -remove all hilit code from all Gnus hooks -(@code{gnus-group-prepare-hook} and @code{gnus-summary-prepare-hook}). -Gnus provides various integrated functions for highlighting. These are -faster and more accurate. To make life easier for everybody, Gnus will -by default remove all hilit calls from all hilit hooks. Uncleanliness! -Away! - Packages like @code{expire-kill} will no longer work. As a matter of fact, you should probably remove all old @sc{gnus} packages (and other code) when you start using Gnus. More likely than not, Gnus already diff --git a/lisp/progmodes/f90.el b/lisp/progmodes/f90.el index 526865e6f61..197ec7f2e26 100644 --- a/lisp/progmodes/f90.el +++ b/lisp/progmodes/f90.el @@ -116,12 +116,11 @@ ;; non-nil, the line numbers are never touched. ;; 2) Multi-; statements like "do i=1,20 ; j=j+i ; end do" are not handled ;; correctly, but I imagine them to be rare. -;; 3) Regexps for hilit19 are no longer supported. -;; 4) For FIXED FORMAT code, use fortran mode. -;; 5) Preprocessor directives, i.e., lines starting with # are left-justified +;; 3) For FIXED FORMAT code, use fortran mode. +;; 4) Preprocessor directives, i.e., lines starting with # are left-justified ;; and are untouched by all case-changing commands. There is, at present, no ;; mechanism for treating multi-line directives (continued by \ ). -;; 6) f77 do-loops do 10 i=.. ; ; 10 continue are not correctly indented. +;; 5) f77 do-loops do 10 i=.. ; ; 10 continue are not correctly indented. ;; You are urged to use f90-do loops (with labels if you wish). ;; List of user commands diff --git a/lisp/ps-print.el b/lisp/ps-print.el index af366066f71..58b701e22cd 100644 --- a/lisp/ps-print.el +++ b/lisp/ps-print.el @@ -1320,11 +1320,11 @@ Please send all bug fixes and enhancements to ;; Known bugs and limitations of ps-print ;; -------------------------------------- ;; -;; Automatic font-attribute detection doesn't work well, especially with -;; hilit19 and older versions of get-create-face. Users having problems with -;; auto-font detection should use the lists `ps-italic-faces', `ps-bold-faces' -;; and `ps-underlined-faces' and/or turn off automatic detection by setting -;; `ps-auto-font-detect' to nil. +;; Automatic font-attribute detection doesn't work well. Users having +;; problems with auto-font detection should use the lists +;; `ps-italic-faces', `ps-bold-faces' and `ps-underlined-faces' and/or +;; turn off automatic detection by setting `ps-auto-font-detect' to +;; nil. ;; ;; Still too slow; could use some hand-optimization. ;; diff --git a/lisp/vc/ediff.el b/lisp/vc/ediff.el index 7841c256034..63369462e89 100644 --- a/lisp/vc/ediff.el +++ b/lisp/vc/ediff.el @@ -89,12 +89,11 @@ ;; underlining. However, if the region is already underlined by some other ;; overlays, there is no simple way to temporarily remove that residual ;; underlining. This problem occurs when a buffer is highlighted with -;; hilit19.el or font-lock.el packages. If this residual highlighting gets -;; in the way, you can do the following. Both font-lock.el and hilit19.el -;; provide commands for unhighlighting buffers. You can either place these -;; commands in `ediff-prepare-buffer-hook' (which will unhighlight every -;; buffer used by Ediff) or you can execute them interactively, at any time -;; and on any buffer. +;; font-lock.el packages. If this residual highlighting gets in the way, you +;; can do the following. font-lock.el provides commands for unhighlighting +;; buffers. You can either place these commands in `ediff-prepare-buffer-hook' +;; (which will unhighlight every buffer used by Ediff) or you can execute +;; them interactively, at any time and in any buffer. ;;; Acknowledgments: -- 2.39.5