From: jadamson@partners.org (Joel J. Adamson)
To: Joe Bloggs <who@cares.invalid>
Cc: help-gnu-emacs@gnu.org
Subject: Re: first copy & paste not working
Date: Mon, 05 May 2008 10:06:46 -0400 [thread overview]
Message-ID: <87wsm89761.fsf@W0053328.mgh.harvard.edu> (raw)
In-Reply-To: <874p9g5yut.fsf@DEBLAP1.BeNet> (Joe Bloggs's message of "Fri, 02 May 2008 19:45:30 +0100")
Joe Bloggs <who@cares.invalid> writes:
> jadamson@partners.org (Joel J. Adamson) writes:
>
>> Joe Bloggs <who@cares.invalid> writes:
>>
>>> I can only yank my emacs text if I repeat the emacs cut/copy,
>>> othewise it just keeps yanking the external text. Can anyone help?
>> Hi Joe, good to see you again.
>> Which Emacs version and operating system are you using (specifically
>> which Unix?)?
>
> Emacs 21.4a on Debian etch, which is the latest version in the etch
> repository.
A friend of mine advised me, after I found the latest Emacs in Debian
was 21.4, that adding the unstable repositories, and/or Ubuntu
repositories is a must for using up-to-date software on Debian. Any
Debian users like to comment?
> Couldn't find anything newer in backports, and don't really want to
> build one myself as it could be more hassle than it's worth.
Then allow me to correct you: building Emacs from CVS is a
piece-of-cake.
(equal '(build emacs-from-cvs) 'piece-of-cake)
=> t
I only had to learn how to do it once, and then I set up building a
Slackware package as a cron job; every week I have a brand new Emacs
from CVS waiting for me on Monday.
make bootstrap
make
make install
and Emacs does the rest.
Check out http://www.emacswiki.org/cgi-bin/wiki/EmacsFromCVS
Joel
--
Joel J. Adamson
Biostatistician
Pediatric Psychopharmacology Research Unit
Massachusetts General Hospital
Boston, MA 02114
(617) 643-1432
(303) 880-3109
Public key: http://pgp.mit.edu
http://www.unc.edu/~adamsonj
The information transmitted in this electronic communication is intended only
for the person or entity to whom it is addressed and may contain confidential
and/or privileged material. Any review, retransmission, dissemination or other
use of or taking of any action in reliance upon this information by persons or
entities other than the intended recipient is prohibited. If you received this
information in error, please contact the Compliance HelpLine at 800-856-1983 and
properly dispose of this information.
next prev parent reply other threads:[~2008-05-05 14:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-02 1:35 first copy & paste not working Joe Bloggs
2008-05-02 14:09 ` Joel J. Adamson
2008-05-02 17:31 ` Mike Treseler
2008-05-02 21:44 ` Peter Dyballa
[not found] ` <mailman.11085.1209737396.18990.help-gnu-emacs@gnu.org>
2008-05-02 18:45 ` Joe Bloggs
2008-05-05 14:06 ` Joel J. Adamson [this message]
[not found] ` <mailman.11202.1209996421.18990.help-gnu-emacs@gnu.org>
2008-05-05 14:27 ` Rupert Swarbrick
2008-05-05 17:09 ` Joel J. Adamson
[not found] ` <mailman.11208.1210007351.18990.help-gnu-emacs@gnu.org>
2008-05-05 17:18 ` Rupert Swarbrick
2008-05-06 12:42 ` Joe Bloggs
2008-05-07 5:15 ` Kevin Rodgers
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=87wsm89761.fsf@W0053328.mgh.harvard.edu \
--to=jadamson@partners.org \
--cc=help-gnu-emacs@gnu.org \
--cc=who@cares.invalid \
/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).