Re: Unable to use <space> & other characters in message mode

Re: Unable to use <space> & other characters in message mode

[Reiner Steib]

On Thu, Nov 19 2009, Graham Murray wrote:

> Gnus v5.13
> GNU Emacs 23.1.50.1 (i686-pc-linux-gnu, GTK+ Version 2.18.3)
>  of 2009-11-19 on newton

> When composing mail, pressing space (and other characters which
> terminate a word) emacs gives an error and backtrace. Pressing C-q
> before the character allows it to be entered. I am using emacs cvs
> retrieved about 1 hour ago.

When did it start to fail?  I don't recall any recent related changes
in message mode.

Maybe this one:

,----
| 2009-11-19  Stefan Monnier  <monnier@iro.umontreal.ca>
| 
| 	* abbrev.el (abbrev-with-wrapper-hook): (re)move...
| 	* simple.el (with-wrapper-hook): ...to here.  Add argument `args'.
| 	* minibuffer.el (completion-in-region-functions): New hook.
| 	(completion-in-region): New function.
| 	* emacs-lisp/lisp.el (lisp-complete-symbol):
| 	* pcomplete.el (pcomplete-std-complete): Use it.
`----

Maybe loading message.el and abbrev.el (instead of the *.elc) files
gives a better backtrace.

As it doesn't seem to fail for everyone, it might be only in your
setup.

Bye, Reiner.
-- 
       ,,,
      (o o)
---ooO-(_)-Ooo---  |  PGP key available  |  http://rsteib.home.pages.de/

Re: Unable to use <space> & other characters in message mode

[Reiner Steib]

On Sat, Nov 21 2009, Reiner Steib wrote:

> When did it start to fail?  I don't recall any recent related changes
> in message mode.
>
> Maybe this one:
>
> ,----
> | 2009-11-19  Stefan Monnier  <monnier@iro.umontreal.ca>
> | 
> | 	* abbrev.el (abbrev-with-wrapper-hook): (re)move...
> | 	* simple.el (with-wrapper-hook): ...to here.  Add argument `args'.
> | 	* minibuffer.el (completion-in-region-functions): New hook.
> | 	(completion-in-region): New function.
> | 	* emacs-lisp/lisp.el (lisp-complete-symbol):
> | 	* pcomplete.el (pcomplete-std-complete): Use it.
> `----
>
> Maybe loading message.el and abbrev.el (instead of the *.elc) files
> gives a better backtrace.
>
> As it doesn't seem to fail for everyone, it might be only in your
> setup.

Please first try "make bootstrap" ...

,----[ http://thread.gmane.org/jwvtywqcypf.fsf-monnier+emacsbugreports@gnu.org ]
| From: Stefan Monnier <monnier@iro.umontreal.ca>
| Subject: bug#4967: 23.1.50; mail abbrev to aggresive
| Newsgroups: gmane.emacs.bugs, gmane.emacs.pretest.bugs
| To: john ffitch <jpff@codemist.co.uk>
| Cc: emacs-pretest-bug@gnu.org, 4967@emacsbugs.donarmstrong.com
| Date: Thu, 19 Nov 2009 10:38:00 -0500
| Message-ID: <jwvtywqcypf.fsf-monnier+emacsbugreports@gnu.org>
| Reply-To: Stefan Monnier <monnier@iro.umontreal.ca>,
| 	4967@emacsbugs.donarmstrong.com
| 
| > Debugger entered--Lisp error: (invalid-function with-wrapper-hook)
| 
| Try "make bootstrap".
| 
|         Stefan
`----

Bye, Reiner.
-- 
       ,,,
      (o o)
---ooO-(_)-Ooo---  |  PGP key available  |  http://rsteib.home.pages.de/

Re: Unable to use <space> & other characters in message mode

[Graham Murray]

Reiner Steib <reinersteib+gmane@imap.cc> writes:

> On Thu, Nov 19 2009, Graham Murray wrote:
>
>> Gnus v5.13
>> GNU Emacs 23.1.50.1 (i686-pc-linux-gnu, GTK+ Version 2.18.3)
>>  of 2009-11-19 on newton
>
>> When composing mail, pressing space (and other characters which
>> terminate a word) emacs gives an error and backtrace. Pressing C-q
>> before the character allows it to be entered. I am using emacs cvs
>> retrieved about 1 hour ago.
>
> When did it start to fail?  I don't recall any recent related changes
> in message mode.
>
> Maybe this one:
>
> ,----
> | 2009-11-19  Stefan Monnier  <monnier@iro.umontreal.ca>
> | 
> | 	* abbrev.el (abbrev-with-wrapper-hook): (re)move...
> | 	* simple.el (with-wrapper-hook): ...to here.  Add argument `args'.
> | 	* minibuffer.el (completion-in-region-functions): New hook.
> | 	(completion-in-region): New function.
> | 	* emacs-lisp/lisp.el (lisp-complete-symbol):
> | 	* pcomplete.el (pcomplete-std-complete): Use it.
> `----
>
> Maybe loading message.el and abbrev.el (instead of the *.elc) files
> gives a better backtrace.
>
> As it doesn't seem to fail for everyone, it might be only in your
> setup.

I think that it was only a temporary problem, as it works normally again
now that I have done another CVS update (emacs HEAD) and rebuilt
emacs. Maybe someone was committing at the same time as I was updating
my working directory, and I pulled in a partially updated change.