Replies: 5 comments 1 reply
-
On Sun, Feb 23, 2025 at 10:21 AM mcctuxic ***@***.***> wrote:
Hi Travis,
would it be possible without too much hassle to make the line editor
accessible/useable for own programs...for example
as an replacement or additon to ACCEPT?
Cheers!
If the line editor has been enabled it is usable from within ACCEPT by
default. (In testing this I found a bug in the line editor, though, where
if there is text in the current line already and one attempts to scroll to
history that goes beyond the end of the current line and you are at the
bottom of the terminal it bumps the text up an extra line ─ I had honestly
never tested the line editor with extra text on the current line *and*
scrolling to longer history items before.)
Travis
… Message ID: ***@***.***>
|
Beta Was this translation helpful? Give feedback.
1 reply
-
On Sun, Feb 23, 2025 at 10:37 AM Travis Bemann ***@***.***> wrote:
On Sun, Feb 23, 2025 at 10:21 AM mcctuxic ***@***.***>
wrote:
> Hi Travis,
>
> would it be possible without too much hassle to make the line editor
> accessible/useable for own programs...for example
> as an replacement or additon to ACCEPT?
>
> Cheers!
>
>
If the line editor has been enabled it is usable from within ACCEPT by
default. (In testing this I found a bug in the line editor, though, where
if there is text in the current line already and one attempts to scroll to
history that goes beyond the end of the current line and you are at the
bottom of the terminal it bumps the text up an extra line ─ I had honestly
never tested the line editor with extra text on the current line *and*
scrolling to longer history items before.)
And now I am having trouble reproducing the bug I thought I just found...
… Message ID: ***@***.***>
>
|
Beta Was this translation helpful? Give feedback.
0 replies
-
On 02/23 08:41, tabemann wrote:
On Sun, Feb 23, 2025 at 10:37 AM Travis Bemann ***@***.***> wrote:
> On Sun, Feb 23, 2025 at 10:21 AM mcctuxic ***@***.***>
> wrote:
>
>> Hi Travis,
>>
>> would it be possible without too much hassle to make the line editor
>> accessible/useable for own programs...for example
>> as an replacement or additon to ACCEPT?
>>
>> Cheers!
>>
>>
> If the line editor has been enabled it is usable from within ACCEPT by
> default. (In testing this I found a bug in the line editor, though, where
> if there is text in the current line already and one attempts to scroll to
> history that goes beyond the end of the current line and you are at the
> bottom of the terminal it bumps the text up an extra line ─ I had honestly
> never tested the line editor with extra text on the current line *and*
> scrolling to longer history items before.)
>
And now I am having trouble reproducing the bug I thought I just found...
> Message ID: ***@***.***>
>>
>
...may be a special character in the buffer beforehand ? Just a wild
guess...
|
Beta Was this translation helpful? Give feedback.
0 replies
-
On Sun, Feb 23, 2025 at 10:53 AM mcctuxic ***@***.***> wrote:
Hi Travis,
Currently I am (trying to) program a busy beaver turing machine and am at
that point when one needs to input the different
state changes to perform via ACCEPT....and it is very good to have the
line editor already available so I don't need to care
about a way to correct typos. GREAT! :) As always: Thanks a lot! :)
Cheers!
You're welcome!
Note that the line editor under ACCEPT, like at the REPL, implements input
history and a simple paste buffer that can be used across multiple calls to
ACCEPT. The only gotcha is that it does not have any means of separating
history and the paste buffer from the REPL from that under ACCEPT, so
ACCEPT has access to the REPL history and paste buffer, and vice versa. (I
don't see this as a problem, because if this were changed then it would be
desired to also have a way to separate such out between calls to ACCEPT in
different contexts, something I do not want to implement.)
Travis
… Message ID: <tabemann/zeptoforth/repo-discussions/192/comments/12292879@
github.com>
|
Beta Was this translation helpful? Give feedback.
0 replies
-
On Sun, Feb 23, 2025 at 11:12 AM mcctuxic ***@***.***> wrote:
On 02/23 08:41, tabemann wrote:
> On Sun, Feb 23, 2025 at 10:37 AM Travis Bemann ***@***.***> wrote:
>
> > On Sun, Feb 23, 2025 at 10:21 AM mcctuxic ***@***.***>
> > wrote:
> >
> >> Hi Travis,
> >>
> >> would it be possible without too much hassle to make the line editor
> >> accessible/useable for own programs...for example
> >> as an replacement or additon to ACCEPT?
> >>
> >> Cheers!
> >>
> >>
> > If the line editor has been enabled it is usable from within ACCEPT by
> > default. (In testing this I found a bug in the line editor, though,
where
> > if there is text in the current line already and one attempts to
scroll to
> > history that goes beyond the end of the current line and you are at the
> > bottom of the terminal it bumps the text up an extra line ─ I had
honestly
> > never tested the line editor with extra text on the current line *and*
> > scrolling to longer history items before.)
> >
>
>
> And now I am having trouble reproducing the bug I thought I just found...
>
> > Message ID: ***@***.***>
> >>
> >
...may be a special character in the buffer beforehand ? Just a wild
guess...
I am stumped as to what happened. I thought for a moment that it might
only occur on the first call to ACCEPT after ENABLE-LINE so I tried that.
No cigar. I also thought that it might only occur when the cursor is not at
the bottom row of the terminal, so I tried that as well. Also no cigar. I
also tried both of these use cases together. The issue was still not
elicited. Hmmph.
Travis
… Message ID: <tabemann/zeptoforth/repo-discussions/192/comments/12292979@
github.com>
|
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi Travis,
would it be possible without too much hassle to make the line editor accessible/useable for own programs...for example
as an replacement or additon to ACCEPT?
Cheers!
Beta Was this translation helpful? Give feedback.
All reactions