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: Re: new *Help* argument highlighting Date: 10 May 2004 22:30:40 -0400 Sender: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Message-ID: <87zn8fogbg.fsf-monnier+emacs@gnu.org> References: <20040510013534.F994.LEKTU@mi.madritel.es> <20040510020140.F99A.LEKTU@mi.madritel.es> <87llk0qftn.fsf-monnier+emacs@gnu.org> <87vfj3kam4.fsf@mail.jurta.org> NNTP-Posting-Host: deer.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: sea.gmane.org 1084242957 21876 80.91.224.253 (11 May 2004 02:35:57 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Tue, 11 May 2004 02:35:57 +0000 (UTC) Cc: bob@rattlesnake.com, emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Tue May 11 04:35:49 2004 Return-path: Original-Received: from quimby.gnus.org ([80.91.224.244]) by deer.gmane.org with esmtp (Exim 3.35 #1 (Debian)) id 1BNN7V-0005n2-00 for ; Tue, 11 May 2004 04:35:49 +0200 Original-Received: from monty-python.gnu.org ([199.232.76.173]) by quimby.gnus.org with esmtp (Exim 3.35 #1 (Debian)) id 1BNN7V-0000Wf-00 for ; Tue, 11 May 2004 04:35:49 +0200 Original-Received: from localhost ([127.0.0.1] helo=monty-python.gnu.org) by monty-python.gnu.org with esmtp (Exim 4.34) id 1BNN3q-0000hE-Ek for emacs-devel@quimby.gnus.org; Mon, 10 May 2004 22:32:02 -0400 Original-Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.34) id 1BNN3V-0000gW-1p for emacs-devel@gnu.org; Mon, 10 May 2004 22:31:41 -0400 Original-Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.34) id 1BNN2y-0000bX-0b for emacs-devel@gnu.org; Mon, 10 May 2004 22:31:40 -0400 Original-Received: from [209.226.175.93] (helo=tomts36-srv.bellnexxia.net) by monty-python.gnu.org with esmtp (Exim 4.34) id 1BNN2i-0000XW-Sx for emacs-devel@gnu.org; Mon, 10 May 2004 22:30:53 -0400 Original-Received: from alfajor ([67.68.218.161]) by tomts36-srv.bellnexxia.net (InterMail vM.5.01.06.05 201-253-122-130-105-20030824) with ESMTP id <20040511023044.JSVO11251.tomts36-srv.bellnexxia.net@alfajor>; Mon, 10 May 2004 22:30:44 -0400 Original-Received: by alfajor (Postfix, from userid 1000) id 57823D73CE; Mon, 10 May 2004 22:30:40 -0400 (EDT) Original-To: Juri Linkov In-Reply-To: <87vfj3kam4.fsf@mail.jurta.org> Original-Lines: 37 User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3.50 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.4 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Xref: main.gmane.org gmane.emacs.devel:23103 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:23103 >> As I said, I haven't seen a single complaint about the font-size change >> in Info-mode in Emacs-21. > Perhaps you haven't seen complaints about font sizes in Info-mode, > because users who don't like that, has silently changed sizes > in their .emacs files :-) Of course. I don't expect that everybody liked it. But if they don't whine, they get what they deserve. When I compare that to the reaction w.r.t colors, I conclude that "font-size changes are pretty safe". >> With the 6x13 font I use, "m" in bold looks basically like a solid block, >> but I've never found it to be unreadable because it still looks clearly >> different from all others (including "w"). >> Is your situation similar except that the solid block does bother you >> (maybe because you sight is not as good as mine)? > This is clearly my situation with my 6x10 font, where the text > displayed in this font is hardly readable. I've often heard comments about my 6x13 font being pretty small already, so I don't expect too many people to use a 6x10 font. And those people should expect to have to fiddle with things to get good results. So I don't think it's a class of users we should worry too much about. The case of Robert's 10x20 font is different since it should be a "pretty safe size" and the user probably expects things to be readable without much fiddling. > I tried this patch a month ago, but it often causes crashes. So without > hope to get this patch working without crashes, I solved this particular > problem with a small piece of code in .emacs: An elisp approach is indeed much safer. If it's good enough, maybe we should try such an approach (we could make it much cleaner than your code by hooking directly in face-spec-set or face-spec-choose). Stefan