From: Bernt Hansen <bernt@norang.ca>
To: TonyMc <afmcc@btinternet.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: ot: windows xemacs question
Date: Sun, 18 Mar 2012 09:35:33 -0400 [thread overview]
Message-ID: <87pqcac9qy.fsf@norang.ca> (raw)
In-Reply-To: <fljbm75a3a3oga5744uat3djf3tnr0qvfl@4ax.com> (TonyMc's message of "Sun, 18 Mar 2012 12:07:27 +0000")
TonyMc <afmcc@btinternet.com> writes:
> On Sat, 17 Mar 2012 14:53:07 -0400 (EDT), you wrote:
>
>>I had a read of the setup instructions for emacs on windows and
>>unfortunately so many of them involve modifying the windows registry. A
>>very experienced software specialist told me it's best never to use
>>software that requires these modifications because sooner rather than
>>later windows will crash and then the whole mess has to be reinstalled
>>after that. He had no idea about xemacs but he told me emacs and windows
>>do not live happily on machines together. So I'm wondering if xemacs
>>might end up being any better and figured this being the closest list to
>>emacs support I'm on that actually works to ask this question here.
>
> Not sure where you got your info, but it is misleading and should not
> put you off. "Installing" GNU Emacs on Windows involves unzipping a
> directory tree, that is all. Download emacs-23.4-bin-i386.zip and
> unzip it to e.g. the root of the C: drive. Then you can run emacs as
> C:\emacs-23.4\bin\runemacs.exe.
I agree that no registry changes should be/are required. I use windows
at work with an unzipped emacs and I've never touched the registry.
Regards,
Bernt
next prev parent reply other threads:[~2012-03-18 13:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-17 18:53 ot: windows xemacs question Jude DaShiell
2012-03-18 12:07 ` TonyMc
2012-03-18 13:35 ` Bernt Hansen [this message]
2012-03-18 12:37 ` Charles
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.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87pqcac9qy.fsf@norang.ca \
--to=bernt@norang.ca \
--cc=afmcc@btinternet.com \
--cc=emacs-orgmode@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/org-mode.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).