unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Kevin Rodgers <ihs_4664@yahoo.com>
Subject: Re: bug in auto-capitalize.el
Date: Wed, 08 Sep 2004 16:15:50 -0600	[thread overview]
Message-ID: <413F8496.4070402@yahoo.com> (raw)
In-Reply-To: mailman.2018.1094672043.1998.bug-gnu-emacs@gnu.org

Norman Werner wrote:
 > The following mail is from the original bug report to the maintainer
 > of auto-capitalize.el   kevinr@ihs.com
 >
 > Unfortunately the mail could not be delivered :
 >
 > SMTP error from remote mailer after RCPT TO:<kevinr@ihs.com>:
 > host mail1.ihs.com [170.207.70.222]: 553 5.7.1
 > <kevinr@ihs.com>... norman.werner@student.uni-magdeburg.de not
 > allowed to send to recipient
 >
 > Since I could not contact the maintainer directly I am now writing to
 > your address

Please don't bother the Emacs maintainers with something they are not
responsible for.  If you had taken even a minute to search for me via
my name (on e.g. http://groups.google.com/) you would have found my
current address: <ihs_4664@yahoo.com>.

 > -------Beginning of Message ------------
 >
 >
 > I experienced what I think is a bug in auto-capitalize.
 >
 > On (gnu)emacs 21.3.1 event-to-character is called with 4 arguments while a
 > maximum of 2 is allowed. So the debugger is entered.
 >
 > I think the offending code is in defun auto-capitalize:
 > ....
 > (let ((self-insert-char
 >          (cond ((fboundp 'event-to-character) ; XEmacs
 >                     (event-to-character last-command-event
 > 		 
	nil nil t))
 >                (t last-command-event)))) ; GNU Emacs
 > ...
 >
 > The comments indicates that you think that  event-to-character is
 > unbound in gnu-emacs. But it exists as a function of one (optional two
 > arguments.)

No, it doesn't exist at all in GNU Emacs 21.3.  You can confirm that
by invoking emacs with the -q and --no-site-file command line options,
and typing `C-h v event-to-character'.

You must be loading some kind of XEmacs compatibility package that is
ironically incompatible with XEmacs.

 > I propose the fixes :
 > (let ((self-insert-char
 >          (cond ((featurep 'xemacs) ; XEmacs
 >                     (event-to-character last-command-event
 > 		 
	nil nil t))
 >                (t last-command-event)))) ; GNU Emacs
 > Or
 >
 > (let ((self-insert-char
 >          (cond ((featurep 'xemacs) ; XEmacs
 >                     (event-to-character last-command-event
 > 		 
	nil nil t))
 >                (t (event-to-character last-command-event))))) ; GNU Emacs
 >
 > I couldn't test this since I don't have xemacs installed. But It should be ok

(featurep 'xemacs) is evil.

-- 
Kevin Rodgers

       reply	other threads:[~2004-09-08 22:15 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.2018.1094672043.1998.bug-gnu-emacs@gnu.org>
2004-09-08 22:15 ` Kevin Rodgers [this message]
     [not found] ` <mailman.2045.1094682093.1998.bug-gnu-emacs@gnu.org>
2004-09-09 16:02   ` bug in auto-capitalize.el Kevin Rodgers
2004-09-09  3:27 Norman Werner

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

  List information: https://www.gnu.org/software/emacs/

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

  git send-email \
    --in-reply-to=413F8496.4070402@yahoo.com \
    --to=ihs_4664@yahoo.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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).