On 6/17/2016 5:33 PM, Scott Robison wrote:
On Fri, Jun 17, 2016 at 6:04 PM, Warren Young mailto:w...@etr-usa.com>> wrote:
For any blob data that Fossil considers “text,” why not strip all
CRs on ingest, then based on either a setting or platform check
inject CRs as necessary wh
On Fri, Jun 17, 2016 at 6:04 PM, Warren Young wrote:
> On Jun 17, 2016, at 1:59 PM, Scott Robison
> wrote:
> >
> > Would it be a bad thing to just settle on LF only going forward, always
> stripping CR?
>
> The argument over canonicalizing all text input to LF has been had here
> before — with m
On Jun 17, 2016, at 1:59 PM, Scott Robison wrote:
>
> Would it be a bad thing to just settle on LF only going forward, always
> stripping CR?
The argument over canonicalizing all text input to LF has been had here before
— with me as at least one of its proponents — but I did not get the sense
On Fri, Jun 17, 2016 at 1:53 PM, Warren Young wrote:
> While trying to replicate the problem reported in another thread,[1] I
> noticed an odd behavior. If I edit a comment via fossil ui, then pull the
> change and try to edit it locally with fossil amend, Vim shows ^M
> characters at the end of
While trying to replicate the problem reported in another thread,[1] I noticed
an odd behavior. If I edit a comment via fossil ui, then pull the change and
try to edit it locally with fossil amend, Vim shows ^M characters at the end of
every line, implying that Fossil UI has transformed the LF
5 matches
Mail list logo