From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Ilya Zakharevich Newsgroups: gmane.emacs.help Subject: Re: In emacs 23 compile-mode doesn't recognize (c)perl error messages Date: Fri, 16 Oct 2009 23:36:11 +0000 (UTC) Organization: U.C. Berkeley Math. Department. Message-ID: References: <6d2cb724-900e-4e8a-9145-8b271037c8e2@z24g2000yqb.googlegroups.com> <1544A0C5-7D0B-4B56-BC70-C8684173706A@Web.DE> <5397B484-241E-4DF2-AA2C-F2AA26C464E0@web.de> <4681fb35-bcea-4553-af4c-8621af25055d@11g2000yqp.googlegroups.com> <6c3419ad-8de9-4e56-bab0-23ab0d7d8135@x37g2000yqj.googlegroups.com> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Trace: ger.gmane.org 1255736570 28158 80.91.229.12 (16 Oct 2009 23:42:50 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Fri, 16 Oct 2009 23:42:50 +0000 (UTC) To: help-gnu-emacs@gnu.org Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Sat Oct 17 01:42:40 2009 Return-path: Envelope-to: geh-help-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1MywRR-0004Xn-O4 for geh-help-gnu-emacs@m.gmane.org; Sat, 17 Oct 2009 01:42:38 +0200 Original-Received: from localhost ([127.0.0.1]:38362 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MywRR-0002Km-4e for geh-help-gnu-emacs@m.gmane.org; Fri, 16 Oct 2009 19:42:37 -0400 Original-Path: news.stanford.edu!usenet.stanford.edu!goblin1!goblin.stu.neva.ru!feeder.eternal-september.org!eternal-september.org!not-for-mail Original-Newsgroups: gnu.emacs.help Original-Lines: 49 Original-X-Trace: news.eternal-september.org U2FsdGVkX1/+a/K82n6M+GZ+fAdQiy9iUACFS/X37+eVzHthBNCdIvMpyYrsPV5OiU7yGb/X17Hunik3d7aeADx78U2it1lU9hwwH6ZBu09Nnn5/mONuej6DoT5yZJ1cdPtKbjwkCNGNciIlePdfxQ== Original-X-Complaints-To: abuse@eternal-september.org Original-NNTP-Posting-Date: Fri, 16 Oct 2009 23:36:11 +0000 (UTC) X-Auth-Sender: U2FsdGVkX18D3fr+YgTh131jAYKc6tWmocYHUKWvXoI= Cancel-Lock: sha1:STJaEhOtyYEnafoRqj+wThEiAZg= User-Agent: slrn/0.9.8.1pl1 (Linux) Original-Xref: news.stanford.edu gnu.emacs.help:173957 X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Users list for the GNU Emacs text editor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.help:69041 Archived-At: On 2009-10-16, LanX wrote: > Hi > >> ???  Just use Emacs with a good code viewer (I use my imenu-go.el and >> a handful of other tricks).  Do not see how breaking into parts would >> simplify anything... > > Well it wasn't meant just for me but for all users. How many perl- > developers know elisp? How would breaking into parts fix this? > And how many of them can handle 9000 lines of code? ??? Myself, I see no difference between working with 1000 LOC and 9000 LOC - as far as I can jump between functions without effort. >> > together with a testsuite written in perl? >> >> Supporting a testsuite usually means 1.5x increase of time.  Assume an >> estimate of extra 250hours. Who is going to invest in it?  Given that >> "mine" cperl-mode.el is "already working", definitely not me... > > My idea is that the perl&&emacs-community could/would supply > testcases for every problem/bug they encounter. I do not think this will change my estimate much... (And I do not have so much believe that communities work the way you think they do...) >> > And sorry to say so - some aspects of cperl-mode are very outdated, >> > e.g there is no up-to-date info-file for perldocs. >> >> ???  Make it. > > Actually I'm trying to, but I'm not really sure if it's worth it, > since there are already good html-versions of perldoc, even solutions > which are rendering just-in-time any module in INC. > I didn't mean to demand of you making a new info-file but to suggest > (for the sake of simplicity) to skip an outdated feature from the > menu. a) I do not find it outdated. (IMO, HTML (and PDF) are not suitable for documentation.) b) How would removing it help somebody? Yours, Ilya