From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: "Lennart Borgman (gmail)" Newsgroups: gmane.emacs.devel Subject: Re: Simple Tasks, new TODO category Date: Sun, 20 Jan 2008 19:13:47 +0100 Message-ID: <47938F5B.6090405@gmail.com> References: <200801192020.m0JKKUWl017748@sallyv1.ics.uci.edu> <200801201710.m0KHAoKn021472@sallyv1.ics.uci.edu> <479388A9.9010600@gmail.com> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Trace: ger.gmane.org 1200852853 2703 80.91.229.12 (20 Jan 2008 18:14:13 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sun, 20 Jan 2008 18:14:13 +0000 (UTC) Cc: Dan Nicolaescu , emacs-devel@gnu.org To: dhruva Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sun Jan 20 19:14:32 2008 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1JGega-0004b7-17 for ged-emacs-devel@m.gmane.org; Sun, 20 Jan 2008 19:14:24 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1JGegA-00025G-Kg for ged-emacs-devel@m.gmane.org; Sun, 20 Jan 2008 13:13:58 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1JGeg7-000252-1n for emacs-devel@gnu.org; Sun, 20 Jan 2008 13:13:55 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1JGeg6-00024f-3v for emacs-devel@gnu.org; Sun, 20 Jan 2008 13:13:54 -0500 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1JGeg5-00024b-PQ for emacs-devel@gnu.org; Sun, 20 Jan 2008 13:13:53 -0500 Original-Received: from ch-smtp02.sth.basefarm.net ([80.76.149.213]) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1JGeg5-0003XD-Gi for emacs-devel@gnu.org; Sun, 20 Jan 2008 13:13:53 -0500 Original-Received: from c83-254-148-228.bredband.comhem.se ([83.254.148.228]:64619 helo=[127.0.0.1]) by ch-smtp02.sth.basefarm.net with esmtp (Exim 4.68) (envelope-from ) id 1JGefz-0007Db-8H; Sun, 20 Jan 2008 19:13:50 +0100 User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.9) Gecko/20071031 Thunderbird/2.0.0.9 Mnenhy/0.7.5.666 In-Reply-To: X-Antivirus: avast! (VPS 080120-1, 2008-01-20), Outbound message X-Antivirus-Status: Clean X-Originating-IP: 83.254.148.228 X-Scan-Result: No virus found in message 1JGefz-0007Db-8H. X-Scan-Signature: ch-smtp02.sth.basefarm.net 1JGefz-0007Db-8H d37835ba4b98652be2ad3be599831cee X-detected-kernel: by monty-python.gnu.org: Linux 2.6? (barebone, rare!) 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: news.gmane.org gmane.emacs.devel:87113 Archived-At: dhruva wrote: > Hello, > > On Jan 20, 2008 11:15 PM, Lennart Borgman (gmail) > wrote: >> - Printing is broken on w32 and some weeks ago I discovered that Emacs >> can hang completely if a user tries to print. Unsaved data can be lost, >> of course! > > Could you please send me a scenario to reproduce the printing/problem > hang, I will debug it and try fixing it. Does current (HEAD) Emacs > have native printing support on M$ or does it relay on some lisp code > to use a helper application to print? I was using 'notepad'/'wordpad' > as a helper function to print earlier but have not used it in recent > times though. > > I do not have UI related experience and hence may not be able to get > to work immediately. > > -dky Hi dky, The information is in this thread: http://lists.gnu.org/archive/html/emacs-devel/2008-01/msg00850.html But as Dan said this is not a simple issue that we can fix now. Instead I agree with what Jason said in this thread. We should simply warn the user about the problem (and I believe I said in the thread what I believe is reasonable to do). However adding a warning and a defcustom to avoid the warning should be rather easy (but not very simple).