Developer forums (C::B DEVELOPMENT STRICTLY!) > Plugins development

Support for man pages in the help plugin

(1/3) > >>

Ceniza:
I just finished implementing support for man pages in the help plugin, and it seems to be working fine so far.

Configuration looks like this:


And man page like this:


You can also specify more than one path for man pages (e.g. man:/usr/share/man;/usr/local/share/man;/another/dir/with/man/pages) if you want/need to.

It searches for man pages recursively (be careful with this), and it handles plain text, gz and bz2.

I still need to test it on Windows, update the project files and commit the changes (BerliOS is down ATM). Right now, it's only configured to be compiled using autotools.

I hope you find it useful (when I be able to commit it).

rjmyst3:
that is awesome.
good work!  :D

raph:
Wow, really glad to hear this. I'll definetly use this feature on my new laptop.

mariocup:
Hi Cenzia,

I did not know that the Help Plugin support different protocols like http (Google search)


--- Code: ---http://www.google.de/search?hl=de&q=$(keyword)&btnG=Google-Suche&meta=

--- End code ---

Finding out that, I came to new ideas. I have different headers that are included in a my project. For these headers exist a html documentation. So it would be great to select e.g. mydef/asc0.h in the editor


--- Code: ---#include <mydef/asc0.h>

--- End code ---

and jump to e.g. firefox

file:///<envar>/html/$(keyword)tml

But the help plugin does not know how to handle the file:/// protocol. Is there a easy way to support that feature. I would appreciate, because my controller has 2000 registers and so it is helpful to get quick the documentation to a header file.

Ceniza:
Just tell the plugin you're specifying a command, then prepend the browser's executable name. Something like this:

firefox file:///<envvar>/html/$(keyword).html

Add the whole path to the executable if you have to.

Navigation

[0] Message Index

[#] Next page