unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: viewing files crashes emacs
Date: Wed, 17 Jan 2024 14:30:16 +0200	[thread overview]
Message-ID: <83le8ob0rr.fsf@gnu.org> (raw)
In-Reply-To: <290b7865-86fd-46d9-875f-730273994069@verizon.net> (message from Tom Goldring on Wed, 17 Jan 2024 01:06:57 -0500)

> Date: Wed, 17 Jan 2024 01:06:57 -0500
> From: Tom Goldring <proto.enigma@verizon.net>
> 
> I'm using emacs 28.2 on a Mac laptop. Normally I view or edit files from 
> Dired by putting the cursor on a file name and typing V (to view) or 
> pressing Enter (to edit). This used to work perfectly well and still 
> does for most files, but now there are some text files (mostly perl 
> scripts, usually having no extension) that will cause emacs to 
> completely lock up so nothing I do within emacs has any effect, and all 
> I can do is kill the process from the command line or using "Force Quit 
> Applications from the OS), and then run emacs again. This will happen 
> consistently for some files but not for most others. I don't know if the 
> affected files contain one or more characters that cause this to happen, 
> because they behave normally if I "cat" them from the shell or view them 
> with TextEdit.

I suspect that this is due to some infloop in python.el which we
already fixed in Emacs 29.  So please try upgrading to Emacs 29, and
if that doesn't solve the problem, report a bug with an example of a
file that causes such lockups.



  reply	other threads:[~2024-01-17 12:30 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <290b7865-86fd-46d9-875f-730273994069.ref@verizon.net>
2024-01-17  6:06 ` viewing files crashes emacs Tom Goldring
2024-01-17 12:30   ` Eli Zaretskii [this message]
2024-01-18 16:59   ` Stefan Monnier via Users list for the GNU Emacs text editor

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=83le8ob0rr.fsf@gnu.org \
    --to=eliz@gnu.org \
    --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).