Bug#887145: RFA: bluefish -- advanced Gtk+ text editor for web and software development
Package: wnpp
Severity: normal
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
I request an adopter for the bluefish package. I've happily maintained it for
around 12 years. Now I'm rarely using it and package management lacks behind.
This package deserves better.
It is usually a low maintenance package and has an active and responsive
upstream. The packaging and backporting files for Debian are currently located
in the upstream subversion repository at sourceforge.net. Bugs are tracked with
GNOME bugzilla. Backporting is done as a service to Debian users and requires
a few changes to the default packaging files, so there are different branches
for the packaging files. I tried to keep the differences as small as possible.
If you have any questions, please ask.
Regards, Daniel
The package description is:
Bluefish is a powerful editor targeted towards programmers and web
developers, with many options to write websites, scripts and programming
code. Bluefish supports a wide variety of programming and markup languages
and has many features, e.g.
.
- Customizable code folding, auto indenting and completion
- Support for remote files operation over FTP, SFTP, HTTPS, WebDAV, etc.
- Site upload and download
- Powerful search and replace engine
- Customizable integration of external programs such as lint, make, etc
- Snippets plugin to automate often used code
- Code-aware in-line spell checking
- Zencoding or Emmet support
- Bookmarks panel
.
but is still lightweight and fast.
.
For validation of CSS/HTML/XML documents you need csstidy, tidy, weblint
and/or xmllint. For preview to work, you need a web browser that can view
local files given to it on the command line. For PHP or Python bluefish
supports php-codesniffer and pylint. Tools not suggested but supported
are make, perl, php5-cli and java-compiler.
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEEvu1N7VVEpMA+KD3HS80FZ8KW0F0FAlpbXVwACgkQS80FZ8KW
0F08EBAA2vR7vjo5fYp8NRR/jQ5qxiZjGhjHIdbrzrctclPzyB3whZD9C2rIPkOr
rQGBOSn3HmUmwrFn8ckwFKlSrAYY8s2FM2tZO50HAn2CXLaJpMTxiiEWwxxEKN07
IaM3jRAAR8T3tD6+H/6RMl+0fQuouR+YIkaYCMqwJjpZNjBSHE9qtqUQcUXP+dP4
WpDTJw6K/RJpLCnli0hwkZgzqpi4YVpZJ+YRX1bJQYiifWLxOeG0nWlnkHAZlH2E
1uOhfIiv24FVTC3FoYSLP72befhJvupoJKzknhXCKW+ig73fPqGeZhIF2LqHj/vr
b+5M7mShsGby/h+On+LcinQJzGCuOC9ahbDClx62UTTXnPCpbvaY3JJZNVJVFfit
qww5ga/GPLd/ZmSWdwpzqHY0yuFCkTzTcukhV9YNDcgp98PL4s3UkF4r/qRW14At
p81GtbjMYj+6sygCjGWbkv3TGgdiMIMjozhxYjjcZ2BdjtehrVhSJauydnIPNk3o
a3anPyQHL+jPh6I7ldgsVmVHaUEQgja/S2fZvCt9oH3CPWZGknvhMC2MDwHSuxuT
9EjKF997FXJQ4PmHHXEJBjtqSua/7hYvveqSJzltIbzbl09ngtdW5qqOV9GXmYOq
qcadzhzE+k3XrCgN2hDS/tQ/4IApu4keHBREz8/Af2CpdzQ+G/I=
=ekAT
-----END PGP SIGNATURE-----
Reply to: