From: Eli Zaretskii <eliz@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: Runemacs.exe and emacs.exe don't seem to run
Date: Fri, 17 Feb 2012 10:21:32 +0200 [thread overview]
Message-ID: <83fwe9x437.fsf@gnu.org> (raw)
In-Reply-To: <20285.39826.996746.959465@rocky.wb5aoh.ampr.org>
> From: Tami <kd5rju@wb5aoh.dyndns.org>
> Date: Thu, 16 Feb 2012 18:13:06 -0600
>
> Can you get around the upgrade problem by just adding .el files?
Sorry, but that's a very bad advice. Emacs Lisp files from a newer
version will most probably be incompatible with the old Emacs binary.
And even if they are compatible, one would need several addition Lips
files on which the first ones depend.
The OP's problem is most probably caused by incorrect upgrade
procedure. In particular, the upgrade should NOT be done by using the
bare-bin zip file. Just download the bin distribution, unzip it,
update PATH to point to its bin subdirectory and remove the bin
subdirectory of the old one, and start using the new one.
next prev parent reply other threads:[~2012-02-17 8:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-11 1:58 Runemacs.exe and emacs.exe don't seem to run Douglas Harter
2012-02-17 0:13 ` Tami
2012-02-17 8:21 ` Eli Zaretskii [this message]
[not found] <mailman.3657.1328926291.15002.help-gnu-emacs@gnu.org>
2012-02-11 3:22 ` Jason Rumney
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=83fwe9x437.fsf@gnu.org \
--to=eliz@gnu.org \
--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).