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 08:47:44 -0800	[thread overview]
Message-ID: <24105.52784.451816.290915@retriever.mtv.corp.google.com> (raw)
In-Reply-To: <83muaetfzt.fsf@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.
Eli Zaretskii writes:
 > > From: "T.V Raman" <raman@google.com>
 > > Cc: jpff@codemist.co.uk,  rpluim@gmail.com,  emacs-devel@gnu.org
 > > Date: Wed, 22 Jan 2020 19:47:41 -0800
 > > 
 > > I didn't say anything was wrong, I said it's hard for a user to figure
 > > out what to use given a set of requirements.
 > 
 > Sorry, I didn't realize your question was in the context of the font
 > backends, I thought it was a more general question about font setup.
 > Our best knowledge about the latter is already in fontest.el.  OTOH,
 > the issue with fonts vs font backends is unrelated to fontsets.

-- 
Id: kg:/m/0285kf1 

-- 
Id: kg:/m/0285kf1 



  reply	other threads:[~2020-01-23 16:47 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 [this message]
2020-01-23 18:14               ` Eli Zaretskii
2020-01-23 18:17                 ` T.V Raman

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.52784.451816.290915@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).