: Re: [fossil-users] Developing on Unix and Windows
2009/10/24
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
2009/10/24
> 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 pretty
much anyt
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
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
--
Dmitry Chestnykh
Coding Robots
http://www.codingrobots.com
dmi...@codingrobots.com
On 24.10.2009, a
Hello,
I want to throw in my 2 cents, too.
I don't see why fossil shouldn't provide any facility to run files through a
filter or preprocessor before checkin, after check out and maybe there are
other actions when running a file through a filter is useful or necessary.
When a developer uses t
To: fossil-users@lists.fossil-scm.org
> Sent: __aolWsbDateToL10n__Wed, 21 Oct 2009 11:42:47
> -0400__aolWsbDateToL10n__
> Subject: Re: [fossil-users] Developing on Unix and Windows
>
> On Wed, 2009-10-21 at 17:09 +0200, Ramon Ribó wrote:
>> 1- A TCL file is checked in on windows
t; Sent: __aolWsbDateToL10n__Wed, 21 Oct 2009 11:42:47
> -0400__aolWsbDateToL10n__
> Subject: Re: [fossil-users] Developing on Unix and Windows
>
> On Wed, 2009-10-21 at 17:09 +0200, Ramon Ribó wrote:
>> 1- A TCL file is checked in on windows
>> 2- It is checked out on uni
ossil-users] Developing on Unix and Windows
On Wed, 2009-10-21 at 17:09 +0200, Ramon Ribó wrote:
> 1- A TCL file is checked in on windows
> 2- It is checked out on unix and line ending is "\r\n"
When the file is created on Windows, it should be created using unix
line endings.
My proposal is to use an editor that is aware of DOS and UNIX line
endings.
- Altu
-Original Message-
From: Ramon Ribó
To: fossil-users@lists.fossil-scm.org
Sent: __aolWsbDateToL10n__Wed, 21 Oct 2009 16:36:47
+0200__aolWsbDateToL10n__
Subject: Re: [fossil-users] Developing on Unix
On Wed, 2009-10-21 at 18:47 +0200, Ramon Ribó wrote:
> 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.
If there is, in fact, a problem. Obviously I can't tell you you don't
have a problem if you thi
> 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 setti
On Wed, 2009-10-21 at 17:09 +0200, Ramon Ribó wrote:
> 1- A TCL file is checked in on windows
> 2- It is checked out on unix and line ending is "\r\n"
When the file is created on Windows, it should be created using unix
line endings. This is very easy to do in most editors. You can just set
it
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- chmo
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.
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
d...
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 adding a file
it is necessary to s
On Oct 21, 2009, at 7:57 AM, 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 line ends
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
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 line ends, we can checkout this file on unix and it
will have "\n" li
19 matches
Mail list logo
