From: Neil Jerram <neil@ossau.uklinux.net>
Cc: guile-user@gnu.org
Subject: Re: GDS does not support Emacs 23?
Date: Sat, 23 Sep 2006 22:52:38 +0100 [thread overview]
Message-ID: <87r6y2i72x.fsf@ossau.uklinux.net> (raw)
In-Reply-To: <873baiwnb9.fsf@www.williamxu.com> (William Xu's message of "Sun, 24 Sep 2006 00:38:18 +0800")
William Xu <william.xwl@gmail.com> writes:
> Neil Jerram <neil@ossau.uklinux.net> 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
Guile-user@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-user
next prev parent reply other threads:[~2006-09-23 21:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-19 20:29 GDS does not support Emacs 23? netawater
2006-09-22 18:29 ` Neil Jerram
2006-09-22 23:10 ` William Xu
2006-09-23 9:48 ` Neil Jerram
2006-09-23 16:38 ` William Xu
2006-09-23 21:52 ` Neil Jerram [this message]
2006-09-24 11:56 ` William Xu
2006-09-27 18:40 ` Neil Jerram
2006-09-23 16:30 ` netawater
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87r6y2i72x.fsf@ossau.uklinux.net \
--to=neil@ossau.uklinux.net \
--cc=guile-user@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).