unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: larsi@gnus.org, 16815@debbugs.gnu.org
Subject: bug#16815: 24.3.50; Provide completion for `describe-font' (enhancement request)
Date: Fri, 29 Apr 2016 12:33:50 -0700 (PDT)	[thread overview]
Message-ID: <6d9ffd0e-3581-4ab9-bc06-99be7c95ecbb@default> (raw)
In-Reply-To: <<831t5ow76o.fsf@gnu.org>>

> IMO, this is madness: you are bloating the Emacs session with hundreds
> of fonts, most of which Emacs will never need to use, or even know
> about.  We certainly shouldn't do anything like that in Emacs.

I don't think it is madness.  I (and others) have been taking
advantage of it for a long time.

> The doc string of describe-font clearly says that the font must be one
> which Emacs already loaded, so completing on all the _installed_ fonts
> is definitely not TRT.

I certainly wouldn't have a problem with that: completing against
the installed fonts is fine by me.  My reply to Lars was to make
the point that this is about choosing a font, not choosing a
fontset - completion should be against font names.

[Note: Things are a lot different if you can complete against
parts of the font name, and especially if you can do so
progressively, to narrow down the matching candidates.  If
all you have is a single pattern-match attempt then the
completion behavior is much less helpful/interesting.]





      parent reply	other threads:[~2016-04-29 19:33 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-19 21:03 bug#16815: 24.3.50; Provide completion for `describe-font' (enhancement request) Drew Adams
2016-04-29 17:35 ` Lars Ingebrigtsen
2016-04-29 18:39   ` Drew Adams
2016-04-29 19:23     ` Eli Zaretskii
2019-11-02 16:23       ` Lars Ingebrigtsen
2019-11-02 17:25         ` Eli Zaretskii
2019-11-03 15:33           ` Lars Ingebrigtsen
     [not found]   ` <<640c1da6-43a2-4c50-b50f-675f0b316b8b@default>
     [not found]     ` <<831t5ow76o.fsf@gnu.org>
2016-04-29 19:33       ` Drew Adams [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=6d9ffd0e-3581-4ab9-bc06-99be7c95ecbb@default \
    --to=drew.adams@oracle.com \
    --cc=16815@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).