On Fri, 09 Mar 2012 08:53:21 +0100
Martijn Coppoolse
li...@martijn.coppoolse.com wrote:
Why is that a bad practice? Because there's programs (like Fossil)
that won't let you work with them?
The first three hits on Google with the query using brackets in filenames
gives:
On Fri, Mar 9, 2012 at 04:18, Gour g...@atmarama.net wrote:
What do you mean 'pre-existing'? Software is created by you. Can you
show me some sotware project using names with such funky characters?
Gour,
one size fits all does not work in real life. For instance, brackets,
spaces, etc. are
Leo,
I think that you have described fairly well the situation.
I am a Unix/Windows user since the Silicon Graphics time. I would never
put brackets on a file name. However, I fail to understand why the SCM tool
should prohibit to do so to people that think differently. Specially on
On Fri, Mar 9, 2012 at 1:04 PM, Ramon Ribó ram...@compassis.com wrote:
To create a fossil branch with the modification is a practical idea only
if you are a lonely developer or in a very controlled team. How do you say
to a new developer?: Please use fossil, but not the standard one, because
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
On Fri, Mar 9, 2012 at 07:11, Stephan Beal sgb...@googlemail.com wrote:
Perhaps we could/should make the set of illegal characters a config option,
defaulting to the current set?
This may cause problem with globing.
--Leo--
___
fossil-users mailing
Lol...
coincidently i was just reading:
http://www.boost.org/doc/libs/1_49_0/libs/filesystem/v3/doc/tutorial.html
and their tut5.cpp example demonstrates using \u263A (a smiley face!) in
filenames.
--
- stephan beal
http://wanderinghorse.net/home/stephan/
http://gplus.to/sgbeal
I'm in the mood for some long winded editorializing
Bob Coder is moving his development team off of AntiquatedSCM and on to one
of the fancy new distributed SCMs that are all the rage. They look at git
but it seems kinda complicated and one of the devs suggests Fossil. Wow,
nice, simple,
If it is just three lines of code that filter out those characters, how
difficult would it be to wrap those into a configurable option, enabled
by default but with an option to disable for those who really know what
they're doing?
best,
Steve
On 3/8/2012 6:22 PM, Matt Welland wrote:
I'm
On 09/03/2012, at 8:22 AM, Matt Welland wrote:
I'm in the mood for some long winded editorializing
Bob Coder is moving his development team off of AntiquatedSCM and on to one
of the fancy new distributed SCMs that are all the rage. They look at git but
it seems kinda complicated and
On 8 March 2012 03:18, Gour g...@atmarama.net wrote:
I already voiced a release engineer's reluctance to pursue Fossil due
to the restriction of '[]'s.
I'm with computers since time of Apple's IIe and never encountered need
to have filenames with '[]'s.
Never worked with VMS then, I'm
On Fri, 9 Mar 2012 12:07:18 +0800
Michael Richter ttmrich...@gmail.com
wrote:
Never worked with VMS then, I'm gathering. Or a few other such OSes.
I did work with VMS, but didn't own VMS machine...even used punchcards
with IBM 370...but, still, never encountered need for having those
strange
On Thu, 8 Mar 2012 17:22:14 -0700
Matt Welland estifo...@gmail.com wrote:
IMHO a more viable philosophy is to use documentation and methodology
to make seamless interoperability between Windows and Unix/Linux
possible for teams that need it. Otherwise where possible and where
the code cost is
Matt Wellandestifo...@gmail.com wrote:
IMHO a more viable philosophy is to use documentation and methodology
to make seamless interoperability between Windows and Unix/Linux
possible for teams that need it. Otherwise where possible and where
the code cost is not too high, independently make
Thank you for examples. I wish to say that I have a high regard for
the work being done and my objections were and are sole for putting
that work and effort to good use.
In some contexts fossil might try to treat [abcdef] as a uuid or wiki page
name, and would fail to do so (or, just as bad,
2012/3/7 sky5w...@gmail.com:
If you are considering cross-platform issues, is it not unreasonable
to add your choice of CSM's requirements?
A brief wiki survey lists the older win95 VFAT restrictions include:
|\?*:+[]/
I understand the effort to prevent trouble (and that's what people
will
On Tue, Mar 6, 2012 at 4:14 PM, Ștefan Fulea fulea.ste...@gmail.com wrote:
I've looked at the posts related to prohibited characters and I still
don't get it! The addition of files containing square brackets - why
does it have to be an error? Why isn't it just a warning? If you don't
I remember having tried to fossilize files in the Ms Office 2007 formats;
the docx, xlsx, etc. formats are merely zips containing mainly XML files.
The
root file is called [Content-Types].xml
Even if it is not sane to include such characters in file names, those
characters
happen to exist.
On
On Wed, 7 Mar 2012 07:11:58 +0100
Benoit Mortgat mort...@gmail.com wrote:
I remember having tried to fossilize files in the Ms Office 2007
formats; the docx, xlsx, etc. formats are merely zips containing
mainly XML files.
When I need to track such files (e.g. Gnucash, Gnumeric), I save them
19 matches
Mail list logo
