This is from the help page on the extension:
The optional "[repository]" section specifies the line endings to use for
files stored
in the repository. It has a single setting, "native", which determines the
storage line
endings for files declared as "native" in the "[patterns]" section. It can
be
On 2011-02-01 15:33, Discrete Dreamscape wrote:
> Possible cover-all solution: use Mercurial's "eol" extension. It's
> worked pretty well for me so far, and handily autofixed all the DOS
> endings in a particular fork I looked at in one go. It works much like
> the autoprops configuration does i
Possible cover-all solution: use Mercurial's "eol" extension. It's worked
pretty well for me so far, and handily autofixed all the DOS endings in a
particular fork I looked at in one go. It works much like the autoprops
configuration does in Subversion; hopefully with less pain.
Enable it (should
For those that have already followed the instructions there - the coding
standard says to prefer tabs, not spaces, which is the opposite of what the
page was instructing until just now.
Celi
On Tue, Feb 1, 2011 at 7:35 AM, Oz Linden (Scott Lawrence) wrote:
> Other than a few files that appear
Added Programmer's Notepad (my favorite for Windows).
Ricky
Cron Stardust
On Tue, Feb 1, 2011 at 4:35 AM, Oz Linden (Scott Lawrence)
wrote:
> Other than a few files that appear to be completely Windows specific,
> and I did not know for sure did not require them, I've converted all the
> DOS lin
Other than a few files that appear to be completely Windows specific,
and I did not know for sure did not require them, I've converted all the
DOS line endings in viewer-development back to plain linefeeds. I'll be
checking regularly for any that get added (hopefully before they get
into the m
