On Fri, 9 Mar 2012 06:51:14 -0500 Leo Razoumov <slonik...@gmail.com> wrote:
> one size fits all does not work in real life. I'm aware of it. > For instance, brackets, spaces, etc. are used in file names generated > by certain medical imagining machines. Do those 'medical' machines create text files? > And when you deal with medical technicians, nurses, medical students > and above all physicians telling them that your software cannot handle > file names with spaces is a sure bet to loose their interest. > I agree that if I am naming a file, I will > produce a name that is shell friendly and avoid using random > characters. But I should be able, in principle, to import someone > else's file which is named using different conventions. > That said, I personally have no problem maintaining a separate branch > where I modify fossil code to suit my needs. OK. That's my point. Fossil is meant for specific purpose and why make it vulnerable for those using it 'according to the spec' because some users have strange needs? > You can think of OOXML as compressed tar archives. They are text XML > files underneath. I know about them. Just tried to save one file in LibreOffice as flat-xml (.fodt extension) so where is the problem with brackets? The file can be normally named and saved. Btw, I use Gnucash & Gnumeric non-compressed files and track them with Fossil, so I know what I'm talking about. > You can diff and merge them the same way you diff and merge regular > XML or HTML files. You just store and track OOXML files in expanded > form. Good luck. ;) > Tooling and retooling should not be too intrusive. Remember, tools are > here to help people not to add extra hustle to their already complex > work. If your tool is a nuisance people will shun using it. Not > everyone is as passionate about SCM tools as people on this list. It's not the point about being passionate about SCM tools, but the point is to use SCM tools "for what they are meant"! I did ask on this list how to 'abuse' Fossil and use it to track patient records in our small clinic, but I have to be aware that such usage is not in accordance with original usage of Fossil and have to adjust to the situation. Trying to use hammer (Fossil) believing that all files are nails is the problem I'm talking here, nothing else. > Please, keep discussion devoid of emotions. It is a technical list and > we are all friends here. What emotions? I tried to give sincere advise if people find that Fossil is not according to their needs. If you have burning need to track empty dirs, I will simply point out that Mercurial is not the tool for you. Why should Mercurial adjust to those wanting tracking empty dirs if it's against their design? Fortunately, there are enough choices, and they're even free if maintaining separate branch and three lines of code is too much. Richard's explanation: >The reason such names are disallowed is because they are prone to error. >Not in Fossil itself, but in other software. For example: optional external >merge and diff programs that people might choose to set up. So for safety's >sake , Fossil goes to the extra trouble of disallowing them. is very clear and since he is giving software for free, it's simple as "take it or leave it". btw, if you look in the archives I was (amongst others) complaining a lot about Fossil not having support 'standard' wiki markup (e.g. markdown), but after putting everything on the scale, I've decided that things which Fossil provides are outweighting missing bits. Simple like that and no emotions and I'm ending this thread from my side. ;) Sincerely, Gour -- Not by merely abstaining from work can one achieve freedom from reaction, nor by renunciation alone can one attain perfection. http://atmarama.net | Hlapicina (Croatia) | GPG: 52B5C810
signature.asc
Description: PGP signature
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
