On 10/27/17 1:37 AM, Jan Beulich wrote:
On 26.10.17 at 23:05, wrote:
>> On 10/18/17 4:50 AM, Jan Beulich wrote:
>> On 17.10.17 at 23:41, wrote:
From: David Esler
In 9180f5365524 a change was made to the send_chr function to take in
C-strings and print out a character
>>> On 26.10.17 at 23:05, wrote:
> On 10/18/17 4:50 AM, Jan Beulich wrote:
> On 17.10.17 at 23:41, wrote:
>>> From: David Esler
>>>
>>> In 9180f5365524 a change was made to the send_chr function to take in
>>> C-strings and print out a character at a time until a NULL was
>>> encountered. Ho
On 10/18/17 4:50 AM, Jan Beulich wrote:
On 17.10.17 at 23:41, wrote:
>> From: David Esler
>>
>> In 9180f5365524 a change was made to the send_chr function to take in
>> C-strings and print out a character at a time until a NULL was
>> encountered. However there is no code to increment the cu
On 10/18/17 4:50 AM, Jan Beulich wrote:
On 17.10.17 at 23:41, wrote:
>> From: David Esler
>>
>> In 9180f5365524 a change was made to the send_chr function to take in
>> C-strings and print out a character at a time until a NULL was
>> encountered. However there is no code to increment the cu
On Tue, Oct 17, 2017 at 04:41:37PM -0500, Doug Goldstein wrote:
> From: David Esler
>
> In 9180f5365524 a change was made to the send_chr function to take in
> C-strings and print out a character at a time until a NULL was
> encountered. However there is no code to increment the current character
>>> On 17.10.17 at 23:41, wrote:
> From: David Esler
>
> In 9180f5365524 a change was made to the send_chr function to take in
> C-strings and print out a character at a time until a NULL was
> encountered. However there is no code to increment the current character
> position resulting in an en
From: David Esler
In 9180f5365524 a change was made to the send_chr function to take in
C-strings and print out a character at a time until a NULL was
encountered. However there is no code to increment the current character
position resulting in an endless loop of the first character. This adds
a
