William Xu <[EMAIL PROTECTED]> writes:
> Neil Jerram <[EMAIL PROTECTED]> writes:
>
>> Yes, that is a problem that isn't well handled at the moment. I've
>> been thinking about this and have two possible solutions in mind.
>>
>> 1. (Easier) Change the GDS elisp code so that the gds-server process
>> is only started when needed. This would probably avoid most
>> occurrences of the reported problem, because most users will
>> probably do GDS stuff in just one Emacs session.
>>
>> 2. (Harder) Create a new GDS "broker" component to handle the
>> possibility of multiple Emacs sessions running multiple
>> gds-servers.
>>
>> Any thoughts/preference?
>
> i'd prefer solution 2, but solution 1 is acceptable.
I agree. I should get to this in the next month or so. If anyone
would like to help, please let me know.
> As for solution 1, maybe we could let newer gds-server override
> older one, just like emacs server's way.
That's interesting. How can one call bind() so that it steals the
address and port number from a previous listen socket?
Regards,
Neil
_______________________________________________
Guile-user mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/guile-user
