similar to: Injecting source reference from external editors (emacs).

Displaying 20 results from an estimated 900 matches similar to: "Injecting source reference from external editors (emacs)."

2011 Nov 19
0
Problems with new srcref warnings in R 2.14 (development)
Dear R developers, Print method for function now tries to open the source file associated with srcref of the function. It outputs only the warning, if file cannot be open, and forgets to print the function definition. Example: eval(parse(text = "tf <- function(a){ b <- a^4 b }", srcfile = srcfile("xxx at 17"))) > tf <srcref: file "xxx at 17"
2012 Mar 13
0
ess-tracebug to open a file
Dear all, First I would like to thank the ESS people's all the hard work. I am watching the project closely and witnessing the improvements day by day. Besides I found a strange situation using `ess-tracebug'. Please tell me if I am wrong or this is a bug. Start Emacs with "emacs -Q" and load ESS and enable ess-tracebug. Create a file named `testFun1.R' with the
2007 Nov 12
3
DO NOT REPLY [Bug 5075] New: Syncing with --iconv may yield protocol error
https://bugzilla.samba.org/show_bug.cgi?id=5075 Summary: Syncing with --iconv may yield protocol error Product: rsync Version: 3.0.0 Platform: All OS/Version: All Status: NEW Severity: major Priority: P3 Component: core AssignedTo: wayned@samba.org ReportedBy: lennart.samba@lovstrand.com
2007 Sep 18
1
DO NOT REPLY [Bug 4981] New: iconv confusion
https://bugzilla.samba.org/show_bug.cgi?id=4981 Summary: iconv confusion Product: rsync Version: 3.0.0 Platform: PPC OS/Version: Mac OS X Status: NEW Severity: normal Priority: P3 Component: core AssignedTo: wayned@samba.org ReportedBy: joe07734@gmail.com QAContact:
2011 Apr 06
1
executing from .R source file in the src package
Can I run R code straight from R src (.R) file instead of .rdb/.rdx? I of course tried simply unzipping tar.gz in the R_LIBS directory but R complains with "not a valid installed package". Real issue: I am very new to R and all, so this could be something basic. I'm trying to use ess-tracebug (Emacs front-end to trace/browser et al). It works great when I trace functions in .R
2012 Dec 19
0
¿Trucos para debug de código en paralelo?
Hola: ¿Y alguien tiene alguna recomendación para 'depurar' programas de R que se corren en paralelo? Por ahora estoy usando snowFall, y desde hace pocas semanas se me ha colado algun bug (en algun sitio que no acabo de encontrar) que aparece sólo cuando lo ejecuto en paralelo, y no cuando ejecuto en modo secuencial (no paralelo, quiero decir) el mísmo código. Parece ser que existen
2016 Oct 31
1
problems with ESS 16.10-1 and R version 3.3.2
Hello everyone, does anyone reported similar problems with ess 16.10-1 and R version 3.3.2 RC? These are the steps I do to reproduce it - Open any R script - C-c C-n (or C-c C-j) on any line to start the interactive session - the R process is started but it's hanging and emacs "freeze" (any command is ignored) R version 3.3.2 RC (2016-10-23 r71578) -- "Sincere Pumpkin
2013 Jun 24
0
sys.source() does not provide the parsing info to eval()
Hello, It seems that the parsing information attached to expressions parsed by the parse() function when keep.source=TRUE is not provided to the eval() function. Please consider this code: path <- tempfile() code <- '(function() print( str( sys.calls() ) ))()' writeLines(code, path) sys.source(path, envir=globalenv(), keep.source=TRUE) > OUTPUT: Dotted pair list of 4 $ :
2012 Mar 14
1
[ESS] completion in [] (R internal completion fails)
Hello, I am forwarding this from ESS mailing list, as it's a failure of internal R completion system: This fails: utils:::.assignLinebuffer('iris[iris$Spec') utils:::.assignEnd(15) utils:::.guessTokenFromLine() utils:::.completeToken() utils:::.retrieveCompletions() ## -> [1] "iris[iris$Spec" This works utils:::.assignLinebuffer('iris[ iris$Spec') # note the
2013 Jan 14
1
Issue with getParserData in R3.0.0
Hello, I am migrating my package lambda.r to R3.0.0 and am experiencing some issues with the getParserData function (which replaces the parser package). Basically the function works in the R shell but fails when either called from RUnit or from R CMD check. I've narrowed it down to the function getSrcfile, which is returning different values depending on the code path. From the command line
2019 Jan 02
6
[Bug 13735] New: Synchronize files when the sending side has newer change times while modification times and sizes are identical on both sides
https://bugzilla.samba.org/show_bug.cgi?id=13735 Bug ID: 13735 Summary: Synchronize files when the sending side has newer change times while modification times and sizes are identical on both sides Product: rsync Version: 3.1.3 Hardware: All OS: All Status: NEW
2024 May 30
1
[External] Re: Segfault when parsing UTF-8 text with srcrefs
I get an R error and no segfault: > parse(textConnection(text), srcfile = srcfile) Error in parse(textConnection(text), srcfile = srcfile) : test.r:1:1: unexpected $end 1: ? ^ This is R 4.3.0, so maybe the bug has been introduced since then... Version and system info: > version _ platform x86_64-pc-linux-gnu arch x86_64 os linux-gnu system
2019 Jul 05
0
parse() drops parse data when encountering `` (bug?)
Hi, I've noticed that partial parse data from parse() is irretrivable when it errors due to encountering '``' - two backticks in sequence. The print output also looks more limited than a regular parser error which leads me to suspect this is a bug. If this is the case could someone with the authority please add it to R's bug tracker? My reprex follows. Thanks, Miles ``` r
2024 May 28
2
Segfault when parsing UTF-8 text with srcrefs
Hi all, When I run the following code, R segfaults: text <- "?" srcfile <- srcfilecopy("test.r", text) parse(textConnection(text), srcfile = srcfile) It doesn't segfault if text is ASCII, or it's not wrapped in textConnection, or srcfile isn't set. Hadley -- http://hadley.nz [[alternative HTML version deleted]]
2009 May 21
3
file descriptor leak in getSrcLines in R 2.10.0 svn 48590
I noticed the following file descriptor leak when I couldn't remove a package unless I shut down the R session that had loaded and used it. The function that triggered the problem printed the output of a call to parse(). Each time one prints a srcref a connection is opened and not closed. It looks like it happens in as.character.srcref's call to getSrcLines, which has some logic I
2009 Feb 12
1
Why is srcref of length 6 and not 4 ?
Hello, Consider this file (/tmp/test.R) : <file> f <- function( x, y = 2 ){ z <- x + y print( z ) } </file> I get this in R 2.7.2 : > p <- parse( "/tmp/test.R" ) > str( attr( p, "srcref" ) ) List of 1 $ :Class 'srcref' atomic [1:4] 1 1 4 1 .. ..- attr(*, "srcfile")=Class 'srcfile' length 4 <environment>
2024 May 28
1
Segfault when parsing UTF-8 text with srcrefs
On 5/28/24 19:35, Hadley Wickham wrote: > Hi all, > > When I run the following code, R segfaults: > > text <- "?" > srcfile <- srcfilecopy("test.r", text) > parse(textConnection(text), srcfile = srcfile) > > It doesn't segfault if text is ASCII, or it's not wrapped in > textConnection, or srcfile isn't set. Thanks, this is
2004 May 07
1
meetme conf-background.agi
Hello there! Somebody tried the meetme|b which initiates the conf-background AGI. Actually I want to originate another call from a conference.my AGI originates the call and connects it to the conference, but the calleeee is nowhere My extension exten => 21,1,meetme(21|pb) and my AGI **************************************************************************** #!/usr/bin/perl -w
2004 May 10
1
AGI.pm wait_for_digit() not working for me!!!
Hello everybody!!! I really need your help guys, I am using the AGI mode in meetme application, and I want that AGI should wait for an input from the client/user i.e. a digit and then proceed, but I have used that AGI function agi->wait_for_digit(), but no use....my agi just passes, or ignores this function, where AGI should stop here and wait for the input.... .....my extension in my
2009 Oct 30
1
.Rprofile replacement function setwd() causing errors
In my .Rprofile I have the following functions which display the current directory in the main R window title bar, and modify base::setwd() to keep this up to date. I like this because I can always tell where I am in the file system. cd <- function(dir) { base::setwd(dir) utils::setWindowTitle( short.path(base::getwd()) ) } short.path <- function(dir, len=2) { np