Ronan> I'm patching this rather haphazardly right now. Is it just me,
Ronan> or is elisp lacking either (a) a means of regexp-escaping a
Ronan> string, and/or (b) a function that does what INSTR used in
Ronan> BASIC, i.e. tell you if one string occurs within another
Ronan> (without any of that reg
Ronan Waide <[EMAIL PROTECTED]> writes:
> (b) a function that does what INSTR used in BASIC, i.e. tell you if
> one string occurs within another (without any of that regexp stuff,
> obviously)?
(require 'cl-seq)
(search "" "hihihihihi q hihihihihi")
--
Alan Shutko <[EMAIL PROTECTED]> -
On April 3, [EMAIL PROTECTED] said:
>
> (a)
>
> regexp-quote is a built-in function.
>
> Return a regexp string which matches exactly STRING and nothing else.
>
> (regexp-quote STRING)
>
> Howard
>
Yay! thanks, now that I know what I'm looking for, I can find it in
the manual :)
Waider.
--
On Wednesday Apr 3, 2002, Ronan Waide wrote:
> On March 28, [EMAIL PROTECTED] said:
> > -BEGIN PGP SIGNED MESSAGE-
> > Hash: SHA1
> >
> > Hi,
> >
> > I just tried to use bbdb-merge-file with bbdb from current cvs (update
> > today). I
On March 28, [EMAIL PROTECTED] said:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Hi,
>
> I just tried to use bbdb-merge-file with bbdb from current cvs (update
> today). I get the following backtrace
I'm patching this rather haphazardly right now. Is it ju
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
I just tried to use bbdb-merge-file with bbdb from current cvs (update
today). I get the following backtrace
,
| Signaling: (invalid-regexp "Unmatched [ or [^")
| string-match("[MDN:5536:EXCH" "[MDN:5536:EXCH&q
Hmm, that was bizarre. Here's what I'd intended to appear on the list:
On December 22, [EMAIL PROTECTED] said:
>
> Yep, I'd managed to dig this up myself, and discovered that the
> breakage is not related to the file format change. I need to find out
> what it IS related to before I can fix it.
Did I miss the mime encoding on this?
> T24gRGVjZW1iZXIgMjIsIHBhdHJpY2tAY2hhb3Mub3JnLnVrIHNhaWQ6DQo+IA0KPiAgIG1hcGNh
--snipped--
Chris
___
bbdb-info mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/mailman/listinfo/bbdb-info
On December 22, [EMAIL PROTECTED] said:
>
> mapcar(#[(rec) "\304 \205
> ! #\207" [rec match-fun r override bbdb-merge-record] 4] ())
> bbdb-merge-file("/tmp/.bbdb")
> call-interactively(bbdb-merge-file)
> execute-extende
Waider:
> > The main reason why I upgraded to 2.2 was the new bbdb-merge
> > functionality, but when I try bbdb-merge-file I get the error
> >
> > Wrong type argument: listp, -129453780
>
> Can you please set stack-track-on-error to t and reproduce this so I
On December 10, [EMAIL PROTECTED] said:
>
> The main reason why I upgraded to 2.2 was the new bbdb-merge
> functionality, but when I try bbdb-merge-file I get the error
>
> Wrong type argument: listp, -129453780
Can you please set stack-track-on-error to t and reproduce this
The main reason why I upgraded to 2.2 was the new bbdb-merge
functionality, but when I try bbdb-merge-file I get the error
Wrong type argument: listp, -129453780
Has anyone else had this problem? I haven't tried to investigate it
yet, but if I replace my real .bbdb files with test
Patrick Campbell-Preston writes:
> The main reason why I upgraded to 2.2 was the new bbdb-merge
> functionality, but when I try bbdb-merge-file I get the error
> Wrong type argument: listp, -129453780
M-: (setq debug-on-error t)
This will get you a stack trace, which can he
13 matches
Mail list logo
