From: Michael Albinus <michael.albinus@gmx.de>
To: 60796@debbugs.gnu.org
Cc: eliz@gnu.org, stephen.berman@gmx.net, emacsbugs@caseyconnor.org
Subject: bug#60796: 27.1; Opening file ending in .sh inside a directory ending in .deb causes hang/100% thread usage
Date: Sun, 15 Jan 2023 16:15:49 +0100 [thread overview]
Message-ID: <87v8l7oml6.fsf@gmx.de> (raw)
In-Reply-To: <01905a9b-5728-9ac2-8a95-a2762bdb20b3@caseyconnor.org> (Casey Connor via's message of "Sat, 14 Jan 2023 10:53:28 -0800")
Casey Connor via "Bug reports for GNU Emacs, the Swiss army knife of
text editors" <bug-gnu-emacs@gnu.org> writes:
Hi Casey,
> Thanks -- does that mean I should not report to Debian as a bug there?
Yes, I believe it isn't a Debian issue.
Best regards, Michael.
next prev parent reply other threads:[~2023-01-15 15:15 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
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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87v8l7oml6.fsf@gmx.de \
--to=michael.albinus@gmx.de \
--cc=60796@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=emacsbugs@caseyconnor.org \
--cc=stephen.berman@gmx.net \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.