Re: gcc tab completion strangeness

[asjo@koldfront.dk (Adam Sjøgren)]

On Mon, 31 Jan 2011 10:05:38 -0500, Stefan wrote:

>> I looks quite ugly.

> Yes, I'd rather not hard code that much info about BBDB-internals in
> message.el.  Can you try the patch below instead, which should work
> about as well, but without relying on internal knowledge about BBDB?

In my brief testing your patch below works great - thanks for looking
into this!

> === modified file 'lisp/gnus/message.el'
> --- lisp/gnus/message.el	2011-01-25 04:08:28 +0000
> +++ lisp/gnus/message.el	2011-01-31 15:04:55 +0000
> @@ -7867,7 +7867,12 @@
>  	 (eudc-expand-inline))
>  	((and (memq 'bbdb message-expand-name-databases)
>  	      (fboundp 'bbdb-complete-name))
> -	 (bbdb-complete-name))
> +         (let ((starttick (buffer-modified-tick)))
> +           (or (bbdb-complete-name)
> +               ;; Apparently, bbdb-complete-name can return nil even when
> +               ;;  completion took place.  So let's double check the buffer was
> +               ;;  not modified.
> +               (!= starttick (buffer-modified-tick)))))
>  	(t
>  	 (expand-abbrev))))
 

  Best regards,

    Adam

-- 
 "My ethicator machine must've had a built-in moral           Adam Sjøgren
  compromise spectral release phantasmatron!"            asjo@koldfront.dk