unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 58021@debbugs.gnu.org, manuel@ledu-giraud.fr
Subject: bug#58021: 29.0.50; Remove old font.c code
Date: Sat, 24 Sep 2022 11:25:38 +0200	[thread overview]
Message-ID: <87pmfl15v1.fsf@gnus.org> (raw)
In-Reply-To: <83r102ozo0.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 23 Sep 2022 18:53:19 +0300")

Eli Zaretskii <eliz@gnu.org> writes:

> Would it help if we move that to the end of the file?
>
> My primary motivation for leaving this is to try to attract someone to
> get involved in maintaining and developing font.c and fontset.c.
> We've all but lost our only expert on this, and leaving this part of
> Emacs without an active maintainer is bad for us.  I might even add a
> comment there that encourages people to finish implementation of at
> least some of that stuff, in the hope that this will bring on board
> someone capable and motivated.

Adding some commentary to it to explain what the purpose of the code is
(and why it hasn't been enabled) would be helpful, at least.

But the code's been around since 2006, apparently, so at some point it's
probably time to admit defeat.  But perhaps adding some text to explain
why it's there will entice somebody to look at it?  And then if that
hasn't happened at the 20 year anniversary of the code, we can revisit
this issue.





  reply	other threads:[~2022-09-24  9:25 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-23  9:11 bug#58021: 29.0.50; Remove old font.c code Manuel Giraud
2022-09-23 10:07 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-09-23 10:49 ` Eli Zaretskii
2022-09-23 15:41   ` Lars Ingebrigtsen
2022-09-23 15:53     ` Eli Zaretskii
2022-09-24  9:25       ` Lars Ingebrigtsen [this message]
2022-09-26  6:36         ` Eli Zaretskii
2022-09-26 10:58           ` Lars Ingebrigtsen

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=87pmfl15v1.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=58021@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=manuel@ledu-giraud.fr \
    /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).