unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Jean-Christophe Helary <jean.christophe.helary@traduction-libre.org>
To: Emacs developers <emacs-devel@gnu.org>
Subject: Re: write-region bug ?
Date: Thu, 9 Jan 2020 00:27:35 +0900	[thread overview]
Message-ID: <81246516-A350-4E2A-9F1C-F80BFA0C0316@traduction-libre.org> (raw)
In-Reply-To: <219F7B4D-88EA-4EE3-A8EB-244A08F43B63@traduction-libre.org>



> On Jan 6, 2020, at 14:58, Jean-Christophe Helary <jean.christophe.helary@traduction-libre.org> wrote:
> 
> 
> 
>> On Jan 6, 2020, at 14:29, Eli Zaretskii <eliz@gnu.org> wrote:
>> 
>> This is explained at the very beginning of the "Files" node in the Emacs manual.  The Glossary also explains that under Saving and under Visiting. These are very basic notions in Emacs, so if the relations between a buffer visiting a file and what happens when you save that buffer aren't clear to you, I suggest a good reading of those parts in the manual.
> 
> I'm right there. Thank you.


File A.txt contains:
(write-region "stuff" nil "B.txt" nil t nil t)

File B.txt is empty until I run file A.txt.


The manual says:

25.4 Writing to Files

write-region

"If visit is t, then Emacs establishes an association between the buffer and the file: the buffer is then visiting that file."


25.1 Visiting Files

"Visiting a file means reading a file into a buffer. Once this is done, we say that the buffer is visiting that file, and call the file the visited file of the buffer."


→ My understanding from the above manual quotes is that file B.txt is read into the buffer where file A.txt is.

I don't know how that should look like, but what I see is seemingly the opposite: full contents of file A.txt is written to file B.txt.

There is obviously something that I am missing in the documentation.

Jean-Christophe 


  reply	other threads:[~2020-01-08 15:27 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-02 16:54 write-region bug ? Jean-Christophe Helary
2020-01-02 17:08 ` Andreas Schwab
2020-01-02 17:22   ` Jean-Christophe Helary
2020-01-02 17:25   ` Eli Zaretskii
2020-01-02 17:35     ` Jean-Christophe Helary
2020-01-04 19:58     ` Stefan Monnier
2020-01-04 20:19       ` Eli Zaretskii
2020-01-04 22:58         ` Stefan Monnier
2020-01-05  2:01           ` Jean-Christophe Helary
2020-01-05  3:33             ` Eli Zaretskii
2020-01-05  5:14               ` Jean-Christophe Helary
2020-01-05 15:20                 ` Eli Zaretskii
2020-01-05  3:37           ` Eli Zaretskii
2020-01-05  4:54             ` Stefan Monnier
2020-01-05 15:35               ` Eli Zaretskii
2020-01-05 16:42                 ` Jean-Christophe Helary
2020-01-06  3:37                   ` Eli Zaretskii
2020-01-06  3:50                     ` Jean-Christophe Helary
2020-01-06  5:29                       ` Eli Zaretskii
2020-01-06  5:58                         ` Jean-Christophe Helary
2020-01-08 15:27                           ` Jean-Christophe Helary [this message]
2020-01-08 16:05                             ` Eli Zaretskii
2020-01-09  0:04                               ` Jean-Christophe Helary
2020-01-09  0:43                                 ` Noam Postavsky
2020-01-09 12:30                             ` Jean-Christophe Helary
2020-01-09 14:07                               ` Eli Zaretskii
2020-01-09 14:39                                 ` Jean-Christophe Helary
2020-01-09 17:03                                   ` Eli Zaretskii
2020-01-09 23:21                                     ` Jean-Christophe Helary
2020-01-05 17:37                 ` Stefan Monnier
2020-01-05 18:26                   ` Eli Zaretskii
2020-01-05 19:27                     ` Stefan Monnier

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=81246516-A350-4E2A-9F1C-F80BFA0C0316@traduction-libre.org \
    --to=jean.christophe.helary@traduction-libre.org \
    --cc=emacs-devel@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).