From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.devel Subject: ps-print-buffer with unexpected chars Date: Wed, 19 Jan 2005 14:51:41 -0500 Message-ID: NNTP-Posting-Host: deer.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: sea.gmane.org 1106164574 10863 80.91.229.6 (19 Jan 2005 19:56:14 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Wed, 19 Jan 2005 19:56:14 +0000 (UTC) Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed Jan 19 20:55:56 2005 Return-path: Original-Received: from lists.gnu.org ([199.232.76.165]) by deer.gmane.org with esmtp (Exim 3.35 #1 (Debian)) id 1CrLvo-0001Bm-00 for ; Wed, 19 Jan 2005 20:55:56 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1CrM7l-00064a-GX for ged-emacs-devel@m.gmane.org; Wed, 19 Jan 2005 15:08:17 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1CrM53-0005EW-QZ for emacs-devel@gnu.org; Wed, 19 Jan 2005 15:05:30 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1CrM4v-0005A4-Q7 for emacs-devel@gnu.org; Wed, 19 Jan 2005 15:05:24 -0500 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1CrM4v-00059J-Bv for emacs-devel@gnu.org; Wed, 19 Jan 2005 15:05:21 -0500 Original-Received: from [132.204.24.67] (helo=mercure.iro.umontreal.ca) by monty-python.gnu.org with esmtp (Exim 4.34) id 1CrLro-0002kD-OV for emacs-devel@gnu.org; Wed, 19 Jan 2005 14:51:48 -0500 Original-Received: from hidalgo.iro.umontreal.ca (hidalgo.iro.umontreal.ca [132.204.27.50]) by mercure.iro.umontreal.ca (Postfix) with ESMTP id 569D18282AA; Wed, 19 Jan 2005 14:51:48 -0500 (EST) Original-Received: from asado.iro.umontreal.ca (asado.iro.umontreal.ca [132.204.24.84]) by hidalgo.iro.umontreal.ca (Postfix) with ESMTP id 39B3C4AC1C6; Wed, 19 Jan 2005 14:51:42 -0500 (EST) Original-Received: by asado.iro.umontreal.ca (Postfix, from userid 20848) id 1EF464BB60; Wed, 19 Jan 2005 14:51:42 -0500 (EST) Original-To: emacs-devel@gnu.org User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/21.3.50 (gnu/linux) X-DIRO-MailScanner-Information: Please contact the ISP for more information X-DIRO-MailScanner: Found to be clean X-DIRO-MailScanner-SpamCheck: n'est pas un polluriel, SpamAssassin (score=-4.747, requis 5, autolearn=not spam, AWL 0.15, BAYES_00 -4.90) X-MailScanner-From: monnier@iro.umontreal.ca X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: main.gmane.org gmane.emacs.devel:32390 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:32390 If I do ps-print-buffer on a buffer that has chars that ps-print doesn't know how to encode for Postscript, it just tells me "Font for some characters not found, continue anyway?". Problem is that it's hard to make a decision when you don't know which chars caused a problem. We should do something like it is done when saving a file, where Emacs shows a sample of the chars that posed problems. Stefan