Re: Backspace across wrapped line

[Jakob Eriksson]

Wow that thing looks like a good match. Small, self contained
and under a liberal license. (Simplified BSD)


On 05/03/16 18:35, Michel Pelletier wrote:
> There's also the option of using an optional third party library like
> https://github.com/antirez/linenoise
> 
> On Sat, Mar 5, 2016 at 9:02 AM, Jakob Eriksson 
> wrote:
> 
>> A shotgun approach would be to create a screen editor of sorts,
>> with a repl in it. That is probably overkill.
>>
>>
>>
>> On 05/03/16 16:18, Alexander Burger wrote:
>>> Hi all,
>>>
>>> since early versions of PicoLisp I have a problem with the behavior of
>>> terminals.
>>>
>>> It concerns the REPL line editor in debug mode, the way how a backspace
>>> behaves across a wrapped line.
>>>
>>>
>>> To move backwards in the line, the line editor sends a Ctrl-H to the
>>> terminal. This happens not only explicitly (e.g. when the user types 'h'
>>> in vi-mode), but also implicitly when the line is refreshed.
>>>
>>> The problem arises when the line gets longer than the number of columns
-- 
UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe

Re: Backspace across wrapped line

[Michel Pelletier]

There's also the option of using an optional third party library like
https://github.com/antirez/linenoise

On Sat, Mar 5, 2016 at 9:02 AM, Jakob Eriksson 
wrote:

> A shotgun approach would be to create a screen editor of sorts,
> with a repl in it. That is probably overkill.
>
>
>
> On 05/03/16 16:18, Alexander Burger wrote:
> > Hi all,
> >
> > since early versions of PicoLisp I have a problem with the behavior of
> > terminals.
> >
> > It concerns the REPL line editor in debug mode, the way how a backspace
> > behaves across a wrapped line.
> >
> >
> > To move backwards in the line, the line editor sends a Ctrl-H to the
> > terminal. This happens not only explicitly (e.g. when the user types 'h'
> > in vi-mode), but also implicitly when the line is refreshed.
> >
> > The problem arises when the line gets longer than the number of columns

Re: Backspace across wrapped line

[Jakob Eriksson]

A shotgun approach would be to create a screen editor of sorts,
with a repl in it. That is probably overkill.



On 05/03/16 16:18, Alexander Burger wrote:
> Hi all,
> 
> since early versions of PicoLisp I have a problem with the behavior of
> terminals.
> 
> It concerns the REPL line editor in debug mode, the way how a backspace
> behaves across a wrapped line.
> 
> 
> To move backwards in the line, the line editor sends a Ctrl-H to the
> terminal. This happens not only explicitly (e.g. when the user types 'h'
> in vi-mode), but also implicitly when the line is refreshed.
> 
> The problem arises when the line gets longer than the number of columns.
> Terminals show different behavior here: Some move back to the last
> column of the previous line (this is OK), and some stay in the first
> column of the next line (this results in a mess).
> 
> XTerm is OK, but the linux consoles (tty1 ... tty7) are not. Gnome seems
> to have a config option for that.
> 
> 
> It would be nice if we could control it directly frow within the line
> editor. I tried various 'stty' and tcsetattr(termios) parameters, but
> without avail.
> 
> Does anybody have an idea?
> 
> ♪♫ Alex
> 
-- 
UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe

Backspace across wrapped line

[Alexander Burger]

Hi all,

since early versions of PicoLisp I have a problem with the behavior of
terminals.

It concerns the REPL line editor in debug mode, the way how a backspace
behaves across a wrapped line.


To move backwards in the line, the line editor sends a Ctrl-H to the
terminal. This happens not only explicitly (e.g. when the user types 'h'
in vi-mode), but also implicitly when the line is refreshed.

The problem arises when the line gets longer than the number of columns.
Terminals show different behavior here: Some move back to the last
column of the previous line (this is OK), and some stay in the first
column of the next line (this results in a mess).

XTerm is OK, but the linux consoles (tty1 ... tty7) are not. Gnome seems
to have a config option for that.


It would be nice if we could control it directly frow within the line
editor. I tried various 'stty' and tcsetattr(termios) parameters, but
without avail.

Does anybody have an idea?

♪♫ Alex
-- 
UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe