| === duanedes1gn is now known as M0hi | ||
| === M0hi is now known as Guest96191 | ||
| === Guest96191 is now known as duanedesign | ||
| === bregma_ is now known as bregma | ||
| xXx8xXx | hi, can i have 1 question about man pages? | 14:16 |
|---|---|---|
| === jjesse_ is now known as jjesse | ||
| xXx8xXx | im good in this room, when i have questions about man pages? | 14:26 |
| xXx8xXx | hm? :) | 14:33 |
| xXx8xXx | help:D | 14:34 |
| xXx8xXx | is here anyone? | 14:48 |
| MrChrisDruif | xXx8xXx; yup | 14:49 |
| xXx8xXx | oo thx :) | 14:49 |
| MrChrisDruif | And 25 others, but I can't confirm they're all active | 14:49 |
| xXx8xXx | can i have questin about man page? | 14:49 |
| MrChrisDruif | sup? | 14:49 |
| MrChrisDruif | Well...if you ask I can see if I can answer it =) | 14:50 |
| xXx8xXx | man pages consist from more sections ( description, see also, history, bugs) | 14:50 |
| xXx8xXx | can i for example through groff generate only 1 from this section? | 14:50 |
| MrChrisDruif | I don't follow your drift? | 14:52 |
| xXx8xXx | sry ma english is bad | 14:53 |
| xXx8xXx | man page: description, history, bugs, see also etc .. | 14:54 |
| xXx8xXx | i need only 1 section from all this section, for example scetion SEE ALSo | 14:54 |
| xXx8xXx | groff -Tascii -a -man | 14:54 |
| xXx8xXx | can i do this with groff? | 14:55 |
| MrChrisDruif | I'm not an expert, but what happens when you try that? | 14:55 |
| xXx8xXx | yes, this generate full man page | 14:56 |
| xXx8xXx | but i nedd only 1 section | 14:56 |
| xXx8xXx | not full man page | 14:56 |
| MrChrisDruif | Have you tried "man -a 'whatever' | groff -T"? | 15:01 |
| bregma | xXx8xXx, no groff will not do that | 15:02 |
| MrChrisDruif | I'm not sure about | but with that pipe as it's called you direct the other program | 15:02 |
| xXx8xXx | must not only with groff | 15:03 |
| xXx8xXx | i can use other commands | 15:03 |
| xXx8xXx | can you show me some example with | ? | 15:03 |
| bregma | groff is just a runoff processor, it does not understand the semantics of the text | 15:03 |
| bregma | you could write a python script that would extract what you need from the groff -Tascii output | 15:04 |
| xXx8xXx | im programming my program in python:) | 15:06 |
| xXx8xXx | but see also can be in the end of man page | 15:06 |
| xXx8xXx | and also it possible that see also isnt in the end of man page | 15:07 |
| xXx8xXx | for example man page: | 15:07 |
| xXx8xXx | DESCRIPTION | 15:07 |
| xXx8xXx | SEE ALSO | 15:07 |
| xXx8xXx | the end | 15:07 |
| xXx8xXx | but can be: | 15:07 |
| xXx8xXx | DESCRIPTION | 15:07 |
| xXx8xXx | SEE ALSO | 15:07 |
| xXx8xXx | BUGS | 15:07 |
| xXx8xXx | HISTORY | 15:07 |
| xXx8xXx | the end | 15:07 |
| xXx8xXx | how can i do this in python when i wanna only see also section? | 15:08 |
| bregma | all I can suggest is reading through the text matching section headers, and when you see the one you want, grab all the text up to the next section header or end of file | 15:10 |
| bregma | section headers are documented in 'man man-pages' | 15:10 |
| xXx8xXx | thank you, but for example COLOPHON or HISTORY is not in man-pages | 15:12 |
| xXx8xXx | and i see this 2 headers in some man page | 15:12 |
| bregma | if you're parsing the raw groff input, you can rely on .SH as the section header directive, problem is then you have raw groff input as your text | 15:16 |
| xXx8xXx | yes, i parse text generated from groff | 15:17 |
| xXx8xXx | not source man page | 15:18 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!