From: sparky1685@yahoo.co.uk (Sparky)
Subject: Re: emacsclient not working as documented
Date: 26 Apr 2004 05:37:15 -0700 [thread overview]
Message-ID: <e609ea08.0404260437.7db154d2@posting.google.com> (raw)
In-Reply-To: 87y8omyt41.fsf@osu.edu
Benjamin Rutt <rutt.4+news@osu.edu> wrote in message >
> 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,
Thanks very much for the instructions - much appreciated. It all
worked perfectly and emacsclient is indeed working as expected from
the command line now. I don't imagine many people use the jump to
column feature in emacs, but it will be a lifesaver when editing music
notation in lilypond.
Many thanks
Mark
prev parent reply other threads:[~2004-04-26 12:37 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
2004-04-26 12:37 ` Sparky [this message]
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=e609ea08.0404260437.7db154d2@posting.google.com \
--to=sparky1685@yahoo.co.uk \
/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).