From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: jean.christophe.helary@traduction-libre.org,
schwab@linux-m68k.org, emacs-devel@gnu.org
Subject: Re: write-region bug ?
Date: Sun, 05 Jan 2020 05:37:18 +0200 [thread overview]
Message-ID: <83r20efua9.fsf@gnu.org> (raw)
In-Reply-To: <jwv4kxa7ruw.fsf-monnier+emacs@gnu.org> (message from Stefan Monnier on Sat, 04 Jan 2020 17:58:21 -0500)
> From: Stefan Monnier <monnier@iro.umontreal.ca>
> Cc: schwab@linux-m68k.org, jean.christophe.helary@traduction-libre.org,
> emacs-devel@gnu.org
> Date: Sat, 04 Jan 2020 17:58:21 -0500
>
> >> OTOH, the VISIT argument can't make sense when the text comes from
> >> a string rather than from a buffer.
> >
> > Why does it not make sense? FILENAME is still provided.
>
> VISIT basically tells that the buffer should be considered as
> visiting FILENAME. Here, we have VISIT and FILENAME but we don't have
> the buffer (except that by accident).
I don't think it's up to us to second-guess the caller, whether this
is an accident or not. I can envision legitimate use cases where this
can be useful.
next prev parent reply other threads:[~2020-01-05 3:37 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 [this message]
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
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=83r20efua9.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=jean.christophe.helary@traduction-libre.org \
--cc=monnier@iro.umontreal.ca \
--cc=schwab@linux-m68k.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).