[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: python's error numbers are not parsible by next-error

From: Dan Jacobson
Subject: Re: python's error numbers are not parsible by next-error
Date: 10 May 2002 05:08:58 +0800
User-agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.1

>>>>> "R" == Richard Stallman <address@hidden> writes:

R> Does this handle it right?

I sure hope so.  Wouldn't want the number one editor not to work with
the number one language.  Unfortunately, due to limited facilities* it
is not convenient for me to test it.  My role was to alert those
number one folks that there was a meshing improvement needed.
Besides, I only studied python for one day, and that was a few weeks
ago.  Its reviews say it is the coolest, so I was upset that the two
number ones didn't mesh yet.
* mental. 

[ P.S. I have gone back to "spam saftey tab on email address" since each
account I had got buried in spam more than POP could download before
procmail could get to it, and all I have left is the one the ISP gave
me. Wonder how long that will last. ]

R> *** compile.el.~1.253.~      Sat Apr  6 10:50:48 2002
R> --- compile.el       Wed May  8 16:16:47 2002
R> ***************
R> *** 363,368 ****
R> --- 363,372 ----
R>       (".*\"\\([^,\" \n\t]+\\)\", lines? \
R>   \\([0-9]+\\)\\([\(.]\\([0-9]+\\)\)?\\)?[:., (-]" 1 2 4)
R> +     ;; Python:
R> +     ;;  File "foobar.py", line 5, blah blah
R> +    ("^File \"\\([^,\" \n\t]+\\)\", line \\([0-9]+\\)," 1 2)
R> + 
R>       ;; Caml compiler:
R>       ;;  File "foobar.ml", lines 5-8, characters 20-155: blah blah
R>      ("^File \"\\([^,\" \n\t]+\\)\", lines? \\([0-9]+\\)[-0-9]*, characters? 
\\([0-9]+\\)" 1 2 3)
http://jidanni.org/ Taiwan(04)25854780

reply via email to

[Prev in Thread] Current Thread [Next in Thread]