Free don t software for linux

Pydiction 1.1 offers you a powerful and very useful utility which allows you to Tab-complete Python code in Vim, including: standard, custom and third-party modules and packages. Plus keywords, built-ins, and string literals. It consists of three main files:

• python_pydiction.vim -- The Vim plugin that creates the Tab-completion functionality for Python files.
• complete-dict -- A Vim dictionary file that contains Python keywords and module structure. This is what the plugin looks at to know which things are completable.
• pydiction.py -- (Optional) Python script used to generate the dictionary. You can optionally run this script to add more modules to complete.

Major Features:

1. Pydiction can complete Python's keywords, built-in functions, and string literals, as well as standard, custom and third-party package and module names and their attributes and methods. It can also complete fully-qualified names such as "module.submodule.method", as well as non-fully qualified names such as simply "method".
2. Pydiction uses the Tab key to do completion, rather than inefficient Ctrl key combinations and the like.
3. Unlike omni-completion, Pydiction works with more than just imported modules. For example you can complete Python built-in functions and keywords, such as "print", "raw_input", and so on.
4. Pydiction doesn't require Python support to be compiled into your version of Vim, nor do you need to have Python installed on the machine you use it from (unless you want to use pydiction.py)
5. Using a special dictionary file to complete from, Pydiction doesn't pollute any other menus that you you may be using for other types of completion, such as omni-completion or ins-completion.
6. Since Pydiction uses a dictionary of possible completion items, it can complete 3rd-party modules much more accurately, and quickly, than other ways. And you have full control over what can and cannot complete. If it's unable to complete anything, you can either use pydiction.py--to automatically add a new module's contents to the dictionary-- or you can manually add them using a text editor. The dictionary is just a plain text file, which also makes it portable across all platforms.
7. Also because Pydiction uses a dictionary file, you don't have to import a module before you can complete it, nor do you even have to have the module installed on your machine. This makes completion faster than omni-completion since it doesn't need to do any type deducing.
8. Pydiction only attempts to complete while editing Python files.
9. You can still use omni-completion, and other forms of completion, with Pydiction. In fact, they can all make a great team.
10. Pydiction knows when you're completing a callable method or not and, if you are, it will automatically insert an opening parentheses.
11. The Tab key will work as normal for everything else. Pydiction will only try to use the Tab key to complete Python code if you're editing a Python file and you first type part of some Python module or keyword.
12. Pydiction is far form perfect, but it was created because none of the other forms of Python completion for Vim were perfect either. There is a new project underway called PySmell that also looks promising. Keep in mind that Pydiction was originally started in 2003 and back then there wasn't really anything else.

Enhancements:

• Added quoted string method completion
• ZSI Web Services module completion
• Fixed a bug with the -v option.

config-mplayer 0.1 offers you a small but very useful GUI program which is designed for customising your mplayer configuration. It is NOT a wrapper or GUI version of mplayer. It's only business is showing some configuration options and rewriting the mplayer config whenever you change them. The idea is that you can customise it with YOUR desired configuration options just by editing a few files.

Major Features:

1. Switching my audio output between rooms (devices).
2. Changing the DISPLAY which mplayer will play on - for playing on my main desktop, my TV, or within VNC (and in the case of VNC - selecting the SDL driver which actually works over VNC).
3. Switching the video to use X11 so that I can take a screenshot.
4. Changing the aspect ratio of a video when the file is incorrect.
5. Toggling the 'eq2' filter on when I start a second instance of mplayer and the first instance has got the overlay brightness control.
6. Starting in fullscreen
7. Cropping the black borders off of a PAL video within a wide format stream.
8. Adding a volume filter for low or high volume video files.
9. Toggling deinterlacing.
10. Forcing the OSD on or off.
11. Forcing the index of a dodgy file to be rebuilt.
12. Switching to using a different XV port when the main one decides to stop working and just stays blue (very rare these days).
13. Selecting an MPEG-TS transport stream pid.
14. Adjusting subtitle position

Requirements:

• GTK version 2.xxx
• perl GTK2 bindings (perl-gtk2 or gtk2-perl depending on your system)
• You don't need any GNOME rubbish installed