Tidydoc 0.4 (Default branch)


 
Thread Tools Search this Thread
Special Forums News, Links, Events and Announcements Software Releases - RSS News Tidydoc 0.4 (Default branch)
# 1  
Old 02-04-2009
Tidydoc 0.4 (Default branch)

The goal of Tidydoc is to make documentation organization easier. It makes it easy to add documents to a repository, give them the right names, put them into the right directories, and reorganize them a posteriori. Then it can generate a set of HTML pages to browse your documents and a BibTeX file to reference them. Every operation can be done through a Web interface if you are running a Web server, and/or through command line scripts. This allows documents to be uploaded remotely using scp or any other file transfer program. Tidydoc is written in Python in a spirit of flexibility and easy tweaking, but its default behavior should fit the needs of most people. License: GNU General Public License (GPL) Changes:
The Web interface has been improved with a more compact default HTML template, dynamic folding of document details, and support for search queries. Image

Image

More...
Login or Register to Ask a Question

Previous Thread | Next Thread
Login or Register to Ask a Question
ARCHPATH(1)						      General Commands Manual						       ARCHPATH(1)

NAME
archpath - output arch (tla/Bazaar) archive names, with support for branches SYNOPSIS
archpath archpath branch archpath branch--version DESCRIPTION
archpath is intended to be run in an arch (tla or Bazaar) working copy. In its simplest usage, archpath with no parameters outputs the package name (archive/category--branch--version) associated with the working copy. If a parameter is given, it may either be a branch--version, in which case archpath will output a corresponding package name in the current archive and category, or a plain branch name (without '--"), in which case archpath will output a corresponding package name in the current archive and category and with the same version as the current working copy. This is useful for branching. For example, if you're using Bazaar and you want to create a branch for a new feature, you might use a com- mand like this: baz branch $(archpath) $(archpath new-feature) Or if you want to tag your current code onto a 'releases' branch as version 1.0, you might use a command like this: baz branch $(archpath) $(archpath releases--1.0) That's much easier than using 'baz tree-version' to look up the package name and manually modifying the result. AUTHOR
archpath was written by Colin Watson <cjwatson@debian.org>. Like archpath, this manual page is released under the GNU General Public License, version 2 or later. DEBIAN
Debian Utilities ARCHPATH(1)