Re: [Rd] Halfway through writing an "IDE" with support for R; Proof of concept, and request for suggestions.
Honestly, I don't see the motivation for this. There are many similar projects that are mature, so my feedback would be: don't reinvent the wheel and contribute to those. Iñaki El vie., 14 jun. 2019 3:18, Abby Spurdle escribió: > I thought that I'd get more feedback. > But it's ok, I understand. > > I wanted to note that I've moved symbyont to GitLab, which is where I > should have put it, in the first place. > > Also, I'm not planning to start another thread. > However, if anyone has suggestions six months from now (or six years from > now...), you're still welcome to email me, and I will try to listen... > > [[alternative HTML version deleted]] > > __ > R-devel@r-project.org mailing list > https://stat.ethz.ch/mailman/listinfo/r-devel > [[alternative HTML version deleted]] __ R-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-devel
[Rd] R 3.6.1 scheduled for July 5
Full schedule is available on developer.r-project.org. -- Peter Dalgaard, Professor, Center for Statistics, Copenhagen Business School Solbjerg Plads 3, 2000 Frederiksberg, Denmark Phone: (+45)38153501 Office: A 4.23 Email: pd@cbs.dk Priv: pda...@gmail.com __ R-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-devel
Re: [Rd] compiler flags for performance
On 13/06/2019 16:14, Dirk Eddelbuettel wrote: > On 13 June 2019 at 16:05, lejeczek via R-devel wrote: > | I'd like to ask, and I believe this place here should be best as who can > | know better, if building R with different compilers and opt flags is > | something worth investing time into? > | > | Or maybe this a subject that somebody has already investigated. If yes > | what then are the conclusion? > | > | Reason I ask is such that, on Centos 7.6 with different compilers from > | stock repo but also from so called software collections, do not > | render(with flags for performance) an R binaries which would perform any > | better, according to R-benchmark-25 at least, then "vanilla" packages > | shipped from distro. > | > | And that makes me curious - is it because R is such a case which is > | prone to any compiler performance optimizations? > | > | Maybe there is more structured and organized way to conduct such > | different-compilers-optimizations benchmarks/test? > | > | What do devel can say and advise with regards to compile-for-performance > | subject? > > Of course you do that, and add those switches to ~/.R/Makeconf. The > resulting binaries may become non-portable. > > E.g. "at work" we use -march=native quite a bit but it means can't share > libraries from a beefier dev box with skinnier deployment boxen as they don't > have the same chipset even thought the are both x86_64 and use the same Linux > distro. > > As for which switches help in which way on different compiler: that is > probably best seen as a black box. Time and profile locally, I no longer try > to generalize. The newer 'link-time-optimizations' can help too, they > certainly make builds longer ... > > Dirk > I've tried the "usual" tweaks and what puzzles me is the fact, that -march=native and -lto(s) + Os/3 do not help much, make almost invisible improvements (again, judging by results from R-benchmark-25) with gcc >= 7 as compared to distro's package which is built with -O2 -mtune=generic and no ltos. Would there be other(better) way to test core R? What king of R perf increases do you guys see with compiler's opt flags, if any? regards, L. __ R-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-devel
Re: [Rd] [R] Open a file which name contains a tilde
Hi John,
First, the unix and linux filesystem allows the use of any nonzero character in
its filesystem filenames and the c functions open / fopen, symlink. rename,
chdir and so on don't care about any tilde. If the open systemcall gets a file
which begins with a tilde then it will try to open this filename without any
preceding modification.
So the tilde expansion is not really a unix idiom. It is rather an idiom of its
unix shells like bash. But beware, the bash treats the tilde as home path not
in all cases.
Inside of quotes the tilde keeps unaltered. So bedides any cenvenience
functionality which can lead to failing code the bash has a very clean way to
access files in a unique way.
And here is the problem wirh R.
The R shell has no quoting mechanism for this use case. It provides the tilde
expansion after a string has been defined. In the bash it is the opposite.
First the string gets defined ( for instance ~"/abc.txt" would expand to
"/home/user/abc.txt" or "~/abc.txt" keeps "~/abc.txt" and that means a
directory named '~' with a directory entry named 'abc.txt' inside of it) and
after it is defined it keeps consistent and can be passed to every function.
Actually R has already a clean string datatype. But by the transition to
filesystem operations the expansion takes place. In my opinion at the wrong
place. And additionally there exists no quoting mechanism which allows to keep
tildes unaltered. It would be better to clear distinguish between a string
which is passed to the filesystem calls and some convenience expansion
mechanisms.
But it is like it is. For my need I created a solution which takes strings
unaltered and so I can fulfil my work.
And for whom who is interested in it, can take a look:
https://github.com/schwidom/simplefs
Suggestions are welcome.
Kind regards
Frank Schwidom
On 2019-06-12 12:50:12, John via R-help wrote:
> On Wed, 5 Jun 2019 18:07:15 +0200
> Frank Schwidom wrote:
>
> In reading file names, names with spaces require escaping of the
> spaces, and you are using not only a tilde but the space as spell. The
> tilde is conventionally read as wild card representing the leading
> portion of the file address, which is what you see here:
>
> The long standing convention in unix and linux is that a tilde is
> shorthand for your home directory, just as "./" is the local directory
> and "../" is one step back up the directory tree. The output of
> path.expand() varies in how your string is constructed:
>
> 1. > path.expand("ab")
>[1] "ab"
> 2. > path.expand("a b")
>[1] "a b"
> 3. > path.expand("a ~b")
>[1] "a ~b"
> 4. > path.expand("a ~ b")
>[1] "a /home/john b"
> 5. > path.expand("a ~/b")
>[1] "a /home/john/b"
> 6. > path.expand("~/a b")
>[1] "/home/john/a b"
>
> Notice that the spaces have an effect on how the tilde is parsed in
> the string. The next to last case sees a string with three elements:
> "a", the local path, and "b". The last expands the tilde as the "path"
> to a hypothetical file "b" in the home directory. In the sixth case the
> same behaviour occurs.
>
> If you read the help for path.expand(), the routine expects
> "leading" tildes, which explains the free floating "path in the fourth
> example. In the third example, where the forward slash is omitted, the
> routine simply treats the tilde as part of a string.
>
> Also note this at http://www.linfo.org/file_name.html:
>
> "...file names only use alphanumeric characters (mostly lower case),
> underscores, hyphens and periods. Other characters, such as dollar
> signs, percentage signs and brackets, have special meanings to the
> shell and can be distracting to work with. File names should never
> begin with a hyphen."
>
> The probable "bug" is that none of the programmers imagined that anyone
> would use special characters within file names, "legal" or not, (just
> not done, don't y' know). In any case the simple solution, if you
> really, really need a tilde in a filename, is to avoid setting it off in
> spaces, or any other character that could mislead a routine into
> treating it conventionally as shorthand for you home directory.
>
> JWDougherty
>
> __
> r-h...@r-project.org mailing list -- To UNSUBSCRIBE and more, see
> https://stat.ethz.ch/mailman/listinfo/r-help
> PLEASE do read the posting guide http://www.R-project.org/posting-guide.html
> and provide commented, minimal, self-contained, reproducible code.
>
__
R-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-devel
Re: [Rd] [R] Open a file which name contains a tilde
On 14/06/2019 14:43, Frank Schwidom wrote: Hi John, First, the unix and linux filesystem allows the use of any nonzero character in its filesystem filenames Well, even it's not the central point of the discussion let make this assertion more correct. It depends on file system. E.g. JFS (https://en.wikipedia.org/wiki/JFS_%28file_system%29) abides to this rule while very popular ext4 (https://en.wikipedia.org/wiki/Ext4) does not. In addition to NUL character, the latter forbids '/' as well. Best, Serguei. __ R-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-devel
Re: [Rd] inappropriate warning in latticeExtra
This is still not repaired in
R version 3.6.0 Patched (2019-05-17 r76528)
> library(latticeExtra)
> a <- xyplot(1 ~ 1)
> c(a,a)
Warning message:
In formals(fun) : argument is not a function
Can we have it in R-3.6.1 that Peter just announced?
Rich
On Mon, Apr 2, 2018 at 4:08 AM Deepayan Sarkar
wrote:
>
> On Fri, Mar 23, 2018 at 7:58 AM, Richard M. Heiberger wrote:
> > The warning message in the last line of this email is incorrect.
> > This is behavior which Duncan Murdoch labeled a bug in
> >https://stat.ethz.ch/pipermail/r-help/2017-December/450494.html
>
> Yes, sorry, this has been fixed in the r-forge sources for a while
> now, but I haven't had the time to finish up some other fixes and push
> an update to CRAN.
>
> Hopefully over the summer break.
>
> Regards,
> -Deepayan
>
>
> > This is a fresh install of R-devel (2018-03-21 r74436)
> >
> >
> >
> >
> > R Under development (unstable) (2018-03-21 r74436) -- "Unsuffered
> > Consequences"
> > Copyright (C) 2018 The R Foundation for Statistical Computing
> > Platform: x86_64-w64-mingw32/x64 (64-bit)
> >
> > R is free software and comes with ABSOLUTELY NO WARRANTY.
> > You are welcome to redistribute it under certain conditions.
> > Type 'license()' or 'licence()' for distribution details.
> >
> > Natural language support but running in an English locale
> >
> > R is a collaborative project with many contributors.
> > Type 'contributors()' for more information and
> > 'citation()' on how to cite R or R packages in publications.
> >
> > Type 'demo()' for some demos, 'help()' for on-line help, or
> > 'help.start()' for an HTML browser interface to help.
> > Type 'q()' to quit R.
> >
> >> library(latticeExtra)
> > Error in library(latticeExtra) :
> > there is no package called ‘latticeExtra’
> >> install.packages("latticeExtra")
> > Warning in install.packages("latticeExtra") :
> > 'lib = "C:/Program Files/R/R-devel/library"' is not writable
> > --- Please select a CRAN mirror for use in this session ---
> > also installing the dependency ‘RColorBrewer’
> >
> > Warning: unable to access index for repository
> > http://www.stats.ox.ac.uk/pub/RWin/bin/windows/contrib/3.5:
> > cannot open URL
> > 'http://www.stats.ox.ac.uk/pub/RWin/bin/windows/contrib/3.5/PACKAGES'
> > trying URL
> > 'https://cran.wu.ac.at/bin/windows/contrib/3.5/RColorBrewer_1.1-2.zip'
> > Content type 'application/zip' length 55444 bytes (54 KB)
> > downloaded 54 KB
> >
> > trying URL
> > 'https://cran.wu.ac.at/bin/windows/contrib/3.5/latticeExtra_0.6-28.zip'
> > Content type 'application/zip' length 2191524 bytes (2.1 MB)
> > downloaded 2.1 MB
> >
> > package ‘RColorBrewer’ successfully unpacked and MD5 sums checked
> > package ‘latticeExtra’ successfully unpacked and MD5 sums checked
> >
> > The downloaded binary packages are in
> >
> > C:\Users\rmh.DESKTOP-60G4CCO\AppData\Local\Temp\RtmpqA7Rqg\downloaded_packages
> >> library(latticeExtra)
> > Loading required package: lattice
> > Loading required package: RColorBrewer
> >> a <- xyplot(1 ~ 1)
> >> c(a,a)
> > Warning message:
> > In formals(fun) : argument is not a function
> >>
> >
> > __
> > R-devel@r-project.org mailing list
> > https://stat.ethz.ch/mailman/listinfo/r-devel
__
R-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-devel
Re: [Rd] compiler flags for performance
On Fri, Jun 14, 2019 at 1:44 PM lejeczek via R-devel wrote: > On 13/06/2019 16:14, Dirk Eddelbuettel wrote: > > On 13 June 2019 at 16:05, lejeczek via R-devel wrote: > > | I'd like to ask, and I believe this place here should be best as who > can > > | know better, if building R with different compilers and opt flags is > > | something worth investing time into? > > | > > | Or maybe this a subject that somebody has already investigated. If yes > > | what then are the conclusion? > It is worth spending sometime,but all in all, you may end disapointed. There are other things you may try: new Intel Linux distro (optimized for Intelprocessors); build with Clang compiler instead of GCC; use optimized BLAS (that's indeed a very good idea,look for openblas). I have build R with Intel MKL.The libraries are free for one year (maybe did it change). The build is far from being trivial. Please find on my github[0] some details > | > > | Reason I ask is such that, on Centos 7.6 with different compilers from > > | stock repo but also from so called software collections, do not > > | render(with flags for performance) an R binaries which would perform > any > > | better, according to R-benchmark-25 at least, then "vanilla" packages > > | shipped from distro. > > | > > | And that makes me curious - is it because R is such a case which is > > | prone to any compiler performance optimizations? > > | > > | Maybe there is more structured and organized way to conduct such > > | different-compilers-optimizations benchmarks/test? > > | > > | What do devel can say and advise with regards to > compile-for-performance > > | subject? > > > > Of course you do that, and add those switches to ~/.R/Makeconf. The > > resulting binaries may become non-portable. > > > > E.g. "at work" we use -march=native quite a bit but it means can't share > > libraries from a beefier dev box with skinnier deployment boxen as they > don't > > have the same chipset even thought the are both x86_64 and use the same > Linux > > distro. > > > > As for which switches help in which way on different compiler: that is > > probably best seen as a black box. Time and profile locally, I no > longer try > > to generalize. The newer 'link-time-optimizations' can help too, they > > certainly make builds longer ... > > > > Dirk > > > I've tried the "usual" tweaks and what puzzles me is the fact, that > -march=native and -lto(s) + Os/3 do not help much, make almost invisible > improvements (again, judging by results from R-benchmark-25) with gcc >= > 7 as compared to distro's package which is built with -O2 -mtune=generic > and no ltos. > > Would there be other(better) way to test core R? > > What king of R perf increases do you guys see with compiler's opt flags, > if any? > > regards, L. > > [0] https://github.com/gabx/R-project/tree/master/R-mkl > > > __ > R-devel@r-project.org mailing list > https://stat.ethz.ch/mailman/listinfo/r-devel > [[alternative HTML version deleted]] __ R-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-devel
Re: [Rd] compiler flags for performance
On 14 June 2019 at 15:22, arnaud gaboury wrote: | I have build R with Intel MKL.The libraries are free for one year (maybe | did it change). The build is far from being trivial. Please find on my | github[0] some details Gee, when oh when does this "meme" of "I built R with MKL" die? BLAS/LAPACK are _an interface_ and once you tell R to configure with BLAS as a shared library, _all_ matching BLAS/LAPACK libraries become _pluggable_. My gcbd package and vignette demonstrated that a decade+ ago (then using Goto). It also holds for MKL, and these days Intel tries harder with a) friendlier licenses and b) better packaging -- they even give .deb (and I believe .rpm). So now you just drop MKL in/out with a single script which you can find here https://github.com/eddelbuettel/mkl4deb with supporting blog posts at http://dirk.eddelbuettel.com/blog/2018/04/15#018_mkl_for_debian_ubuntu So please, let's not repeat this 'you have to use Revolution / Microsoft / $whatever R to get MKL' or 'you have to recompile R for MKL'. Lastly, if it matters is up to the beholder. Because the optmization in the MKL appears to come from _many_ explicit code paths for many Intel cpu (micro-)architectures, the installed footprint is sizeable -- IIRC it was 2gb when I wrote the blog post above. My linear algebra use (at home) is light so I just kept OpenBLAS which is almost as fast, and proper free software with a smaller installation footprint. Your mileage, as they say, may vary. Dirk -- http://dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org __ R-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-devel
Re: [Rd] inappropriate warning in latticeExtra
On 14/06/2019 9:12 a.m., Richard M. Heiberger wrote:
This is still not repaired in
R version 3.6.0 Patched (2019-05-17 r76528)
library(latticeExtra)
a <- xyplot(1 ~ 1)
c(a,a)
Warning message:
In formals(fun) : argument is not a function
Can we have it in R-3.6.1 that Peter just announced?
That looks like a bug in the latticeExtra package, not in base R. In
particular, the latticeExtra:::c.trellis function appears to be trying
to take the formals of NULL, and that's why you get the warning.
Duncan Murdoch
Rich
On Mon, Apr 2, 2018 at 4:08 AM Deepayan Sarkar
wrote:
On Fri, Mar 23, 2018 at 7:58 AM, Richard M. Heiberger wrote:
The warning message in the last line of this email is incorrect.
This is behavior which Duncan Murdoch labeled a bug in
https://stat.ethz.ch/pipermail/r-help/2017-December/450494.html
Yes, sorry, this has been fixed in the r-forge sources for a while
now, but I haven't had the time to finish up some other fixes and push
an update to CRAN.
Hopefully over the summer break.
Regards,
-Deepayan
This is a fresh install of R-devel (2018-03-21 r74436)
R Under development (unstable) (2018-03-21 r74436) -- "Unsuffered Consequences"
Copyright (C) 2018 The R Foundation for Statistical Computing
Platform: x86_64-w64-mingw32/x64 (64-bit)
R is free software and comes with ABSOLUTELY NO WARRANTY.
You are welcome to redistribute it under certain conditions.
Type 'license()' or 'licence()' for distribution details.
Natural language support but running in an English locale
R is a collaborative project with many contributors.
Type 'contributors()' for more information and
'citation()' on how to cite R or R packages in publications.
Type 'demo()' for some demos, 'help()' for on-line help, or
'help.start()' for an HTML browser interface to help.
Type 'q()' to quit R.
library(latticeExtra)
Error in library(latticeExtra) :
there is no package called ‘latticeExtra’
install.packages("latticeExtra")
Warning in install.packages("latticeExtra") :
'lib = "C:/Program Files/R/R-devel/library"' is not writable
--- Please select a CRAN mirror for use in this session ---
also installing the dependency ‘RColorBrewer’
Warning: unable to access index for repository
http://www.stats.ox.ac.uk/pub/RWin/bin/windows/contrib/3.5:
cannot open URL
'http://www.stats.ox.ac.uk/pub/RWin/bin/windows/contrib/3.5/PACKAGES'
trying URL
'https://cran.wu.ac.at/bin/windows/contrib/3.5/RColorBrewer_1.1-2.zip'
Content type 'application/zip' length 55444 bytes (54 KB)
downloaded 54 KB
trying URL
'https://cran.wu.ac.at/bin/windows/contrib/3.5/latticeExtra_0.6-28.zip'
Content type 'application/zip' length 2191524 bytes (2.1 MB)
downloaded 2.1 MB
package ‘RColorBrewer’ successfully unpacked and MD5 sums checked
package ‘latticeExtra’ successfully unpacked and MD5 sums checked
The downloaded binary packages are in
C:\Users\rmh.DESKTOP-60G4CCO\AppData\Local\Temp\RtmpqA7Rqg\downloaded_packages
library(latticeExtra)
Loading required package: lattice
Loading required package: RColorBrewer
a <- xyplot(1 ~ 1)
c(a,a)
Warning message:
In formals(fun) : argument is not a function
__
R-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-devel
__
R-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-devel
__
R-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-devel
Re: [Rd] inappropriate warning in latticeExtra
Yes. You identified it a while ago and Deepayan wrote that he fixed it on
r-forge a year ago. It still isn't on cran.
On Fri, Jun 14, 2019 at 16:04 Duncan Murdoch
wrote:
> On 14/06/2019 9:12 a.m., Richard M. Heiberger wrote:
> > This is still not repaired in
> > R version 3.6.0 Patched (2019-05-17 r76528)
> >> library(latticeExtra)
> >> a <- xyplot(1 ~ 1)
> >> c(a,a)
> > Warning message:
> > In formals(fun) : argument is not a function
> >
> > Can we have it in R-3.6.1 that Peter just announced?
>
> That looks like a bug in the latticeExtra package, not in base R. In
> particular, the latticeExtra:::c.trellis function appears to be trying
> to take the formals of NULL, and that's why you get the warning.
>
> Duncan Murdoch
>
> >
> > Rich
> >
> > On Mon, Apr 2, 2018 at 4:08 AM Deepayan Sarkar
> > wrote:
> >>
> >> On Fri, Mar 23, 2018 at 7:58 AM, Richard M. Heiberger
> wrote:
> >>> The warning message in the last line of this email is incorrect.
> >>> This is behavior which Duncan Murdoch labeled a bug in
> >>> https://stat.ethz.ch/pipermail/r-help/2017-December/450494.html
> >>
> >> Yes, sorry, this has been fixed in the r-forge sources for a while
> >> now, but I haven't had the time to finish up some other fixes and push
> >> an update to CRAN.
> >>
> >> Hopefully over the summer break.
> >>
> >> Regards,
> >> -Deepayan
> >>
> >>
> >>> This is a fresh install of R-devel (2018-03-21 r74436)
> >>>
> >>>
> >>>
> >>>
> >>> R Under development (unstable) (2018-03-21 r74436) -- "Unsuffered
> Consequences"
> >>> Copyright (C) 2018 The R Foundation for Statistical Computing
> >>> Platform: x86_64-w64-mingw32/x64 (64-bit)
> >>>
> >>> R is free software and comes with ABSOLUTELY NO WARRANTY.
> >>> You are welcome to redistribute it under certain conditions.
> >>> Type 'license()' or 'licence()' for distribution details.
> >>>
> >>>Natural language support but running in an English locale
> >>>
> >>> R is a collaborative project with many contributors.
> >>> Type 'contributors()' for more information and
> >>> 'citation()' on how to cite R or R packages in publications.
> >>>
> >>> Type 'demo()' for some demos, 'help()' for on-line help, or
> >>> 'help.start()' for an HTML browser interface to help.
> >>> Type 'q()' to quit R.
> >>>
> library(latticeExtra)
> >>> Error in library(latticeExtra) :
> >>>there is no package called ‘latticeExtra’
> install.packages("latticeExtra")
> >>> Warning in install.packages("latticeExtra") :
> >>>'lib = "C:/Program Files/R/R-devel/library"' is not writable
> >>> --- Please select a CRAN mirror for use in this session ---
> >>> also installing the dependency ‘RColorBrewer’
> >>>
> >>> Warning: unable to access index for repository
> >>> http://www.stats.ox.ac.uk/pub/RWin/bin/windows/contrib/3.5:
> >>>cannot open URL
> >>> 'http://www.stats.ox.ac.uk/pub/RWin/bin/windows/contrib/3.5/PACKAGES'
> >>> trying URL '
> https://cran.wu.ac.at/bin/windows/contrib/3.5/RColorBrewer_1.1-2.zip'
> >>> Content type 'application/zip' length 55444 bytes (54 KB)
> >>> downloaded 54 KB
> >>>
> >>> trying URL '
> https://cran.wu.ac.at/bin/windows/contrib/3.5/latticeExtra_0.6-28.zip'
> >>> Content type 'application/zip' length 2191524 bytes (2.1 MB)
> >>> downloaded 2.1 MB
> >>>
> >>> package ‘RColorBrewer’ successfully unpacked and MD5 sums checked
> >>> package ‘latticeExtra’ successfully unpacked and MD5 sums checked
> >>>
> >>> The downloaded binary packages are in
> >>>
> C:\Users\rmh.DESKTOP-60G4CCO\AppData\Local\Temp\RtmpqA7Rqg\downloaded_packages
> library(latticeExtra)
> >>> Loading required package: lattice
> >>> Loading required package: RColorBrewer
> a <- xyplot(1 ~ 1)
> c(a,a)
> >>> Warning message:
> >>> In formals(fun) : argument is not a function
>
> >>>
> >>> __
> >>> R-devel@r-project.org mailing list
> >>> https://stat.ethz.ch/mailman/listinfo/r-devel
> >
> > __
> > R-devel@r-project.org mailing list
> > https://stat.ethz.ch/mailman/listinfo/r-devel
> >
>
>
[[alternative HTML version deleted]]
__
R-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-devel
Re: [Rd] Halfway through writing an "IDE" with support for R; Proof of concept, and request for suggestions.
On Fri, Jun 14, 2019 at 7:24 PM Iñaki Ucar wrote: > > There are many similar projects that are mature I'm not sure what projects you're referring to. If we create some constraints: (1) Internal systems consoles (*plural*). Rules out most things. Noting that many tools are designed to bypass the console. (2) Modern user interface. Rules out Vim and Emacs. (3) File system based rather than (IDE-dependent) project based. Rules out Eclipse and many other IDEs. (4) Multi-language focus. Rules out RStudio and many other IDEs. (5) Completely open source and completely free. Also rules out RStudio, which limites many features to it's enterprise edition. (6) Cross platform desktop application, not web based. (However, there is a need for web based tools). None of the tools that I've looked at satisfy these constraints. But if you know of some, I'd like to know... And I would consider contributing... [[alternative HTML version deleted]] __ R-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-devel
Re: [Rd] Halfway through writing an "IDE" with support for R; Proof of concept, and request for suggestions.
On Sat, 15 Jun 2019 at 01:24, Abby Spurdle wrote: > > None of the tools that I've looked at satisfy these constraints. > But if you know of some, I'd like to know... And I would consider > contributing... What about Atom, VS Code and the like? Or what about taking a project that meets most of the constraints and pushing to cover all of them, or even forking it and modifying the part you don't like? Iñaki __ R-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-devel
Re: [Rd] Halfway through writing an "IDE" with support for R; Proof of concept, and request for suggestions.
> What about Atom, VS Code and the like? Or what about taking a project > that meets most of the constraints and pushing to cover all of them, > or even forking it and modifying the part you don't like? I'm not prepared to endorse GitHub affiliated software. [[alternative HTML version deleted]] __ R-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-devel
