Re: [fossil-users] Developing on Unix and Windows

2009-10-24 Thread altufaltu 
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?


- Altu


-Original Message-
From: Stephen De Gabrielle spdegabrie...@gmail.com
To: fossil-users@lists.fossil-scm.org
Sent: Fri, Oct 23, 2009 1:44 pm
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 jos...@letterblock.com
 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
   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 as your default and no one gets hurt. Everything except Notepad can
 view it fine.

   1- I create a nice README or License file for my application in unix
   3- README files are open by the user (not by my that I use a
 wonderful
  convert-all editor). In Windows, they typically open with
 Notepad.
   4- The file is viewed as with one very long line

 Since your end users are not likely to checkout your code from fossil, I
 don't think fossil's behavior is very relevant here. Either create your
 README with windows line endings, or add some kind of conversion into
 your build process when you produce packages for end users.

 For source code, my experience is that unix endings work everywhere for
 running or viewing--except windows notepad. If there is any language
 available on both windows and linux where a file will run/compile on
 windows if it has windows endings *but not* if it has unix endings and
 likewise will run on linux only with unix endings, then I have some
 sympathy for your plight. Frankly, though, probably not enough that I
 would want to see such an ugly feature built into fossil.

 --
 Joshua Paine
 LetterBlock: Web applications built with joy
 http://letterblock.com/
 301-576-1920

 ___
 fossil-users mailing list
 fossil-users@lists.fossil-scm.org
 http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users


 ___
 fossil-users mailing list
 fossil-users@lists.fossil-scm.org
 http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users




-- 

--
Stephen De Gabrielle
stephen.degabrie...@acm.org
Telephone +44 (0)20 85670911
Mobile+44 (0)79 85189045
http://www.degabrielle.name/stephen
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users


 




___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] Committing a subdirectory

2009-10-24 Thread D. Richard Hipp 

On Oct 24, 2009, at 10:57 AM, Nick B wrote:

 I have a number of modified files but I would like to commit only a
 few files in a single subdirectory.

 Typing fossil changes returns
 snip list of EDITED files
 MISSING  brightside/images/bg.gif
 EDITED   brightside/images/headerbg.gif
 EDITED   brightside/images/tableft.gif
 EDITED   brightside/images/tabright.gif

 In the parent directory if I enter:
 fossil commit images or fossil commit images/ returns
 fossil: fossil knows nothing about: images/

 Similarly if I use:

 fossil commit images/* returns
 fossil: fossil knows nothing about: images/bg.gif.old

 In this case the file bg.gif.old can be safely ignored as I only want
 to commit edited files.

 What command do I use to commit the subdirectory images?

There is no command to commit a subdirectory.  You can commit  
individual files by naming them on the commit command-line, but there  
is no shorthand for specifying all the files in a subdirectory.

In your case, it might work to do:

 fossil commit images/*.gif

since the .gif suffix will omit the .old file.  But there is no  
general solution at this time.

You are welcomed to contribute one :-)



 Thanks
 ___
 fossil-users mailing list
 fossil-users@lists.fossil-scm.org
 http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

D. Richard Hipp
d...@hwaci.com



___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] Developing on Unix and Windows

2009-10-24 Thread Rüdiger Härtel 
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.

Ruediger
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users