unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: jadamson@partners.org (Joel J. Adamson)
To: Dan Espen <daneNO@MORE.mk.SPAMtelcordia.com>
Cc: help-gnu-emacs@gnu.org
Subject: Re: hang while marking large region
Date: Mon, 12 May 2008 13:50:38 -0400	[thread overview]
Message-ID: <8763tjs975.fsf@W0053328.mgh.harvard.edu> (raw)
In-Reply-To: <iclk2f8r8r.fsf@verizon.net> (Dan Espen's message of "Mon, 12 May 2008 15:41:00 GMT")

Dan Espen <daneNO@MORE.mk.SPAMtelcordia.com> writes:

> jadamson@partners.org (Joel J. Adamson) writes:
>
>> andrew.tao@gmail.com writes:
>>
>>> hello,
>>>
>>> i'm using 21.1.13 xemacs. when i set the mark and then scroll to a
>>> distant area in a text file, xemacs hangs. we're talking about a few
>>> megabytes of data being marked.
>>
>> Please distinguish between Emacs using an X display and the separate
>> software project XEmacs.
>>
>>> it seems that xemacs must be trying to copy the marked region
>>> somewhere and then hanging.
>>>
>>> any ideas for a workaround?
>>
>> Workaround: don't use XEmacs.
>>
>> This is a known problem.  I had this same problem and the solution was
>> to switch.
>>
>> http://steve-yegge.blogspot.com/2008/04/xemacs-is-dead-long-live-xemacs.html
>
> Never seen the XEmacs stability problem you describe.

I didn't describe it, Steve Yegge described it.  I didn't have the
stability problems he describes either, but I did have annoying hang-ups
with fontification and a few other things.

> That said, switching to GNU Emacs is probably a good way to go.

You can find a page on the subject here:
http://www.emacswiki.org/cgi-bin/wiki/EmacsAndXEmacs

That page helped me make the choice.  Like I said, I can't remember why
I picked XEmacs, I think because I saw a screenshot of it heavily
customized.  However, my customizations now go a lot further in Emacs.

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

Ineffective security measure:

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.







      reply	other threads:[~2008-05-12 17:50 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-09 16:45 hang while marking large region andrew.tao
2008-05-09 16:50 ` Sven Joachim
2008-05-09 17:50   ` Dan Espen
2008-05-10 18:51 ` Peter Dyballa
2008-05-12 14:18 ` Joel J. Adamson
     [not found] ` <mailman.11507.1210601915.18990.help-gnu-emacs@gnu.org>
2008-05-12 15:01   ` David Kastrup
2008-05-12 16:09     ` Joel J. Adamson
2008-05-12 16:46       ` David Kastrup
2008-05-12 15:41   ` Dan Espen
2008-05-12 17:50     ` Joel J. Adamson [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=8763tjs975.fsf@W0053328.mgh.harvard.edu \
    --to=jadamson@partners.org \
    --cc=daneNO@MORE.mk.SPAMtelcordia.com \
    --cc=help-gnu-emacs@gnu.org \
    /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).