unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Dan Jacobson <jidanni@deadspam.com>
Subject: Re: python's error numbers are not parsible by next-error
Date: 08 May 2002 08:53:52 +0800	[thread overview]
Message-ID: <m2wuuf31en.fsf@jidanni.org> (raw)
In-Reply-To: 200205070458.g474wg902449@aztec.santafe.edu

>>>>> "RMS" == Richard Stallman <rms@gnu.org> writes:

RMS> Could you please show me one complete Python error message?
RMS> That will give me the information I need to handle them properly.

$ echo bla|python /dev/stdin
Traceback (innermost last):
  File "/dev/stdin", line 1, in ?
NameError: bla

or something like that.  You really don't want to be asking me, as
I've only used python for one day.  I will post to the python groups
to tell them to post the real answer to gnu.emacs.bug.
-- 
http://jidanni.org/ Taiwan(04)25854780

       reply	other threads:[~2002-05-08  0:53 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <m2n0vds9nk.fsf@jidanni.org>
     [not found] ` <200205070458.g474wg902449@aztec.santafe.edu>
2002-05-08  0:53   ` Dan Jacobson [this message]
     [not found]     ` <200205090245.g492jVi05603@aztec.santafe.edu>
2002-05-09 21:08       ` python's error numbers are not parsible by next-error Dan Jacobson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=m2wuuf31en.fsf@jidanni.org \
    --to=jidanni@deadspam.com \
    --cc=kindly_remove_this_part_first_jidanni@ms46.hinet.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).