[fossil-users] Command-line wildcards
I actually wanted to simply post a bug report to the ticket system, but it's telling me it will be deleted unless I go through the hoops of the mailing list registration process. (Uh?!? Why then technically enable anonymous ticket submissions in the 1st place?) Oh well... My findings: In a directory that contains several .* files and subfolders, several *.css files and a single .php file, the following work fine with version 1.24, but only output a usage info with 1.25+ (fossil: Usage: fossil set ?PROPERTY? ?VALUE?): fossil set ignore-glob .* fossil set ignore-glob *.css But *this one* works with both versions: fossil set ignore-glob *.php My conclusion is this must have something to do with command line argument globing (so I assume it has something to do with ticket [8ca2aae391], but I can't be sure), and argument separation, b/c it seems to work if the wildcard expands to a single directory entry. I switched back to version 1.24 b/c of this, but I'm hoping this can be fixed. Best regards, Zoc ___ 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] Command-line wildcards
On Wed, Aug 21, 2013 at 7:49 AM, fossilscm@xoxy.net wrote: I actually wanted to simply post a bug report to the ticket system, but it's telling me it will be deleted unless I go through the hoops of the mailing list registration process. (Uh?!? Why then technically enable anonymous ticket submissions in the 1st place?) Oh well... My findings: In a directory that contains several .* files and subfolders, several *.css files and a single .php file, the following work fine with version 1.24, but only output a usage info with 1.25+ (fossil: Usage: fossil set ?PROPERTY? ?VALUE?): fossil set ignore-glob .* fossil set ignore-glob *.css Did you try quoting to prevent the command-line wildcard expansion? fossil set ignore-glob .* But *this one* works with both versions: fossil set ignore-glob *.php My conclusion is this must have something to do with command line argument globing (so I assume it has something to do with ticket [8ca2aae391], but I can't be sure), and argument separation, b/c it seems to work if the wildcard expands to a single directory entry. I switched back to version 1.24 b/c of this, but I'm hoping this can be fixed. Best regards, Zoc ___ 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...@sqlite.org ___ 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] Command-line wildcards
Yes, I did. (That was my 1st thought, too.) Sorry, forgot to mention it. On Wed, Aug 21, 2013 at 1:51 PM, Richard Hipp - d...@sqlite.org fossilscm.zoc.5877ad8d94.drh#sqlite@ob.0sg.net wrote: On Wed, Aug 21, 2013 at 7:49 AM, fossilscm@xoxy.net wrote: I actually wanted to simply post a bug report to the ticket system, but it's telling me it will be deleted unless I go through the hoops of the mailing list registration process. (Uh?!? Why then technically enable anonymous ticket submissions in the 1st place?) Oh well... My findings: In a directory that contains several .* files and subfolders, several *.css files and a single .php file, the following work fine with version 1.24, but only output a usage info with 1.25+ (fossil: Usage: fossil set ?PROPERTY? ?VALUE?): fossil set ignore-glob .* fossil set ignore-glob *.css Did you try quoting to prevent the command-line wildcard expansion? fossil set ignore-glob .* But *this one* works with both versions: fossil set ignore-glob *.php My conclusion is this must have something to do with command line argument globing (so I assume it has something to do with ticket [8ca2aae391], but I can't be sure), and argument separation, b/c it seems to work if the wildcard expands to a single directory entry. I switched back to version 1.24 b/c of this, but I'm hoping this can be fixed. Best regards, Zoc ___ 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...@sqlite.org ___ 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] Command-line wildcards
2013/8/21 fossilscm@xoxy.net: In a directory that contains several .* files and subfolders, several *.css files and a single .php file, the following work fine with version 1.24, but only output a usage info with 1.25+ (fossil: Usage: fossil set ?PROPERTY? ?VALUE?): This is already fixed in version 1.26. Regards, Jan Nijtmans ___ 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] Command-line wildcards
2013/8/21 Jan Nijtmans jan.nijtm...@gmail.com: 2013/8/21 fossilscm@xoxy.net: In a directory that contains several .* files and subfolders, several *.css files and a single .php file, the following work fine with version 1.24, but only output a usage info with 1.25+ (fossil: Usage: fossil set ?PROPERTY? ?VALUE?): This is already fixed in version 1.26. Oops, I was too fast without reading the message well. Correct answer is: There are two possible ways: - Use fossil ui, go to Admin-Settings and modify the settings there. - Quote it with single quotes. Regards, Jan Nijtmans ___ 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] Command-line wildcards
On Wed, Aug 21, 2013 at 1:49 PM, fossilscm@xoxy.net wrote: I actually wanted to simply post a bug report to the ticket system, but it's telling me it will be deleted unless I go through the hoops of the mailing list registration process. (Uh?!? Why then technically enable anonymous ticket submissions in the 1st place?) Oh well... To cut down on bug db junk. Fossil is of a size where any pressing issues are covered directly on the mailing lists. We rarely go through the tickets and things get lost that way (it would be fair to call this a cultural issue, but there has so far been no pressing need for change there). If someone brings it up on the list first, the chances of the bug getting addressed skyrocket from near 0 to... well, above 0 ;). -- - stephan beal http://wanderinghorse.net/home/stephan/ http://gplus.to/sgbeal ___ 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] Command-line wildcards
@Jan: Nope it's not fixed in 1.26. In fact I noticed it with 1.26, then regressed to 1.25 to check if the bug was there, then to 1.24. (I intentionally used the plus sign when referring to 1.25+) On Wed, Aug 21, 2013 at 1:56 PM, Jan Nijtmans - jan.nijtm...@gmail.com fossilscm.zoc.1c6a0fe4b8.jan.nijtmans#gmail@ob.0sg.net wrote: 2013/8/21 fossilscm@xoxy.net: In a directory that contains several .* files and subfolders, several *.css files and a single .php file, the following work fine with version 1.24, but only output a usage info with 1.25+ (fossil: Usage: fossil set ?PROPERTY? ?VALUE?): This is already fixed in version 1.26. Regards, Jan Nijtmans ___ 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] Command-line wildcards
Just re-confirmed: $ fossil set ignore-glob *.css Usage: fossil set ?PROPERTY? ?VALUE? $ fossil ver This is fossil version 1.26 [c9cb6e7293] 2013-06-18 21:09:23 UTC On Wed, Aug 21, 2013 at 2:10 PM, Zoran Isailovski fossilscm@xoxy.netwrote: @Jan: Nope it's not fixed in 1.26. In fact I noticed it with 1.26, then regressed to 1.25 to check if the bug was there, then to 1.24. (I intentionally used the plus sign when referring to 1.25+) On Wed, Aug 21, 2013 at 1:56 PM, Jan Nijtmans - jan.nijtm...@gmail.com fossilscm.zoc.1c6a0fe4b8.jan.nijtmans#gmail@ob.0sg.net wrote: 2013/8/21 fossilscm@xoxy.net: In a directory that contains several .* files and subfolders, several *.css files and a single .php file, the following work fine with version 1.24, but only output a usage info with 1.25+ (fossil: Usage: fossil set ?PROPERTY? ?VALUE?): This is already fixed in version 1.26. Regards, Jan Nijtmans ___ 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] Command-line wildcards
Thanks for the advice. However, I had already tried the single quote thing earlier, but I dismissed it, because AFAIK single quotes are not handled as string delimiters in the Windows shell, and: $ fossil set ignore-glob *.xxx $ fossil set ignore-glob ignore-glob (local) *.xxx But: $ fossil set ignore-glob '*.css' $ fossil set ignore-glob ignore-glob (local) '*.css' The single quotes become part of the property value. (Not sure if this stops fossil from processing it correctly though.) Be that as it may, both the fossil ui thing and the single quote thing can IMO only be workarounds, not the real deal; the latter b/c numerous other scripts (of mine, but I'd assume of other people too) depend on a normal argument passing. On Wed, Aug 21, 2013 at 1:59 PM, Jan Nijtmans - jan.nijtm...@gmail.com fossilscm.zoc.1c6a0fe4b8.jan.nijtmans#gmail@ob.0sg.net wrote: 2013/8/21 Jan Nijtmans jan.nijtm...@gmail.com: 2013/8/21 fossilscm@xoxy.net: In a directory that contains several .* files and subfolders, several *.css files and a single .php file, the following work fine with version 1.24, but only output a usage info with 1.25+ (fossil: Usage: fossil set ?PROPERTY? ?VALUE?): This is already fixed in version 1.26. Oops, I was too fast without reading the message well. Correct answer is: There are two possible ways: - Use fossil ui, go to Admin-Settings and modify the settings there. - Quote it with single quotes. Regards, Jan Nijtmans ___ 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] Command-line wildcards
@ Stephan Beal: So fossil is refusing to eat it's own dog food - or rather one of its more unique assets: The integrated wiki and ticket system? :-) But since I must accept the culture of the place I'm visiting, perhaps you can help out a novice mailman list fellow: Is there any way to only receive emails from threads I am participating in? On Wed, Aug 21, 2013 at 1:59 PM, Stephan Beal - sgb...@googlemail.com fossilscm.zoc.4adf3ee589.sgbeal#googlemail@ob.0sg.net wrote: On Wed, Aug 21, 2013 at 1:49 PM, fossilscm@xoxy.net wrote: I actually wanted to simply post a bug report to the ticket system, but it's telling me it will be deleted unless I go through the hoops of the mailing list registration process. (Uh?!? Why then technically enable anonymous ticket submissions in the 1st place?) Oh well... To cut down on bug db junk. Fossil is of a size where any pressing issues are covered directly on the mailing lists. We rarely go through the tickets and things get lost that way (it would be fair to call this a cultural issue, but there has so far been no pressing need for change there). If someone brings it up on the list first, the chances of the bug getting addressed skyrocket from near 0 to... well, above 0 ;). -- - stephan beal http://wanderinghorse.net/home/stephan/ http://gplus.to/sgbeal ___ 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] Command-line wildcards
On Wed, Aug 21, 2013 at 2:31 PM, fossilscm@xoxy.net wrote: @ Stephan Beal: So fossil is refusing to eat it's own dog food - or rather one of its more unique assets: The integrated wiki and ticket system? :-) This problem is Windows-specific. In every Unix shell *.css, '*.css will be equivalent (they arrive in the app _without_ the quotes). Using *.css MIGHT be equivalent: most shells will not expand the wildcard unless there is a match, and if there is no match then they leave it intact (bash has a configuration option to change this and replace a non-matching wildcard with an empty string). The main difference is that in Unix the shell does a surprising amount of pre-processing of the CLI args before passing them on the app, meaning that all apps get a consistent view of CLI args. Windows, OTOH leaves the developer to do it all himself. The dogfood here is without a doubt the Windows shell. But since I must accept the culture of the place I'm visiting, perhaps you can help out a novice mailman list fellow: Is there any way to only receive emails from threads I am participating in? i haven't used Windows (outside of customer sites and an occasional game of Empire at War) since last millennium - i can't suggest much of anything in that regard except maybe to find something more... well, more. :) -- - stephan beal http://wanderinghorse.net/home/stephan/ http://gplus.to/sgbeal ___ 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] Command-line wildcards
It's a problem with the way MinGW parses and passes the command line. When main is called in fossil, the arguments are already expanded. As for the fix, I am not sure yet. On Wed, Aug 21, 2013 at 2:36 PM, Stephan Beal sgb...@googlemail.com wrote: On Wed, Aug 21, 2013 at 2:31 PM, fossilscm@xoxy.net wrote: @ Stephan Beal: So fossil is refusing to eat it's own dog food - or rather one of its more unique assets: The integrated wiki and ticket system? :-) This problem is Windows-specific. In every Unix shell *.css, '*.css will be equivalent (they arrive in the app _without_ the quotes). Using *.css MIGHT be equivalent: most shells will not expand the wildcard unless there is a match, and if there is no match then they leave it intact (bash has a configuration option to change this and replace a non-matching wildcard with an empty string). The main difference is that in Unix the shell does a surprising amount of pre-processing of the CLI args before passing them on the app, meaning that all apps get a consistent view of CLI args. Windows, OTOH leaves the developer to do it all himself. The dogfood here is without a doubt the Windows shell. But since I must accept the culture of the place I'm visiting, perhaps you can help out a novice mailman list fellow: Is there any way to only receive emails from threads I am participating in? i haven't used Windows (outside of customer sites and an occasional game of Empire at War) since last millennium - i can't suggest much of anything in that regard except maybe to find something more... well, more. :) -- - stephan beal http://wanderinghorse.net/home/stephan/ http://gplus.to/sgbeal ___ 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] Command-line wildcards
On Wed, Aug 21, 2013 at 8:31 AM, fossilscm@xoxy.net wrote: @ Stephan Beal: So fossil is refusing to eat it's own dog food - or rather one of its more unique assets: The integrated wiki and ticket system? :-) We find that anonymously contributed tickets and wiki are generally of low quality, and not the sort of thing that we want to preserve in the permanent record of a repository. Hence we have chosen to filter through the mailing list first. This is a judgement call. You can run your project differently, if you desire. Wiki and ticketing are used extensively in self-hosting Fossil - dogfood is eaten - just not by anonymous. -- D. Richard Hipp d...@sqlite.org ___ 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] Command-line wildcards
Following change fixes it for met with MinGW 32 bit on windows 7.
$ fossil diff src/main.c
argc in wmain 3
--- src/main.c
+++ src/main.c
@@ -522,11 +522,13 @@
*/
#if defined(_WIN32) !defined(BROKEN_MINGW_CMDLINE)
int _dowildcard = -1; /* This turns on command-line globbing in MinGW-w64
*/
int wmain(int argc, wchar_t **argv)
#else
+int_CRT_glob = 0;
int main(int argc, char **argv)
+
#endif
{
const char *zCmdName = unknown;
int idx;
int rc;
I did not test this with the 64bit version of MinGW. Using an unquoted * in
this case still works as expected.
Mark
On Wed, Aug 21, 2013 at 2:42 PM, Mark Janssen mpc.jans...@gmail.com wrote:
It's a problem with the way MinGW parses and passes the command line. When
main is called in fossil, the arguments are already expanded. As for the
fix, I am not sure yet.
On Wed, Aug 21, 2013 at 2:36 PM, Stephan Beal sgb...@googlemail.comwrote:
On Wed, Aug 21, 2013 at 2:31 PM, fossilscm@xoxy.net wrote:
@
Stephan Beal: So fossil is refusing to eat it's own dog food - or
rather one of its more unique assets: The integrated wiki and ticket
system? :-)
This problem is Windows-specific. In every Unix shell *.css, '*.css
will be equivalent (they arrive in the app _without_ the quotes). Using
*.css MIGHT be equivalent: most shells will not expand the wildcard unless
there is a match, and if there is no match then they leave it intact (bash
has a configuration option to change this and replace a non-matching
wildcard with an empty string).
The main difference is that in Unix the shell does a surprising amount of
pre-processing of the CLI args before passing them on the app, meaning that
all apps get a consistent view of CLI args. Windows, OTOH leaves the
developer to do it all himself.
The dogfood here is without a doubt the Windows shell.
But since I must accept the culture of the place I'm visiting, perhaps
you can help out a novice mailman list fellow: Is there any way to only
receive emails from threads I am participating in?
i haven't used Windows (outside of customer sites and an occasional game
of Empire at War) since last millennium - i can't suggest much of anything
in that regard except maybe to find something more... well, more.
:)
--
- stephan beal
http://wanderinghorse.net/home/stephan/
http://gplus.to/sgbeal
___
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] Command-line wildcards
On Wed, Aug 21, 2013 at 2:48 PM, Mark Janssen mpc.jans...@gmail.com wrote: I did not test this with the 64bit version of MinGW. Using an unquoted * in this case still works as expected. as expected means, i assume: resolves to a list of all files matching * in the current directory? (That's the expected Unix behaviour, anyway.) -- - stephan beal http://wanderinghorse.net/home/stephan/ http://gplus.to/sgbeal ___ 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] Command-line wildcards
Yes, for example fossil add * will still do the right thing. On Wed, Aug 21, 2013 at 2:51 PM, Stephan Beal sgb...@googlemail.com wrote: On Wed, Aug 21, 2013 at 2:48 PM, Mark Janssen mpc.jans...@gmail.comwrote: I did not test this with the 64bit version of MinGW. Using an unquoted * in this case still works as expected. as expected means, i assume: resolves to a list of all files matching * in the current directory? (That's the expected Unix behaviour, anyway.) -- - stephan beal http://wanderinghorse.net/home/stephan/ http://gplus.to/sgbeal ___ 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] Command-line wildcards
Sorry for spamming, but with the change it works within msys, but it fails on the windows command line. Seems like a bit of a Catch 22 caused by the different idea windows and unix have about how to pass arguments. On Wed, Aug 21, 2013 at 2:52 PM, Mark Janssen mpc.jans...@gmail.com wrote: Yes, for example fossil add * will still do the right thing. On Wed, Aug 21, 2013 at 2:51 PM, Stephan Beal sgb...@googlemail.comwrote: On Wed, Aug 21, 2013 at 2:48 PM, Mark Janssen mpc.jans...@gmail.comwrote: I did not test this with the 64bit version of MinGW. Using an unquoted * in this case still works as expected. as expected means, i assume: resolves to a list of all files matching * in the current directory? (That's the expected Unix behaviour, anyway.) -- - stephan beal http://wanderinghorse.net/home/stephan/ http://gplus.to/sgbeal ___ 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] Command-line wildcards
2013/8/21 Mark Janssen mpc.jans...@gmail.com: Sorry for spamming, but with the change it works within msys, but it fails on the windows command line. Seems like a bit of a Catch 22 caused by the different idea windows and unix have about how to pass arguments. See: http://www.fossil-scm.org/fossil/info/8ca2aae391 And: http://www.fossil-scm.org/fossil/info/8205c01cd4 Different people have different expectations. Regards, Jan Nijtmans ___ 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] Command-line wildcards
@Stephen: But since I must accept the culture of the place I'm visiting, perhaps you can help out a novice mailman list fellow: Is there any way to only receive emails from threads I am participating in? i haven't used Windows (outside of customer sites and an occasional game of Empire at War) since last millennium - i can't suggest much of anything in that regard except maybe to find something more... well, more. Uh? My question was about the mailman mailing list?!? How is that related to Windows? In any other respect, I take your response as rather... snobbish. Not sure how much of it represent the fossil position, but If fossil does not *want* to support windows, then it should remove the windows edition instead of so obviously looking down on its (I'd suppose many) windows users. But thanks anyway. :-( On Wed, Aug 21, 2013 at 2:36 PM, Stephan Beal - sgb...@googlemail.com fossilscm.zoc.4adf3ee589.sgbeal#googlemail@ob.0sg.net wrote: On Wed, Aug 21, 2013 at 2:31 PM, fossilscm@xoxy.net wrote: @ Stephan Beal: So fossil is refusing to eat it's own dog food - or rather one of its more unique assets: The integrated wiki and ticket system? :-) This problem is Windows-specific. In every Unix shell *.css, '*.css will be equivalent (they arrive in the app _without_ the quotes). Using *.css MIGHT be equivalent: most shells will not expand the wildcard unless there is a match, and if there is no match then they leave it intact (bash has a configuration option to change this and replace a non-matching wildcard with an empty string). The main difference is that in Unix the shell does a surprising amount of pre-processing of the CLI args before passing them on the app, meaning that all apps get a consistent view of CLI args. Windows, OTOH leaves the developer to do it all himself. The dogfood here is without a doubt the Windows shell. But since I must accept the culture of the place I'm visiting, perhaps you can help out a novice mailman list fellow: Is there any way to only receive emails from threads I am participating in? i haven't used Windows (outside of customer sites and an occasional game of Empire at War) since last millennium - i can't suggest much of anything in that regard except maybe to find something more... well, more. :) -- - stephan beal http://wanderinghorse.net/home/stephan/ http://gplus.to/sgbeal ___ 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] Command-line wildcards
Uhm, perhaps a naive outsider question, but how came the issue wasn't there before 1.25, if it's the differences in how the different shells process CLI arguments? Did the shells not remain the same in between? On Wed, Aug 21, 2013 at 3:02 PM, Mark Janssen - mpc.jans...@gmail.com fossilscm.zoc.aac92b9903.mpc.janssen#gmail@ob.0sg.net wrote: Sorry for spamming, but with the change it works within msys, but it fails on the windows command line. Seems like a bit of a Catch 22 caused by the different idea windows and unix have about how to pass arguments. On Wed, Aug 21, 2013 at 2:52 PM, Mark Janssen mpc.jans...@gmail.comwrote: Yes, for example fossil add * will still do the right thing. On Wed, Aug 21, 2013 at 2:51 PM, Stephan Beal sgb...@googlemail.comwrote: On Wed, Aug 21, 2013 at 2:48 PM, Mark Janssen mpc.jans...@gmail.comwrote: I did not test this with the 64bit version of MinGW. Using an unquoted * in this case still works as expected. as expected means, i assume: resolves to a list of all files matching * in the current directory? (That's the expected Unix behaviour, anyway.) -- - stephan beal http://wanderinghorse.net/home/stephan/ http://gplus.to/sgbeal ___ 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 ___ 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] Command-line wildcards
On Wed, Aug 21, 2013 at 9:23 AM, fossilscm@xoxy.net wrote: Uhm, perhaps a naive outsider question, but how came the issue wasn't there before 1.25, if it's the differences in how the different shells process CLI arguments? Did the shells not remain the same in between? My guess is that the one of the prebuild binaries was compiled with MinGW and the other with MSVC. -- D. Richard Hipp d...@sqlite.org ___ 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] Command-line wildcards
On Wed, Aug 21, 2013 at 3:18 PM, fossilscm@xoxy.net wrote: Uh? My question was about the mailman mailing list?!? How is that related to Windows? Because your top-post came immediately after such a question i took it out of context. In any other respect, I take your response as rather... snobbish. Not sure how much of it represent the fossil position, but If Nothing i say should be interpreted as an official statement unless Richard echoes me ;). i'm just a minion here (though admittedly a loud one. ;) Feel free to ignore anything i say and i won't take it personally. i apologize if it came across as snobbish (i did - i admit that). i was following the wildcard thread and i get really sick of people blaming fossil for Windows' broken CLI handling and filename/getenv encoding, which puts me in a snarky state of mind. My apologies for that. fossil does not *want* to support windows, then it should remove the windows edition instead of so obviously looking down on its (I'd suppose many) windows users. But thanks anyway. :-( Fossil wants to - _i_ don't want to ;). Plenty of people here have put in a great deal of effort to work around Windows' deficiencies (and yes, they are deficiencies). As a good example, the filename handling code - all of it is there only to support OS(es) which do their own thing regarding encoding of filenames. -- - stephan beal http://wanderinghorse.net/home/stephan/ http://gplus.to/sgbeal ___ 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] Command-line wildcards
@Stephan Beal: Thanks man. And I'll admit I might have been a tick too sensible about it. :-) I'm very well aware that Windows is a bloated piece of ... code full of deficiencies. But if something used to work well up to a certain version (I'm using fossil since years, could have been 0.something if memory serves), it does come accross... eccentric... to blame the OS (whichever it is) all of a sudden. Anyway, I did not want to go in too deep about the whole matter. I thought you guys would want feedback on issues because it is a chance to improve things (and make them work even on the crappiest of platforms ;-)). It wasn't my intention to judge or blame anyone or anything. On Wed, Aug 21, 2013 at 4:15 PM, Stephan Beal - sgb...@googlemail.com fossilscm.zoc.4adf3ee589.sgbeal#googlemail@ob.0sg.net wrote: On Wed, Aug 21, 2013 at 3:18 PM, fossilscm@xoxy.net wrote: Uh? My question was about the mailman mailing list?!? How is that related to Windows? Because your top-post came immediately after such a question i took it out of context. In any other respect, I take your response as rather... snobbish. Not sure how much of it represent the fossil position, but If Nothing i say should be interpreted as an official statement unless Richard echoes me ;). i'm just a minion here (though admittedly a loud one. ;) Feel free to ignore anything i say and i won't take it personally. i apologize if it came across as snobbish (i did - i admit that). i was following the wildcard thread and i get really sick of people blaming fossil for Windows' broken CLI handling and filename/getenv encoding, which puts me in a snarky state of mind. My apologies for that. fossil does not *want* to support windows, then it should remove the windows edition instead of so obviously looking down on its (I'd suppose many) windows users. But thanks anyway. :-( Fossil wants to - _i_ don't want to ;). Plenty of people here have put in a great deal of effort to work around Windows' deficiencies (and yes, they are deficiencies). As a good example, the filename handling code - all of it is there only to support OS(es) which do their own thing regarding encoding of filenames. -- - stephan beal http://wanderinghorse.net/home/stephan/ http://gplus.to/sgbeal ___ 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] Command-line wildcards
On Wed, Aug 21, 2013 at 7:43 PM, fossilscm@xoxy.net wrote: @Stephan Beal: Thanks man. And I'll admit I might have been a tick too sensible about it. :-) ...Anyway, I did not want to go in too deep about the whole matter. I thought you guys would want feedback on issues because it is a chance to improve things (and make them work even on the crappiest of platforms ;-)). It wasn't my intention to judge or blame anyone or anything. You weren't at all out of line/over-sensitive. i took your post out of context and responded poorly to it (regardless of context). We very much appreciate any and all feedback, and a negative response from one of the devs (in this case me) does not in any way reflect on the feedback itself (well, except that Richard's decisions trump all others ;). -- - stephan beal http://wanderinghorse.net/home/stephan/ http://gplus.to/sgbeal ___ 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] Command-line wildcards
@Richard: My guess is that the one of the prebuild binaries was compiled with MinGW and the other with MSVC. Just to provide some information so you can verify your guess: I've been using fossil since years now, (on XP, Vista, and now Win7,) and I updated regularly (though I can't be sure I got every single update). I never had this issue (nor any other - kudos!) until 1.25. So if the used compiler varied randomly, the assumption doesn't hold - as I surely would have hit at least some MinGW-compiled version. On Wed, Aug 21, 2013 at 3:50 PM, Richard Hipp - d...@sqlite.org fossilscm.zoc.5877ad8d94.drh#sqlite@ob.0sg.net wrote: On Wed, Aug 21, 2013 at 9:23 AM, fossilscm@xoxy.net wrote: Uhm, perhaps a naive outsider question, but how came the issue wasn't there before 1.25, if it's the differences in how the different shells process CLI arguments? Did the shells not remain the same in between? My guess is that the one of the prebuild binaries was compiled with MinGW and the other with MSVC. -- D. Richard Hipp d...@sqlite.org ___ 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
