all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Dan Jacobson <jidanni@jidanni.org>
Cc: 73727@debbugs.gnu.org
Subject: bug#73727: dired-view-file vs. emacs -nw
Date: Thu, 10 Oct 2024 14:29:00 +0300	[thread overview]
Message-ID: <86set419j7.fsf@gnu.org> (raw)
In-Reply-To: <87iku0z1cj.3.fsf@jidanni.org> (message from Dan Jacobson on Thu,  10 Oct 2024 18:41:48 +0800)

tags 73727 notabug wontfix
thanks

> From: Dan Jacobson <jidanni@jidanni.org>
> Date: Thu, 10 Oct 2024 18:41:48 +0800
> 
> v runs the command dired-view-file which works great even on images etc.
> except when the user is using emacs -nw, in which case it just spews the
> a lot of binary stuff on the screen which the user was not expecting.
> Therefore it should say "xyz.jpg cannot be shown properly on your
> terminal." (If they really want to see the bytes, they can use
> find-file.)

That's not the Emacs way.  Emacs allows users to visit any kind of
files, including those which display as binary garbage.  Moreover,
even on GUI frames, users can customize Emacs to never show image
files as images when they are visited.  Refusing to visit an image
file just because it cannot be displayed as an image is something
Emacs never did and should not do.

dired-view-file's doc string says:

  In Dired, examine a file in view mode, returning to Dired when done.
  When file is a directory, show it in this buffer if it is inserted.
  Otherwise, display it in another buffer.

There's nothing here about showing image files as images or not at
all.  Perhaps you were confused by the "view" part, but that refers to
view-mode, not to "viewing" an image.

So I don't see any bugs here, and don't think we should "fix" anything
in this matter.





  reply	other threads:[~2024-10-10 11:29 UTC|newest]

Thread overview: 4+ 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 [this message]
2024-10-11  8:16   ` Dan Jacobson
2024-10-11  9:28     ` Eli Zaretskii

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=86set419j7.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=73727@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 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.