Message-ID: <23964.14723.714441.966553@stat.math.ethz.ch>
Date: 2019-10-08T07:23:47Z
From: Martin Maechler
Subject: Strange "no-echo" in place of "slave"
In-Reply-To: <BE5D03DD-25FD-47C7-B92A-29CE99F2BD7A@gmail.com>
>>>>> peter dalgaard
>>>>> on Sun, 6 Oct 2019 16:13:58 +0200 writes:
> The first of Suharno's examples can be viewed that way,
> because R under ESS is not a "slave" in the technical
> sense, just a situation where you do not want keyboard
> input to be echoed. "Non-echoing" might have been better
> language though.
> The 2nd example really is of the master/slave variety,
> and to my knowledge nothing to do with echoing, so looks
> like a search-and-replace oversight. Presumably, "worker
> thread" (or thereabouts) would be a better replacement.
> -pd
Yes indeed, thank you, Suharto, Gabe and Peter.
I've updated the 2nd example (using "worker")
Martin
>> On 6 Oct 2019, at 14:00 , Gabriel Becker
>> <gabembecker at gmail.com> wrote:
>>
>> As far as I know, not being involved with the effort at
>> all, they are removing the term 'slave' and replacing it
>> with 'no-echo' which is intended to be fully synonmyous
>> with the meaning of the old 'slave' term.
>>
>> ~G
>>
>> On Sun, Oct 6, 2019 at 10:56 PM suharto_anggono--- via
>> R-devel < r-devel at r-project.org> wrote:
>>
>>> SVN revision replaces "slave" with "no-echo" in R devel.
>>>
>>>
>>> In each of the following, "no-echo" is rather strange to
>>> me.
>>>
>>> - src/gnuwin32/README.Rterm 3) As a no-echo process for
>>> ESS mode in NTEmacs with flag --ess.
>>>
>>> - src/library/grDevices/src/qdCocoa.m /* the no-echo
>>> thread work until this is NO */
>>>