From: Drew Adams <drew.adams@oracle.com>
To: "Clément Pit--Claudel" <clement.pitclaudel@live.com>,
26959@debbugs.gnu.org
Subject: bug#26959: Feature request: bold underlines
Date: Wed, 17 May 2017 07:04:42 -0700 (PDT) [thread overview]
Message-ID: <49a934d2-fd0b-4b5d-bd77-379d0d3f95fc@default> (raw)
In-Reply-To: <2e85019c-a970-dfcb-9c33-233c39fc59b4@live.com>
> > See my reply to bug #26958. Should we have two requests:
> > 1. Wavy (and plain) underline to follow text scaling (#26958).
> > 2. Be able to configure underline line-width (#26959).
>
> Yes, that's a great summary.
>
> > Is #2 enough? If we could customize the :line-width for :underline
> > (and :overline? and :strike-through?), would that be sufficient, or
> > is there also a need for such lines to be sensitive to text scaling?
>
> I don't think so — sensitivity to text scaling would be a useful, distinct
> feature. Otherwise Lisp code will have to inspect font sizes and adjust
> thickness based on it, which will cause inconsistencies. Additionally, the
> amount of space between the text and the underline needs to be adjusted when
> the font size changes — and this is currently done on GNU/Linux already.
Whatever decision is made about what the most appropriate behavior
is, should we make it optional, e.g., give users a way to _not_
scale such lines, boxes, etc.?
next prev parent reply other threads:[~2017-05-17 14:04 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-17 4:16 bug#26959: Feature request: bold underlines Clément Pit--Claudel
2017-05-17 4:21 ` Drew Adams
2017-05-17 4:39 ` Clément Pit--Claudel
2017-05-17 14:04 ` Drew Adams [this message]
2017-05-17 15:06 ` Clément Pit--Claudel
2017-05-17 16:06 ` Drew Adams
2017-05-17 18:48 ` Clément Pit--Claudel
2017-05-17 19:48 ` Drew Adams
2017-05-17 20:11 ` Clément Pit--Claudel
2017-05-17 21:09 ` Drew Adams
2017-05-17 21:22 ` Clément Pit--Claudel
2017-05-17 21:37 ` Drew Adams
2017-05-17 15:39 ` Eli Zaretskii
2017-05-17 18:59 ` Clément Pit--Claudel
2017-05-18 4:10 ` 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
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=49a934d2-fd0b-4b5d-bd77-379d0d3f95fc@default \
--to=drew.adams@oracle.com \
--cc=26959@debbugs.gnu.org \
--cc=clement.pitclaudel@live.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).