From: dkcombs@panix.com (David Combs)
Subject: Re: Has anyone actually built emacs 21.3 for SOLARIS (sparc)?
Date: Mon, 26 May 2003 02:46:06 +0000 (UTC) [thread overview]
Message-ID: <barv5e$bid$1@reader1.panix.com> (raw)
In-Reply-To: slrnbd1sfl.2fng.phil+s3@bolthole.com
In article <slrnbd1sfl.2fng.phil+s3@bolthole.com>,
Philip Brown <phil+s3@bolthole.no-bots.com> wrote:
>FYI: there are now binaries of emacs 21.3, for solaris 8 and later, on
>mirror sites of www.blastwave.org
Since I've already got the sources downloaded,
and I'll probably soon have it "made" ok,
I probably won't get the blastwave "binary"
(actually, solaris "package"?).
But a question:
Suppose in a case like this, you like the current
version ok, but want to try the new one.
However, in case it's not so great after all,
I'd want to keep using the OLD one.
Looking at the blastwave page, it implies (says
right out!) that the new one gets installed
OVER the old one -- the old one would be GONE,
no?
So, first question: how to be able to restore
the "old" one?
Second question (similar): Suppose you want
to *compare* how they run'; you want to
be able to run either one, or, for emacs,
have both running at the same time, switching
between via switching from one (cde) window
to another.
How to do that?
Thanks!
David
next prev parent reply other threads:[~2003-05-26 2:46 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-20 16:41 Has anyone actually built emacs 21.3 for SOLARIS (sparc)? David Combs
2003-05-20 18:10 ` Stefan Monnier
2003-05-20 19:38 ` Dave Uhring
2003-05-20 18:39 ` Dave Uhring
2003-05-21 21:47 ` David Combs
2003-05-21 22:37 ` Stefan Monnier
2003-05-21 23:15 ` Darren Dunham
2003-05-22 0:54 ` Stefan Monnier
2003-05-22 15:06 ` bbense+gnu.emacs.help.comp.unix.solaris.May.22.03
2003-05-22 15:45 ` Dave Uhring
2003-05-23 5:28 ` David Combs
2003-05-23 9:18 ` David Combs
2003-05-23 10:45 ` Dave Uhring
2003-05-26 0:44 ` David Combs
2003-05-23 10:41 ` Dave Uhring
2003-05-23 4:36 ` David Combs
2003-05-23 5:53 ` Miles Bader
2003-05-22 8:02 ` David Combs
2003-05-22 13:56 ` Stefan Monnier
2003-05-22 14:53 ` David Combs
2003-05-20 19:53 ` Bijan Soleymani
2003-05-20 21:03 ` Dave Uhring
2003-05-21 8:50 ` David Combs
2003-05-21 15:55 ` Dave Uhring
2003-05-21 22:24 ` David Combs
2003-05-21 22:49 ` Stefan Monnier
2003-05-21 23:34 ` Dave Uhring
2003-05-22 8:07 ` David Combs
2003-05-22 13:48 ` Casper H.S. Dik
2003-05-22 14:45 ` Dave Uhring
2003-05-24 7:29 ` David Combs
2003-05-24 14:55 ` Dave Uhring
2003-05-25 16:40 ` Philip Brown
2003-05-26 2:46 ` David Combs [this message]
2003-05-26 19:14 ` Philip Brown
2003-05-26 13:13 ` David Combs
2003-05-26 15:46 ` Dave Uhring
2003-05-26 22:49 ` David Combs
2003-05-26 23:44 ` Dave Uhring
2003-05-27 0:10 ` Dave Uhring
2003-06-03 7:13 ` David Combs
2003-06-03 7:09 ` David Combs
2003-06-03 13:47 ` Dave Uhring
2003-05-27 15:42 ` Kevin Rodgers
2003-06-03 7:19 ` David Combs
2003-05-21 21:44 ` David Combs
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='barv5e$bid$1@reader1.panix.com' \
--to=dkcombs@panix.com \
/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).