From: SourceForge.net <no...@so...> - 2007-05-17 00:31:09
|
Feature Requests item #1711398, was opened at 2007-05-02 10:27 Message generated for change (Comment added) made by miesfeld You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=684733&aid=1711398&group_id=119701 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: APIs Group: None >Status: Pending >Resolution: Accepted Priority: 5 Private: No Submitted By: Swifty (steve_j_swift) >Assigned to: Mark Miesfeld (miesfeld) Summary: SysFileTree Case independant filename matching Initial Comment: There seems to be no way (on systems with case sensitive filesystems) with SysFileTree of finding, for example *.jpg where "jpg" could be in any case. The only mechanism seems to be to search for *.* then select the files that match *.jpg in REXX itself. This can be very time consuming. I would suggest adding "I" to the SysFileTree options, implying case-insensitive matching, in the same way that "I" implies case-insensitive sorting in SysStemSort. Doing in SysFileTree should be faster than doing it in REXX. I've been asked why the files are in varying case in the first place. They've been deposited in a public directory from a variety of case-independant systems, so we have no control of the case of the files. ---------------------------------------------------------------------- >Comment By: Mark Miesfeld (miesfeld) Date: 2007-05-16 17:31 Message: Logged In: YES user_id=191588 Originator: NO This is implemented in SVN with revision 389. ---------------------------------------------------------------------- Comment By: Swifty (steve_j_swift) Date: 2007-05-05 09:31 Message: Logged In: YES user_id=1364573 Originator: YES I was going to say: Lee, you already have what you want - just miss the "I" off the sysfile options... :-) ---------------------------------------------------------------------- Comment By: Mark Miesfeld (miesfeld) Date: 2007-05-04 23:37 Message: Logged In: YES user_id=191588 Originator: NO Lee, In your example of foobar, FOOBAR, and FooBar - there is no "correct" one. The 'correct' answer is all three. What Steve wants, is to be able to find all 3 files, without knowing ahead of time what the (case sensitive) spelling of any of them is. If he specifies *bar, he only gets one of them. Although, for what Steve really wants, this is a better example: pict.jpg myPict.JPG pictures.jpg seacoast.txt seacoast.Jpg doc.doc sample.txt README.first first.jPG He wants to use SysFileTree to pull all the *.jpg files out (no matter how the users have named their files.) I can see how people might find use for this. For instance, say in large source tree you want to gather up all the 'readme' files and do some processing on them. But, you don't know if the read me files are ReadMe, readme.first README, etc. A case insensitive search for *readme* would be userful. I had just this problem a few months ago with the Linux source tree. Of course there are ways to do this using standard Unix tools. But, some things are easier to do in ooRexx, for some people, than they are using sed, awk, and find. <grin. ---------------------------------------------------------------------- Comment By: pragmatic_lee (pragmatic_lee) Date: 2007-05-04 13:13 Message: Logged In: YES user_id=1223125 Originator: NO Consider this: Filespec says to find all files named "FOOBAR" Linux is perfectly happy with "different" files in the same folder having these names foobar -- lower case FOOBAR -- upper case FooBar -- camel case If a case insensitive SysFileTree is run, then all 3 of the above would match - which one is the correct one? My suggestion is to "honor" the case sensitivity of the Linux file system. ---------------------------------------------------------------------- Comment By: Mark Miesfeld (miesfeld) Date: 2007-05-04 09:53 Message: Logged In: YES user_id=191588 Originator: NO I'm the one that encouraged Steve to open this RFE. I did that more to try and promote participation in the project than a belief it was a desperately needed enhancement. <grin> After a quick glance at the code, it looks doable to me. So, I think the question is more of is it something that should be done. I also guess I should move the discussion over to the developers list; it is not likely to be very visible here. ---------------------------------------------------------------------- Comment By: Rick McGuire (bigrixx) Date: 2007-05-03 03:37 Message: Logged In: YES user_id=1125291 Originator: NO This is just an acknowlegement that your RFE has been received. This particular extension is going to require some discussion among the developers about whether it can or should be implemented. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=684733&aid=1711398&group_id=119701 |
From: SourceForge.net <no...@so...> - 2007-05-17 12:47:01
|
Feature Requests item #1711398, was opened at 2007-05-02 12:27 Message generated for change (Comment added) made by wdashley You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=684733&aid=1711398&group_id=119701 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: APIs >Group: Next Release Status: Pending >Resolution: Fixed Priority: 5 Private: No Submitted By: Swifty (steve_j_swift) Assigned to: Mark Miesfeld (miesfeld) Summary: SysFileTree Case independant filename matching Initial Comment: There seems to be no way (on systems with case sensitive filesystems) with SysFileTree of finding, for example *.jpg where "jpg" could be in any case. The only mechanism seems to be to search for *.* then select the files that match *.jpg in REXX itself. This can be very time consuming. I would suggest adding "I" to the SysFileTree options, implying case-insensitive matching, in the same way that "I" implies case-insensitive sorting in SysStemSort. Doing in SysFileTree should be faster than doing it in REXX. I've been asked why the files are in varying case in the first place. They've been deposited in a public directory from a variety of case-independant systems, so we have no control of the case of the files. ---------------------------------------------------------------------- >Comment By: David Ashley (wdashley) Date: 2007-05-17 07:47 Message: Logged In: YES user_id=931756 Originator: NO The docs are updated in SVN revision 390 for this RFE. ---------------------------------------------------------------------- Comment By: Mark Miesfeld (miesfeld) Date: 2007-05-16 19:31 Message: Logged In: YES user_id=191588 Originator: NO This is implemented in SVN with revision 389. ---------------------------------------------------------------------- Comment By: Swifty (steve_j_swift) Date: 2007-05-05 11:31 Message: Logged In: YES user_id=1364573 Originator: YES I was going to say: Lee, you already have what you want - just miss the "I" off the sysfile options... :-) ---------------------------------------------------------------------- Comment By: Mark Miesfeld (miesfeld) Date: 2007-05-05 01:37 Message: Logged In: YES user_id=191588 Originator: NO Lee, In your example of foobar, FOOBAR, and FooBar - there is no "correct" one. The 'correct' answer is all three. What Steve wants, is to be able to find all 3 files, without knowing ahead of time what the (case sensitive) spelling of any of them is. If he specifies *bar, he only gets one of them. Although, for what Steve really wants, this is a better example: pict.jpg myPict.JPG pictures.jpg seacoast.txt seacoast.Jpg doc.doc sample.txt README.first first.jPG He wants to use SysFileTree to pull all the *.jpg files out (no matter how the users have named their files.) I can see how people might find use for this. For instance, say in large source tree you want to gather up all the 'readme' files and do some processing on them. But, you don't know if the read me files are ReadMe, readme.first README, etc. A case insensitive search for *readme* would be userful. I had just this problem a few months ago with the Linux source tree. Of course there are ways to do this using standard Unix tools. But, some things are easier to do in ooRexx, for some people, than they are using sed, awk, and find. <grin. ---------------------------------------------------------------------- Comment By: pragmatic_lee (pragmatic_lee) Date: 2007-05-04 15:13 Message: Logged In: YES user_id=1223125 Originator: NO Consider this: Filespec says to find all files named "FOOBAR" Linux is perfectly happy with "different" files in the same folder having these names foobar -- lower case FOOBAR -- upper case FooBar -- camel case If a case insensitive SysFileTree is run, then all 3 of the above would match - which one is the correct one? My suggestion is to "honor" the case sensitivity of the Linux file system. ---------------------------------------------------------------------- Comment By: Mark Miesfeld (miesfeld) Date: 2007-05-04 11:53 Message: Logged In: YES user_id=191588 Originator: NO I'm the one that encouraged Steve to open this RFE. I did that more to try and promote participation in the project than a belief it was a desperately needed enhancement. <grin> After a quick glance at the code, it looks doable to me. So, I think the question is more of is it something that should be done. I also guess I should move the discussion over to the developers list; it is not likely to be very visible here. ---------------------------------------------------------------------- Comment By: Rick McGuire (bigrixx) Date: 2007-05-03 05:37 Message: Logged In: YES user_id=1125291 Originator: NO This is just an acknowlegement that your RFE has been received. This particular extension is going to require some discussion among the developers about whether it can or should be implemented. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=684733&aid=1711398&group_id=119701 |
From: SourceForge.net <no...@so...> - 2007-10-03 12:34:47
|
Feature Requests item #1711398, was opened at 2007-05-02 13:27 Message generated for change (Settings changed) made by bigrixx You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=684733&aid=1711398&group_id=119701 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: APIs >Group: v3.2.0 Status: Pending Resolution: Fixed Priority: 5 Private: No Submitted By: Swifty (steve_j_swift) Assigned to: Mark Miesfeld (miesfeld) Summary: SysFileTree Case independant filename matching Initial Comment: There seems to be no way (on systems with case sensitive filesystems) with SysFileTree of finding, for example *.jpg where "jpg" could be in any case. The only mechanism seems to be to search for *.* then select the files that match *.jpg in REXX itself. This can be very time consuming. I would suggest adding "I" to the SysFileTree options, implying case-insensitive matching, in the same way that "I" implies case-insensitive sorting in SysStemSort. Doing in SysFileTree should be faster than doing it in REXX. I've been asked why the files are in varying case in the first place. They've been deposited in a public directory from a variety of case-independant systems, so we have no control of the case of the files. ---------------------------------------------------------------------- Comment By: David Ashley (wdashley) Date: 2007-05-17 08:47 Message: Logged In: YES user_id=931756 Originator: NO The docs are updated in SVN revision 390 for this RFE. ---------------------------------------------------------------------- Comment By: Mark Miesfeld (miesfeld) Date: 2007-05-16 20:31 Message: Logged In: YES user_id=191588 Originator: NO This is implemented in SVN with revision 389. ---------------------------------------------------------------------- Comment By: Swifty (steve_j_swift) Date: 2007-05-05 12:31 Message: Logged In: YES user_id=1364573 Originator: YES I was going to say: Lee, you already have what you want - just miss the "I" off the sysfile options... :-) ---------------------------------------------------------------------- Comment By: Mark Miesfeld (miesfeld) Date: 2007-05-05 02:37 Message: Logged In: YES user_id=191588 Originator: NO Lee, In your example of foobar, FOOBAR, and FooBar - there is no "correct" one. The 'correct' answer is all three. What Steve wants, is to be able to find all 3 files, without knowing ahead of time what the (case sensitive) spelling of any of them is. If he specifies *bar, he only gets one of them. Although, for what Steve really wants, this is a better example: pict.jpg myPict.JPG pictures.jpg seacoast.txt seacoast.Jpg doc.doc sample.txt README.first first.jPG He wants to use SysFileTree to pull all the *.jpg files out (no matter how the users have named their files.) I can see how people might find use for this. For instance, say in large source tree you want to gather up all the 'readme' files and do some processing on them. But, you don't know if the read me files are ReadMe, readme.first README, etc. A case insensitive search for *readme* would be userful. I had just this problem a few months ago with the Linux source tree. Of course there are ways to do this using standard Unix tools. But, some things are easier to do in ooRexx, for some people, than they are using sed, awk, and find. <grin. ---------------------------------------------------------------------- Comment By: pragmatic_lee (pragmatic_lee) Date: 2007-05-04 16:13 Message: Logged In: YES user_id=1223125 Originator: NO Consider this: Filespec says to find all files named "FOOBAR" Linux is perfectly happy with "different" files in the same folder having these names foobar -- lower case FOOBAR -- upper case FooBar -- camel case If a case insensitive SysFileTree is run, then all 3 of the above would match - which one is the correct one? My suggestion is to "honor" the case sensitivity of the Linux file system. ---------------------------------------------------------------------- Comment By: Mark Miesfeld (miesfeld) Date: 2007-05-04 12:53 Message: Logged In: YES user_id=191588 Originator: NO I'm the one that encouraged Steve to open this RFE. I did that more to try and promote participation in the project than a belief it was a desperately needed enhancement. <grin> After a quick glance at the code, it looks doable to me. So, I think the question is more of is it something that should be done. I also guess I should move the discussion over to the developers list; it is not likely to be very visible here. ---------------------------------------------------------------------- Comment By: Rick McGuire (bigrixx) Date: 2007-05-03 06:37 Message: Logged In: YES user_id=1125291 Originator: NO This is just an acknowlegement that your RFE has been received. This particular extension is going to require some discussion among the developers about whether it can or should be implemented. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=684733&aid=1711398&group_id=119701 |
From: SourceForge.net <no...@so...> - 2007-11-03 15:23:57
|
Feature Requests item #1711398, was opened at 2007-05-02 12:27 Message generated for change (Settings changed) made by wdashley You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=684733&aid=1711398&group_id=119701 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: APIs Group: v3.2.0 >Status: Closed Resolution: Fixed Priority: 5 Private: No Submitted By: Swifty (steve_j_swift) Assigned to: Mark Miesfeld (miesfeld) Summary: SysFileTree Case independant filename matching Initial Comment: There seems to be no way (on systems with case sensitive filesystems) with SysFileTree of finding, for example *.jpg where "jpg" could be in any case. The only mechanism seems to be to search for *.* then select the files that match *.jpg in REXX itself. This can be very time consuming. I would suggest adding "I" to the SysFileTree options, implying case-insensitive matching, in the same way that "I" implies case-insensitive sorting in SysStemSort. Doing in SysFileTree should be faster than doing it in REXX. I've been asked why the files are in varying case in the first place. They've been deposited in a public directory from a variety of case-independant systems, so we have no control of the case of the files. ---------------------------------------------------------------------- Comment By: David Ashley (wdashley) Date: 2007-05-17 07:47 Message: Logged In: YES user_id=931756 Originator: NO The docs are updated in SVN revision 390 for this RFE. ---------------------------------------------------------------------- Comment By: Mark Miesfeld (miesfeld) Date: 2007-05-16 19:31 Message: Logged In: YES user_id=191588 Originator: NO This is implemented in SVN with revision 389. ---------------------------------------------------------------------- Comment By: Swifty (steve_j_swift) Date: 2007-05-05 11:31 Message: Logged In: YES user_id=1364573 Originator: YES I was going to say: Lee, you already have what you want - just miss the "I" off the sysfile options... :-) ---------------------------------------------------------------------- Comment By: Mark Miesfeld (miesfeld) Date: 2007-05-05 01:37 Message: Logged In: YES user_id=191588 Originator: NO Lee, In your example of foobar, FOOBAR, and FooBar - there is no "correct" one. The 'correct' answer is all three. What Steve wants, is to be able to find all 3 files, without knowing ahead of time what the (case sensitive) spelling of any of them is. If he specifies *bar, he only gets one of them. Although, for what Steve really wants, this is a better example: pict.jpg myPict.JPG pictures.jpg seacoast.txt seacoast.Jpg doc.doc sample.txt README.first first.jPG He wants to use SysFileTree to pull all the *.jpg files out (no matter how the users have named their files.) I can see how people might find use for this. For instance, say in large source tree you want to gather up all the 'readme' files and do some processing on them. But, you don't know if the read me files are ReadMe, readme.first README, etc. A case insensitive search for *readme* would be userful. I had just this problem a few months ago with the Linux source tree. Of course there are ways to do this using standard Unix tools. But, some things are easier to do in ooRexx, for some people, than they are using sed, awk, and find. <grin. ---------------------------------------------------------------------- Comment By: pragmatic_lee (pragmatic_lee) Date: 2007-05-04 15:13 Message: Logged In: YES user_id=1223125 Originator: NO Consider this: Filespec says to find all files named "FOOBAR" Linux is perfectly happy with "different" files in the same folder having these names foobar -- lower case FOOBAR -- upper case FooBar -- camel case If a case insensitive SysFileTree is run, then all 3 of the above would match - which one is the correct one? My suggestion is to "honor" the case sensitivity of the Linux file system. ---------------------------------------------------------------------- Comment By: Mark Miesfeld (miesfeld) Date: 2007-05-04 11:53 Message: Logged In: YES user_id=191588 Originator: NO I'm the one that encouraged Steve to open this RFE. I did that more to try and promote participation in the project than a belief it was a desperately needed enhancement. <grin> After a quick glance at the code, it looks doable to me. So, I think the question is more of is it something that should be done. I also guess I should move the discussion over to the developers list; it is not likely to be very visible here. ---------------------------------------------------------------------- Comment By: Rick McGuire (bigrixx) Date: 2007-05-03 05:37 Message: Logged In: YES user_id=1125291 Originator: NO This is just an acknowlegement that your RFE has been received. This particular extension is going to require some discussion among the developers about whether it can or should be implemented. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=684733&aid=1711398&group_id=119701 |