unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Benjamin Rutt <rutt.4+news@osu.edu>
Subject: Re: emacsclient not working as documented
Date: Fri, 23 Apr 2004 23:03:58 -0400	[thread overview]
Message-ID: <87y8omyt41.fsf@osu.edu> (raw)
In-Reply-To: e609ea08.0404231410.517ef41f@posting.google.com

sparky1685@yahoo.co.uk (Sparky) writes:

> Thanks for the info. I'm quite new to linux and haven't quite got my
> head around the CVS system yet, so I guess this will be my excuse to
> learn :-) It's good to know that I can at least hope to get things
> working this way.

CVS is pretty easy to learn, but to help you get started building
emacs from CVS, here are the basic commands I use:

$ cd /tmp
$ mkdir emacsbuild
$ cd emacsbuild
$ export CVS_RSH=ssh
$ cvs -z3 -d :ext:anoncvs@subversions.gnu.org:/cvsroot/emacs co emacs
$ cd emacs
$ ./configure
$ make bootstrap
$ su -c 'make install'

Then, to try it out, just run /usr/local/bin/emacs.

If the build fails, you can always replace the cvs command with 

cvs -z3 -d :ext:anoncvs@subversions.gnu.org:/cvsroot/emacs co -D "2 days ago" emacs

and keep trying larger values for the 2 in "2 days ago" until you get
checkout one that builds.

Hope this helps,
-- 
Benjamin Rutt

  reply	other threads:[~2004-04-24  3:03 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-22 22:11 emacsclient not working as documented Sparky
2004-04-23 18:32 ` Benjamin Rutt
2004-04-23 22:10   ` Sparky
2004-04-24  3:03     ` Benjamin Rutt [this message]
2004-04-26 12:37       ` Sparky

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=87y8omyt41.fsf@osu.edu \
    --to=rutt.4+news@osu.edu \
    /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).