From: "Lennart Borgman" <lennart.borgman.073@student.lu.se>
Cc: guy@wyrdrune.com, Emacs Devel <emacs-devel@gnu.org>
Subject: Re: Some findings and suggestion about Emacs on w32
Date: Sat, 23 Oct 2004 15:01:26 +0200 [thread overview]
Message-ID: <00d901c4b900$9b774500$0200a8c0@sedrcw11488> (raw)
In-Reply-To: m33c061fjs.fsf@kfs-l.imdomain.dk
----- Original Message -----
From: "Kim F. Storm" <storm@cua.dk>
: "Lennart Borgman" <lennart.borgman.073@student.lu.se> writes:
:
: > 4) Addpm.exe besides changing the registry adds an shortcut to the Start
: > menu in GNU Emacs/Emacs that points to runemacs.exe. This is perhaps not
: > very good? Adding this entry could make a user believe that this is how
: > Emacs should be used. (I believed that for a long time and therefore did
not
: > use Emacs. I wanted to, but it did not gave me the functionality I
needed
: > invoked this way! I needed gnuserv.) I suggest that addpm.exe should not
add
: > this entry.
:
: I completely disagree!
:
: Once you have started emacs (from the start menu), what business do
: you have outside emacs (i.e. in Windoze land)?
Of course you have a point there, but why not have the freedom of working
different ways? Does not that make the learning curve less steep? I have
seen people hesitating to begin using Emacs just because there is too much
to learn to begin with. If we want people to use Emacs I think we should
make it as easy as possible to begin. They will learn more after a while.
Another trouble with this menu entry: What will happen if you start Emacs a
second time from that Start menu entry?
What I would want is that this entry pointed to gnuclientw.exe (or
emacsclient.exe). But there is a trouble with this too. In the case of
gnuclientw.exe gnuserv.el must be started too. But an idea hit me:
gnuserv.el could be started by gnuclientw.exe! The version of gnuclientw.exe
that comes from http://www.wyrdrune.com/ has a switch -e for executing lisp.
I believe this could be used - have to give it a test... - what would you
think of a menu entry like this instead?
BTW the name of the entry is "GNU Emacs". I thought that just "Emacs" was
preferred?
: > 5) Emacs without gnuserv is in my opinion very crippled on w32. Gnuserv
: > should in my opinion be part of Emacs distribution for ms windows. I
suggest
: > the version from http://www.wyrdrune.com/. I suggest that CVS should
include
: > this gnuserv.
:
: Sure, we should include a version of emacsclient which works with emacs'
: new internal emacsserver -- today I guess it will work fine with sockets
: (rather than mailslots which IIRC gnuserv uses).
Can you tell me more about emacsserver/emacsclient? Does it work like
gnuserv or are there big differences?
Is not the main thing to get this kind of functionality working on w32 right
from the distribution, without having to install more things? Since gnuserv
exists and works well on w32 today would it not be good to include it now?
(The gnuserv at wyrdrune uses sockets. I do not know if that is important
here.)
Of course I have nothing against including emacsclient instead if it works!
- Lennart
next prev parent reply other threads:[~2004-10-23 13:01 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-22 22:24 Some findings and suggestion about Emacs on w32 Lennart Borgman
2004-10-22 23:47 ` Kim F. Storm
2004-10-23 13:01 ` Lennart Borgman [this message]
2004-10-24 22:23 ` Kim F. Storm
2004-10-24 22:44 ` Stefan
2004-10-24 22:58 ` Guy Gascoigne-Piggford
2004-10-24 23:36 ` Stefan
2004-10-24 23:44 ` Lennart Borgman
2004-10-24 22:57 ` Guy Gascoigne-Piggford
2004-10-25 7:13 ` David Kastrup
2004-10-25 8:13 ` Kim F. Storm
2004-10-25 16:50 ` Lennart Borgman
[not found] ` <m3sm 81q3ut.fsf@kfs-l.imdomain.dk>
2004-10-26 8:29 ` Kim F. Storm
2004-10-26 17:29 ` Lennart Borgman
2004-10-26 17:43 ` Jason Rumney
2004-10-26 17:54 ` Stephan Stahl
2004-10-26 17:58 ` Lennart Borgman
2004-10-26 21:59 ` Kim F. Storm
2004-10-26 23:03 ` Lennart Borgman
2004-10-26 17:55 ` Lennart Borgman
2004-10-26 18:50 ` Guy Gascoigne - Piggford
2004-10-26 20:48 ` Lennart Borgman
2004-10-23 12:42 ` Benjamin Riefenstahl
2004-10-23 13:15 ` Lennart Borgman
2004-10-23 13:40 ` Benjamin Riefenstahl
2004-10-23 17:39 ` Jason Rumney
2004-10-24 18:39 ` Benjamin Riefenstahl
2004-10-24 20:02 ` Jason Rumney
2004-10-24 20:25 ` Lennart Borgman
2004-10-24 20:43 ` Jason Rumney
2004-10-24 22:01 ` Guy Gascoigne-Piggford
2004-10-23 13:54 ` Richard Stallman
2004-10-23 17:44 ` Jason Rumney
2004-10-23 18:58 ` Guy Gascoigne-Piggford
2004-10-24 1:17 ` Lennart Borgman
2004-10-24 12:14 ` Jason Rumney
2004-10-24 12:46 ` Kim F. Storm
2004-10-25 4:30 ` Dhruva Krishnamurthy
2004-10-25 20:28 ` Lennart Borgman
2004-10-24 22:06 ` Stefan
2004-10-25 8:42 ` Kim F. Storm
2004-10-25 9:00 ` Guy Gascoigne-Piggford
2004-10-25 9:29 ` Kim F. Storm
2004-10-25 10:42 ` Dhruva Krishnamurthy
2004-10-25 11:39 ` Stefan
2004-10-25 12:06 ` Kim F. Storm
2004-10-25 12:25 ` Stefan
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='00d901c4b900$9b774500$0200a8c0@sedrcw11488' \
--to=lennart.borgman.073@student.lu.se \
--cc=emacs-devel@gnu.org \
--cc=guy@wyrdrune.com \
/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).