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: Mon, 11 Apr 2011 14:39:15 -0400 Message-ID: <87vcykaazw.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> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: dough.gmane.org 1302581130 32325 80.91.229.12 (12 Apr 2011 04:05:30 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Tue, 12 Apr 2011 04:05:30 +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 06:05:21 2011 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from [140.186.70.17] (helo=lists.gnu.org) by lo.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1Q9Uqv-00067t-0n for ged-emacs-devel@m.gmane.org; Tue, 12 Apr 2011 06:05:21 +0200 Original-Received: from localhost ([::1]:41369 helo=lists2.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Q9Uqu-0008CM-HS for ged-emacs-devel@m.gmane.org; Tue, 12 Apr 2011 00:05:20 -0400 Original-Received: from eggs.gnu.org ([140.186.70.92]:56747) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Q9Sdm-0003PV-TK for emacs-devel@gnu.org; Mon, 11 Apr 2011 21:43:44 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Q9M17-0007K6-KJ for emacs-devel@gnu.org; Mon, 11 Apr 2011 14:39:19 -0400 Original-Received: from vm-emlprdomr-03.its.yale.edu ([130.132.50.144]:47689) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Q9M17-0007I0-Ho; Mon, 11 Apr 2011 14:39:17 -0400 Original-Received: from furball (dhcp128036014198.central.yale.edu [128.36.14.198]) (authenticated bits=0) by vm-emlprdomr-03.its.yale.edu (8.14.4/8.14.4) with ESMTP id p3BIdFhj005081 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 11 Apr 2011 14:39:16 -0400 Original-Received: by furball (Postfix, from userid 1000) id DF8BF160328; Mon, 11 Apr 2011 14:39:15 -0400 (EDT) In-Reply-To: <83oc4cr7fe.fsf@gnu.org> (Eli Zaretskii's message of "Mon, 11 Apr 2011 21:04:21 +0300") 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 X-Broken-Reverse-DNS: no host name found for IP address 140.186.70.17 Xref: news.gmane.org gmane.emacs.devel:138420 Archived-At: Eli Zaretskii writes: >> > No, I was trying to suggest something much simpler: see if these >> > characters can be displayed, e.g. with unencodable-char-position (and >> > something similar for GUI sessions), and if so, use surrogates >> > directly in the code, without going through glyphless-char-display. >> >> How would this handle the multi-tty case? > > The only thing that matters on a tty is its encoding, which you pass > to unencodable-char-position. > > If you mean that some frames can be GUI frames, then you can always > know what kind of frame is the selected one, right? > > Or are you thinking about something else? Suppose we make the *Process List* buffer and display it in a GUI terminal. Then, we create a text terminal in the same Emacs session, and display that same buffer in the text terminal. The buffer has to display correctly, without a priori knowledge of the terminal(s) on which it is to be displayed. Therefore, checking unencodable-char-position at buffer creation time does not work. The fallback behavior has to be done at redisplay time.