Since open-command parses filenames for colons (:) if the filename contains a colon, it'll fail to open. This isn't common as I don't think that's a POSIX filename but some guy at work thought it was would fun to use datetimes as file names...
I'm not sure what the best solution is but I think that I'll make it so that ait only cares about the colon if the string after it is a value number. I don't think there would be many cases where that will be an issue. For example, 2023-11-07T16:50.sql wouldn't trigger the line number colon thing because 50.sql isn't a number.
Since open-command parses filenames for colons (:) if the filename contains a colon, it'll fail to open. This isn't common as I don't think that's a POSIX filename but some guy at work thought it was would fun to use datetimes as file names...
I'm not sure what the best solution is but I think that I'll make it so that ait only cares about the colon if the string after it is a value number. I don't think there would be many cases where that will be an issue. For example, `2023-11-07T16:50.sql` wouldn't trigger the line number colon thing because `50.sql` isn't a number.
Kevin "The Nuclear" Bloom
Since open-command parses filenames for colons (:) if the filename contains a colon, it'll fail to open. This isn't common as I don't think that's a POSIX filename but some guy at work thought it was would fun to use datetimes as file names...
I'm not sure what the best solution is but I think that I'll make it so that ait only cares about the colon if the string after it is a value number. I don't think there would be many cases where that will be an issue. For example,
2023-11-07T16:50.sqlwouldn't trigger the line number colon thing because50.sqlisn't a number.