From: Eli Zaretskii <eliz@gnu.org>
To: Jarek Czekalski <jarekczek@poczta.onet.pl>
Cc: 16062@debbugs.gnu.org
Subject: bug#16062: [SPAM] bug#16062: 24.3; Missing .png file gives poor error message when opened
Date: Fri, 06 Dec 2013 10:38:55 +0200 [thread overview]
Message-ID: <83vbz21ihs.fsf@gnu.org> (raw)
In-Reply-To: <52A18350.8090108@poczta.onet.pl>
> Date: Fri, 06 Dec 2013 08:57:04 +0100
> From: Jarek Czekalski <jarekczek@poczta.onet.pl>
>
> W dniu 2013-12-06 08:18, Eli Zaretskii pisze:
> > How should Emacs know whether you intend to visit an existing file or
> > create a new one?
>
> It seems so easy to determine what is the intention of visiting a png
> file.
Is it? What if I come up with an Emacs mode that lets users _create_
PNG files?
> But if Emacs admin does not know that, then I assume I make some
> silly newbie mistake and it is in fact impossible.
I didn't ask the (slightly provocative) question to indicate that I
consider your request silly. I asked it to put the issue in
perspective. I agree it would be good to make the error message more
clear in this case, I just suggest that we think about the possible
alternatives to "File does not exist", because we don't show such a
message when users visit non-existent files.
IOW, I submit that the problem is with image-mode throwing an error in
this case, instead of showing "(New file)" in the echo area, just like
we do with any non-existing file. We could also turn image-mode off
in such a case, although the correctness of that is less clear to me.
next prev parent reply other threads:[~2013-12-06 8:38 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-05 21:27 bug#16062: 24.3; Missing .png file gives poor error message when opened Alex Willisson
2013-12-06 7:18 ` Eli Zaretskii
2013-12-06 7:57 ` bug#16062: [SPAM] " Jarek Czekalski
2013-12-06 8:38 ` Eli Zaretskii [this message]
2013-12-06 21:05 ` Jarek Czekalski
2013-12-07 7:27 ` Eli Zaretskii
2013-12-13 21:58 ` Juri Linkov
2013-12-14 6:51 ` Eli Zaretskii
2020-08-20 18:10 ` Lars Ingebrigtsen
2020-08-20 18:29 ` Eli Zaretskii
2020-08-20 18:39 ` Lars Ingebrigtsen
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=83vbz21ihs.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=16062@debbugs.gnu.org \
--cc=jarekczek@poczta.onet.pl \
/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.