search for: mdoc

Guus The mdoc warnings (on FreeBSD 8) are getting a little bit annoying at times: anywi at lcrproxy:/usr/ports/security/tinc/work/tinc-1.0.19/doc % man tinc.conf 2>&1 | head -5 mdoc warning: Empty input line #6 mdoc warning: Empty input line #10 mdoc warning: Empty input line #15 mdoc warning: Empty inpu...

On 2016-09-28 00:10, Ingo Schwarze wrote: > The patch also inserts a few needless .PP before .SH, but that does > no harm. mdoc2man.awk is a terrible hack and not a proper parser > in the first place, so we shouldn't expect beauty in its output. > If the output is correct and portable, that's good enough. At some > point, we should replace mdoc2man.awk with mandoc -Tman anyway. > The last time i tried,...

...> Because it is a terrible manpage format > > and the toolchain produces broken crap. > > I have no specific knowledge on this, but would just like to "me too" > to this thread that whatever format is used, it MUSTN'T impact on the > quality of any resultant man/mdoc conversion. What I am proposing is to _write_ the mdoc(7) manpages, not have them produced by some toolchain or another. > </bikeshed> I am concerned that you consider the quality of documentation bikeshiding.

http://bugzilla.mindrot.org/show_bug.cgi?id=550 Summary: Problems with .Ql in mdoc Product: Portable OpenSSH Version: -current Platform: All OS/Version: All Status: NEW Severity: minor Priority: P2 Component: Documentation AssignedTo: openssh-unix-dev at mindrot.org ReportedBy: cjwats...

Estimados compañeros me tiene loco un problema de codificación que no logro resolver. Importo un fichero cuyo nombre tiene acento. Pongamos por ejemplo "Adrián.doc". Escribo el siguiente comando: mdoc<-list.files(path = dest,pattern = "*.doc", full.names = TRUE) Entonces mdoc, además del path, se me presenta como: "Adria´n.doc" Aunque le quite la tilde con: mdoc1<-iconv(mdoc,"UTF-8","latin1"," ") Como necesito llamar al fichero o fich...

...rible manpage format > > > and the toolchain produces broken crap. > > > > I have no specific knowledge on this, but would just like to "me too" > > to this thread that whatever format is used, it MUSTN'T impact on the > > quality of any resultant man/mdoc conversion. > > What I am proposing is to _write_ the mdoc(7) manpages, > not have them produced by some toolchain or another. I know. And Paul suggested xml, and you replied that it's crap. Other people were suggesting other tools. I was just adding to the conversation that if some o...

...smb group. I have tried chmod 2777 /mnt/MtAthos-c and just plain 777. Neither makes any difference. The directory is set uid=1001, gid=1001 (smbuser and smb) I have tried mounting the drive every way imaginable. Here are just a couple of the lines I've tried in my fstab: \\MtAthos\MtAthos-MDoc /mnt/MtAthos-MDoc smbfs o,guest,exec,rw,uid=1001,gid=1001,fmask=2777,dev,suid 0 0 \\MtAthos\MtAthos-c /mnt/MtAthos-c smbfs o,guest,dmask=777,fmask=777 0 0 \\sinai\Sinai-MDoc /mnt/Sinai-MDoc smbfs o,guest 0 0 It appears to be having problems changing from my uid (nmetsovo) to the smbuse...

Dear authors of Vorbis, currently, the manpages that come with vorbistools are written in the traditional man(7) markup language. I am proposing to rewrite them into the semantic markup of the mdoc(7) language. I am willing to do the work. Both the man(7) and mdoc(7) languages have been around for decades, and are supported by the prevalent formatters: groff(1) on most Linuxes and mandoc(1) on the *BSDs and some others. In particular, there is nothing to install or reconfigure on most system...

Dear authors of NSD, currently, the manpages that come with NSD are written in the traditional man(7) markup language. I am proposing to rewrite them into the semantic markup of the mdoc(7) language. I am willing to do the work. See a version of nsd-checkzone.8 below as an example. Both the man(7) and mdoc(7) languages have been around for decades, and are supported by the prevalent formatters: groff(1) on most Linuxes and mandoc(1) on the *BSDs and some others. In particular, the...

Hi, On systems that have mandoc installed but are missing an nroff binary, the configure script will fall back to pre-formatted manual pages despite the fact that mandoc could be used. The proposed patch adds mandoc as a valid formatter to configure.ac. As mandoc supports the -mdoc flag, it can simply be added to the list of nroff-like binaries. Wolfgang -------------- next part -------------- A non-text attachment was scrubbed... Name: mandoc-configure-ac.patch Type: text/x-diff Size: 504 bytes Desc: not available URL: <http://lists.mindrot.org/pipermail/openssh-unix-dev...

Dear authors of Opus, currently, the manpages that come with opus-tools are written in the traditional man(7) markup language. I am proposing to rewrite them into the semantic markup of the mdoc(7) language. I am willing to do the work. Both the man(7) and mdoc(7) languages have been around for decades, and are supported by the prevalent formatters: groff(1) on most Linuxes and mandoc(1) on the *BSDs and some others. In particular, there is nothing to install or reconfigure on most system...

ping On Jun 23 09:05:38, hans at stare.cz wrote: > Dear authors of vorbis-tools, > > the manpages are currently writen using the man(7) markup language. > Would there be any interest in having them rewritten to mdoc(7)? > > The mdoc(7) language allows for _semantic_ markup, expressing > things like "this is an optional argument", as opposed to the physical > markup like "put this in italics and add brackets" in man(7). > See a proposed rewrite of ogginfo.1 below as an exampl...

...erpages for ARMv7 * FreeBSD/ARM Toolchain Improvements Ports * FreeBSD Haskell Ports * GNOME/FreeBSD * KDE/FreeBSD * PyPy * Wine32 on FreeBSD/amd64 * Xfce/FreeBSD * xorg on FreeBSD Miscellaneous * BXR.SU -- Super User's BSD Cross Reference * mdoc.su -- Short Manual Page URLs __________________________________________________________________ AMD GPU Kernel Mode-Setting (KMS) Support URL: https://wiki.freebsd.org/AMD_GPU Contact: Jean-S?bastien P?dron <dumbbell at FreeBSD.org> Contact: J.R. Oldroyd <jr at opal.com&gt...

I've noticed that the man pages provided in the tarball do not work on Solaris - the output is not formatted as expected. On a linux box it is possible to view the man pages using nroff -mdoc ./sshd.8, where prepended file is /usr/lib/groff/tmac/tmac.doc. There does not appear to be an equivelent macro file on Solaris 2.6. Does anybody know how I can get the man pages to display properly on Solaris. Thanks

The attached patch (relative to the current CVS snapshot) uses a perl script to convert the OpenSSH manpages from the BSD -mdoc format to the -man format used by other systems. This allows the unformatted manpages to be installed normally, rather than defaulting to preformatted pages. I'd like to see this patch integrated into the portable version of OpenSSH. Please let me know what you think about this. Thanks! --...

Version info: OpenSSH_7.3p1, OpenSSL 1.0.2i 22 Sep 2016, Arch linux The ssh-agent.1 man page seems to have an indentation oddity, at least, as formatted with recent Arch linux manpage toolset. Here's what appears in the formatted output just after the description of the the "-t" option: ---------- Begin formatted output ------------------------------------- -t life

Hello, I am stumped on a problem I am having with Shorewall 2.0.1 on Mandrake 10. My setup is as follows. I have a /28 and have assiigned all ip addresses to my firewall using aliases. I am able to setup rules to allow specific traffic to specfic ip addresses on the firewall like so: ACCEPT net:w.x.y.z $FW:w.x.y.z tcp 22 This works great for TCP and UDP traffic. I can

Below is a diff to vcut.c and its vcut.1 manpage, which - rewrites the manpage in the mdoc(7) markup as offered in my previous message, and while there: - drops the [] around cutpoint as it is _not_ optional - adds the [] around [+] as it _is_ optional - drops the argument name difference between "cutpoint" and "cuttime" - adds the usage sentence about "."...

Hi Team, I'm looking to "upgrade" my sites ssh installation from the original. I have built openssh-2.3.0p1 and it looks good. I am puzzled as to why there are so many source distributions? However, that is not why am writing - the man pages provided do not format with either Solaris 'nroff -man' or 'groff -man'. What am I missing here? Thanks for your help. Scott

AIX v4.3 returns the correct error $ /usr/bin/nroff -mdoc a /usr/bin/nroff: 1004-010 Cannot find or open /usr/lib/tmac/tmac.doc $ echo $? 130 $ EdGy