[slime-devel] Re: default connections

[Roman Budzianowski]

I think you are misunderstanding the purpose of the feature.
It seems to me very valuable when one works with more then
one lisp, i.e. connection at a time.

Being able to do C-c C-c in a buffer without worrying which lisp it's  
going
to go to is a good thing.

Roman

On Sep 26, 2008, at 2:13 PM, Tobias C. Rittweiler wrote:

> Knut Olav Bøhmer <knut-olav.bohmer at telenor.com> writes:
>
>> Tobias C. Rittweiler wrote:
>>
>>    Slime-cycle-connections making the new connection buffer-local
>> means for example that making another connection the default
>> connection via slime-list-connections will lead to surprises.
>>
>> There will be no surprises. You will anyway need to keep track of  
>> your
>> connection. You can do that by looking at the connection-name in the
>> mode-line.
>
> It will lead to surprises, as the connection to become the new default
> won't become the connection of .lisp buffers you used
> `slime-cycle-connection' in.
>
>
>>    Additionally, buffer-local connections can become stale, rendering
>> the .lisp buffer useless.
>>
>> If the buffer-local connection become sale, you will avoid running
>> lisp-commands in another random default connection.
>
> It became only stale because it was unnecessarily made buffer-local by
> `slime-cycle-connection'.
>
>
> I'll remove the line in question. It seems to be highly specific to  
> your
> personal use case; you can easily write something for your own  
> personal
> use on top of a `slime-cycle-connection' that doesn't make the new
> connection buffer-local automatically.
>
>  -T.
>
> _______________________________________________
> slime-devel site list
> slime-devel at common-lisp.net
> http://common-lisp.net/mailman/listinfo/slime-devel