Your message dated Sun, 30 Mar 2008 21:18:10 +0000
with message-id <[EMAIL PROTECTED]>
and subject line Bug#415485: fixed in pylint 0.14.0-2.1
has caused the Debian Bug report #415485,
regarding /usr/share/emacs/site-lisp/pylint/pylint.el: binds keys
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [EMAIL PROTECTED]
immediately.)


-- 
415485: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=415485
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: pylint
Version: 0.12.1-1
Severity: normal
File: /usr/share/emacs/site-lisp/pylint/pylint.el

pylint.el binds [f1], [f2] and [f3] in the python mode map, without
asking.  It should not.

I personally feel that pylint.el should not bind any keys at all.  If
you feel pylint.el really must bind keys, I would draw your attention
to the recommendations of the Emacs Lisp manual, such as

    The key sequences bound in a minor mode should consist of `C-c'
    followed by one of `.,/?`'"[]\|~!#$%^&*()-_+='.  (The other
    punctuation characters are reserved for major modes.)

Also note that next-error is (apparently) already bound to C-x ` in
all buffers.  I strongly feel that mode-local bindings for next-error
and/or previous-error are also quite silly.

Finally, I advise you to use EVAL-AFTER-LOAD (and DEFINE-KEY) instead
of a hook, since the forms in python.el really only need to be
evaluated once per emacs process, not every time the user opens a
Python file.


--- End Message ---
--- Begin Message ---
Source: pylint
Source-Version: 0.14.0-2.1

We believe that the bug you reported is fixed in the latest version of
pylint, which is due to be installed in the Debian FTP archive:

pylint_0.14.0-2.1.diff.gz
  to pool/main/p/pylint/pylint_0.14.0-2.1.diff.gz
pylint_0.14.0-2.1.dsc
  to pool/main/p/pylint/pylint_0.14.0-2.1.dsc
pylint_0.14.0-2.1_all.deb
  to pool/main/p/pylint/pylint_0.14.0-2.1_all.deb



A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to [EMAIL PROTECTED],
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Yaroslav Halchenko <[EMAIL PROTECTED]> (supplier of updated pylint package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [EMAIL PROTECTED])


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Format: 1.7
Date: Mon, 03 Mar 2008 22:22:07 -0500
Source: pylint
Binary: pylint
Architecture: source all
Version: 0.14.0-2.1
Distribution: unstable
Urgency: low
Maintainer: Sylvain Thénault <[EMAIL PROTECTED]>
Changed-By: Yaroslav Halchenko <[EMAIL PROTECTED]>
Description: 
 pylint     - python code static checker
Closes: 415485 427244 431653 448102
Changes: 
 pylint (0.14.0-2.1) unstable; urgency=low
 .
   * Non-maintainer upload.
   * BF: flavor -> debian-emacs-flavor in startup
   * NF: added pylint-options variable visible to users to tune up (closes:
     #427244)
   * BF: reenabled installation of pylint.el (closes: #448102)
   * Recent upstream of pylint.el fixed few bugs which weren't closed
     in the upload to Debian. Since this is first upload which enables
     pylint.el, imho it is ok to close them here (closes: #415485, #431653)
Files: 
 5bfc40905cb83f6ad0e42585489058d1 718 python optional pylint_0.14.0-2.1.dsc
 00b84886f3bf5e6bd33cccbb52c6904e 6714 python optional pylint_0.14.0-2.1.diff.gz
 2d347f824b77284a91c8539963abdf6a 122482 python optional 
pylint_0.14.0-2.1_all.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFHzMZWjRFFY3XAJMgRAqtgAJwPQpnZXAUfxYwBdNdOJy/5unVetgCgkxmw
mjYUM45kJMzVm9s8hP78AwA=
=lw4H
-----END PGP SIGNATURE-----



--- End Message ---

Reply via email to