unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Kangas <stefan@marxist.se>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 46853@debbugs.gnu.org, larsi@gnus.org
Subject: bug#46853: Confusing terminology "face height" instead of "font size"
Date: Thu, 4 Mar 2021 10:05:28 -0800	[thread overview]
Message-ID: <CADwFkmmQ8gc7aMa+3jf3hmUOgp8wCK4BBoPQfqOAxTp_80syRA@mail.gmail.com> (raw)
In-Reply-To: <838s73jasx.fsf@gnu.org>

Eli Zaretskii <eliz@gnu.org> writes:

>> It also maintains the terminological confusion that is the reason for
>> this bug report -- i.e. it talks about "the default face" instead of
>> "the font size" [in the current buffer].
>
> There's no such thing as "the font in the current buffer" in modern
> Emacs, because we are capable of using quite a few fonts in the same
> buffer.

(Right, but I didn't write "the font in the current buffer".  ;-))

> Which doc string are you alluding to here?  There's IMO a difference
> between doc strings of user commands and doc strings of the rest of
> the functions and variables.  The latter don't need to cater too much
> to users, so they can be more rigorous.  Doc strings for user commands
> and options should perhaps start with an easier to understand text,
> but should afterwards have notes that prevent erroneous
> interpretation.

Perhaps we are in violent agreement, because I agree completely.

> IOW, we need to consider the doc strings on a case by case basis.

I'll rework the patch (more carefully this time) so we have a better
basis for such a discussion.





  reply	other threads:[~2021-03-04 18:05 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-01 16:40 bug#46853: Confusing terminology "face height" instead of "font size" Stefan Kangas
2021-03-01 17:06 ` Eli Zaretskii
2021-03-01 19:31   ` Stefan Kangas
2021-03-01 19:46     ` Eli Zaretskii
2021-03-01 17:12 ` Lars Ingebrigtsen
2021-03-01 17:17   ` Eli Zaretskii
2021-03-01 19:15   ` Stefan Kangas
2021-03-01 19:25     ` Lars Ingebrigtsen
2021-03-01 19:33       ` Lars Ingebrigtsen
2021-03-01 19:37         ` Lars Ingebrigtsen
2021-03-01 19:50           ` Eli Zaretskii
2021-03-01 19:48         ` Eli Zaretskii
2021-03-01 20:05           ` Lars Ingebrigtsen
2021-03-01 20:17             ` Eli Zaretskii
2021-03-03 22:43               ` Stefan Kangas
2021-03-04 13:41                 ` Eli Zaretskii
2021-03-04 18:05                   ` Stefan Kangas [this message]
2022-06-19 23:27             ` Lars Ingebrigtsen
2021-03-01 19:35       ` Eli Zaretskii
2021-03-01 19:45         ` Lars Ingebrigtsen
2021-03-01 19:59           ` Eli Zaretskii
2021-03-04  0:16             ` Stefan Kangas
2021-03-04 13:46               ` Eli Zaretskii
2021-03-04 17:35                 ` Stefan Kangas
2021-03-01 19:33     ` 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=CADwFkmmQ8gc7aMa+3jf3hmUOgp8wCK4BBoPQfqOAxTp_80syRA@mail.gmail.com \
    --to=stefan@marxist.se \
    --cc=46853@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=larsi@gnus.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 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).