Bug#298588: RFP: mpedit -- Minimum profit text editor for programmers
Package: wnpp
Severity: wishlist
* Package name : mpedit
Version : 3.3.11
Upstream Author :
* URL : http://www.triptico.com/software/mp.html
* License : GPL
Description : Minimum profit text editor for programmers
(Include the long description here.)
Features
- Multiple files can be edited at the same time and blocks copied and
pasted among them.
- Syntax highlighting for many popular languages / file formats: C,
C++, Perl, Shell Scripts, Ruby, Php, SQL, Python, HTML...
- Creative use of tags: tags created by the external utility ctags are
used to move instantaneously to functions or variables inside your
current source tree. Tags are visually highlighted (underlined), and
symbol completion can be triggered to avoid typing your own function
names over and over.
- Intelligent help system: pressing F1 over any word of a text being
edited triggers the underlying system help (calling man when editing
C or Shell files, perldoc with Perl, ri on Ruby, winhelp on MS
Windows...).
- Understandable interface: drop-down menus, reasonable default key
bindings.
- Configurable keys, menus and colors.
- Text templates can be easily defined / accessed.
- Multiplatform: Console/curses, GTK+ (1.2 and 2.0), MS Windows.
- Automatic indentation, word wrapping, internal grep, learning /
repeating functions.
- Search and replace using plain text or regular expressions
(including a special function to replace text on all open files).
- Small memory footprint.
- Multilingual.
- Password-protected, encrypted text files (using the ARCFOUR
algorithm).
- It helps you abandon vi, emacs and other six-legged freaks
definitely.
- Awesome easter egg.
unofficial Debian package available from dev site
deb http://www.triptico.com/debian unstable/
-- System Information:
Debian Release: 3.1
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 2.6.10-1-686
Locale: LANG=C, LC_CTYPE=C (charmap=ISO-8859-1) (ignored: LC_ALL set to en_US)
Reply to: