[Erc-discuss] Re: Setting erc-auto-query to 'bury

[Peter Jones]

Peter Jones <address@hidden> writes:
> William Xu <address@hidden> writes:
>> Peter Jones <address@hidden> writes:
>>
>>> I currently have erc-auto-query set to 'bury.  I would expect that when
>>> someone queries me, that ERC would create a new buffer, and then bury
>>> it.
>>>
>>> What happens instead is that when the buffer does not yet exist, ERC
>>> creates it, and makes it the current buffer.  Thus, when I'm typing
>>> somewhere, and somebody queries me, my typing is interrupted with a new
>>> ERC buffer.
>>>
>>> What am I doing wrong?
>>
>> You missed this? 
>>
>>   (setq erc-join-buffer 'bury)
>
> Hmm, maybe I can't do what I want then.  I have erc-join-buffer set to
> 'buffer, because if I'm in an ERC buffer, and do something like /join, I
> want that new buffer to be my current buffer.
>
> However, if ERC is creating a new buffer, and I'm doing something else,
> say writing code, I certainly don't want the new ERC buffer selected and
> made current.
>
> I'll play with erc-join-buffer, thanks.

The erc-join-buffer variable wasn't the problem.  Looks like this is a
bug in ERC that was fixed in commit 074f92f by jbms:

,----
| @@ -4020,7 +4020,7 @@ and as second argument the event parsed as a vector."
|                (string= target (erc-current-nick)))
|            (not (erc-get-buffer query proc))
|            (not (erc-is-message-ctcp-and-not-action-p msg))
| -          (let ((erc-join-buffer erc-auto-query))
| +          (let ((erc-query-display erc-auto-query))
|              (erc-cmd-QUERY query))
|            nil))))
`----

Now I have to decided if I want to patch ERC 5.3, or take the plunge and
play with the bleeding edge.

-- 
Peter Jones, http://pmade.com
pmade inc.  Louisville, CO US