unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Protesilaos Stavrou <info@protesilaos.com>
Cc: emacs-devel@gnu.org, stefankangas@gmail.com, monnier@iro.umontreal.ca
Subject: Re: Semantic hl-line-mode (was: ELPA: add lin.el)
Date: Sat, 13 Nov 2021 17:06:30 +0200	[thread overview]
Message-ID: <83bl2oxfgp.fsf@gnu.org> (raw)
In-Reply-To: <87pmr8j6k5.fsf@protesilaos.com> (message from Protesilaos Stavrou on Wed, 10 Nov 2021 18:53:30 +0200)

> From: Protesilaos Stavrou <info@protesilaos.com>
> Cc: monnier@iro.umontreal.ca, emacs-devel@gnu.org
> Date: Wed, 10 Nov 2021 18:53:30 +0200
> 
> +The distinction between these two types of line highlighting allows
> +users/themes to apply different styles to the applicable faces, each
> +optimized for its context: the standard 'hl-line' may become more
> +subtle, while the 'hl-line-line-oriented' ought to be more prominent.

It sounds like the last part (after the colon) is the important part,
and is the reason for having a separate face.  So I wonder whether the
documentation could be made more up-to-a-point by stating this right
from the beginning.  Then I think you will be able to omit a large
part of the rest, because the above makes the reason very clear.

Thanks.



      reply	other threads:[~2021-11-13 15:06 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-05 19:29 ELPA: add lin.el Protesilaos Stavrou
2021-11-05 20:28 ` Stefan Kangas
2021-11-06  4:55   ` Protesilaos Stavrou
2021-11-06  6:12     ` Stefan Kangas
2021-11-09 19:46 ` Protesilaos Stavrou
2021-11-09 20:15   ` Stefan Monnier
2021-11-09 20:38     ` Protesilaos Stavrou
2021-11-10 14:14     ` Semantic hl-line-mode (was: ELPA: add lin.el) Protesilaos Stavrou
2021-11-10 14:33       ` Eli Zaretskii
2021-11-10 14:53         ` Stefan Kangas
2021-11-10 16:53           ` Protesilaos Stavrou
2021-11-13 15:06             ` Eli Zaretskii [this message]

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

  List information: https://www.gnu.org/software/emacs/

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

  git send-email \
    --in-reply-to=83bl2oxfgp.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=info@protesilaos.com \
    --cc=monnier@iro.umontreal.ca \
    --cc=stefankangas@gmail.com \
    /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 public inbox

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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).