unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Stephen Berman <stephen.berman@gmx.net>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Casey Connor <emacsbugs@caseyconnor.org>, 60796@debbugs.gnu.org
Subject: bug#60796: 27.1; Opening file ending in .sh inside a directory ending in .deb causes hang/100% thread usage
Date: Sat, 14 Jan 2023 12:20:27 +0100	[thread overview]
Message-ID: <875yd9xszo.fsf@gmx.net> (raw)
In-Reply-To: <83h6wt8s8a.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 14 Jan 2023 09:56:05 +0200")

On Sat, 14 Jan 2023 09:56:05 +0200 Eli Zaretskii <eliz@gnu.org> wrote:

>> Date: Fri, 13 Jan 2023 23:43:17 -0800
>> From: Casey Connor <emacsbugs@caseyconnor.org>
>> Cc: 60796@debbugs.gnu.org
>>
>> Oops, sorry, I just noticed the Cc on these emails that I should have
>> been using. Repeating what I said in (accidental) privacy:
>>
>> I installed Ubuntu Server 22.10 in a VM, booted, installed emacs-nox
>> package from repo, did mkdir asdf.deb, cd asdf.deb, emacs -Q, and the
>> problem happens there, in case that's useful. (v27.1)
>>
>> I realized that it doesn't matter what you are editing (if anything), it
>> just needs to be opened inside a directory ending in .deb.
>
> Maybe there are local Debian changes?  I suggest to report this to the
> distro first.

I can reproduce the problem in my Emacs 27 branch from the Savannah repo
built on non-Debian GNU/Linux; I cannot reproduce it with Emacs 26 or 28
and later.  (Emacs 26 does not recognize tramp-archive-enabled, in 27
and later it does and the default value it t.)

Steve Berman





  reply	other threads:[~2023-01-14 11:20 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-13 23:19 bug#60796: 27.1; Opening file ending in .sh inside a directory ending in .deb causes hang/100% thread usage Casey Connor via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-01-14  3:15 ` Ruijie Yu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-01-14  7:21 ` Eli Zaretskii
2023-01-14  7:43   ` Casey Connor via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-01-14  7:56     ` Eli Zaretskii
2023-01-14 11:20       ` Stephen Berman [this message]
2023-01-14 18:53         ` Casey Connor via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-01-15 15:15           ` Michael Albinus
2023-01-15 15:14         ` Michael Albinus
2023-01-15 16:00           ` Stephen Berman
2023-01-15 16:09             ` Michael Albinus
2023-01-15 16:16               ` Stephen Berman
2023-01-15 16:21                 ` Michael Albinus
2023-01-15 16:34                   ` Stephen Berman
2023-01-15 16:47                     ` Michael Albinus
2023-01-15 17:04                       ` Stephen Berman
2023-01-15 18:25                         ` Michael Albinus
2023-01-15 19:05                           ` Stephen Berman
2023-01-14  8:47     ` Michael Albinus
2023-01-15  7:18       ` Jean Louis

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=875yd9xszo.fsf@gmx.net \
    --to=stephen.berman@gmx.net \
    --cc=60796@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=emacsbugs@caseyconnor.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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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).