Gnus development mailing list
 help / color / mirror / Atom feed
From: Reiner Steib <reinersteib+gmane@imap.cc>
To: ding@gnus.org, wahjava@gmail.com (Ashish Shukla आशीष शुक्ल)
Cc: bugs@gnus.org
Subject: Bogus definition of replace-in-string in color-theme.el (was: Error)
Date: Wed, 14 May 2008 21:48:41 +0200	[thread overview]
Message-ID: <v9prrovf8m.fsf@marauder.physik.uni-ulm.de> (raw)
In-Reply-To: <87abisj1bv.fsf@chateau.d.lf> ("Ashish Shukla =?utf-8?B?4KSG?= =?utf-8?B?4KS24KWA4KS3IOCktuClgeCkleCljeCksiIncw==?= message of "Wed, 14 May 2008 21:59:56 +0530")

On Wed, May 14 2008, Ashish Shukla आशीष शुक्ल wrote:

> While going through some of the messages in Maildir, I got the
> following error:
>
> ggogle in #emacs concluded that it is due to wrong number of arguments
> passed in 'mm-replace-in-string' function (which is actually an alias ro
> 'replace-in-string' function in color-theme.el) call, which expects 3,
> but actually 4 arguments are passed.
>
> ---->8---->8----
> Debugger entered--Lisp error: (wrong-number-of-arguments #[(target old new)
[...]
> Hope to see it fixed soon.

This is a bug in `color-theme.el' which causes problems with Gnus,
emacs-jabber, muse etc.  I already pointed out the bug to it's
maintainer.  Alas, without any response upto now.

,----
| From: Reiner Steib
| Subject: Bogus definition of replace-in-string in color-theme.el (was: Fwd: Re: Error viewing PGP/mime signed messages)
| To: Xavier Maillard <xma // gnu.org>
| Cc: Katsumi Yamaoka <yamaoka@jpl.org>
| Date: Wed, 19 Mar 2008 13:39:51 +0100
| Message-ID: <v9d4pqj39g.fsf@marauder.physik.uni-ulm.de>
| 
| Hi Xavier,
|
| please fix the use of `replace-in-string' in color-theme.el ASAP (see
| the problem described below and in <https://gna.org/bugs/?9494>).
| 
| No package should ever define functions and variables out of it's own
| name space:
| 
| ,----[ (info "(elisp)Coding Conventions") ]
| |    * If a package needs to define an alias or a new function for
| |      compatibility with some other version of Emacs, name it with the
| |      package prefix, not with the raw name with which it occurs in the
| |      other version.  Here is an example from Gnus, which provides many
| |      examples of such compatibility issues.
| | 
| |           (defalias 'gnus-point-at-bol
| |             (if (fboundp 'point-at-bol)
| |                 'point-at-bol
| |               'line-beginning-position))
| `----
| [ Forwarded articles from
|   <http://thread.gmane.org/gmane.emacs.gnus.general/66521/focus=66522>
|   stripped. ]
`----

See <http://thread.gmane.org/gmane.emacs.gnus.general/66521/focus=66522>
or article <b4my78gr3rs.fsf@jpl.org> for a patch to `color-theme.el'.

Bye, Reiner.
-- 
       ,,,
      (o o)
---ooO-(_)-Ooo---  |  PGP key available  |  http://rsteib.home.pages.de/



       reply	other threads:[~2008-05-14 19:48 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <87abisj1bv.fsf@chateau.d.lf>
2008-05-14 19:48 ` Reiner Steib [this message]
2008-05-14 20:12   ` Bogus definition of replace-in-string in color-theme.el Ashish Shukla आशीष शुक्ल
2008-05-14 20:30     ` Reiner Steib

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

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

  git send-email \
    --in-reply-to=v9prrovf8m.fsf@marauder.physik.uni-ulm.de \
    --to=reinersteib+gmane@imap.cc \
    --cc=Reiner.Steib@gmx.de \
    --cc=bugs@gnus.org \
    --cc=ding@gnus.org \
    --cc=wahjava@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.
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 NNTP newsgroup(s).