similar to: False positives in check for lost braces (in tools::checkRd())

Displaying 20 results from an estimated 200 matches similar to: "False positives in check for lost braces (in tools::checkRd())"

2023 Nov 07
1
False positives in check for lost braces (in tools::checkRd())
This is a known issue already reported to the Rdpack maintainer. In some cases, the Rd code generated by Rdpack's macros contains unnecessary braces that trigger the check note because they match the pattern "text{text}" that detects common mistakes like "code{x}" (missing an escape for the macro name). Rdpack's fork of tools::deparseLatex() is being updated to
2023 Nov 07
1
False positives in check for lost braces (in tools::checkRd())
On Tue, 7 Nov 2023 17:13:05 +0100 Martin Becker <martin.becker at mx.uni-saarland.de> wrote: > More specifically, a 'Lost braces' NOTE is issued (at least > sometimes) when using the \insertRef{...}{...} command from the > Rdpack package. Does anything change if you use the development version of Rdpack (not currently on CRAN)? Apparently, the latest commit performs some
2012 Jan 13
1
checkRd freezes while parsing erroneous preprocessor macros
Dear developers, I came across with a bug while parsing Rd files. Given is the following minimal Rd file: ---- \name{foo} \title{foo} \description{ #ifdef windows win #endifd #ifdef unix unix #endif } ---- By accident I have a typo at line 6, instead of having #endif I typed #endifd. If I run checkRd(), parse_Rd(), Rd2HTML(), or others including the command line "R CMD Rconv" R
2011 Mar 16
0
tools::checkRd() output different from R CMD check
Hello, When running tools::checkRd() on a single .Rd file, should I expect the output to be the same as that generated by R CMD check when it checks .Rd files? R CMD check finds the following warning: * checking Rd \usage sections ... WARNING > Assignments in \usage in documentation object 'ilm': > result <- ilm(celfiles, threshold = 350, satLim = 10000) > Functions with
2024 Jan 30
1
linear programming in R | limits to what it can do, or my mistake?
Apart from the fact that the statement "such that t1+t2+t3+t4=2970 (as it must)" is not correct, the LP can be implemented as follows: library(lpSolve) LHS <- rbind( c(0,0,0,0, 1, 0, 0,0), c(1,0,0,0,-1, 1, 0,0), c(0,1,0,0, 0,-1, 1,0), c(0,0,1,0, 0, 0,-1,1), cbind(-diag(4),diag(4)), c(0,0,0,0,0,1,0,0), c(0,0,0,0,0,0,1,0), c(0,0,0,0,0,0,0,1) ) RHS <-
2018 Feb 01
3
Best practices in developing package: From a single file
On Thu, Feb 1, 2018 at 5:24 AM, Lionel Henry <lionel at rstudio.com> wrote: > On 31 janv. 2018, at 09:08, Gabriel Becker <gmbecker at ucdavis.edu> wrote: > > > it *actively discourages* the bits it doesn't directly support. > > It may be discouraging to include Rd syntax in roxygen docs but only > because the LaTeX-like syntax of Rd is burdensome, not because
2018 Feb 01
1
Best practices in developing package: From a single file
It is indeed a matter of what the developer is comfortable with and the one-stop solution provided by devtools is difficult to beat. This may also vary across projects. I use EMACS/ESS with and without roxygen2. In some cases EMACS/ESS+Org mode provides stunning benefits. Updating "usage" statements in Rd files was mentioned several times. Rdpack::reprompt() does this and more for
2011 Jul 26
0
[PATCH 7/7] Xen: fix braces and tabs coding style issue in xenbus_probe.c This is a patch to the xenbus_probe.c file that fixed up braces and tabs errors found by the checkpatch.pl tools.
From: Ruslan Pisarev <ruslan at rpisarev.org.ua> Signed-off-by: Ruslan Pisarev <ruslan at rpisarev.org.ua> --- drivers/xen/xenbus/xenbus_probe.c | 7 +++---- 1 files changed, 3 insertions(+), 4 deletions(-) diff --git a/drivers/xen/xenbus/xenbus_probe.c b/drivers/xen/xenbus/xenbus_probe.c index 7397695..3b53452 100644 --- a/drivers/xen/xenbus/xenbus_probe.c +++
2011 Jul 26
0
[PATCH 7/7] Xen: fix braces and tabs coding style issue in xenbus_probe.c This is a patch to the xenbus_probe.c file that fixed up braces and tabs errors found by the checkpatch.pl tools.
From: Ruslan Pisarev <ruslan at rpisarev.org.ua> Signed-off-by: Ruslan Pisarev <ruslan at rpisarev.org.ua> --- drivers/xen/xenbus/xenbus_probe.c | 7 +++---- 1 files changed, 3 insertions(+), 4 deletions(-) diff --git a/drivers/xen/xenbus/xenbus_probe.c b/drivers/xen/xenbus/xenbus_probe.c index 7397695..3b53452 100644 --- a/drivers/xen/xenbus/xenbus_probe.c +++
2011 Jul 26
0
[PATCH 7/7] Xen: fix braces and tabs coding style issue in xenbus_probe.c This is a patch to the xenbus_probe.c file that fixed up braces and tabs errors found by the checkpatch.pl tools.
From: Ruslan Pisarev <ruslan at rpisarev.org.ua> Signed-off-by: Ruslan Pisarev <ruslan at rpisarev.org.ua> --- drivers/xen/xenbus/xenbus_probe.c | 7 +++---- 1 files changed, 3 insertions(+), 4 deletions(-) diff --git a/drivers/xen/xenbus/xenbus_probe.c b/drivers/xen/xenbus/xenbus_probe.c index 7397695..3b53452 100644 --- a/drivers/xen/xenbus/xenbus_probe.c +++
2006 Aug 18
1
Migration crashes when using braces to delimit blocks
Hi, I have been using a bit of ruby here and there for scripting jobs for a year or so, and more recently have started dabbling in rails. I was wondering if anyone can help me with a strange behaviour I am getting when trying to run a migration. If I delimit a block for the create_table method with braces, the migration crashes, whereas the exact same code with the braces replaced by
2007 Mar 03
1
Ajax.Updater with evalScripts: true strips curly braces
When I return an html fragment to Ajax.Updater with evalScripts: true set, and there is a script fragment with curly braces in it (a function declaration or an object literal), the curly braces are getting stripped out somehow, and leaving me with invalid JS. I think this is the case because I put an alert in the evalScripts method right before the "return eval(script)" and it had no
2014 Dec 30
0
[PATCH] mc: add missing braces
Several braces were misplaced unintentionally. That caused the msi handling became part of the default case of the first switch statement. So add the missing ones. Signed-off-by: Vince Hsu <vinceh at nvidia.com> --- nvkm/subdev/mc/base.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/nvkm/subdev/mc/base.c b/nvkm/subdev/mc/base.c index ca7cee3a314a..25e3b9644a3f
2016 Sep 21
0
[PATCH 3/5] GPU-DRM-nouveau: Delete unnecessary braces
From: Markus Elfring <elfring at users.sourceforge.net> Date: Wed, 21 Sep 2016 08:28:08 +0200 Do not use curly brackets at four source code places where a single statement should be sufficient. Signed-off-by: Markus Elfring <elfring at users.sourceforge.net> --- drivers/gpu/drm/nouveau/nvkm/subdev/fb/ramgt215.c | 14 +++++--------- 1 file changed, 5 insertions(+), 9 deletions(-)
2016 Sep 21
0
GPU-DRM-nouveau: Delete unnecessary braces
> The original style was correct, the new style is wrong. I find your feedback interesting for further clarifications. > Multi-line indents get curly braces for readability. How do you think about to transform such an information into an official specification for the the document "CodingStyle"? Regards, Markus
2016 Sep 21
1
[PATCH 3/5] GPU-DRM-nouveau: Delete unnecessary braces
The original style was correct, the new style is wrong. Multi-line indents get curly braces for readability. regards, dan carpenter
2020 Mar 28
0
[klibc:update-dash] dash: parser: Only accept single-digit parameter expansion outside of braces
Commit-ID: 82ab2c44da800190b0a92336162ca67ba4673600 Gitweb: http://git.kernel.org/?p=libs/klibc/klibc.git;a=commit;h=82ab2c44da800190b0a92336162ca67ba4673600 Author: Herbert Xu <herbert at gondor.apana.org.au> AuthorDate: Mon, 27 May 2019 13:39:37 +0800 Committer: Ben Hutchings <ben at decadent.org.uk> CommitDate: Sat, 28 Mar 2020 21:42:55 +0000 [klibc] dash: parser: Only
2001 Jul 10
1
Mis-matched braces in Rd files (PR#1019)
This is related to the wishlist item 856 that Paul Gilbert submitted. If there's a missing closing brace, a whole section can silently disappear. It would be nice if the help parser (or CHECK) checked for matching braces in help files, and reported an error when they don't match over the whole file, or when one section is started within another one. For example: \name{test}
2003 Nov 05
1
objects inside curly braces
Hello, I am running a program in r that calls a function, which calls another function, which calls another etc. These functions are of the form: example<- function(x,y,z) {x, y, and z are defined within curly braces like this} Here's my question. To start the main function, I input as an initial parameter a matrix of regressors of the form: MyMatrix<-cbind(this.one,that.one)
2007 Sep 24
1
PicTeX output: how to suppress escaping of $ signs and braces?
Dear All, I'm trying to draw a TeX histogram with the following pair of commands, pictex(file = "realhisto.tex") hist(Peaklist$V3,xlab="Height $z/\\ut{mm}$",ylab="Probability density $\\phi{}(z-z_0)/(1/\\ut{mm})$") However, in the resulting file realhisto.tex, I get, for example \put {Height \$z/\ut\{mm\}\$} [lB] <0.00pt,0.00pt> at 136.13 9.17 when