From: Eli Zaretskii <eliz@gnu.org>
To: Arash Esbati <arash@gnu.org>
Cc: 67713-done@debbugs.gnu.org
Subject: bug#67713: [PATCH] 30.0.50; Small change to display.texi
Date: Sat, 09 Dec 2023 13:06:26 +0200 [thread overview]
Message-ID: <83bkazy6rx.fsf@gnu.org> (raw)
In-Reply-To: <m2plzglk6a.fsf@macmutant.fritz.box> (message from Arash Esbati on Fri, 08 Dec 2023 17:43:09 +0100)
> From: Arash Esbati <arash@gnu.org>
> Cc: 67713@debbugs.gnu.org
> Date: Fri, 08 Dec 2023 17:43:09 +0100
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> > Thanks, but why is it so important to follow the order in the @item?
>
> One point (which is minor) is that my brain can parse that information
> easier if they are in order. The major point is that couple of lines
> above in display.texi (and also in other places in the manual), the
> information is provided in that order:
>
> @item @code{(:color @var{color} :style @var{style} :position @var{position})}
> @var{color} is either a string, or the symbol @code{foreground-color},
> meaning the foreground color of the face. Omitting the attribute
> @code{:color} means to use the foreground color of the face.
> @var{style} should be a symbol @code{line} or @code{wave}, meaning to
> use a straight or wavy line. Omitting the attribute @code{:style}
> means to use a straight line. @var{position}, if non-@code{nil}, means to
> display the underline at the descent of the text, instead of at the
> baseline level. If it is a number, then it specifies the amount of
> pixels above the descent to display the underline.
>
> But I'm easy, feel free to reject; it is really a minor issue.
I installed this on the emacs-29 branch, and I'm closing this bug.
Thanks.
next prev parent reply other threads:[~2023-12-09 11:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-08 16:03 bug#67713: [PATCH] 30.0.50; Small change to display.texi Arash Esbati
2023-12-08 16:26 ` Eli Zaretskii
2023-12-08 16:43 ` Arash Esbati
2023-12-09 11:06 ` Eli Zaretskii [this message]
2023-12-09 13:48 ` Arash Esbati
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=83bkazy6rx.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=67713-done@debbugs.gnu.org \
--cc=arash@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.