From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Paul Eggert Newsgroups: gmane.emacs.devel Subject: Re: A simple solution to "Upcoming loss of usability ..." Date: Thu, 25 Jun 2015 15:45:34 -0700 Organization: UCLA Computer Science Department Message-ID: <558C848E.7080108@cs.ucla.edu> References: <87egkzg7gb.fsf@gmail.com> <558C2E25.10303@cs.ucla.edu> <20150625205844.GA6883@acm.fritz.box> <558C81E4.6010008@cs.ucla.edu> <558C8354.6090308@yandex.ru> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-Trace: ger.gmane.org 1435272382 22682 80.91.229.3 (25 Jun 2015 22:46:22 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Thu, 25 Jun 2015 22:46:22 +0000 (UTC) Cc: emacs-devel@gnu.org To: Dmitry Gutov Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri Jun 26 00:46:14 2015 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1Z8FuQ-0007pN-5o for ged-emacs-devel@m.gmane.org; Fri, 26 Jun 2015 00:46:14 +0200 Original-Received: from localhost ([::1]:57684 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Z8FuK-0004yS-DF for ged-emacs-devel@m.gmane.org; Thu, 25 Jun 2015 18:46:08 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:39224) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Z8Ftr-0004yC-MC for emacs-devel@gnu.org; Thu, 25 Jun 2015 18:45:40 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Z8Ftn-0003OY-JS for emacs-devel@gnu.org; Thu, 25 Jun 2015 18:45:39 -0400 Original-Received: from zimbra.cs.ucla.edu ([131.179.128.68]:40841) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Z8Ftn-0003OS-D5 for emacs-devel@gnu.org; Thu, 25 Jun 2015 18:45:35 -0400 Original-Received: from localhost (localhost [127.0.0.1]) by zimbra.cs.ucla.edu (Postfix) with ESMTP id F25BF160844; Thu, 25 Jun 2015 15:45:34 -0700 (PDT) Original-Received: from zimbra.cs.ucla.edu ([127.0.0.1]) by localhost (zimbra.cs.ucla.edu [127.0.0.1]) (amavisd-new, port 10032) with ESMTP id sde64ayJ2Kj0; Thu, 25 Jun 2015 15:45:34 -0700 (PDT) Original-Received: from localhost (localhost [127.0.0.1]) by zimbra.cs.ucla.edu (Postfix) with ESMTP id 52485160846; Thu, 25 Jun 2015 15:45:34 -0700 (PDT) X-Virus-Scanned: amavisd-new at zimbra.cs.ucla.edu Original-Received: from zimbra.cs.ucla.edu ([127.0.0.1]) by localhost (zimbra.cs.ucla.edu [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id NOSGjnv3fCqj; Thu, 25 Jun 2015 15:45:34 -0700 (PDT) Original-Received: from [192.168.1.9] (pool-100-32-155-148.lsanca.fios.verizon.net [100.32.155.148]) by zimbra.cs.ucla.edu (Postfix) with ESMTPSA id 37985160840; Thu, 25 Jun 2015 15:45:34 -0700 (PDT) User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.7.0 In-Reply-To: <558C8354.6090308@yandex.ru> X-detected-operating-system: by eggs.gnu.org: GNU/Linux 3.x X-Received-From: 131.179.128.68 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:187543 Archived-At: Dmitry Gutov wrote: > >> I have been seriously considering font-lock approaches but so far they >> appear to be more confusing and less reliable than the alternatives. >> For example, how would font-lock alter the quotes that Emacs outputs in >> batch diagnostics? > > It probably won't, you'll need a different function. OK, that can be the format-message function already discussed. So the font-lock proposal isn't intended to address the problem of diagnostics, or of info or help buffers for that matter; it's intended only to address the issue of displaying docstrings to a developer who's editing Elisp code. Is that correct?