You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
walk.go calculates the hash (sha256sum) of every file in an specific directory matching file pattern. It writes to JSON file
see.py reads the contents of this JSON file and generates a custom HTML file
see could reads several JSON files
It reads hash, date of modification, size and permissions of each file
It finds the files which has the same content, although their have different file names or are in different places.
It ignores symlinks because it could contain recursively things from other places (you could calculate hash in the original directory)
Dependencies: only Python 3 and Go programming language (1.0 or above)
Installation
Copy walk.go and compile it
Copy the file ‘see.py’.
Usage
See ‘./walk —help’:
$ ./walk —help Usage of ./walk: output=./output.json The JSON output file in which we save the results path=./ Source of files pattern=“": Pattern search expression of searching files </pre> </div>
See ‘./see.py —help’:
<div width=”200px“> <pre> $ ./see.py —help usage: see.py [h] ]]
optional arguments: h, —help show this help message and exit —sources [SOURCES [SOURCES …]] The JSON files in which we have hash values —output OUTPUT The output html file in which we put the results
</pre> </div>
h3. Example
For example, for searching jpg files i ‘foo’ and ‘bla’ directories, you could run:
<div width=”200px“> <pre> ./walk path=foopattern=”*.jpg"output=output1.json ./walk path=blapattern=“*.jpg” -output=output2.json ./see —sources ./output1.json ./output2.json —output files.html
instead of one you could see in main project page. The issue is in -- within
code.
Can you solve that?
Thanks,
Xan.
The text was updated successfully, but these errors were encountered:
Hi,
Running pandoc -f textile with this file produces this output:
instead of one you could see in main project page. The issue is in -- within
The text was updated successfully, but these errors were encountered: