search for: backquot

...4)^2 > lm(`a(b)` ~ `c(d)`) Error in model.matrix.default(mt, mf, contrasts) : model frame and formula mismatch in model.matrix() To fix it replace this line in model.matrix.default: reorder <- match(attr(t, "variables")[-1], names(data)) with these two lines: strip.backquote <- function(x) gsub("^`(.*)`", "\\1", x) reorder <- match(strip.backquote(attr(t, "variables"))[-1], strip.backquote(names(data)))

...least about the following query!) Reading the draft proofs of an article I've been asked to look through, I find the typesetter has set what would normally be entered as source("xyz.R") or source('xyz.R') as source(`xyz.R') i.e. it has come out with an opening backquote, then xyz.R, then a closing forward quote. I suspect the intervention of "intelligent" software (? la Word's "clever quotes"). Well, the cure is clear and I'm not asking about that. But I got curious about what role the backquote might play in R syntax (if any). As a s...

Thanks to Bill Dunlap for the clarification. On follow-up it turns out that this will be an issue for many if not most of the routines in the survival package: a lot of them look at the terms structure and make use of the dimnames of attr(terms, 'factors'), which also keeps the unneeded backquotes. Others use the term.labels attribute. To dodge this I will need to create a fixterms() routine which I call at the top of every single routine in the library. Is there a chance for a fix at a higher level? Terry T. On 03/05/2018 03:55 PM, William Dunlap wrote: > I believe this has to...

...ibs/klibc/klibc.git;a=commit;h=5048195d282d48b25a9a0164e60cd0e6708ec8a9 Author: Herbert Xu <herbert at gondor.apana.org.au> AuthorDate: Thu, 15 Mar 2018 18:27:30 +0800 Committer: Ben Hutchings <ben at decadent.org.uk> CommitDate: Fri, 25 Jan 2019 02:57:21 +0000 [klibc] parser: Fix backquote support in here-document EOF mark Currently using backquotes in a here-document EOF mark is broken because dash tries to do command substitution on it. This patch fixes it by checking whether we're looking for an EOF mark during tokenisation. Reported-by: Harald van Dijk <harald at gigaw...

...ibc/klibc.git;a=commit;h=e90b159a00304664ddc94fca392146f4bde1bcec Author: Herbert Xu <herbert at gondor.apana.org.au> AuthorDate: Thu, 15 Mar 2018 18:27:30 +0800 Committer: Ben Hutchings <ben at decadent.org.uk> CommitDate: Sat, 28 Mar 2020 21:42:54 +0000 [klibc] dash: parser: Fix backquote support in here-document EOF mark [ dash commit c166b718b496da63c4df7a0972df2fc6cd38256b ] Currently using backquotes in a here-document EOF mark is broken because dash tries to do command substitution on it. This patch fixes it by checking whether we're looking for an EOF mark during token...

...5b9a81bd70582edfa9d7ead08be Author: Nikolai Merinov <n.merinov at inango-systems.com> AuthorDate: Mon, 29 Apr 2019 19:13:37 +0500 Committer: Ben Hutchings <ben at decadent.org.uk> CommitDate: Sat, 28 Mar 2020 21:42:55 +0000 [klibc] dash: expand: Fix trailing newlines processing in backquote expanding [ dash commit c4f4ee8ecf85834811c252fc1df3892863572bbd ] According to POSIX.1-2008 we should remove newlines only at the end of the substitution. Newlines-only substitions causes dash to remove newlines before beggining of the substitution. The following code: cat <<END...

I believe this has to do terms() making "term.labels" (hence the dimnames of "factors") with deparse(), so that the backquotes are included for non-syntactic names. The backquotes are not in the column names of the input data.frame (nor model frame) so you get a mismatch when subscripting the data.frame or model.frame with elements of terms()$term.labels. I think you can avoid the problem by adding right after ll &...

I''m trying to stub(!) the Kernel.` (backquote) method and I''m having confusing (to me) results. Here''s the method I''m spec''ing: class Barcode ... def raw_barcodes self.make_temporary_copy `OcrBarcode #{self.temp_file_path}` end ... end And this is my (newbish) attempt at the spec: describ...

A user reported a problem with the survdiff function and the use of variables that contain a space.? Here is a simple example.? The same issue occurs in survfit for the same reason. lung2 <- lung names(lung2)[1] <- "in st"?? # old name is inst survdiff(Surv(time, status) ~ `in st`, data=lung2) Error in `[.data.frame`(m, ll) : undefined columns selected In the body of the code

...;>> that >>> this will be an issue for many if not most of the routines in the >>> survival >>> package: a lot of them look at the terms structure and make use of the >>> dimnames of attr(terms, 'factors'), which also keeps the unneeded >>> backquotes. Others use the term.labels attribute. To dodge this I will >>> need to create a fixterms() routine which I call at the top of every >>> single >>> routine in the library. >>> >>> Is there a chance for a fix at a higher level? >>> >>&g...

...will be an issue for many if not most of the routines in the >>>> survival >>>> package: a lot of them look at the terms structure and make use of the >>>> dimnames of attr(terms, 'factors'), which also keeps the unneeded >>>> backquotes. Others use the term.labels attribute. To dodge this I will >>>> need to create a fixterms() routine which I call at the top of every >>>> single >>>> routine in the library. >>>> >>>> Is there a chance for a fix a...

That's more or less right. We wrote a terms.merMod method, which accesses the terms component of the @frame slot, which we have modified upstream ... Do you mean term.labels rather than term.names? BTW ?terms.object says (under the "term.labels" element): Non-syntactic names will be quoted by backticks: this makes it easier to re-construct the formula from the term

I''ve done tons of searching on this so I apologize if this is one of those common knowledge things. I am relying on Kernel#` and Kernel#system to run some command line utilities in my Rails app. This worked great until I moved to Apache (win32). When running FCGI, neither of these methods work (both return nil). When running CGI, system seems to work, but ` doesn''t. I have

...rification. On follow-up it turns out that >> this will be an issue for many if not most of the routines in the survival >> package: a lot of them look at the terms structure and make use of the >> dimnames of attr(terms, 'factors'), which also keeps the unneeded >> backquotes. Others use the term.labels attribute. To dodge this I will >> need to create a fixterms() routine which I call at the top of every single >> routine in the library. >> >> Is there a chance for a fix at a higher level? >> >> Terry T. >> >> >&gt...

...s name fn <- paste(i, ".txt", sep="") # make the filename s <- read.delim(fn, header = FALSE) # now put it all together # …except that I don't want to reassign s, I want to evaluate it and make its value a variable with its own value. } } If this were Lisp I'd use backquotes (or "backticks", as some say) and commas—examples of read macros—to do this, but I can't find anything analogous for R. How might I accomplish this in R? Sincerely, Frank Tamborello, PhD W. M. Keck Postdoctoral Fellow School of Biomedical Informatics University of Texas Health Sci...

Since my previous question didn''t get much attention, I thought I''d make the subject more expressive. I didn''t realize the list had this much traffic. Is anyone using system or "backquote" to run commands in Rails? These work fine in webrick, but both return nil when running in Apache FCGI. In CGI mode, system seems to work, but backquote doesn''t. Any ideas? Been banging my head on the wall for a while. BTW, this is on Windows. Mark -------------- next part -----...

Dear R-devel, There is a new feature in R-devel, which explicitly refers to LISP @ operator for splicing. > The backquote function bquote() has a new argument splice to enable splicing a computed list of values into an expression, like ,@ in LISP's backquote. Although the most upvoted SO question asking for exactly LISP's @ functionality in R doesn't seems to be addressed by this new feature. Is it poss...

...8 @@ done: else { if (readtoken() != TRP) synexpect(TRP); + setinputstring(nullstr); + parseheredoc(); } + heredoclist = saveheredoclist; + (*nlpp)->n = n; - if (oldstyle) { - /* - * Start reading from old file again, ignoring any pushed back - * tokens left from the backquote parsing - */ - popfile(); + /* Start reading from old file again. */ + popfile(); + /* Ignore any pushed back tokens left from the backquote parsing. */ + if (oldstyle) tokpushback = 0; - } while (stackblocksize() <= savelen) growstackblock(); STARTSTACKSTR(out);

Dear List, Is it possible to have function names like ? (unicode universal quantifier)? This question is inspired by agda source code, which supports this. http://www.cs.nott.ac.uk/~nad/listings/lib-0.4/Algebra.html It would be handy to use. My guess is, however, that it's not supportet in R. Regards, Steve

DTraceToolkit has a dtrace script (Proc/pidpersec.d) that refers to a variable mpid as below profile:::tick-1sec { printf("%-22Y %8d %6d\n", walltimestamp, `mpid, pids); pids = 0; } Where is `mpid getting picked from (it isn''t declared anywhere else)? What does the character ` in `mpid signify? I do not see any reference to this variable in the dtrace