unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "T.V Raman" <raman@google.com>
To: eliz@gnu.org
Cc: raman@google.com, jpff@codemist.co.uk, rpluim@gmail.com,
	emacs-devel@gnu.org
Subject: Re: Question on fonts
Date: Thu, 23 Jan 2020 10:17:35 -0800	[thread overview]
Message-ID: <24105.58175.156582.36127@retriever.mtv.corp.google.com> (raw)
In-Reply-To: <8336c6t4zi.fsf@gnu.org>

we're talking across one another.

I did not suggest a change in core emacs, I suggested that someone
interested in helping users ease into emacs could write up a set of
font choices that work in a given situation. Let's close this thread.
Eli Zaretskii writes:
 > > From: "T.V Raman" <raman@google.com>
 > > Date: Thu, 23 Jan 2020 08:47:44 -0800
 > > Cc: raman@google.com,
 > >     jpff@codemist.co.uk,
 > >     rpluim@gmail.com,
 > >     emacs-devel@gnu.org
 > > 
 > > More precisely, my question was in the context of helping users choose
 > > a font that is best suited to their needs --- the task is likely
 > > something that can be achieved by someone with  the
 > > interest/motivation creating an appropriate theme.
 > 
 > So you did mean a more general question.
 > 
 > In that case, I don't see how we could do a better job than we already
 > have in fontest.el.  The problem here is that (a) we cannot know which
 > fonts are installed on the end-user's machine, and (b) many fonts that
 > people so like to use and advertise aren't free, so we don't want to
 > promote them by including them in our fontest.  And on top of all
 > that, there's the personal preferences of each user, which IME are
 > quite different.

-- 
Id: kg:/m/0285kf1 

-- 
Id: kg:/m/0285kf1 



      reply	other threads:[~2020-01-23 18:17 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-21 18:09 Question on fonts john
2020-01-21 20:05 ` Robert Pluim
2020-01-22 20:52   ` john
2020-01-23  1:19     ` T.V Raman
2020-01-23  3:35       ` Eli Zaretskii
2020-01-23  3:47         ` T.V Raman
2020-01-23  9:44           ` VanL
2020-01-23 14:16           ` Eli Zaretskii
2020-01-23 16:47             ` T.V Raman
2020-01-23 18:14               ` Eli Zaretskii
2020-01-23 18:17                 ` T.V Raman [this message]

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=24105.58175.156582.36127@retriever.mtv.corp.google.com \
    --to=raman@google.com \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=jpff@codemist.co.uk \
    --cc=rpluim@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).