unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Harry Putnam <reader@newsguy.com>
Subject: Re: 64 bit processor and emacs
Date: Mon, 09 Feb 2004 07:11:54 -0600	[thread overview]
Message-ID: <m3y8rcpfc5.fsf@newsguy.com> (raw)
In-Reply-To: uy8rcu7u0.fsf@elta.co.il

Eli Zaretskii <eliz@elta.co.il> writes:

>> From: Harry Putnam <reader@newsguy.com>
>> Date: Sun, 08 Feb 2004 21:37:59 -0600
>> 
>> Any one here have experience with emacs on a 64 bit processor?
>> If so, are there got_chas or what ever.  Is anyone here who can
>> summarize why a 64 bit processor is good or better?  AT least
>> privately if its too off topic here.
>
> Emacs supports 64-bit builds on a few platforms, as described in NEWS.
> The primary advantage is that the maximum buffer size is greatly
> enlarged.
>
> What else do you need to know?

Thanks Eli,
I'm building up a system for editing and capturing video.  I'm
looking at athlon 64 bit processor.   Near as I can tell, I'll have
to leave my favorite linux OS behind to take advantage of the
software for this kind of work that is available for MicroSoft OS.

I was afraid I might have a problem getting a good working install of
emacs which I would be lost without.  So it will likely be Athlon64
FX and Win XP pro.

I'm not that conversant on windows OS.  I know people run emacs on it
and I've seen many posts from you relating to emacs on that os.

I guess it would just be the normal ntemacs type of install?

  reply	other threads:[~2004-02-09 13:11 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-09  3:37 64 bit processor and emacs Harry Putnam
2004-02-09  5:42 ` Eli Zaretskii
2004-02-09 13:11   ` Harry Putnam [this message]
2004-02-09 17:17     ` Eli Zaretskii
     [not found]   ` <mailman.2114.1076336718.928.help-gnu-emacs@gnu.org>
2004-02-09 16:46     ` Stefan Monnier
2004-02-10 18:34     ` Jason Dufair

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=m3y8rcpfc5.fsf@newsguy.com \
    --to=reader@newsguy.com \
    /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).