GNU bug report logs - #49193
Document require-final-newline vs. readonly files

Previous Next

Full log

Message #22 received at 49193 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: Michael Heerdegen <michael_heerdegen <at> web.de>
Cc: 49193 <at> debbugs.gnu.org, jidanni <at> jidanni.org
Subject: Re: bug#49193: Document require-final-newline vs. readonly files
Date: Fri, 25 Jun 2021 09:07:31 +0300

> From: Michael Heerdegen <michael_heerdegen <at> web.de>
> Cc: eliz <at> gnu.org,  jidanni <at> jidanni.org
> Date: Fri, 25 Jun 2021 00:08:34 +0200
> 
> | If the value is ‘visit’, Emacs adds a newline at the end of any file
> | that doesn’t have one, just after it visits the file...
> 
> But that's not true, is it?  The file is not touched.  Is the newline
> still added to the file's buffer?  Or not even that (because the buffer
> is read-only)?
> 
> Would
> 
> | [...] Emacs adds a newline at the end of any file's buffer that
> | doesn’t have one, just after it visits the file...
> 
> be clearer?

Depends on the beholder, I guess.  Many newbies don't understand the
fine difference, and have trouble with the idea that Emacs doesn't
generally manipulate files for editing.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.