search for: preformat

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...

Hi, I have been developing a package in R and have been working on documentation. I have a \details function that contains the following: \details{ some text \preformatted{ [my-section] user = apv host = 127.0.0.1 } } When I run R CMD check I get an error while checking the manual. If I remove: \preformatted{ [my-section] user = apv host = 127.0.0.1 } and replace it with [my-section] user = apv host = 127.0.0.1 the error goes away. Has anybody had this p...

Hi, The "\preformatted" environment in Rd files doesn't seem to escape long sequences of backslashes properly when converted to pdf (LaTeX) documentation. I'm running R version 2.14 (from subversion, revision 57751) on Linux (RHEL). Here's an example from the command line: echo "\title{test}\n...

Hi r-devels, I have two minor problems with special characters in Rd files when used within a \preformatted{} markup command: ------------------------------------------------------ 1. issue: backslash + single brace ------------------------------------------------------ I would like to write "\\\}" to produce \} on output (documenting the need to escape the brace once again before TeX-ing...

This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. ------_=_NextPart_000_01C3BE9C.3FB5BC1A Content-Type: text/plain; charset="iso-8859-1" There is a small bug in the implementation of \preformatted in R 1.8.0: The closing "\end{verbatim}" needs to be followed by a newline, since my latex ignores everything following it on the line. In an .Rd file I have: \details{ This function provides a thin wrapper around the Unix "fork" system call, which will create a new p...

Dear All, I have the following in a .Rd file: ... human readable (not binary) format. The format itself is like the following: \preformatted{ \# vertex1name vertex2name [optionalWeight] vertex3name [optionalWeight] } Here, the first vertex of an edge is preceded with a pound sign ... and it is fine with R 2.9.2, but fails on R-devel, when building the PDF version of the manual: ... * checking PDF version of manual ......

Dear all, On the Broadcom wiki page, I've moved the formatted codes from tables into preformatted blocks. This makes the raw wiki code easier to read, and is consistent with other wiki pages that I've come across during translation. Should the maintainers of that page find such a change undesirable, please feel free to revert. Regards, Timothy Lee

The Rd.sty LaTeX package is used when building the R manuals, and by the LaTeX pages produced from the man pages. I have tracked down some problems G?bor Cs?rdi was having recently (see "Re: [R] preformatted and '#' in manual pages" in R-help) to a LaTeX problem, and am trying to work out how to fix it. Specifically, the .Rd file he was using had a structure like \dQuote{ ... \preformatted{ line 1 line 2 } } which tools::Rd2latex in R translates to the similar LaT...

...the entry point by which the assembly input is parsed. However Hexagon assembly has some features that make it more readable, such as r1 = r2, or if(r1) r2 = mem(#immediate). This makes taking advantage of the existing LLVM code difficult. Currently, I see two options. One is to preformat the assembly string(s) obtained from the td files so that it is matches the format that the tablegen backend expects, and also preformat the assembly input so that it can be matched against the preformatted assembly strings. The other is to write a whole new TD backend that doesn't rely on...

IMHO trailing spaces should be permitted in POD files. Currently they are prevented by the git upload hook. The reason to allow them in POD files is because indentation is used to indicate blocks of preformatted text (the equivalent of <pre> in HTML). To keep code together in the output if it contains blank lines you have to add a line containing a single space. For an example of where this is currently wrong, because we're not allowed to have trailing spaces, see the preformatted code block...

Hi R-devels, I noticed that you are working quite actively on the new Rd-parser and have made it the default renderer in R-2.10.0dev. So I would like to come back on an issue I have already raised on this list last November ("Two minor escaping issues using \preformatted{....} in Rd format") My setting has slightly changed as \preformatted, AFAICS is not supported within \describe environments, so I have switched to \code{} ... The issue is again the correct typesetting of \\\\\% within a \code{}-tag. This sequence occurs within a string (...

...the assembly input is parsed. > > However Hexagon assembly has some features that make it more readable, such as r1 = r2, or if(r1) r2 = mem(#immediate). This makes taking advantage of the existing LLVM code difficult. > > > Currently, I see two options. > > One is to preformat the assembly string(s) obtained from the td files so that it is matches the format that the tablegen backend expects, and also preformat the assembly input so that it can be matched against the preformatted assembly strings. I agree this sounds pretty hacky. > > The other is to write a wh...

HPUX doesn't seem to ship with a set of troff macros that can handle the OpenSSH manpages. Maybe other OSs have this problem? Rather than sodding about with the tmac/ directory, I think we should do one of two things: 1. Ship a set of preformatted manpages, and either auto-install them in $prefix/man/cat{1,1m} or just have instructions in INSTALL to do so 2. Recommend users install groff ;-) Neither is great, but as things stand right now HP users get garbage for manpages. It's not too much effort to provide them with pages prepro...

Hello. I have a server that sends a preformatted email when an event occur. What I need is that when Asterisk receives this email automatically dial a pre-recorded message. It doesn't have to dial ride away, maybe a scheduled cron job will be enough. Is that possible? Any hint? What should I be looking for? Thanks, and sorry for my lous...

...L file example, and the yaml document separator is three dashes, but this conflicts with the separator in webgen. Example: <pre> --- # above line causes error </pre> Second, how can I indent a <pre> block in an ordered list, but still make it highlight at the first colum of the preformatted text? Example: * bulleted instruction to cut and paste file contents <pre> the file contents </pre> * the file contents above are not indented with the bullets Thanks, -- Chad

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! -- Mark D. Roth <roth at feep.net> http://www.feep.net/~roth/ -------------- next part -------------- diff -urN openssh_cvs/Makefile.in openssh_...

...ff-by: Ben Hutchings <ben at decadent.org.uk> --- usr/utils/ls.c | 18 ++++++++---------- 1 file changed, 8 insertions(+), 10 deletions(-) diff --git a/usr/utils/ls.c b/usr/utils/ls.c index 9677bc0f..50af4349 100644 --- a/usr/utils/ls.c +++ b/usr/utils/ls.c @@ -50,7 +50,7 @@ static void do_preformat(const struct stat *st) return; } -static void do_stat(const struct stat *st, const char *path) +static void do_stat(const struct stat *st, int dir_fd, const char *path) { char *fmt, *link_name; int rc; @@ -138,7 +138,7 @@ static void do_stat(const struct stat *st, const char *path) pe...

I have written a function for my 'oce' package that creates a data.frame containing a variable name with a prime in it. (I use prime to indicate coordinate rotation, a reasonably standard convention that motivates the odd variable name.) How can I name that in an Rd file? I tried \code{u'} but R-2.9.0 doesn't like to build my package then, since it thinks I'm opening a

Dear all, HugoDoria's last two edits on the Spacewalk page (http://wiki.centos.org/HowTos/PackageManagement/Spacewalk) have removed line feeds from all preformatted text, as well as pointed to some RHEL6 packages on a page written for CentOS 5. I propose that the page be reverted backed to revision 82. Regards, Timothy

Hi, I've got a buffalo 1TB DriveStation run in RAID 1 mode, i.e. 500G space available, but that beast is preformatted in vfat. Buffalo doesn't recommend to run it as ext2/ext3, so I mount a vfat drive wich has the limitations "no symlinks, no uids, no gids, etc.". As I just want to use the DriveStation as a backup target, I did the following: I created files of 4G size with 'dd if=/dev/zer...