From: Eli Zaretskii <eliz@gnu.org>
To: jidanni@jidanni.org
Cc: 73727-done@debbugs.gnu.org
Subject: bug#73727: dired-view-file vs. emacs -nw
Date: Sun, 27 Oct 2024 12:16:51 +0200 [thread overview]
Message-ID: <86r081am0c.fsf@gnu.org> (raw)
In-Reply-To: <86ldyvyonl.fsf@gnu.org> (message from Eli Zaretskii on Fri, 11 Oct 2024 12:28:14 +0300)
> Cc: 73727@debbugs.gnu.org
> Date: Fri, 11 Oct 2024 12:28:14 +0300
> From: Eli Zaretskii <eliz@gnu.org>
>
> > From: Dan Jacobson <jidanni@jidanni.org>
> > Cc: 73727@debbugs.gnu.org
> > Date: Fri, 11 Oct 2024 16:16:22 +0800
> >
> > All I know is a couple more erroneous keystroks, and one ends up
> > accidentally editing one of these files, with its regexp parser choking
> > long lines... might end up using all the CPU...
>
> dired-view-file visits the file in read-only mode, so you are not
> supposed to edit it unless you really mean to...
>
> IOW, it sounds like there was some cockpit error in your case, and you
> somehow decided that it's Emacs's fault. It isn't.
No substantial new information or comments about this in more than 2
weeks, so I'm now closing this bug.
prev parent reply other threads:[~2024-10-27 10:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-10 10:41 bug#73727: dired-view-file vs. emacs -nw Dan Jacobson
2024-10-10 11:29 ` Eli Zaretskii
2024-10-11 8:16 ` Dan Jacobson
2024-10-11 9:28 ` Eli Zaretskii
2024-10-25 22:05 ` Dan Jacobson
2024-10-26 7:04 ` Eli Zaretskii
2024-10-26 8:57 ` Dan Jacobson
2024-10-26 13:30 ` Eli Zaretskii
2024-10-27 10:16 ` Eli Zaretskii [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=86r081am0c.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=73727-done@debbugs.gnu.org \
--cc=jidanni@jidanni.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).