Re: [ESS] change error-tolerance of ESS

2025-02-02 Thread Heinz Tuechler via ESS-help

Enrico Schumann wrote/hat geschrieben on/am 31.01.2025 07:47:

On Tue, 21 Jan 2025, Heinz Tuechler via ESS-help writes:


Dear All,

having a problem with XLConnect I wonder, if one can change the
error-tolerance of ESS.
My present problem is that executing library(XLConnect) in R 4.4.2 on
Windows leads to an immediate end of the R-session if done in emacs 26.3
with ESS 18.10.2 .
If executed with rterm.exe XLConnect is loaded without any error or
warning message.
After a call like
wb <- loadWorkbook("writeWorksheet.xlsx", create = TRUE)
the following messages are displayed:

2025-01-21T19:35:19.801Z main ERROR Unable to locate configured
LoggerContextFactory
org.apache.logging.log4j.simple.SimpleLoggerContextFactory
2025-01-21T19:35:19.801Z main ERROR Log4j2 could not find a logging
implementation. Please add log4j-core to the classpath. Using
SimpleLogger to log to the console...

but the call is executed without problems. Obviously rterm.exe tolerates
the error. Is there some setting for ESS to behave as rterm.exe?


You could try telling ESS to use a specific version of
rterm as the R process; put something like this in your
init file:

(setq-default inferior-R-program-name
  "C:/Program Files/R/R-4.4.2/bin/x64/Rterm.exe")

(Adjust the path as necessary, of course.)

kind regards
Enrico



Dear Enrico,

thank you for your suggestion. I have
(setq inferior-R-program-name "d:/rw442/bin/x64/rterm.exe") in my .emacs
. Now I tried your proposal, but did not note any difference.
In general I don't have problems with ess and R, it's just the command
"library(XLConnect)". That leads to an immediate quit of the R-session.

As mentioned, I can call library(XLConnect) in a batch execution, and
for now I do it that way, if I need XLConnect. In future I will probably
use openxlsx, which seemingly works for me.

best regards,

Heinz

__
ESS-help@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/ess-help


Re: [ESS] change error-tolerance of ESS

2025-01-30 Thread Enrico Schumann via ESS-help
On Tue, 21 Jan 2025, Heinz Tuechler via ESS-help writes:

> Dear All,
>
> having a problem with XLConnect I wonder, if one can change the
> error-tolerance of ESS.
> My present problem is that executing library(XLConnect) in R 4.4.2 on
> Windows leads to an immediate end of the R-session if done in emacs 26.3
> with ESS 18.10.2 .
> If executed with rterm.exe XLConnect is loaded without any error or
> warning message.
> After a call like
> wb <- loadWorkbook("writeWorksheet.xlsx", create = TRUE)
> the following messages are displayed:
>
> 2025-01-21T19:35:19.801Z main ERROR Unable to locate configured
> LoggerContextFactory
> org.apache.logging.log4j.simple.SimpleLoggerContextFactory
> 2025-01-21T19:35:19.801Z main ERROR Log4j2 could not find a logging
> implementation. Please add log4j-core to the classpath. Using
> SimpleLogger to log to the console...
>
> but the call is executed without problems. Obviously rterm.exe tolerates
> the error. Is there some setting for ESS to behave as rterm.exe?

You could try telling ESS to use a specific version of
rterm as the R process; put something like this in your
init file:

(setq-default inferior-R-program-name
  "C:/Program Files/R/R-4.4.2/bin/x64/Rterm.exe")

(Adjust the path as necessary, of course.)

kind regards
Enrico

> It would, of course, be desirable to eliminate the error, but I did not
> succeed. And seemingly XLConnect works as expected despite the error
> message.
>
> best regards,
>
> Heinz
>

-- 
Enrico Schumann
Lucerne, Switzerland
https://enricoschumann.net

__
ESS-help@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/ess-help


Re: [ESS] change error-tolerance of ESS

2025-01-22 Thread Heinz Tuechler via ESS-help

Martin Maechler wrote/hat geschrieben on/am 22.01.2025 12:00:

Dear Heinz,  your ESS 18.10.2  is quite old by now.

I'm not at all sure if the XLConnect problem is solved in current ESS or not.
I see you are using Windows ('rterm.exe'), so you may get a newer
ESS+emacs version from Vincent Goulet's page
(--> https://ess.r-project.org/  -> [Downloads] --> Windows   leads
you to   https://emacs-modified.gitlab.io/windows/
  that page says  ESS 24.01.1 (development version) which is much
newer than yours {and the Emacs version, probably, too}.

My guess would be that it even could be an  Emacs rather then ESS "bug" ..

I hope this helps a bit.
Martin



Dear Martin,

best thanks for your response. I did not mention it, but I tried also
ess-25.01.0 , but it made no difference. The R-session is finishes as if
I had issued q('no'). Therefore I don't know, how I could debug or trace
the error. I tried debug(library) and then library(XLConnect), but that
was not conclusive to me.
So it may have to do with emacs, but how could I find it out?
For the moment I can live without calling XLConnect from emacs/ESS.
If you know of some material describing, how to analyse such a problem,
please let me know.

best regards,

Heinz


On Tue, Jan 21, 2025 at 8:50 PM Heinz Tuechler via ESS-help
 wrote:


Dear All,

having a problem with XLConnect I wonder, if one can change the
error-tolerance of ESS.
My present problem is that executing library(XLConnect) in R 4.4.2 on
Windows leads to an immediate end of the R-session if done in emacs 26.3
with ESS 18.10.2 .
If executed with rterm.exe XLConnect is loaded without any error or
warning message.
After a call like
wb <- loadWorkbook("writeWorksheet.xlsx", create = TRUE)
the following messages are displayed:

2025-01-21T19:35:19.801Z main ERROR Unable to locate configured
LoggerContextFactory
org.apache.logging.log4j.simple.SimpleLoggerContextFactory
2025-01-21T19:35:19.801Z main ERROR Log4j2 could not find a logging
implementation. Please add log4j-core to the classpath. Using
SimpleLogger to log to the console...

but the call is executed without problems. Obviously rterm.exe tolerates
the error. Is there some setting for ESS to behave as rterm.exe?

It would, of course, be desirable to eliminate the error, but I did not
succeed. And seemingly XLConnect works as expected despite the error
message.

best regards,

Heinz

__
ESS-help@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/ess-help






__
ESS-help@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/ess-help


Re: [ESS] change error-tolerance of ESS

2025-01-22 Thread Martin Maechler via ESS-help
Dear Heinz,  your ESS 18.10.2  is quite old by now.

I'm not at all sure if the XLConnect problem is solved in current ESS or not.
I see you are using Windows ('rterm.exe'), so you may get a newer
ESS+emacs version from Vincent Goulet's page
(--> https://ess.r-project.org/  -> [Downloads] --> Windows   leads
you to   https://emacs-modified.gitlab.io/windows/
  that page says  ESS 24.01.1 (development version) which is much
newer than yours {and the Emacs version, probably, too}.

My guess would be that it even could be an  Emacs rather then ESS "bug" ..

I hope this helps a bit.
Martin

On Tue, Jan 21, 2025 at 8:50 PM Heinz Tuechler via ESS-help
 wrote:
>
> Dear All,
>
> having a problem with XLConnect I wonder, if one can change the
> error-tolerance of ESS.
> My present problem is that executing library(XLConnect) in R 4.4.2 on
> Windows leads to an immediate end of the R-session if done in emacs 26.3
> with ESS 18.10.2 .
> If executed with rterm.exe XLConnect is loaded without any error or
> warning message.
> After a call like
> wb <- loadWorkbook("writeWorksheet.xlsx", create = TRUE)
> the following messages are displayed:
>
> 2025-01-21T19:35:19.801Z main ERROR Unable to locate configured
> LoggerContextFactory
> org.apache.logging.log4j.simple.SimpleLoggerContextFactory
> 2025-01-21T19:35:19.801Z main ERROR Log4j2 could not find a logging
> implementation. Please add log4j-core to the classpath. Using
> SimpleLogger to log to the console...
>
> but the call is executed without problems. Obviously rterm.exe tolerates
> the error. Is there some setting for ESS to behave as rterm.exe?
>
> It would, of course, be desirable to eliminate the error, but I did not
> succeed. And seemingly XLConnect works as expected despite the error
> message.
>
> best regards,
>
> Heinz
>
> __
> ESS-help@r-project.org mailing list
> https://stat.ethz.ch/mailman/listinfo/ess-help



-- 
Martinhttp://stat.ethz.ch/~maechler
Seminar für Statistik, ETH Zürich HG G 14.2   Rämistrasse 101
CH-8092 Zurich, SWITZERLAND   ☎ +41 44 632 3408<><

__
ESS-help@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/ess-help