Gnus development mailing list
 help / color / mirror / Atom feed
From: Daiki Ueno <ueno@unixuser.org>
To: XeCycle <xecycle@gmail.com>
Cc: ding@gnus.org
Subject: Re: Inconsistency between `mml2015-use' and `mml2015-verify-function'
Date: Fri, 26 Aug 2011 18:04:55 +0900	[thread overview]
Message-ID: <m34o14pmq0.fsf-ueno@unixuser.org> (raw)
In-Reply-To: <877h6038qg.fsf@gmail.com> (xecycle@gmail.com's message of "Fri, 26 Aug 2011 15:57:59 +0800")

XeCycle <xecycle@gmail.com> writes:

>>>> Debugger entered--Lisp error: (wrong-number-of-arguments #[(target
>>>> old new) "\303\b
>>>> #\207" [old new target replace-regexp-in-string] 4] 4)
>>>>   mm-replace-in-string("\ntest encrypt.\n" "\n" "\n" t)
>>
>> So I guess the culprit is a third-party replace-regexp-in-string defined
>> somewhere.  Could you check where it is defined, with C-h f
>> replace-regexp-in-string?
>
> It showed these:
>
>> replace-regexp-in-string is a compiled Lisp function in
>> `subr.el'.
>
>> (replace-regexp-in-string REGEXP REP STRING &optional FIXEDCASE
>> LITERAL SUBEXP START)

Well, then how about mm-replace-in-string?  Is mm-util.elc correctly
located under /usr/local/share/emacs/24.0.50/lisp/gnus/ or such?

I mean, mm-replace-in-string seems not working for you.  Could you try:
(mm-replace-in-string "\ntest encrypt.\n" "\n" "\n" t)

Regards,
-- 
Daiki Ueno



  reply	other threads:[~2011-08-26  9:04 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-25 12:49 XeCycle
2011-08-25 20:45 ` Daiki Ueno
2011-08-26  1:42   ` XeCycle
2011-08-26  2:00     ` Daiki Ueno
2011-08-26  7:57       ` XeCycle
2011-08-26  9:04         ` Daiki Ueno [this message]
2011-08-26 10:44           ` XeCycle
2011-08-26 14:06           ` XeCycle
2011-08-26 23:29             ` Daiki Ueno
2011-08-27  0:26               ` XeCycle
2011-09-10 22:10             ` Lars Magne Ingebrigtsen

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=m34o14pmq0.fsf-ueno@unixuser.org \
    --to=ueno@unixuser.org \
    --cc=ding@gnus.org \
    --cc=xecycle@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).