Gnus development mailing list
 help / color / mirror / Atom feed
From: Scott Blachowicz <scott@statsci.com>
Cc: ding@ifi.uio.no
Subject: Re: idea.. check and grab new versions..?
Date: Tue, 21 Jan 1997 09:50:29 -0800	[thread overview]
Message-ID: <m0vmkL8-0003xOC@main.statsci.com> (raw)
In-Reply-To: Your message of "21 Jan 1997 07:21:50 -0800." <x020bf835d.fsf@doctor.sdsu.edu>

Mark Boyns <boyns@sdsu.edu> wrote:

> wget -q --timestamping http://www.ifi.uio.no/~larsi/rgnus.tar.gz

But that's the easy part...the slightly harder part is getting it
extracted and built (e.g. using scripts as posted by Jan Vroonhof).  And,
from what I know, there even harder part is getting it done online so that
you can hit an "update gnus" button in a message online (e.g. Lars'
announcements) that will fire it all of, then "exit" your current gnus
version and fire up the new gnus version while you wait (with bonus points
for getting you back in where you left off - reading the announcement
message :-)).

Speaking of all that...does anyone else use both Emacs & XEmacs (depending
on mood, system, etc)?  For gnus builds I usually do something like this:

    mv lisp lisp-src
    rslink lisp-src lisp-e19            # rslink makes a shadow symlink tree
    rslink lisp-src lisp-xemacs
    ln -s lisp-e19 lisp
    GNU make
    rm lisp
    ln -s lisp-xemacs lisp
    GNU make EMACS=xemacs lick

then I put the appropriate lisp-e19 or lisp-xemacs directory in my
load-path.  Some questions...

1) Do I really need to byte compile them separately?  I've had problems
   using .elc from one emacs in the other in the past.  Currently we're
   using Emacs 19.31-34 (depending on platform) and XEmacs 19.13-14.

2) I don't suppose there's any easy (and unobtrusive) ways to incorporate
   something in the standard distribution to allow for this kind of setup,
   is there?

Scott Blachowicz  Ph: 206/283-8802x240   Mathsoft (Data Analysis Products Div)
                                         1700 Westlake Ave N #500
scott@statsci.com                        Seattle, WA USA   98109
Scott.Blachowicz@seaslug.org


  parent reply	other threads:[~1997-01-21 17:50 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1997-01-21 11:16 Andy Eskilsson
1997-01-21 11:56 ` Lars Balker Rasmussen
1997-01-21 15:21   ` Mark Boyns
1997-01-21 16:02     ` Jan Vroonhof
1997-01-21 18:12       ` Manoj Srivastava
1997-01-22  9:43       ` wget, was [Re: idea.. check and grab new versions..?] Jan Vroonhof
1997-01-21 17:50     ` Scott Blachowicz [this message]
1997-01-21 18:35       ` idea.. check and grab new versions..? Shannon F. Stewman
1997-01-22  0:39         ` Justin Sheehy
1997-01-21 21:06           ` Shannon F. Stewman
1997-01-22 16:00         ` William M. Perry
1997-01-21 20:34       ` Andrew J Cosgriff
1997-01-21 22:57       ` Lars Magne Ingebrigtsen
1997-01-22  3:46       ` Danny Siu
1997-01-21 15:57   ` visigoth

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=m0vmkL8-0003xOC@main.statsci.com \
    --to=scott@statsci.com \
    --cc=ding@ifi.uio.no \
    /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 NNTP newsgroup(s).