unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: Stefan Kangas <stefan@marxist.se>
Cc: "18340@debbugs.gnu.org" <18340@debbugs.gnu.org>
Subject: bug#18340: [External] : Re: bug#18340: 24.4.50; Bad UI for `find-file-literally'
Date: Mon, 11 Oct 2021 01:06:09 +0000	[thread overview]
Message-ID: <SJ0PR10MB5488D8BA4C6008A671999286F3B59@SJ0PR10MB5488.namprd10.prod.outlook.com> (raw)
In-Reply-To: <CADwFkm=H=7=N7TrL7KTjkRZZ_9DACLAEcPy044wfd-OqauC=sg@mail.gmail.com>

It's hard for me to believe that this bug report
hasn't been understood.  Let me try one last time.

Emacs 27.2, emacs -Q

foo.el is an existing Elisp file (contents not important).
_______

(setq resize-mini-windows nil)

C-x C-f foo.el

M-x find-file-literally RET foo.el RET

  Do you want to revisit the file literally now? (y or n) y

  You can run the command ‘find-file-literally’ with M-x f-f-l RET

  The file foo.el is already visited normally.
_______

That's all you see.  It's not understandable (to
me).  However, if I go look in *Messages* I see
this additional text, which was not visible
because `resize-mini-windows' is nil:
________
 You have asked to visit it literally,
 meaning no coding system decoding, format conversion, or local variables.
 But Emacs can visit a file in only one way at a time.
________

If you still don't understand the problem, drop it.

But if you now understand the problem, and repro it,
then I'll ask you to reread the original bug report
and see if it doesn't make sense on its own.

I think it does, and I'd completely forgotten about
this bug report.  I just read it afresh myself now,
and I just did what it describes, and saw the
reported problem immediately.

Clearly I'm missing something about what's missing
in others trying to understand this.

  reply	other threads:[~2021-10-11  1:06 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-27 21:37 bug#18340: 24.4.50; Bad UI for `find-file-literally' Drew Adams
2016-05-04  0:59 ` Lars Ingebrigtsen
2016-05-04 14:47   ` Eli Zaretskii
2021-10-10 22:30 ` Stefan Kangas
2021-10-11  1:06   ` Drew Adams [this message]
2021-10-11 11:57     ` bug#18340: [External] : " Eli Zaretskii
2021-10-11  6:17   ` Juri Linkov
2021-10-11 11:41     ` Stefan Kangas

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=SJ0PR10MB5488D8BA4C6008A671999286F3B59@SJ0PR10MB5488.namprd10.prod.outlook.com \
    --to=drew.adams@oracle.com \
    --cc=18340@debbugs.gnu.org \
    --cc=stefan@marxist.se \
    /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).