How to do things
AI Noob vs. Pro

List biggest files
List newest files
Show subdir sizes
Search in files
Replace word in files
List dir differences
Send files in LAN

Free Open Source:

Swiss File Knife

a command line
multi function tool.

remove tabs
list dir sizes
find text
filter lines
find in path
collect text
instant ftp or
http server
file transfer
send text
patch text
patch binary
run own cmd
convert crlf
dup file find
md5 lists
fromto clip
split files
list latest
compare dirs
save typing
trace http
echo colors
head & tail
dep. listing
find classes
speed shell
zip search
zip dir list

Depeche View
Source Research
First Steps

windows GUI

command line
file encryption

free external tools,
zero install effort,
usb stick compliant:

zip and unzip
diff and merge
reformat xml
reformat source

cpp sources

log tracing
mem tracing
using printf


stat. c array
stat. java array
var. c array
var. java array
view all text
as you type
surf over text
find by click
quick copy
multi view
find nearby
find by path
location jump
skip accents
clip match
filter lines
edit text
load filter
hotkey list
receive text
send in C++
send in Java
smooth scroll
touch scroll
fly wxWidgets
fly over Qt
search Java

find out from where in the PATH a command is loaded.
  • Download the free Swiss File Knife Base from Sourceforge.
  • Open the Windows CMD command line, Mac OS X Terminal or Linux shell.
  • OS X : type mv sfk-mac-64.exe sfk and chmod +x sfk then ./sfk
  • Linux: type mv sfk-linux-64.exe sfk and chmod +x sfk then ./sfk. OS X and Linux syntax may differ, check the help within the tool.

sometimes you type a command, e.g. "make", and wonder that it behaves totally unexpected. maybe you have several versions of the command, from different software packages, within your PATH... and according to murphy's laws, you run the wrong version, of course.

but from where within the PATH is it loaded? just type

sfk pathfind yourcommand.exe

to find out. for example:

    sfk pathfind make.exe
    => d:\tools\msys\bin\make.exe

in this example, you see that make.exe is loaded from d:\tools\msys\bin\make.exe. should there be another make.exe further down in the path, then it is ignored. you may also say "sfk where", which is the same, but shorter to type:

    sfk where zip.exe
    => c:\program files\cygwin\bin\zip.exe

windows users may even leave out the file extension: sfk where foobar in this case, sfk finds all files with the specified base name, having one of the extensions from the PATHEXT environment variable. for example:

see also sfk env - search environment variables for words
sfk is a free open-source tool, running instantly without installation efforts. no DLL's, no registry changes - just get sfk.exe from the zip package and use it (binaries for windows, linux and mac are included).


the Daily Landscape image
the Daily Mobile Background