unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Ergus <spacibba@aol.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: help-gnu-emacs@gnu.org
Subject: Re: New line and trailing whitespaces
Date: Tue, 23 Apr 2024 17:38:15 +0200	[thread overview]
Message-ID: <vid6rttxg4l3piuqozcyqk2flw7kqoojssygm7lckmfazqkptp@hpy64mtw3fpu> (raw)
In-Reply-To: <86le544i6t.fsf@gnu.org>

On Tue, Apr 23, 2024 at 11:06:02AM GMT, Eli Zaretskii wrote:
>> Date: Mon, 22 Apr 2024 14:22:43 +0200
>> From: Ergus <spacibba@aol.com>
>> Cc: help-gnu-emacs@gnu.org
>>
>> >> That face seems apply only to the tab whitespace when whitespace-style
>> >> has `tabs`, but not to when `tab-mark` applies.
>> >
>> >You lost me here.  But if all you want is to know what face is used on
>> >some text, simply use "M-x describe-text-properties RET" with point on
>> >that text.
>> >
>> Whitespace mode "shows" the tabs in two (independent) ways:
>>
>> 1. "Colorizing" the tab whitespace with some color (face tabs)
>> 2. Add a mark in the whitespace space like | or � (tab-mark)
>>
>> The whitespace-tab face applies only to 1, but I don't find how to make
>> it apply to 2
>>
>>
>> Define the whitespace-tab face foreground and background
>> (setq-default whitespace-style '(faces tab-mark))
>> (whitespace-mode 1)
>> TAB
>>
>> I see: the �, but it is always white, independently of whitespace-tab face.
>
>You need to customize whitespace-display-mappings.  Specifically, the
>tab-mark element of the value is by default the vector '[?� ?\t], and
>you need to replace each of these two characters with a glyph that has
>the face you want, using make-glyph-code.  Caveat: a comment in
>whitespace.el explains why only newlines are given a face:
>
>	      ;; Only insert face bits on NEWLINE char mapping to avoid
>	      ;; obstruction of other faces like TABs and (HARD) SPACEs
>	      ;; faces, font-lock faces, etc.
>

Ahh this is exactly what I want..

Do you think it worth adding your paragraph as a comment somewhere in
whitespace or reference that in its manual section?



  reply	other threads:[~2024-04-23 15:38 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <kcaicxrup2f3usy37v4aupgu7uvmifnxkeyc2hx5n5qpqnuj7b.ref@okar6momrmhs>
2024-04-20 12:10 ` New line and trailing whitespaces Ergus
2024-04-20 13:50   ` Eli Zaretskii
2024-04-20 14:16     ` Eli Zaretskii
2024-04-21  1:12       ` Ergus
2024-04-21  5:23         ` Eli Zaretskii
2024-04-21 21:05           ` Ergus
2024-04-22  5:39             ` Eli Zaretskii
2024-04-22 12:22               ` Ergus
2024-04-23  8:06                 ` Eli Zaretskii
2024-04-23 15:38                   ` Ergus [this message]
2024-04-23 16:19                     ` Eli Zaretskii
2024-04-24  2:41                       ` Ergus
2024-04-24  7:05                         ` Eli Zaretskii
2024-04-24 14:48                           ` Ergus
2024-04-24 15:45                             ` Eli Zaretskii
2024-04-22 12:34               ` Ergus

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=vid6rttxg4l3piuqozcyqk2flw7kqoojssygm7lckmfazqkptp@hpy64mtw3fpu \
    --to=spacibba@aol.com \
    --cc=eliz@gnu.org \
    --cc=help-gnu-emacs@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.
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).