Re: [h-e-w] Some info about Gnuserv and secure IMAP/SMTP via Gnus

[David Vanderschel]

On Tuesday, October 12, "Edi Weitz" <address@hidden> wrote:
>I've assembled some info about NT Emacs, specifically about the topics
>mentioned in the subject line, on my website. I've also made a little
>patch to gnuclient.c. Maybe this is useful for someone else:

>  <http://weitz.de/win/#emacs>

>Corrections and comments welcome.

Some folks may be interested in comparing Edi's
contribution on gnuserv with what I offered on this
subject over four years ago:

   http://groups.yahoo.com/group/ntemacs-users/message/12487

Mine is more tutorial in approach, more general in
some respects, and has become only slightly dated.

On his Web page, Edi writes:
>... add the lines
>(require 'gnuserv)
>(setq gnuserv-frame (car (frame-list)))
>(gnuserv-start)

>to your .emacs file. The second line will prevent
>Emacs from creating a new frame each time it is
>invoked via gnuclientw - leave it out if you like
>this behaviour.

For me, the default behaviour is preferable.  If I am
invoking emacs from outside any current emacs frame,
what I am doing is probably not directly related to
any existing emacs frames.  Indeed, it may be noted
that I created my own function for closing the
resulting emacs buffer, its window, and its frame in a
single stroke (which stroke, for me, is Alt-F4, as is
typical with Windows programs).  I also set my default
frame size different from my initial frame size so
that it remains apparent which is the initial one.

>There's one little problem: If Emacs was minimized
>and is afterwards invoked via gnuclientw it won't
>return to its maximized state. This is actually a
>shortcoming of NT Emacs ...

I do not experience this problem.  Perhaps it is
because I am still running under Windows 98.  For
those who do experience this problem and do not wish
to use Edi's patched gnuclient.c, it is conceivable
that leaving gnuserv-frame nil will also address this
problem.  (I am assuming that a newly created frame
will always be displayed, but I cannot test my theory
since it never fails for me anyway.)


It should be noted that there are two versions of
gnuclient floating about, one which uses mailslots to
communicate and one which uses TCP/IP.  The latter
offers additional function but depends on your LAN
being up.  (Eg., I can disable gnuclient by telling
ZoneAlarm to stop all Internet traffic.)

The mailslot version is here:

   http://centaur.maths.qmw.ac.uk/Emacs/files/gnuserv.zip

The TCP/IP version is here:

   http://www.wyrdrune.com/index.html?gnuserv.html~main

Regards,
  David V.