similar to: invalid strings while parsing code with inlinedocs package.skeleton.dx()

Displaying 20 results from an estimated 9000 matches similar to: "invalid strings while parsing code with inlinedocs package.skeleton.dx()"

2013 Jan 24
2
functions as arguments to ther functions with inlinedocs
Dear R community, I have a problem when I use functions as default values for argumnents in other functions. When I use curly brackets { here, I can not create a package with inlinedocs. It will give me the error when using package.skeleton() in my package structure: Error in parse(text = utxt) : <text>:4:0: unexpected end of input For example: dummyfunction = function(filters =
2011 Jul 06
1
including figures in html documentation/help
Dear list members, is it somehow possible to include figures to the html help pages of individueal functions (containing for example a plot produced by that function?) I thought about adding these figures into a 'graphs' subfolder of the package folder and then to somehow insert some sort of html link into the documentation code. I use inlinedocs for creating the documentation. Any
2011 Mar 13
2
Problems getting html files out of R CMD check
Hi, I'm trying to R CMD check a package, however I have hit a snag. There seems to be a problem with the creation of the /html files (the only file that's constructed here is the 00Index.html). I've tested each of the .Rd files independently with R CMD Rdconv, they all happily create html files without complaint. R CMD check <package> gives the no warnings. I'm therefore
2008 Apr 16
0
package.skeleton() creates corrupted Rd file (PR#11191)
Calling package.skeleton() results in corrupted Rd-file stub on my system. It (the file) is contaminated with mass question marks. This happens only for package Rd file, Rd stubs for *package functions* are generated nicely. An example of bad Rd file created by package.skeleton(): \name{cmrutils-package} \alias{cmrutils-package} \alias{cmrutils} \docType{package} \title{ What the package does
2008 Jul 06
1
Interpreting messages when building packages
Dear expRts, when I try to build a package by myself, the process fails writing the following messages to 00install.out: * Installing *source* package 'dynalc' ... ** libs WARNING: no source files found chmod: Zugriff auf ?/home/hannes/texte/forschung/clot/programme/dynalc.Rcheck/dynalc/libs/*? nicht m?glich: No such file or directory ** R ** data ** inst ** help Note: removing empty
2001 Sep 28
1
savehistory: Suggestions to a \seealso{} (PR#1104)
Full_Name: Henrik Bengtsson Version: 1.3.1 OS: WinMe Submission from: (NULL) (130.235.2.229) I suggest the following \seealso to be added for savehistory: \seealso{ To execute \code{savehistory} automatically when \R quits see \link{.Last} and \link{.Rprofile}. } -.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.- r-devel mailing list -- Read
2018 Jan 30
0
Best practices in developing package: From a single file
> >> I am wondering what are the best practices for developing an R > >> package. I am aware of Hadley Wickham's best practice > >> documentation/book (http://r-pkgs.had.co.nz/).??I recall a couple of > >> years ago there were some tools for generating a package out of a > >> single file, such as using package.skeleton, but no auto-generated
2009 Aug 09
1
Linking in R package documentation
I have two straightforward questions about linking in the man pages for R packages: First, is it possible to link from within parts of the documentation that are not the \seealso section? For example, I would like to have something like: \arguments{ \item{correlation}{an optional \code{corStruct} object describing the within-group correlation structure; the available classes are given in
1997 Jun 02
1
R-alpha: S doc -> R doc
Attached is the current version of my sd2rd perl script. It has passed tests by Martin, Fritz and myself, and seems to work reasonably well (it should get the arguments lists right, distinguish between VALUE and VALUES, and know about REFERENCES and SEEALSO). Any comments etc are most welcome. -k ************************************************************************ #!/usr/bin/perl -w $\ =
2009 May 04
5
Convert skeleton to "regular" format
Hi there, we just encountered a problem with some tools obviously encoding into the skeleton format by default, which leads to problems with several other tools, in that particular case it's oggCut. When we try to edit/cut an ogg file with it, the program crashes with a segfault. I was able to locate and fix the problem in the oggCut source but I am wondering how to convert my ogg files to a
2006 Jul 19
1
Skeleton output support in speexenc
Hi, I just added skeleton meta data output support in speexenc. The option is disabled by default and can be enabled using -k or --skeleton. I'm using a very simple skeleton API for handling skeleton packet generation which is contained in skeleton.h & skeleton.c. Please check the patch and whether xine/mplayer/quicktime and other players support the skeleton enabled speex file. At the
2008 Feb 01
4
[PATCH] skeleton.c
I'm patching oggenc with this fix. If Conrad reports success in his test, I'll go ahead and patch all other implementations I can find. -Ivo
2008 Feb 01
4
[PATCH] skeleton.c
I'm patching oggenc with this fix. If Conrad reports success in his test, I'll go ahead and patch all other implementations I can find. -Ivo
2010 Apr 29
3
Ogg index and Skeleton 4.0
Hi everybody, I've updated OggIndex to now output Skeleton 4.0 tracks. The differences between Skeleton 3.x and Skeleton 4.0 with OggIndex is: * The fisbone packet now includes a "Radix" field. * The fisbone packet now includes two new compulsory message headers; "Role" and "Name". * The fishead packet no longer includes "start time"
2014 Aug 22
2
Merging Ogg streams whilst updating the Skeleton?
Hi All I'm currently trying to put together an ogg file with two theora streams, a handful of audio streams (probably mixed vorbis and opus), and a Skeleton stream that describes their relationships to each other. I had hoped to be able to use the oggz suite of tools, but I can't seem to get that to work. To generate my theora files, I'm using ffmpeg2theora, which will happily
2008 Feb 12
2
[PATCH] skeleton.c
> Can you commit it in ffmpeg2theora? I think that and Speex are the > only other places where skeleton.c is used, and ffmpeg2theora is > likely to have Skeleton being used by default in the next release. Then maybe it would be a good idea to do the API change needed for checking magic now ?
2013 Jun 07
1
relist() is broken when the skeleton is a list with empty list elements
Hi, relist() is broken when the skeleton is a list with empty list elements: > x <- list(1:3, integer(0), 11:14) > relist(unlist(x), x) [[1]] [1] 1 2 3 [[2]] [1] 11 3 [[3]] [1] 11 12 13 14 Hard to believe that such a bug has been around for 6 years (i.e. since the introduction of relist()) without ever being noticed. Cheers, H. > sessionInfo() R
2008 Jul 15
1
package.skeleton does invalide regular name...
Hi the list, I am using package.skeleton on a file that has a very classic name, but package.skeleton detect it as a invalid name : --- 8< ------- package.skeleton(name="packClassicBis",code_files="./packClassic/R/progClassic.R") Cr?ation des r?pertoires... Cr?ation de DESCRIPTION... Cr?ation de 'Read-and-delete-me'... Recopiage des fichiers de code... Cr?ation
2008 Apr 13
1
R 2.7 package.skeleton
Hi the devel list I am testing package.skeleton in R 2.7 (download today). I get an error that I do not understand. I guess it is not an error from my code since I have no probleme when I source it. So is it a error in package.skeleton? Here is my code : --- 8< ------ File essai.r ------------- setClass( Class="ClusterizLongData", representation=representation(
2011 Jun 09
1
package.sk​eleton() does not create 'data' folder
Hi again, yesterday I mailed this query however I could not see this on the mail list. Therefore, I am reposting it again. I was using package.skeleton() function to create the skeleton of my package in windows. Here is my attempt: rm(list = ls()) setwd("F:/R_PackageBuild") package.skeleton("trial1", namespace = TRUE, code_files = "F:/R_PackageBuild/trial.r") In