I apologise: when I said in an earlier post that i had fixed the problem, that was untrue. I was confusing your bug with another.
Your bug has not yet been addressed or fixed and the bug report is still open.
console control codes in 4.1FE
- tonyw
- AmigaOS Core Developer
- Posts: 1479
- Joined: Wed Mar 09, 2011 1:36 pm
- Location: Sydney, Australia
Re: console control codes in 4.1FE
cheers
tony
tony
Re: console control codes in 4.1FE
@tonyw
When I'm in the early stages of trying to fix lots of errors and warnings, I frequently want to clear the History and the window so that it's easier to get to the top of the errors/warnings in the next compile attempt. As a matter of user convenience, could you add a menu item that clears both the History and the window?
When I'm in the early stages of trying to fix lots of errors and warnings, I frequently want to clear the History and the window so that it's easier to get to the top of the errors/warnings in the next compile attempt. As a matter of user convenience, could you add a menu item that clears both the History and the window?
AmigaOne X1000 with 2GB memory - OS4.1 FE
- broadblues
- AmigaOS Core Developer
- Posts: 600
- Joined: Sat Jun 18, 2011 2:40 am
- Location: Portsmouth, UK
- Contact:
Re: console control codes in 4.1FE
xenic wrote:@tonyw
When I'm in the early stages of trying to fix lots of errors and warnings, I frequently want to clear the History and the window so that it's easier to get to the top of the errors/warnings in the next compile attempt. As a matter of user convenience, could you add a menu item that clears both the History and the window?
try
alias ClearHistory echo NOLINE "*Ec"
Re: console control codes in 4.1FE
Thanks. That's much simpler than typing CLS and then Right-Amiga-Z. I'm adding that alias to my shell-startup as soon as I complete this postbroadblues wrote:
try
alias ClearHistory echo NOLINE "*Ec"
AmigaOne X1000 with 2GB memory - OS4.1 FE
- tonyw
- AmigaOS Core Developer
- Posts: 1479
- Joined: Wed Mar 09, 2011 1:36 pm
- Location: Sydney, Australia
Re: console control codes in 4.1FE
Lazi's original bug has now been fixed. Still checking to make sure that I haven't screwed up something else.
Raziel's report is not a bug at all. When you think of it, all the rows at the top of the screen still have the original background colour in the parts that were not over-written. But when the display starts scrolling, new rows are created at the bottom of the screen, and those rows are created with the current settings, specifically, the new background colour.
So that is why the new rows show the new background colour for their full width.
Raziel's report is not a bug at all. When you think of it, all the rows at the top of the screen still have the original background colour in the parts that were not over-written. But when the display starts scrolling, new rows are created at the bottom of the screen, and those rows are created with the current settings, specifically, the new background colour.
So that is why the new rows show the new background colour for their full width.
cheers
tony
tony
Re: console control codes in 4.1FE
That sounds logical, yestonyw wrote:Lazi's original bug has now been fixed. Still checking to make sure that I haven't screwed up something else.
Raziel's report is not a bug at all. When you think of it, all the rows at the top of the screen still have the original background colour in the parts that were not over-written. But when the display starts scrolling, new rows are created at the bottom of the screen, and those rows are created with the current settings, specifically, the new background colour.
So that is why the new rows show the new background colour for their full width.
But it also means i cannot give automatically created lines that will scroll the shell window a different color without having all new lines be drawn in this color...sigh, back to normal background then
Plus the original bug item
Code: Select all
echo "*E[5;8Hoo"
Code: Select all
echo "*E[26;8Hoo"
Code: Select all
echo "*E[42m"
imho i think there should at least be a check for drawn characters and only apply the background change to them otherwise to the full line?
People are dying.
Entire ecosystems are collapsing.
We are in the beginning of a mass extinction.
And all you can talk about is money and fairytales of eternal economic growth.
How dare you!
– Greta Thunberg
Entire ecosystems are collapsing.
We are in the beginning of a mass extinction.
And all you can talk about is money and fairytales of eternal economic growth.
How dare you!
– Greta Thunberg
- tonyw
- AmigaOS Core Developer
- Posts: 1479
- Joined: Wed Mar 09, 2011 1:36 pm
- Location: Sydney, Australia
Re: console control codes in 4.1FE
If you change the foreground or background colours, no existing text will be touched. New text will be drawn with the new colours, either over old text or on new lines, but old text will not change unless you write over it.
cheers
tony
tony
Re: console control codes in 4.1FE
Just found that CTRL+J does not work in the new shell!
Is this feature dropped by intentionally?
I want it back!
Want it NOW
Is this feature dropped by intentionally?
I want it back!
Want it NOW
- nbache
- Beta Tester
- Posts: 1716
- Joined: Mon Dec 20, 2010 7:25 pm
- Location: Copenhagen, Denmark
- Contact:
Re: console control codes in 4.1FE
What do you mean by "does not work"? What do you expect it to do?lazi wrote:Just found that CTRL+J does not work
What new shell? Please give version numbers of:in the new shell!
- console.device.kmod
- con-handler.kmod
- shell.kmod
- all from your Kickstart dir.
On my system (on a clean public 4.1. Final Edition) I can press Ctrl-J fine, it does the same as when I press Enter or Return.
BTW, whatever it is you're trying to describe, it has nothing to do with console control codes, so you should probably have started a new topic instead.
Best regards,
Niels
Re: console control codes in 4.1FE
That bug was reported back in September 2017 in the "AmigaOS Shell issue (FE Update 1)" topic and Tony said he fixed it. As a beta tester, it might work correctly for you. "Control J" is supposed to let you enter multiple commands and execute them all at once. It's sort of like entering multiple commands with "run" by adding a + at the end of each line like:nbache wrote:On my system (on a clean public 4.1. Final Edition) I can press Ctrl-J fine, it does the same as when I press Enter or Return.
BTW, whatever it is you're trying to describe, it has nothing to do with console control codes, so you should probably have started a new topic instead.
run echo hello +
list ram: +
echo done
With the current publicly available shell, "Control J" works like "Control M" instead.
AmigaOne X1000 with 2GB memory - OS4.1 FE