unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Dmitry Gutov <dgutov@yandex.ru>
Cc: emacs-devel@gnu.org, stefankangas@gmail.com, nicolas.rougier@inria.fr
Subject: Re: Consistent vanilla Emacs
Date: Fri, 15 May 2020 09:37:16 +0300	[thread overview]
Message-ID: <8336814sbn.fsf@gnu.org> (raw)
In-Reply-To: <e660db91-d13a-1721-cc57-a3c4000206f9@yandex.ru> (message from Dmitry Gutov on Fri, 15 May 2020 00:21:57 +0300)

> From: Dmitry Gutov <dgutov@yandex.ru>
> Date: Fri, 15 May 2020 00:21:57 +0300
> 
> > 3. We currently don't ship any fonts with GNU Emacs.  Maybe we should
> >     consider doing that?  It seems to me that many other applications do.
> >     Or maybe we should introduce a stronger set of default fonts for
> >     different systems.
> 
> IIRC Eli said that we can't distribute fonts for our own use only, 
> whatever fonts are needed the user will have to install system-wide, or 
> put into ~/.fonts, at least.

Technically, we _can_ distribute fonts, but doing so will
inconvenience the users to the degree that I think we should avoid
doing that.  Installation of fonts on the system (with implied effects
on other applications) is indeed that inconvenience.  It is true that
there are ways to make the installation local, but that is even more
of the inconvenience, IMO.

So yes, I don't think we should include fonts in our distribution.  We
could advise users to install fonts that we think will make Emacs look
good, and maybe if we do that for some time, distros will start making
those fonts available by default.  But forcing fonts on users is not
TRT, IMO.  Right now, Emacs uses as its default font the font used by
other similar applications, and I think we should continue doing that,
so as to keep Emacs's text look as in other similar applications on
the system.



  parent reply	other threads:[~2020-05-15  6:37 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-14  9:06 Consistent vanilla Emacs Nicolas P. Rougier
2020-05-14 14:20 ` Stefan Kangas
2020-05-14 17:36   ` Nicolas P. Rougier
2020-05-14 18:36     ` Tassilo Horn
2020-05-14 21:21   ` Dmitry Gutov
2020-05-14 22:44     ` Stefan Kangas
2020-05-14 23:45       ` Dmitry Gutov
2020-05-15  1:13         ` Stefan Kangas
2020-05-15  5:18           ` Stefan Kangas
2020-05-15  6:37     ` Eli Zaretskii [this message]
2020-05-15  7:11       ` Nicolas P. Rougier
2020-05-15  7:41         ` Tassilo Horn
2020-05-15 10:01         ` Eli Zaretskii
2020-05-15 10:18           ` Robert Pluim
2020-05-15 21:35             ` Alan Third
2020-05-16  3:33               ` Nicolas P. Rougier
2020-05-14 19:41 ` João Távora
2020-05-14 20:14   ` Dmitry Gutov
2020-05-14 20:19     ` João Távora
2020-05-14 20:25       ` Dmitry Gutov
2020-05-14 20:58     ` Eduardo Ochs

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=8336814sbn.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=dgutov@yandex.ru \
    --cc=emacs-devel@gnu.org \
    --cc=nicolas.rougier@inria.fr \
    --cc=stefankangas@gmail.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).