From: Reiner Steib <reinersteib+gmane@imap.cc>
To: emacs-devel@gnu.org
Subject: Re: Windows: Documentation for bin\*.exe
Date: Thu, 31 Jan 2008 22:54:02 +0100 [thread overview]
Message-ID: <v98x25sltx.fsf@marauder.physik.uni-ulm.de> (raw)
In-Reply-To: v9ps18buab.fsf@marauder.physik.uni-ulm.de
Hi,
I didn't get any reply to the message quoted below.
Reiner.
On Mon, Aug 27 2007, Reiner Steib wrote:
> [Disclaimer: I don't have Windows here now to reproduce or lookup the
> details, so please correct me if my memory is failing.]
>
> In Windows' file manager (explorer.exe), you can right click on a file
> and select "Open With..." (re-translated from German, I'm not sure
> about the exact wording in English) to choose an application for
> opening this file (only this time or for the future for this
> extension). When I want to select Emacs, I browse to the Emacs\bin
> directory and find 14 executables [1]. Okay, I can figure out that
> the most promising are emacs.exe, emacsclient.exe, emacsclientw.exe,
> and runemacs.exe. runemacs.exe in contrast to emacs.exe doesn't open
> a cmd-shell window ("DOS box"). If I have already evaled
> `server-start', emacsclient and emacsclientw would be suitable, but
> which one? So I did some trial and error and somehow found the right
> one. But now Explorer remembered all Emacs executables and in its
> selection dialog box (after "Open with...") presents severals
> executables but they all have the very same description ("GNU Emacs
> for Windows NT/95/98/2000/ME/XP" or similar; FileDescription in
> nt/emacs.rc maybe?) and icon (the new Emacs icon). I can't figure out
> which one is emacs.exe, emacsclient.exe or emacsclientw.exe. Only
> trial and error? (BTW, how to delete existing entries in "Open
> With..."?)
>
> I search for hints in the manual ("grep -nH -e
> 'runemacs\|emacsclient\|\.exe' msdo*.texi" doesn't give only two
> unrelated hits) and nt/, but I couldn't find anything related the
> documentation.
>
> Suggestions:
>
> (a) A README file explaining the purpose of the various *.exe files
> (especially *emacs*.exe) in the bin directory.
>
> (b) The description appearing in the "Open with..." dialog should tell
> about the purpose of the binary (or at least display name of the
> executable).
>
> Bye, Reiner.
>
> [1] c:/Programme/GNU/Emacs/bin$ ls -1 *.exe
> addpm.exe
> cmdproxy.exe
> ctags.exe
> ddeclient.exe
> digest-doc.exe
> ebrowse.exe
> emacs.exe
> emacsclient.exe
> emacsclientw.exe
> etags.exe
> hexl.exe
> movemail.exe
> runemacs.exe
> sorted-doc.exe
next prev parent reply other threads:[~2008-01-31 21:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-27 20:24 Windows: Documentation for bin\*.exe Reiner Steib
2008-01-31 21:54 ` Reiner Steib [this message]
2008-02-01 0:17 ` Jason Rumney
2008-02-01 10:52 ` Eli Zaretskii
2008-02-01 11:08 ` Jason Rumney
2008-02-23 22:30 ` Reiner Steib
2008-02-24 15:35 ` Jason Rumney
2008-03-09 12:24 ` Reiner Steib
2008-02-01 21:14 ` Michael Schierl
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=v98x25sltx.fsf@marauder.physik.uni-ulm.de \
--to=reinersteib+gmane@imap.cc \
--cc=Reiner.Steib@gmx.de \
--cc=emacs-devel@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.
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).