2009/10/24 altufa...@mail.com
Last time I used vi, it showed ^M at end of each line... does the new
version classify files as DOS/Unix and handles edits correctly?
vim (the most common vi variant in use nowadays) is incredibly
configurable. I guarantee you that there's an option for handling
Subject: Re: [fossil-users] Developing on Unix and Windows
vi
emacs
s.
On Fri, Oct 23, 2009 at 8:09 AM, altufa...@mail.com wrote:
I'm not much familiar with editors in unix. Are there good editors in
unix that handle \r\n correctly?
- Altu
-Original Message-
From: Joshua Paine
Am Samstag 24 Oktober 2009 schrieb Dmitry Chestnykh:
Hi,
Instead of making Fossil call filters, why not create scripts that
call Fossil?
my_commit:
#!/bin/sh
run_filter
fossil commit %@
my_checkout:
#!/bin/sh
fossil checkout %@
run_filter
Yes, that also would be a solution.
] Developing on Unix and Windows
Hello,
The conversion of line endings does not affect at all to its sha1
checksum
as it is only an input/output filter. The internal representation of
the file inside
fossil continues to be unique.
Some files need conversion and some other no. In cvs, when
On Wed, Oct 21, 2009 at 01:57:36PM +0200, Ramon Ribó wrote:
Hello,
When developing the same program on Unix and on Windows, cvs
automatically converts the line
end of the files to the appropriates for every platform. In this way,
if we commit a file in windows that
contains \r\n as
On Oct 21, 2009, at 10:36 AM, Ramon Ribó wrote:
In any case, what is your proposal for using fossil to manage a
program
both in unix and windows?
Simple: Use a text editor on windows that understands \n-only line
endings. I understand that they are plentiful.
D. Richard Hipp
On Wed, 2009-10-21 at 16:36 +0200, Ramon Ribó wrote:
In any case, what is your proposal for using fossil to manage a program
both in unix and windows?
Use a competent text editor? Essentially every text editor meant for
programmers can trivially convert line endings or edit in either mode.
Please, do not oversimplify the situation. Just one example:
1- A TCL file is checked in on windows
2- It is checked out on unix and line ending is \r\n
3- Many TCL files start with:
#!/bin/sh
# the next line restarts using wish \
exec wish $0 $@
4- chmod +x
Frankly, though, probably not enough that I
would want to see such an ugly feature built into fossil.
I also like beautiful things and hate ugly things. But life is
sometimes difficult and it is better to fix problems instead
of workaround them.
An alternative solution could be:
fossil
9 matches
Mail list logo
