similar to: Man pages on HPUX (and others?)

Why would this be happening, and how can I fix this - the man subsystem hasn't been working because of this for a while. This is FreeBSD-4.9-Prerelease: # gdb man man GNU gdb 4.18 (FreeBSD) This GDB was configured as "i386-unknown-freebsd"...(no debugging symbols found)... /usr/share/tmac/man: No such file or directory. And when I go to run a manpage, I sometimes get this

Hi Folks, I'm wondering if there are people out there who would be interested in what would be involved in developing an interface between R graphics and the 'pic' language. Explanation; 'pic' has been part of the Unix 'troff' typesetting suite since very early days (1970s), and also of the GNU troff: 'groff'. Its function is to act as a preprocessor,

Documentation for S3 functions is apparently written in troff markup with macro tags like .BG .FN .TL .DN .CS ... Inspection of S3 documentation source files gives a pretty clear idea of what these mean, semantically (and Sd2Rd is a perl script which converts this markup into the Rd format, providing further semantic information along the way). My query is: Can anyone point to troff

Here it is, a missing file "analyze.1" :- /usr/bin/groff -Tps -man /usr/build/llvm/docs/CommandGuide/analyze.1 > /usr/buil d/llvm/docs/CommandGuide/analyze.ps troff: fatal error: can't open `/usr/build/llvm/docs/CommandGuide/analyze.1': No such file or directory make[2]: *** [/usr/build/llvm/docs/CommandGuide/analyze.ps] Error 1 make[2]: Leaving directory

Hi, here's a short summary of all the mails I got concerning the R help system during the last days ... I really want to have all open questions in this list, so if I forgot your most important topic please forgive (and remind me again) ... it's probably only because of lack of time such that I had to compile the list in a hurry ... Ok, here we go: 1) It would be useful to have a button

I have a large number of troff help files which are automatically converted to .Rd files. Many of these have examples which contain the printed output of the examples. This makes example(functionname) not work. Is there a way to avoid removing all this output by delimiting it in some way such that the output will not appear in R-ex? Secondly, it would be nice if there was a place where output

Turns out I did not have Perl installed and hence no pod2man command, so it was not groff after all. But 'true', what ever it does, does not seem to be working on Cygwin. true pod2man --release=1.5 --center="LLVM Command Guide" /usr/build/llvm/../../src/llvm-1.5/docs/CommandGuide/analyze.pod /usr/build/llvm/docs/CommandGuide/analyze.1 'true' seems to behaving like a

Hi Folks, I'm trying to locate the source code for a (typical) R graphics device, in order to study how it's done. The underlying reason is that I'm thinking of trying to create a graphics device for 'pic' (the diagram drawing component of [g]troff). I thought the xfig device would be a good place to look, since the format of an xfig file is similar in nature (though very

The main changes in this release are moving generation of manpages to .rst format and updating default behavior of the protocol version selection (auto-negotiate). webpage: https://wiki.samba.org/index.php/LinuxCIFS_utils tarball: https://download.samba.org/pub/linux-cifs/cifs-utils/ git: git://git.samba.org/cifs-utils.git gitweb:

Am back to the same llvm 'make install' errors as I had before :- Two trivial ones, of uncreated directories :- llvm[2]: Installing Debug /usr/llvm/bin/llvm-ranlib /usr/bin/install: target `/usr/llvm/bin/llvm-ranlib' is not a directory make[2]: *** [/usr/llvm/bin/llvm-ranlib] Error 1 make[2]: Leaving directory `/usr/build/llvm/tools/llvm-ranlib' make[1]: ***

----- KSR[T] Website : http://www.dec.net/ksrt E-mail: ksrt@dec.net ----- KSR[T] Advisory #004 Date: Oct 6, 1997 ID

Aaron Gray wrote: > Turns out I did not have Perl installed and hence no pod2man command, so > it was not groff after all. > > But 'true', what ever it does, does not seem to be working on Cygwin. > > true pod2man --release=1.5 --center="LLVM Command Guide" > /usr/build/llvm/../../src/llvm-1.5/docs/CommandGuide/analyze.pod >

This applies to yesterday's build of FreeBSD-4.8 from CVSup update. # man troff Formatting page, please wait...troff: fatal error: can't find macro file tty-char Done. This started happening at least a few days ago, and I've been unable to resolve it. Since I tried also building from /usr/src/gnu/groff as well, no problems with the compile, but this continues to happen.

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 This package provides the headers and specification documents defining the X Window System Core Protocol, Version 11. It also includes a number of headers that aren't purely protocol related, but are depended upon by many other X Window System packages to provide common definitions and porting layer. No code nor headers were changed in this

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

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 After 3 release candidates, it's finally done - libX11 1.4 is released. As previously warned, libX11 1.4 *requires* libxcb. The Xlib 1.3 branch continues to support the --without-xcb option for the benefit of any remaining distributors who do not yet ship XCB in their stable releases. Changes since the last release candidate: Alan Coopersmith

Kurt, if you really want to find out what things an S help file can contain, you must learn some nroff/troff [ maybe use 'groff', the GNU one ]. As always, ultimate documentation is == source. The definition of the S help is in the two files $SPLUS/cmd/help.[nt]r where nr ^= nroff, i.e. ASCII output tr ^= troff i.e. printed output (e.g via Postscript conversion) help.tr

Hi, I have found an unwanted feature in the Rd to LaTeX convertion regarding \preformatted inside a \section. I have created an Rd example below, which generates an error in the following 'R CMD check' step * creating aroma.affine-manual.tex ... OK * checking aroma.affine-manual.tex ... ERROR LaTeX errors when creating DVI version. This typically indicates Rd problems. I believe

Hi, Miller, Shao: > I am enjoying this discussion Me not. I feel quite misunderstood. hpa: > Actually, I would prefer if you removed this in its current form. Ok. Will do. If any viable solution emerges, please let me know. Have a nice day :) Thomas

On 10/08/2023 17.52, Philippe LeCavalier via samba wrote: > The solution is to update Samba to (security update to 4.17) so that 166 > (and possible 244) work from the client side. If you rely on a client side > solution you will likely continuously revisit this issue. I know I have to update Samba, but it's a hard job on a lot of small installations, and it requires quite a lot of