Re: write-region bug ?

[Eli Zaretskii]

> From: Stefan Monnier <address@hidden>
> Cc: address@hidden,  address@hidden,
>   address@hidden
> Date: Sat, 04 Jan 2020 23:54:56 -0500
> 
> > 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.
> 
> I can entertain the idea that some package out there somehow calls
> write-region with a non-nil `visit` and a string as `start`, but I'm
> hard pressed to imagine a case where this is useful.
> What kind of scenario do you have in mind?

I don't think we must imagine a specific scenario to justify
NON-removal of an old feature, just because someone became confused by
the doc string.  But since you asked...

  (write-region 1 1024 "foo")
  (write-region "\nEnd-of-foo\n." nil "foo" t t)