There was a discussion about `read-passwd' accepting RET as a passphrase character here recently. It seems as if lazy-lock can cause this. However, I have never used lazy-lock, and I get this buggy `read-passwd' behaviour from time to time anyway. O well, maybe it is worth a try for some of the others that reported this. (The bug in `read-passwd' is triggered when you change XEmacs frames, somehow. It is difficult to reproduce.) ---------- Forwarded message ---------- Date: Wed, 26 Sep 2001 21:33:57 -0700 (PDT) From: Don La Dieu <negapluck(a)yahoo.com&gt; To: mailcrypt-bugs(a)lists.sourceforge.net Subject: bug #436809 (mailcrypt accepts "enter" as a passphrase char) "FIXED" -----BEGIN PGP SIGNED MESSAGE----- Brian emailed me this week about a bug report I sent directly to him, but is also covered in Sourceforge bug #436809. (Did I write that?) The short of it is: when you try to enter your passphrase, mailcrypt accepts Enter/Return as a character. This past summer I fixed the problem and promptly forgot about it. After getting Brian's email I poked around to try and figure out what I did, and found a comment (GASP!) in my ~/.emacs. Here it is: ;;; Here we setup font-lock (ie: syntax highlighting)... ;;; *WARNING* lazy-lock breaks mailcrypt (can't use 'Return' key) ;(add-hook 'font-lock-mode-hook 'turn-on-lazy-lock) ;(setq lazy-lock-stealth-time nil) So, if this happens to you, disable lazy-lock. If that doesn't work, then you have bigger problems. :) No, I haven't looked to see where the conflict is in the two packages, and I probably never will. fast-lock is working just peachy for me. __________________________________________________ Do You Yahoo!? Listen to your Yahoo! Mail messages from any phone. http://phone.yahoo.com _______________________________________________ mailcrypt-bugs mailing list mailcrypt-bugs(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mailcrypt-bugs