Re: [go-nuts] when doing a WalkDir of a FileSystem, how do you get access to the path that you are working on

2023-01-15 Thread Tobias Klausmann
Hi! On Sat, 14 Jan 2023, Pat Farrell wrote: > On Saturday, January 14, 2023 at 6:52:15 PM UTC-5 raf wrote: >> The function you implement (WalkDirFunc should receive "p" as the path to >> the parent (that seems to be what you want) and "d" as the current >> directory entry. I am not sure why

Re: [go-nuts] when doing a WalkDir of a FileSystem, how do you get access to the path that you are working on

2023-01-14 Thread Pat Farrell
On Saturday, January 14, 2023 at 6:52:15 PM UTC-5 raf wrote: The function you implement (WalkDirFunc should receive "p" as the path to the parent (that seems to be what you want) and "d" as the current directory entry. I am not sure why in your example you are showing full paths to the file

Re: [go-nuts] when doing a WalkDir of a FileSystem, how do you get access to the path that you are working on

2023-01-14 Thread Raffaele Sena
The function you implement (WalkDirFunc should receive "p" as the path to the parent (that seems to be what you want) and "d" as the current directory entry. I am not sure why in your example you are showing full paths to the file for "p". On Sat, Jan 14, 2023 at 3:39 PM Pat Farrell wrote: >

[go-nuts] when doing a WalkDir of a FileSystem, how do you get access to the path that you are working on

2023-01-14 Thread Pat Farrell
I'm using the reasonably new FileSystem style to do the usual directory walk processing every file in the usual recursive manner. I can't figure out how to get the directory data (the path up to the last /) even though I can see it in the output. I am missing the proper name of the getter, or