all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: 36448@debbugs.gnu.org
Subject: bug#36448: 26.2; doc string of `highlight-lines-matching-regexp'
Date: Sun, 30 Jun 2019 13:40:10 -0700 (PDT)	[thread overview]
Message-ID: <44e129fa-f290-4376-af26-adbe5837fa22@default> (raw)

This part of the doc string is not so good:

  Set face of all lines containing a match of REGEXP to FACE.

That's not what happens - "set" is the wrong verb here (face attributes
are set, but not the displayed face as a whole).

For example, if `font-lock-mode' is enabled and the command highlights a
line that contains text already highlighted by font-lock (e.g. with a
face foreground attribute) then the `highlight-lines-matching-regexp'
highlighting adds its face to the `face' spec for that already
highlighted text.  It does not replace face attributes that are already
set there.

The doc string should just say something similar to what (elisp)
`Highlight Interactively' says:

  Highlight entire lines containing a match for REGEXP, using face
  FACE ('highlight-lines-matching-regexp').

Highlighting "using" FACE is less definitive (more vague) than "setting"
the face to FACE.

If the doc string wants to go into more detail then it can say that FACE
is _added_ to faces already present, or that its attributes are added
merged with those already present.




In GNU Emacs 26.2 (build 1, x86_64-w64-mingw32)
 of 2019-04-13
Repository revision: fd1b34bfba8f3f6298df47c8e10b61530426f749
Windowing system distributor `Microsoft Corp.', version 10.0.17134
Configured using:
 `configure --without-dbus --host=x86_64-w64-mingw32
 --without-compress-install 'CFLAGS=-O2 -static -g3''





             reply	other threads:[~2019-06-30 20:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-30 20:40 Drew Adams [this message]
2019-07-03 12:56 ` bug#36448: 26.2; doc string of `highlight-lines-matching-regexp' Eli Zaretskii

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=44e129fa-f290-4376-af26-adbe5837fa22@default \
    --to=drew.adams@oracle.com \
    --cc=36448@debbugs.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.