A fair amount of nice stuff can only be done using the scheme binding for
witme. For those that don't understand scheme, I have provided some scripts
and information here to help you see the kind of stuff that is available
to you with the scheme interface.
Ok, to start nice and simple... all "filters" are scheme. So to create a
filter that includes all files that are on disk in a view, its easy:
As you can see from the above, its simply a "1".
So now you know how to make a filter that does nothing, lets define one that
has a noticable effect, showing only the directories in the view.
Now to use these just right click the background in a view and pick them
from the filter menu. Alternately you can bind a filter apply type application
to a hotkey. For example, the following will apply the dirs only filter when
I like to bind this to control + 1, so I make a hotkey to bind with
And from a view window, I right click and set "Global hotkey" to "Control
1" and from the next submenu select "apply dirsonly". The difference between
local and global hotkeys is that a local hotkey is only applied to that directory
view, whereas a global hotkey works no matter what directory you are viewing.
Although you can apply sort orders from the menu, it is handy to bind these
to hotkeys too.
To do this setup an application like
And bind this to an event in the same manner as you bound a filter to a hotkey
above. Note that only one application can be bound to a global or local hotkey
at the moment. There is no reason that you can not create an application
that has scheme that calls a bunch of other scheme scripts to give the effect
of many executions for a given hotkey.
To call other scheme from a scheme script, first lookup the script to call
invoke that script. For example the following calls the feh viewer for the
item that was
To bind Control-D to close the current view, simply create a hotkey for Control-D
and an application like the following
When Control-D is globally bound to the above, you can nicely close any active
view window with Control-D.
Podfuk support is done with a little scheme snippit.
Using the above we need to bind to a mime type, so create an rpm type.
Next find a rpm file somewhere, right click it and select from the "type
attach" menu a mouse event, say double left click, and attach "open with
podfuk" that we created above. Assuming your podfuk setup is working, you
should now be able to double click an rpm file to view its contents.
Also of interest, a filter that denies a filename...