similar to: Embedding man pages in driver source code

Hello, At 15:42 -0400 on 2014-6-1 Charles Lepple wrote: > > On May 24, 2014, at 5:49 PM, Stefan Bruda wrote: > > >> Don't worry about the battery physical properties for now - the > >> problem there is that we don't have enough information from the UPS > >> to do a proper calculation. With the V_interval[] settings, you can > >> tweak

On Jun 2, 2014, at 10:25 PM, Stefan Bruda wrote: > Hello, > > At 15:42 -0400 on 2014-6-1 Charles Lepple wrote: >> >> On May 24, 2014, at 5:49 PM, Stefan Bruda wrote: >> >>>> Don't worry about the battery physical properties for now - the >>>> problem there is that we don't have enough information from the UPS >>>> to do a

On Mon, Sep 14, 2009 at 4:49 PM, Arnaud Quette <aquette at alioth.debian.org> wrote: > Author: aquette > Date: Mon Sep 14 20:49:59 2009 > New Revision: 1986 > > Log: > draft index of manual pages > > Added: > branches/AsciiDoc/docs/man/index.txt Cool! One potential issue: /sw/bin/asciidoc --backend=xhtml11 \ --attribute localdate=`TZ=UTC date +%Y-%m-%d` \

All, With AsciiDoc, we can make use of some macros to cut down on some of the repetition in the driver man pages. I don't want to go overboard on this, though - I know that drivers aren't meant to be invoked directly by users anyway. I propose that we put all of the gory details into the nutupsdrv(8) man page (mostly there anyway), and just add a few basic options to the

3a. What part of the documentation needs the most immediate attention? 3b. Will anyone come after me with an axe if I move the entire corpus to ASCIIDOC markup? http://www.methods.co.nz/asciidoc/ 3c. Why isn't the content of the website a branch in the repo? Can we fix things so it is? Hint: If the website becomes a repo branch, I'll reorganize and rewrite that for clarity, too. --

Since I've heard about AsciiDoc (thanks ESR), I'm in the process of revamping the full Network UPS Tools documentation and website. Without going into the usual "it curred my desease, got my wife back home, and made me won a billion", it really saved my life ^_ ^ I was searching for such tool for years! thanks a lot Stuart and others. Kudos for the work! NUT revamp is not yet

Is there a particular reason why we are setting the alternate interface to 0 in drivers/libusb.c? I have seen some documentation which indicates that this should already done by the OS when the device is enumerated. If that is the case, then there is no reason why we should hardcode the alternate interface to 0. If I remove the following code, tripplite_usb seems to work*:

Could someone please check and see what I am doing wrong with automake in branches/AsciiDoc? http://boxster.ghz.cc/projects/nut/browser/branches/AsciiDoc/docs/Makefile.am?rev=1917 The problem is that 'make html' never recurses into docs/website. I have listed 'website' in the 'SUBDIRS' section of docs/Makefile.am, and 'docs/website/Makefile' is listed in the

On Sep 8, 2009, at 8:30 AM, Charles Lepple wrote: [...] > +EXTRA_DIST = tripplite_usb.8.txt \ > + ups.conf.5.txt \ > + upsc.8.txt > + The EXTRA_DIST thing is a hack. Right now, we are not including the generated HTML properly, because I haven't figured out the automake way to do this correctly. Specifically, we want to treat the .txt files as source, and distribute the

On May 24, 2014, at 5:49 PM, Stefan Bruda wrote: >> Don't worry about the battery physical properties for now - the >> problem there is that we don't have enough information from the UPS >> to do a proper calculation. With the V_interval[] settings, you can >> tweak the new state-of-charge calculation to match what you see via >> upsc when the battery is

In r2124 of branches/AsciiDoc (haven't checked where else this is), it looks like we have two duplicated columns. See diff below. This results in the model name showing up in the driver column of the HCL. How is driver.list regenerated from driver.list.in? Do I just need to re-run autoreconf to get the rules up-to-date? Or is this converted manually for the time being? diff --git

Hi, Charles I'm trying compilation but there is no configure command in the cloned git directory of nut. D?a 08.10.2017 o 23:47 Charles Lepple nap?sal(a): > On Oct 8, 2017, at 4:34 PM, tuharsky at misbb.sk wrote: >> Thank You for You reply, Charles >> >> >> D?a 07.10.2017 o 14:30 Charles Lepple nap?sal(a): >>> Is the "lan4.1" cable different

Arnaud, my UPS arrived yesterday; thanks for your generosity. I'm using it to power the computer I'm typing on. This moves NUT up a few places on my priority list. In our last email exchange, I believe we agreed on a couple of major points. I want to confirm these before I start modifying the documentation heavily. 1. asciidoc is a good master format for the in-tree documentation. 2.

Thank You for You reply, Charles D?a 07.10.2017 o 14:30 Charles Lepple nap?sal(a): > Is the "lan4.1" cable different from this one? > http://networkupstools.org/cables.html#_tripp_lite Yes, it is different. The correct cable for this interface version looks like this: http://pinouts.ru/UPS/tripplite_smartpro_cable_pinout.shtml > Are you comfortable with rebuilding the

Model: Tripp-lite OMNIVS1500 Error: Network UPS Tools - UPS driver controller 2.2.1- Network UPS Tools - Tripp Lite OMNIVS and SMARTPRO driver 0.11 (2.2.1-) Warning: This is an experimental driver. Some features may not function correctly. Detected a UPS: unknown/unknown libusb_set_report() returned -1 instead of 8 Could not reset watchdog. Please send model information to nut-upsdev mailing

Hello, At 09:24 -0400 on 2014-5-23 Charles Lepple wrote: > > See attached. Still doesn't have the writable V_interval values, > but I probably won't have time to test that until later. Thank you for the patch. > Don't worry about the battery physical properties for now - the > problem there is that we don't have enough information from the UPS > to do a

Arnaud, Thanks for removing the warning. I suspect that many users still using IE6 are doing so because of their IT department (rather than personal preference). IMHO, browser evangelism is slightly outside the scope of the NUT project :-) On Thu, Sep 3, 2009 at 8:31 AM, Arnaud Quette<aquette at alioth.debian.org> wrote: > Author: aquette > Date: Thu Sep 3 12:31:10 2009 > New

I'm looking for a little bit of help with the man page conversion. So far, about a third of the man pages are converted, and I think it would make sense to have a second or third set of eyes compare the output to be sure that we are not losing any information in the conversion process. In the tarballs generated from the AsciiDoc branch on http://buildbot.ghz.cc/public/nut/ you will find the

On Jul 13, 2010, at 6:59 PM, Arnaud Quette wrote: > Author: aquette > Date: Tue Jul 13 22:59:52 2010 > New Revision: 2472 > URL: http://trac.networkupstools.org/projects/nut/changeset/2472 [...] > Modified: branches/AsciiDoc/docs/Makefile.am > = > = > = > = > = > = > = > = > ====================================================================== > ---

Citeren Arnaud Quette <aquette op alioth.debian.org>: > Author: aquette > Date: Fri Dec 17 23:32:20 2010 > New Revision: 2748 > URL: http://trac.networkupstools.org/projects/nut/changeset/2748 > > Log: > --with-doc=auto now behave depending on AsciiDoc presence Instead of building whatever can be build (depending on the versions found), you now have changed the