From: "B. T. Raven" <nihil@nihilo.net>
To: help-gnu-emacs@gnu.org
Subject: Re: rcirc question
Date: Tue, 01 Mar 2011 23:50:38 -0600 [thread overview]
Message-ID: <FLqdnUeb1_Y2R_DQnZ2dnUVZ_vmdnZ2d@sysmatrix.net> (raw)
In-Reply-To: <86oc5u1nji.fsf@hotmail.com>
Vagn Johansen wrote:
> "B. T. Raven" <nihil@nihilo.net> writes:
>
>> Thanks, Deniz. That last snippet should work for me. I didn't upgrade to
>> ver. 23 because getting emacsclientw to work with ver. 22 was such a
>> nightmare that I am terrified of even looking at the w32 registry again.
>> I will wait until someone comes up with a fool-proof .reg file that I
>> can just incorporate into my registry. I think there are about 500 lines
>> in it now that have some variant of "emacs..." in them.
>
> What did you change in the registry?
>
> emacsclientw usually "just works" via
>
> 1) add (server-start) to .emacs
> 2) run emacsclient -n <filename>
>
I'm pretty sure that at that time emacsclientw didn't "just work."
I start emacs from a shortcut on the desktop with target:
C:\Emacs\bin\runemacs.exe --debug-init
Environment:
ALTERNATE_EDITOR c:\emacs\bin\runemacs.exe
HOME C:\emacs
[HKEY_CLASSES_ROOT\*\shell]
[HKEY_CLASSES_ROOT\*\shell\open]
[HKEY_CLASSES_ROOT\*\shell\open\command]
@="c:\\emacs\\bin\\emacsclientw.exe -n \"%1\""
and this same string in many other places, as well as file associations
for about 30 file extensions, etc. Maybe the answer is as simple as
renaming C:\emacs as c:\emacs22 and then c:\emacs23 as c:\emacs. That
way all the paths should be correct in the registry. I may need a new
auctex and a few other things for emacs ver. 23.
prev parent reply other threads:[~2011-03-02 5:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-28 3:04 rcirc question B. T. Raven
2011-02-28 10:29 ` Deniz Dogan
[not found] ` <mailman.1.1298888972.24467.help-gnu-emacs@gnu.org>
2011-03-01 20:02 ` B. T. Raven
2011-03-01 22:30 ` Vagn Johansen
2011-03-02 5:50 ` B. T. Raven [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=FLqdnUeb1_Y2R_DQnZ2dnUVZ_vmdnZ2d@sysmatrix.net \
--to=nihil@nihilo.net \
--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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.