unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Po Lu via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Hendrik Rommeswinkel <rommeswi@proton.me>
Cc: 56388@debbugs.gnu.org
Subject: bug#56388: Overline equivalent of x-underline-at-descent-line
Date: Tue, 05 Jul 2022 09:51:52 +0800	[thread overview]
Message-ID: <87pmik8gxz.fsf@yahoo.com> (raw)
In-Reply-To: <LjH0oWZPzIpy2sLnMqQ7nanGX5D90QZNdxhKDw6tV9fWYhF5j7jGnS33wOFaNDXHBCpw7XZ0yM4PL98qPZrPhdKWVHwbpBiF5LdeXh9wM98=@proton.me> (Hendrik Rommeswinkel's message of "Mon, 04 Jul 2022 18:25:55 +0000")

Hendrik Rommeswinkel <rommeswi@proton.me> writes:

> I noticed that overline text is not as configurable as underline
> text. Using x-underline-at-descent-line, it is possible to choose
> between placing the underline at the baseline or the bottom line (I
> think the naming of this option is not quite right.). However, it is
> not possible to choose between placing the overline at the ascent line
> or the top line. Instead it is always at the top line. This makes
> overline very ugly when the height of faces differs on a line because
> the overline will appear at the very top of the line instead of on top
> of the font.
>
> It would be nice if there would be an option x-overline-at-ascent-line
> which places the overline at the ascent line (instead of the top
> line).

Instead of making it a user option, how about making it an attribute for
the `:overline' face property?





  reply	other threads:[~2022-07-05  1:51 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-04 18:25 bug#56388: Overline equivalent of x-underline-at-descent-line Hendrik Rommeswinkel via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-07-05  1:51 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2022-07-05  3:14   ` Hendrik Rommeswinkel via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-07-05 11:25   ` Lars Ingebrigtsen
2022-07-07 16:09     ` Hendrik Rommeswinkel via Bug reports for GNU Emacs, the Swiss army knife of text editors

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=87pmik8gxz.fsf@yahoo.com \
    --to=bug-gnu-emacs@gnu.org \
    --cc=56388@debbugs.gnu.org \
    --cc=luangruo@yahoo.com \
    --cc=rommeswi@proton.me \
    /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).