distel-hackers

[Distel-hackers] *Completions* buffer does not closed automatically

[Pierre R. <pra...@ya...>]

The *Completions* buffer does not seem to close automatically after completion.
It seems to be a specific distel problem on my setting. For instance, the
*Completions* buffer closes normally in a plain lisp mode (after multiple
alt-tab in the *Scratch* buffer).

Is it a known problem or it is something specific to my setting ?

Thanks for your help.

Re: [Distel-hackers] *Completions* buffer does not closed automatically

[Bill C. <bil...@gm...>]

Hi Pierre,

Pierre Radermecker <pra...@ya...> writes:

> The *Completions* buffer does not seem to close automatically after completion.
> It seems to be a specific distel problem on my setting. For instance, the
> *Completions* buffer closes normally in a plain lisp mode (after multiple
> alt-tab in the *Scratch* buffer).
>
> Is it a known problem or it is something specific to my setting ?

I believe that distel's completion buffer behaves in a similar manner
to "normal" completion (at least it appears to work the same way for
me). If you're seeing something different, perhaps you could list the
specific steps you take to replicate the behaviour.

- Bill

Re: [Distel-hackers] =?utf-8?q?*Completions*_buffer_does_not_closed?= =?utf-8?q?=09automatically?=

[Pierre R. <pra...@ya...>]

> I believe that distel's completion buffer behaves in a similar manner
> to "normal" completion (at least it appears to work the same way for
> me). If you're seeing something different, perhaps you could list the
> specific steps you take to replicate the behaviour.

Here are the steps with Distel:

1) type "io:f" in the buffer and press alt-tab:
*Completions* buffer open
2) go on typing "orm" in the buffer and press alt-tab:
Automatic completion in the buffer, the *Completions* window stays open.

Here are the steps in the *Scratch* buffer
1) type (gl and press alt-tab:
*Completions* buffer open
2) go on typing "obal-k" in the buffer and press alt-tab:
Automatic completion in the buffer, *Completions* buffer automatically close.

Do you have a similar behavior ?

Thanks for your help (maybe we will meet at OOPSLA in Montréal)

Re: [Distel-hackers] =?utf-8?q?*Completions*_buffer_does_not_closed?= =?utf-8?q?=09automatically?=

[Bill C. <bil...@gm...>]

Hi Pierre,

Pierre Radermecker <pra...@ya...> writes:
>> I believe that distel's completion buffer behaves in a similar manner
>> to "normal" completion (at least it appears to work the same way for
>> me). If you're seeing something different, perhaps you could list the
>> specific steps you take to replicate the behaviour.
>
> Here are the steps with Distel:
>
> 1) type "io:f" in the buffer and press alt-tab:
> *Completions* buffer open
> 2) go on typing "orm" in the buffer and press alt-tab:
> Automatic completion in the buffer, the *Completions* window stays open.
>
> Here are the steps in the *Scratch* buffer
> 1) type (gl and press alt-tab:
> *Completions* buffer open
> 2) go on typing "obal-k" in the buffer and press alt-tab:
> Automatic completion in the buffer, *Completions* buffer automatically close.
>
> Do you have a similar behavior ?

I think I see what's happening. I normally only have one buffer
visible in the Emacs frame, so when I hit M-TAB I always get the
completions buffer shown. You must be displaying 2 buffers in an Emacs
frame. When I do that, I get the results that you do. Does the
attached patch fix the problem for you?

> Thanks for your help (maybe we will meet at OOPSLA in Montréal)

Neat! Yes, I'll be at OOPSLA, but only on Monday (the DLS sessions and
the MSLUG meeting) and a couple of OOPSLA sessions on Tueesday. Will
you be at DLS or MSLUG? 

- Bill

Patch:
Index: elisp/erl-service.el
===================================================================
--- elisp/erl-service.el        (revision 42)
+++ elisp/erl-service.el        (working copy)
@@ -827,6 +827,8 @@
 (defun erl-complete (node)
   "Complete the module or remote function name at point."
   (interactive (list (erl-target-node)))
+  (let ((win (get-buffer-window "*Completions*" 0)))
+    (if win (with-selected-window win (bury-buffer))))
   (let ((end (point))
   (beg (ignore-errors 
          (save-excursion (backward-sexp 1)

Re: [Distel-hackers] =?utf-8?q?*Completions*_buffer_does_not_closed?= =?utf-8?q?=09automatically?=

[Pierre R. <pra...@ya...>]

> I think I see what's happening. I normally only have one buffer
> visible in the Emacs frame, so when I hit M-TAB I always get the
> completions buffer shown. You must be displaying 2 buffers in an Emacs
> frame. When I do that, I get the results that you do. Does the
> attached patch fix the problem for you?

yes, it does. Thanks so much. It is so much better not to have to use the mouse.


> Neat! Yes, I'll be at OOPSLA, but only on Monday (the DLS sessions and
> the MSLUG meeting) and a couple of OOPSLA sessions on Tueesday. Will
> you be at DLS or MSLUG? 
> 

I should attend the DSL on Monday and the 50/50 conference on Tuesday. Look
forward to meeting you there.

Re: [Distel-hackers] =?utf-8?q?*Completions*_buffer_does_not_closed?= =?utf-8?q?=09automatically?=

[Bill C. <bil...@gm...>]

Hi Pierre,

Pierre Radermecker <pra...@ya...> writes:
>> I think I see what's happening. I normally only have one buffer
>> visible in the Emacs frame, so when I hit M-TAB I always get the
>> completions buffer shown. You must be displaying 2 buffers in an Emacs
>> frame. When I do that, I get the results that you do. Does the
>> attached patch fix the problem for you?
>
> yes, it does. Thanks so much. It is so much better not to have to use the mouse.

Ok, I've committed the change.

>> Neat! Yes, I'll be at OOPSLA, but only on Monday (the DLS sessions and
>> the MSLUG meeting) and a couple of OOPSLA sessions on Tueesday. Will
>> you be at DLS or MSLUG? 
>> 
>
> I should attend the DSL on Monday and the 50/50 conference on Tuesday. Look
> forward to meeting you there.

Great, I'll see you at the DSL then.

-Bill