Re: Updated Emacs package, syntax highlighting, new name

Hi Markus,

You wrote:

> Hi Mike,
> 
> Michael Smith writes:
>  > > BTW I've tested 1.5 on the weekend real quick. It was entirely broke
>  > > for me but I didn't have the time to investigate this yet. I'll be
>  > > back with fixes or at least a complete problem description asap.
>  > 
>  > OK -- thanks. Note that when I changed the name to "refdb-mode", I
>  > changed every single variable name as well. So if you still have any
>  > related config variables in your .emacs that you haven't updated to the
>  > new names yet, that may be part of the problem.
>  > 
> 
> I think I've figured it out. First of all, if I cut+paste the elisp
> source from your mails, the backslash ends up as a funny Japanese
> character. Updating from CVS fixes this problem.

I see -- I should have thought about that. The reason for that I have my
mail program, mutt, set up for Japanese, and in Japanese encodings, the
backlash character and Yen symbol are the same character. 

So when I type a backslash in mail messages -- I actually edit as
temporary files vim, it shows up in vim as a Yen symbol. But if I then
open that temp file in Emacs (or some other text editor), before I send
it, it'l still show up as a real backslash. So I guess the problem is
with what mutt does with those messages before I send it them.

I think this is probably also the cause for some of the problems that
Bruce has reported.

Anyway, next time I need to send any code by e-mail, I'll tar it or
compress it first so that mutt doesn't monkey with it.

> Next, there is a small typo ("ID"vs "id") that apparently screws up
> the ID queries, see the appended patch.

Thanks

> Finally, if I use sqlite as a backend (as I did in my preliminary test
> yesterday), all queries for partial strings require a '%'. E.g. to
> find the author entry 'Walsh,N.', you'll either have to type the full
> string or use 'Walsh%'. However, the percent sign is interpreted
> by a format call before it is sent to refdbc, and Emacs complains
> about not getting enough arguments. Can you work around this issue?

Yes, I'm sure I can. I'll get it figured out asap and update the source
in CVS today.

  --Mike

-----BEGIN PGP SIGNATURE-----

iD8DBQE/37MLsGCNMsnBsxkRAiKBAJ9vBPRF15rViQYVNeQ+fayvryygagCeM76P
FqFNPPcIlMXD7SOwzWsGFGs=
=ZwuQ
-----END PGP SIGNATURE-----