[ESS] change error-tolerance of ESS

[Heinz Tuechler]

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
> <ess-help using r-project.org> 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 using r-project.org mailing list
>> https://stat.ethz.ch/mailman/listinfo/ess-help
>
>
>