Re: write-region bug ?

[Jean-Christophe Helary <jean.christophe.helary@traduction-libre.org>]

> On Jan 10, 2020, at 2:03, Eli Zaretskii <eliz@gnu.org> wrote:
> 
>> From: Jean-Christophe Helary <jean.christophe.helary@traduction-libre.org>
>> Date: Thu, 9 Jan 2020 23:39:56 +0900
>> 
>> As I've written in this thread, the manual too was not helping much, neither were the doc strings, so I'm not sure from where I could 
>> 
>>> "have a clear idea what does "visiting a file" means for a buffer and its relation with the file it visits."
> 
> Experience, I guess.

Let me politely suggest, "clearer explanations and edits in the manual." Although nobody has a duty to give explanations, there is a point where replies stop being helpful at all.

Also, somebody who seems to have read what I wrote earlier sent me this offlist:

>> 4) I try to save the modification, not aware, from the frame info or
>> from anywhere else, that I'm targeting ~/B.txt: > > → [Echo] A.txt changed on disk; really edit the buffer? (y, n, r or C-h)
> This is plainly a bug -- buffer-file-truename isn't being updated to match buffer-file-name.  I think that the inexcusable parts of what follows are (mostly) the result of this point.

Thank you to that person.

Jean-Christophe Helary
-----------------------------------------------
http://mac4translators.blogspot.com @brandelune