Hi Lior, I'm making a release of deb-gview 0.0.4 which fixes the other bugs you reported and provides some access to manpages, but not quite as I think you intended.
It's not proving simple to interface with existing manpage editors and viewers when the manpage itself is only in memory (let alone uninstalled). I'm not keen on simply forking an xterm and running 'man' with a temporary file (the screen could get v.messy when multiple deb-gview windows are open) but I think that may be the only practical solution. If gman, gmanedit, manedit or man itself could accept input on stdin it would all be so much easier. Even better if there was a 'libman'. :-( At present, .gz files can be viewed internally in 0.0.4 (albeit some improvements are needed behind the scenes) and this does allow the raw groff source of a manpage to be viewed in the deb-gview window. Yes, it's ugly, yes, it's not what you wanted but if I'm going to add some form of file preview to deb-gview, it's going to need to support more than manpages (images are just as important to me). Formatting groff source internally is only one step away from syntax highlighting all the headers and other text files within the package and I really don't think that is within the scope of deb-gview. My question is: How much do you want this functionality? Is it important to you that the manpage output should be 100% accurate (i.e. produced by man itself) or is some form of "prettified" groff acceptable? A temporary workaround is available with 0.0.4 via copy and paste but that's not particularly friendly either. -- Neil Williams ============= http://www.data-freedom.org/ http://www.nosoftwarepatents.com/ http://www.linux.codehelp.co.uk/
signature.asc
Description: OpenPGP digital signature
