COPYRIGHT FOR CODE AND MANPAGE
are released under GPL law, full text is here: This is slightly incorrect, the GPL is a license, so the correct term would be: COPYRIGHT FOR CODE AND MANPAGE GPL version 3 (or later), full text is here: no, wait, I take that back, just checked man nano, and there is no copyright mention at all in the man file, that makes sense, since the man file is supposed to supply operating information about the application. So I'd just remove that, but check a few other apps to see what they do in their man, I tend to just copy the formats and avoid all creativity, assuming they know what they are doing, heh. Back to top |
well FWIW the reason why I chose "law" is because some companies have been taken to court for breaching the license and selling closed code with GPL in it
>>>without the consent of all contributing authors etc. I think law fixates the mind that we in Linux land respect the law eh? but if upsets you....just remove law. b) yes a number of man pages have no mention of what GPL version the actual code is under...but as you will distribute it ....the man page....it is nice to know they can modify it if certain distros choose to. but if you still concerned just remove the man page as well? regards Back to top |
no, I'm not concerned, I just took a look at what other apps had in their man file, and figured that's the normal way to have it.
Law in this context is however not quite right, it's just a copyright thing. As the person who is making these, you can largely have them be the way you want, but from what I can see, there's a normal way to have them, at least re copyright info. since I've never seen this file type, is it just a text file you edit? Back to top |
After decompression it is a text file.
I use gmanedit to open and edit it....and it re-compresses. However if you are wanting to know the syntax so you can edit yourself . 1) I use 2 different styles simple and "on same line" COMPLEX SIMPLE .B = bold (and in my terminal red) .I = italic (and greeen) .R = Romanised text or normal and normal color but to write the complex line of (and convert to simple) .B inxi \fR[\fB-A\fR] becomes .B inxi .R [ .B -A .R ] which imho it just as hard to read. so complex uses a switch to swap fonts \fB same as .B \fI same as .I \fR same as .R but AFAIK the simple stuff....is only recognised if its on the START of the line but I can write complex on any part of any line that started with simple b) man pages truncate space. this means you need to have a separator normally a paragraph marker .TP but TAB to the next part of the writing is also recognised be manpage. As ppl may have different size terminal or console lines press enter when you think you have typed enough ABOVE is merged to display As ppl may have different size terminal or console lines press enter when you think you have typed enough 2) if that is too much.....tell me what you want and I can still edit? Back to top |
sorry, you must have fallen asleep waiting, but I finally added the man pages to inxi svn, sorry to take so long.
code.google.com/p/inxi/source/browse/trunk/man/inxi.8 Please note these man pages are out of date a bit, maybe I should add some comment to note that the man page might lag behind inxi itself, just like the wiki does. If you want to be able to work directly on them, I can add you to the svn. Back to top |
I will do this by forum reply to pm
your ftp link gives page not found for me so agreed to do by link I may need to rename each file but here is the first change to see if you like the removal of license and chats made alphabetical ompldr.org/vZG52NA its already a gz file so swap into to /usr/share/man/man8 to test the man page 2) I have not yet had a chance to look at your --help to see what switches/parameters I need to update 3) in case your ftp link is fixable don't try to......I am happier to stay a link to host sites Back to top |
Towards the end of the man page, when I view it, it shows this:
:: Code :: -% Overrides defective or corrupted data.
-@ [1-7] - On screen debugger output Reading... -@ 8 - Basic logging. Check /home/yourname/.inxi/inxi*.log 4 Reading... 5 1 Reading... -@ 9 - Full file/sys info logging 6 Reading... 7 2 Reading... -@ 10 - Color logging. 8 Reading... and so on to the end, each line starting with Reading... must be some text thing that triggers that output around that point. Back to top |
magic, the display glitch vanished after leaving it a few minutes. Wonder if the gz was cached and when I updated it, man got confused?
Anyway, it's showing correctly now. Back to top |
hi
well glad that worked. firstly you have a typo that I missed in the older edition as well in inxi --help inxi -v 5 says partion not partition easily fixed and fixed in new manpage ompldr.org/vZG54bg I have yet to look at your wiki as I like to do things slowly but to save time here are the things to look for changes to -M added a line -v 5 typo fixed -x R for raid added -xx D serial number added -xx R block count added cheers filename is inxi.8.gz-v2 rename without the -v2....add into man page area sorry to tell you how to suck eggs but feel you may be still sick so need help? (takes foot out of mouth) Back to top |
ok a quick look at your wiki page and you may be interested in
code.google.com/p/inxi/wiki/inxi -M missing second line of --help -v 5 same typo -x R also missing xx D also missing xx R also missing so at this stage.....I am happy I have got most of the missing stuff in there until your eyesight spots the errors cheers Back to top |
All times are GMT - 8 Hours |