can anyone help him? i really know little about vc, but many of the list
members do, and he is getting very frustrated.
-------- Original Message --------
Subject: Re: has XEmacs been ported to MacosX?
Date: Wed, 02 Aug 2000 14:50:31 -0400
From: Rodney Sparapani <rodney(a)stat.duke.edu>
Organization: Duke Clinical Research Institute
To: Ben Wing <ben(a)666.com>
References: <8l1s5p$qi5$1(a)nnrp1.deja.com> <3975AAD1.314618E1(a)stat.duke.edu>
<m2puo9u1ii.fsf(a)zion.rcn.com> <3976F061.DCCAFF43(a)stat.duke.edu>
<3977D884.1C999ECC(a)666.com> <3978417D.9C31F66C(a)stat.duke.edu>
<397EE0C6.71317C47(a)stat.duke.edu>
Ben:
Now, you've seen it twice. What are you going to do about it?
Rodney
Rodney Sparapani wrote:
Ben:
Are you looking into this?
Rodney
Rodney Sparapani wrote:
> Ben:
>
> I can't find the e-mails. It was back in April or May. But basically, the
problem is
> with VC. We don't have any problems with the same setup under FSF emacs
19.34.2. But,
> it's a dinosaur. So we were planning to upgrade. xemacs seemed like a logical
choice.
> We are testing 21.1; May, 1999. When you first bring a file into RCS, registering
goes
> fine. However, when you want to check-out a file, it attempts to register it
again;
> which fails. If you ignore the failure, then everything behaves normally after
that.
> Please let me know if you have any ideas. I would love to get this resolved.
Frankly,
> I had given up hope. I got alot of friendly advice, but nothing seemed to help. I
> think the consensus was to just ignore it. Normally, I would go along with that,
but
> the whole reason to use version-control, IMO, is to be very conservative.
>
> Rodney
>
> Ben Wing wrote:
>
> > i've never seen these. where have you supplied them? we try hard to fix
bug
> > reports that get to us. if you've supplied them repeatedly, presumably
you
> > still have the emails around and can send them to us?
> >
> > Rodney Sparapani wrote:
> > >
> > > Vin:
> > >
> > > I have supplied them, repeatedly. I don't think they are problems
with XEmacs per
> > > se. I'm guessing that they have to do with subtle differences between
XEmacs and
> > > emacs. The reason that I'm guessing is that no one has been able to
find a
> > > solution. I can't afford to waste time on something that may never be
fixed so we
> > > use emacs. Oh and by the way, I'm not talking about code that I
wrote. These are
> > > packages that come with XEmacs. You are better off with emacs today.
I'd be
> > > thrilled if XEmacs was usable so we would have options. We don't.
> > >
> > > Rodney
> > >
> > > Vin Shelton wrote:
> > >
> > > > Perhaps you could supply a few specific examples of " extermely
> > > > troublesome" behavior. Perhaps your examples might get looked
at if
> > > > you were to supply some.
> > > >
> > > > Please follow-up to xemacs-beta(a)xemacs.org, if you care to.
> > > >
> > > > Vin Shelton
> > > >
> > > > >>>>> On Wed, 19 Jul 2000, Rodney Sparapani
<rodney(a)stat.duke.edu> said:
> > > >
> > > > Rodney> Tony:
> > > > Rodney> I don't think it has. But, is there some reason that
you want XEmacs
> > > > Rodney> rather than emacs? I have found XEmacs to be extremely
troublesome.
> > > > Rodney> I'm hoping that some day that will change, but it
hasn't happened yet.
> > > > Rodney> Of course, alot of problems are caused because of the
schism between the
> > > > Rodney> two camps. For developers of e-lisp packages like myself,
getting a
> > > > Rodney> working version on emacs alone is hard enough and
modifying it for a
> > > > Rodney> second environment is nearly impossible.
> > > >
> > > > Rodney> Rodney
> > > >
> > > > Rodney> tbennett(a)nvidia.com wrote:
> > > >
> > > > >> I'm just looking for XEmacs in tty mode, of course.
> > > > >>
> > > > >> If so, what is the config to use? config.guess was unable
to
> > > > >> figure out a good one.
> > > > >>
> > > > >> --
> > > > >> --tony
> > > > >>
> > > > >> Sent via
Deja.com http://www.deja.com/
> > > > >> Before you buy.
> > > >
> > > > Rodney> --
> > > > Rodney> WWLD? (What Would Lombardi Do?)
> > > > Rodney> Was "Name That Tune" Rigged?
> > > > Rodney> Rodney Sparapani, Duke Clinical Research Institute
> > > > Rodney> For addressing and schedule information
> > > > Rodney> see
http://www.duke.edu/~spara002
> > >
> > > --
> > > WWLD? (What Would Lombardi Do?)
> > > Was "Name That Tune" Rigged?
> > > Rodney Sparapani, Duke Clinical Research Institute
> > > For addressing and schedule information
> > > see
http://www.duke.edu/~spara002
> >
> > --
> > Ben
> >
> > In order to save my hands, I am cutting back on my mail. I also write
> > as succinctly as possible -- please don't be offended. If you send me
> > mail, you _will_ get a response, but please be patient, especially for
> > XEmacs-related mail. If you need an immediate response and it is not
> > apparent in your message, please say so. Thanks for your understanding.
> >
> > See also
http://www.666.com/ben/chronic-pain/
>
> --
> WWLD? (What Would Lombardi Do?)
> Was "Name That Tune" Rigged?
> Rodney Sparapani, Duke Clinical Research Institute
> For addressing and schedule information
> see
http://www.duke.edu/~spara002
--
WWLD? (What Would Lombardi Do?)
Was "Name That Tune" Rigged?
Rodney Sparapani, Duke Clinical Research Institute
For addressing and schedule information
see
http://www.duke.edu/~spara002
--
WWLD? (What Would Lombardi Do?)
Was "Name That Tune" Rigged?
Rodney Sparapani, Duke Clinical Research Institute
For addressing and schedule information
see