From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Chong Yidong Newsgroups: gmane.emacs.devel Subject: Re: tabulated-list-init-header and glyphless-char-display Date: Tue, 12 Apr 2011 12:12:09 -0400 Message-ID: <87ei578n52.fsf@stupidchicken.com> References: <83mxk0u0g7.fsf@gnu.org> <874o68zjhi.fsf@stupidchicken.com> <83k4f4twam.fsf@gnu.org> <8762qnxm44.fsf@stupidchicken.com> <83hba6rqtm.fsf@gnu.org> <87mxjyht7w.fsf@stupidchicken.com> <83pqosra90.fsf@gnu.org> <87pqosg0ea.fsf@stupidchicken.com> <83oc4cr7fe.fsf@gnu.org> <87vcykaazw.fsf@stupidchicken.com> <83mxjwr3ki.fsf@gnu.org> <87lizgto6g.fsf@stupidchicken.com> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: dough.gmane.org 1302624745 21370 80.91.229.12 (12 Apr 2011 16:12:25 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Tue, 12 Apr 2011 16:12:25 +0000 (UTC) Cc: monnier@iro.umontreal.ca, emacs-devel@gnu.org To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue Apr 12 18:12:20 2011 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([140.186.70.17]) by lo.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1Q9gCS-0003fd-HM for ged-emacs-devel@m.gmane.org; Tue, 12 Apr 2011 18:12:20 +0200 Original-Received: from localhost ([::1]:38378 helo=lists2.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Q9gCR-0001Nj-W1 for ged-emacs-devel@m.gmane.org; Tue, 12 Apr 2011 12:12:20 -0400 Original-Received: from eggs.gnu.org ([140.186.70.92]:58164) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Q9gCP-0001NQ-1Q for emacs-devel@gnu.org; Tue, 12 Apr 2011 12:12:18 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Q9gCL-0004cm-Rr for emacs-devel@gnu.org; Tue, 12 Apr 2011 12:12:17 -0400 Original-Received: from vm-emlprdomr-03.its.yale.edu ([130.132.50.144]:54504) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Q9gCL-0004cV-Pz; Tue, 12 Apr 2011 12:12:13 -0400 Original-Received: from furball (dhcp128036014129.central.yale.edu [128.36.14.129]) (authenticated bits=0) by vm-emlprdomr-03.its.yale.edu (8.14.4/8.14.4) with ESMTP id p3CGCAT3031988 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 12 Apr 2011 12:12:12 -0400 Original-Received: by furball (Postfix, from userid 1000) id 21572160447; Tue, 12 Apr 2011 12:12:10 -0400 (EDT) In-Reply-To: (Eli Zaretskii's message of "Tue, 12 Apr 2011 00:51:34 -0400") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.0.50 (gnu/linux) X-Scanned-By: MIMEDefang 2.71 on 130.132.50.144 X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6 (newer, 3) X-Received-From: 130.132.50.144 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:138442 Archived-At: Eli Zaretskii writes: > Then let's extend glyphless-char-display to provide this information. > That is, for each character, it should provide display information > both for GUI and for text-mode displays. It can do that by providing > an option to have an element of the char-table be a vector of 2 > elements, instead of just one value today. Most table entries will > still be symbols like today, but we could have some of them be > vectors, as in this case and in the case of line-drawing characters. > > I think this is better than the text property suggestion, because > glyphless-char-display can be set once and by default, whereas with > text properties each Lisp application that needs it will have to do > that manually. > > WDYT? Instead of changing the meaning of glyphless-char-display, it might be better to use a new char-table---say, fallback-display-table, by analogy with buffer-display-table. OTOH, it's also more complicated to implement than the text-property idea; the mapping must be done somewhere in get_next_display_element, just after we determine the font to use for a multibyte character, compared to just adding a few lines to x_produce_glyphs. But I agree that it's probably a cleaner system. I'll look into it.