unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Richard Stallman <rms@gnu.org>
To: Chong Yidong <cyd@stupidchicken.com>
Cc: lekktu@gmail.com, emacs-devel@gnu.org
Subject: Re: We can use python.el
Date: Mon, 14 May 2007 04:09:41 -0400	[thread overview]
Message-ID: <E1HnVcj-0000f5-HL@fencepost.gnu.org> (raw)
In-Reply-To: <87iraxtzkm.fsf@stupidchicken.com> (message from Chong Yidong on Sat, 12 May 2007 19:03:05 -0400)

    > Are you going to install a fix for the redisplay bug with cancel.pbm?

    It's not a redisplay bug.

It is a bug.  If you think it is not a redisplay bug, what sort
of bug would you call it?

    Is there a compelling reason for fixing this on the branch?  From what
    I understand, there is some problem with the image that causes the bug
    in the first place.

The image is in the Emacs distribution, right?
If the right fix is to fix the image, that is fine with me,
as long as we fix it.

  parent reply	other threads:[~2007-05-14  8:09 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-12 16:47 We can use python.el Richard Stallman
2007-05-12 17:52 ` Chong Yidong
2007-05-12 18:17   ` Juanma Barranquero
2007-05-12 23:03     ` Chong Yidong
2007-05-12 23:36       ` Juanma Barranquero
2007-05-12 23:54         ` Chong Yidong
2007-05-13  1:38           ` Glenn Morris
2007-05-14  8:08             ` Richard Stallman
2007-05-14  8:43               ` Jason Rumney
2007-05-14 14:55                 ` Chong Yidong
2007-05-14 17:45                   ` Glenn Morris
2007-05-14 18:05                     ` Henrik Enberg
2007-05-15  9:47                   ` Richard Stallman
2007-05-15 14:11                     ` Chong Yidong
2007-05-16  1:39                       ` Richard Stallman
2007-05-16  2:51                         ` Chong Yidong
2007-05-16  6:02                       ` Jan Djärv
2007-05-13 10:33       ` Jason Rumney
2007-05-14  8:09       ` Richard Stallman [this message]
2007-05-12 19:02   ` pretest 22.0.100 (was: We can use python.el) Reiner Steib
2007-05-12 22:51     ` pretest 22.0.100 Chong Yidong
2007-05-14 17:01     ` Stefan Monnier
2007-05-14 19:11       ` Juanma Barranquero
2007-05-14 21:26       ` Nick Roberts
2007-05-16 15:48         ` Stefan Monnier
2007-05-17 12:42           ` Andreas Schwab
2007-05-17 12:49           ` Jason Rumney
2007-05-17 13:15             ` David Kastrup
2007-05-17 13:25               ` Jason Rumney
2007-05-17 13:34                 ` David Kastrup
2007-05-17 13:45                 ` Ralf Angeli
2007-05-17 13:57                   ` Ulrich Mueller
2007-05-17 14:02                     ` Alfred M. Szmidt
2007-05-17 13:39             ` Jay Belanger
2007-05-17 14:20             ` Stefan Monnier
2007-05-17 14:32               ` Juanma Barranquero
2007-05-17 16:43               ` Another pretest after 22.0.99 (was: pretest 22.0.100) Reiner Steib
2007-05-13  1:27   ` We can use python.el Michaël Cadilhac
2007-05-14  8:08     ` Richard Stallman

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=E1HnVcj-0000f5-HL@fencepost.gnu.org \
    --to=rms@gnu.org \
    --cc=cyd@stupidchicken.com \
    --cc=emacs-devel@gnu.org \
    --cc=lekktu@gmail.com \
    /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).