From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Eli Zaretskii <eliz@gnu.org>
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 14:27:29 -0500 [thread overview]
Message-ID: <jwvtv594sgz.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <83blrhg3pi.fsf@gnu.org> (Eli Zaretskii's message of "Sun, 05 Jan 2020 20:26:01 +0200")
>> > (write-region 1 1024 "foo")
>> > (write-region "\nEnd-of-foo\n." nil "foo" t t)
>>
>> Which is just as naturally written:
>>
>> (write-region 1 1024 "foo" nil t)
>> (write-region "\nEnd-of-foo\n." nil "foo" t)
>
> But that doesn't make the former illegitimate.
It's not a legitimate *need*. It's a use that happens to work, but it
doesn't show a use-case where you *need* this odd corner case.
So, I'm still at the same point as before: I can imagine existing code
which happens to use this behavior, but not code which needs
this behavior.
> So I don't see any reason to declare it unsupported.
It's simply to try and help users not to shoot themselves in the foot.
I know we usually don't try very hard, so it's not crucial.
Stefan
prev parent reply other threads:[~2020-01-05 19: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
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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=jwvtv594sgz.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=jean.christophe.helary@traduction-libre.org \
--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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.