From: rustom <rustompmody@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: Re: windows setup for emacsclient
Date: Mon, 17 Mar 2008 00:55:46 -0700 (PDT) [thread overview]
Message-ID: <94214c87-1b2c-48e8-b63d-302f015e54d6@s8g2000prg.googlegroups.com> (raw)
In-Reply-To: 2YidnVdFUe41PEHanZ2dnUVZ_ournZ2d@sysmatrix.net
On Mar 16, 10:27 am, "B. T. Raven" <ni...@nihilo.net> wrote:
> rustom wrote:
> > What do I have to do to open a file with emacsclient in windows?
>
> > Yeah I know one must first start emacs with server-start -- I am
> > wondering about the more windows-y part. I am, say, in windows
> > explorer and want to right-click file and choose open in emacsclient.
> > I can even do it now but I have to literally go hunting after it:
> > Shift-rt-click -> Open with ->Browse -> Program Files... -> emacs ->
> > bin -> emacsclientw -> Ok ... -> Ok
> > ...... every time the same bally-hoo.
>
> > Related to this: How to give the -n option? Because otherwise when I
> > kill that buffer emacs pops a window at me saying the client is still
> > waiting for the server or some such thing.
>
> Go to a msdos prompt and type something like:
>
> ftype emacs=c:\emacs\bin\emacsclientw.exe -n "%1"
>
> but with your appropriate path (you can call the part before = whatever
> you want)
>
> and then (for example):
>
> assoc .txt=emacs
>
> Then with regedit make a key
>
> HKEY_CLASSES_ROOT\Applications\emacsclientw.exe\shell\Open\Command
>
> with value:
>
> c:\emacs\bin\emacsclientw.exe -n "%1"
>
> with -a switch you can add an alternate editor. I have seen this set to
> /path/runemacs.exe See:
>
> http://www.emacswiki.org/cgi-bin/wiki/EmacsClient
>
> under emacsclientw for vers. 22
>
> Also under shell (i.e)
>
> HKEY_CLASSES_ROOT\Applications\emacsclientw.exe\shell
>
> I have two names:
>
> FriendlyCache
> FrienllyCacheCTime
>
> of types REG_SZ and REG_BINARY respectively and values
>
> GNU Emacs for Windows NT/95/98/2000/ME/XP
> and
> 00 46 bf f2 04 c1 c7 01
>
> I have no idea what they are or where they came from.
>
> You can associate other filetypes with Emacs via assoc in a dos window
> or else use Tools > Folder Options > File Types in Windows Explorer.
>
> Back up the registry before you mess with it. It is intrinsically
> dangerous to edit it manually. It may be possible to accomplish the
> above without regedit but I don't know how to do it.
>
> Ed
Thanks for the detailed reply. But still some problems:
What Ive done is
ftype emacs=c:\emacs22.1\bin\emacsclientw -n -a c:/emacs22.1\bin
\emacs "%1"
assoc .txt=emacs
Now when emacs (the server) is already running it works fine.
But if not:
1. A box comes up saying emacsclient ERROR: connect no error
Ive to click ok to that
2. Next a command window opens momentarily
3. Finally emacs opens with the file
And the command window remains open
next prev parent reply other threads:[~2008-03-17 7:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-12 16:36 windows setup for emacsclient rustom
2008-03-16 5:27 ` B. T. Raven
2008-03-17 7:55 ` rustom [this message]
2008-03-17 14:14 ` Chris McMahan
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=94214c87-1b2c-48e8-b63d-302f015e54d6@s8g2000prg.googlegroups.com \
--to=rustompmody@gmail.com \
--cc=help-gnu-emacs@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).