unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Dhruva Krishnamurthy" <devel@member.fsf.org>
Cc: Stefan Monnier <monnier@iro.umontreal.ca>,
	Emacs Devel <emacs-devel@gnu.org>
Subject: Re: GNU Emacs: Client/Server
Date: Fri, 06 Feb 2004 15:32:40 +0530	[thread overview]
Message-ID: <20040206100240.4293B4F@frontend3.messagingengine.com> (raw)
In-Reply-To: <x51xp8y1pq.fsf@lola.goethe.zz>


On 06 Feb 2004 10:52:17 +0100, "David Kastrup" <dak@gnu.org> said:
> "Dhruva Krishnamurthy" <devel@member.fsf.org> writes:
> 
> > On 05 Feb 2004 10:05:01 -0500, "Stefan Monnier"
> > <monnier@iro.umontreal.ca> said:
> > > Maybe you know it and you're just experimenting, but I just want to make
> > > sure you do realize that gnuclient/gnuserver already solve those
> > > problems, so clearly there isn't much point is creating yet another system.
> > 
> > What about portability and distribution issues since it is written in C?
> 
> What about it?

Sorry for not being clear. I meant using platform dependend stuff like
sockets and other headers which are not available on windoze platform in
the same way as it is on Unix.

> > My idea was to write the whole stuff in Elisp and allow Emacs to
> > handle the platform dependend stuff.  with this approach, I can be
> > sure that where Emacs runs, the client/server code will run with no
> > extra effort.
> 
> I'd be surprised if you manage to compile Emacs without a C compiler
> on any platform.

In the above statement, I meant the porting issue (in writing it in
Elisp) and not the compilation part of GNU Emacs. I would like to know if
there is anyone who has succeeded in building all the sources in
"lib-src" folder and user "server.el" on a windoze platform (not using
the cygwin layer).

-dhruva
________________________________________
Dhruva Krishnamurthy
Proud FSF member: #1935
http://schemer.fateback.com/

  reply	other threads:[~2004-02-06 10:02 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-29 11:12 GNU Emacs: Client/Server Dhruva Krishnamurthy
2004-01-29 12:03 ` Jan D.
2004-01-29 12:13   ` Dhruva Krishnamurthy
2004-01-29 16:18     ` Kim F. Storm
     [not found]       ` <20040130045855.1A6A92E@frontend3.messagingengine.com>
2004-01-30 10:38         ` Kim F. Storm
2004-01-30 10:31           ` Dhruva Krishnamurthy
2004-01-30 13:03             ` Kim F. Storm
2004-02-01  8:01           ` Richard Stallman
2004-02-01 23:49             ` Kim F. Storm
     [not found]               ` <20040202092212.C73932E@frontend3.messagingengine.com>
     [not found]                 ` <m3isipwuog.fsf@kfs-l.imdomain.dk>
     [not found]                   ` <jwvr7xdjz98.fsf-monnier+emacs/devel@asado.iro.umontreal.ca>
     [not found]                     ` <m31xpdwgot.fsf@kfs-l.imdomain.dk>
     [not found]                       ` <jwvektdifzf.fsf-monnier+emacs/devel@asado.iro.umontreal.ca>
     [not found]                         ` <20040203044651.3E26A31@frontend3.messagingengine.com>
     [not found]                           ` <jwvektc5jed.fsf-monnier+emacs/devel@asado.iro.umontreal.ca>
2004-02-05  9:52                             ` Dhruva Krishnamurthy
2004-02-05 15:05                               ` Stefan Monnier
2004-02-06  5:37                                 ` Dhruva Krishnamurthy
2004-02-06  9:52                                   ` David Kastrup
2004-02-06 10:02                                     ` Dhruva Krishnamurthy [this message]
2004-02-06 13:36                                   ` Stefan Monnier
2004-02-07 19:32                                   ` Richard Stallman
2004-01-29 12:41 ` Kim F. Storm
2004-01-29 12:17   ` Dhruva Krishnamurthy
2004-01-29 13:46     ` Roman Belenov
2004-01-30  5:04       ` Dhruva Krishnamurthy
2004-01-29 15:35 ` Stefan Monnier
2004-02-02 15:15   ` Lőrentey Károly
2004-02-02 16:01     ` Stefan Monnier

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/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20040206100240.4293B4F@frontend3.messagingengine.com \
    --to=devel@member.fsf.org \
    --cc=emacs-devel@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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).