I know an "m" symbol next to a file is modified etc.
Now I'm seeing an "i" symbol next to a ".a" file that I got from an external library.
What does that symbol mean?
Thanks,
Tee
Just figured it out, it is the "ignore" symbol.
Related
The file I'm reading contains one word per line.
I have issues with some of these words, as it seems some characters are unusual. see the following example with the first word of my list
stopwords <- read.csv("stopwords_fr.txt",stringsAsFactors = FALSE,header=FALSE,encoding="UTF-8")$V1
stopwords[1] # "a" , if you copy paste into R studio this character with the quotes around it, you'll see a little red dot preceding the a.
stopwords[1] == "a" # FALSE
How did it happen ? How can I avoid it ? And if I haven't avoided it, how do I convert this dotted "a" into a regular "a" ?
EDIT:
you can reproduce the issue by just copy pasting this in Rstudio:
"a" == "a" # FALSE
here's where I get the file from:
https://sites.google.com/site/kevinbouge/stopwords-lists/stopwords_fr.txt?attredirects=0&d=1
The encoding of the file, according to notepad++, is UTF-8-BOM. But using "UTF-8-BOM" as the encoding doesn't help. though it seemed to work in this answer:
Read a UTF-8 text file with BOM
stopwords <- read.csv("stopwords_fr.txt",stringsAsFactors = FALSE,header=FALSE,encoding="UTF-8-BOM")$V1
stopwords[1] # "a"
I have R version 3.0.2
what do the "I" and "E" symbols with the black backgrounds signify in the HTML reports generated by the istanbul JS code coverage tool?
These symbols are in front of if-else statements.
As you can see in the image you have attached, 'E' is in front of an if-else statement in which the 'Else' block is not covered and 'I' is in front an if-else statement in which the 'If' block is not covered.
Hunspell affix file may contain attribute TRY. What it does?
The Hunspell documentation says:
Hunspell can suggest right word forms, when they differ from the bad input word by one TRY
character. The parameter of TRY is case sensitive.
But I did not understand what it means.
I have following affix and dictionary files:
.aff
SET UTF-8
TRY e
.dic
2
created
create
And Hunspell input:
create
*
created
*
sreate
& sreate 1 0: create
sreated
& sreated 1 0: created
crzated
& crzated 2 0: created, create
You can see, that words "sreate", "sreated", "crzated" differ from the right word forms by "s" and "z" characters. Why this happens?
Thank you in advance.
TRY states a set of letters that can be wrong. If a misspelled word differs from a word in the dictionary file by one of these letters, then Hunspell can suggest that dictionary word.
In your example, the letter e is mistaken as z in crzated. Hence Hunspell replaces z with e.
I'm not sure about sreate and sreated TBH.
I want to enable the auto-complete functionality in emacs for editing my R files. For this, I need to have listed all the keywords in the R language. Does someone know if this is available somewhere? I know I would have to include all the functions names in the external packages I am using, but for now the list of what is in r-cran-base should be fine for me.
Thanks a lot!
apropos with an empty string argument will list all objects on the search path. It is what is used for the tab complete in the default GUI.
apropos("")
[1] "-"
[2] "-.Date"
[3] "-.POSIXt"
[4] "!"
[5] "!.hexmode"
[6] "!.octmode"
...
The R Language Definition lists all of R's keywords. Note that those are also reserved.
The following identifiers have a special meaning and cannot be used for object names
if else repeat while function for in next break TRUE FALSE NULL Inf NaN NA NA_integer_ NA_real_
NA_complex_ NA_character_ ... ..1 ..2 etc.
See ?Reserved, ?Control and maybe ?Syntax and ?Ops.
Just a little heads up that what's being discussed here has nothing to do with actual R keywords, which is its own special thing. I suspect this is what #HongOoi is alluding to.
R keywords exists ostensibly to help group functions by theme, but, except for the special case of internal, isn't widely used.
If you want to see the list of valid keywords you can get it like this
readLines(file.path(R.home("doc"), "KEYWORDS.db"))
try this
ls('package:base')
list all objects in a package
You might go to an R buffer and look at the following variable (given that you have Emacs Speaks Statistics):
ess-R-font-lock-keywords
by using C-h v ess-R-font-lock-keywords.
From there on, you can look in ess-custom.el and find everything you need on the implementation.
Just making sure you really want to do this since ?rcompgen describes the built-in functions by Deepayan Sarkar in the utils-package that already provide "tab-completion".
This is the error it gives me when i try to:
http://localhost/Symfony/web/app_dev.php/
ErrorException: Warning: constant() [function.constant]: Couldn't find constant Monolog\Logger::iNFO in /opt/lampp/htdocs/Symfony/vendor/symfony/src/Symfony/Bundle/MonologBundle/DependencyInjection/MonologExtension.php line 102
I know that the Turkish locale causes this error. But i can not use any other locale than Turkish, i must solve this.
In Turkish language look at these letters:
Lowercase "i" turns to "İ" in uppercase.
Lowercase "ı" turns to "I" in uppercase.
I think this convention is where it conflicts with English language and causes this kind of errors.
But how i can i fix this?
Reported:
https://github.com/symfony/symfony/issues/3198
This is a bug caused by the following piece of code in MonologBundle:
constant('Monolog\Logger::'.strtoupper($handler['level']));
Problem with Turkish locale is known on php.net: http://www.php.net/manual/en/function.strtoupper.php#97667
Report a bug with steps how to reproduce it on github.
Read how to report bugs in the official docs.