From: martin rudalics <rudalics@gmx.at>
To: 11156@debbugs.gnu.org
Subject: bug#11156: 24.0.95; require-final-newline and read-only files
Date: Sat, 14 Apr 2012 20:56:57 +0200 [thread overview]
Message-ID: <4F89C879.6070209@gmx.at> (raw)
In-Reply-To: <20120414134925.D1D9B20217@saturn.ch.ristopher.com>
>> cd /tmp
>> echo -n rms > rms
>> chmod u=r rms
>> emacs -q
>> eval: (setq require-final-newline 'visit)
>> C-x C-f /tmp/rms RET
>>
>> There is a new buffer but no window displays it. The
>> *Messages*-buffer contains `find-file-noselect-1: Buffer is read-only:
>> #<buffer rms>'
>
> It is annoying that one needs to manually switch to the buffer after
> finding a read-only file. But, more important, find-file-hook is not
> run. This breaks lots of packages and makes this issue a severe one for
> me.
`after-find-file' shouldn't try adding a newline if `buffer-read-only'
is non-nil. And the values 'visit and 'visit-save should be documented
in the Elisp manual.
martin
next prev parent reply other threads:[~2012-04-14 18:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-02 21:52 bug#11156: 24.0.95; require-final-newline and read-only files Christopher Schmidt
2012-04-14 13:49 ` Christopher Schmidt
2012-04-14 18:56 ` martin rudalics [this message]
2012-04-15 13:48 ` Christopher Schmidt
2012-04-18 6:25 ` Chong Yidong
2012-05-01 17:02 ` Christopher Schmidt
2012-05-06 5:01 ` Chong Yidong
2012-09-02 18:55 ` bug#11156: 24.2.50; require-final-newline and read-only files (was: bug#11156: 24.0.95; require-final-newline and read-only files) Christopher Schmidt
2012-09-07 10:53 ` bug#11156: 24.2.50; require-final-newline and read-only files Chong Yidong
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=4F89C879.6070209@gmx.at \
--to=rudalics@gmx.at \
--cc=11156@debbugs.gnu.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).