Bug in shell/cli/console

A forum for general AmigaOS 4.x support questions that are not platform-specific
Raziel

Bug in shell/cli/console

Post by Raziel »

1) Get lha from here
2) Unpack
3) Type "lha ?" in a shell not high enough to trigger the "Press space to continue"
4) Click on shell window's close gadget

It printed unwanted text after it got to the end.
21.System:> ;0;0;0;0;0;0;0|

There is even an invisible "1" hidden there. If i delete the whole line and repeat the command from above i get an error telling me:
1lha: Unknown command

I don't know if this a bug in the console or lha acting up because it got an unwanted exit.

I'll try to find another program that does this.
Roland
Posts: 873
Joined: Tue May 02, 2017 8:23 am

Re: Bug in shell/cli/console

Post by Roland »

Raziel wrote: Tue Apr 20, 2021 10:19 am 1) Get lha from here
2) Unpack
3) Type "lha ?" in a shell not high enough to trigger the "Press space to continue"
4) Click on shell window's close gadget

It printed unwanted text after it got to the end.
21.System:> ;0;0;0;0;0;0;0|
Confirmed, the same behaviour here... (AmigaOS FE 4.1u2, X5000).
- Roland -
Raziel

Re: Bug in shell/cli/console

Post by Raziel »

Thank you for confirming

This could be (but not has to be) related to this bug
User avatar
nbache
Beta Tester
Beta Tester
Posts: 1744
Joined: Mon Dec 20, 2010 7:25 pm
Location: Copenhagen, Denmark
Contact:

Re: Bug in shell/cli/console

Post by nbache »

Both observations (the second one being the "invisible" 1) confirmed also in latest beta.

Yes, I think it is at least partly related, but I'll let Tony comment.

Best regards,

Niels
Raziel

Re: Bug in shell/cli/console

Post by Raziel »

Thank you Niels
Raziel

Re: Bug in shell/cli/console

Post by Raziel »

Ping?
xenic
Posts: 1185
Joined: Sun Jun 19, 2011 1:06 am

Re: Bug in shell/cli/console

Post by xenic »

I tested your procedure using the "more" command to read a text file and did not see the extra characters that appear with "lha". However, when I display one of the C: command documentation files with the more command I do see some extra characters ( ^L ) where there are formfeed control codes in the text. My test suggests that the extra characters you get with lha may be an lha issue instead of a console issue. A comment from Tony would be helpful.
AmigaOne X1000 with 2GB memory - OS4.1 FE
Raziel

Re: Bug in shell/cli/console

Post by Raziel »

@xenic

What c commands were giving you problems?
And what were your command to make them appear flawed?

I plan to do some more testing once I'm back home.

Thank you
xenic
Posts: 1185
Joined: Sun Jun 19, 2011 1:06 am

Re: Bug in shell/cli/console

Post by xenic »

Raziel wrote: Sun May 09, 2021 12:12 pm @xenic

What c commands were giving you problems?
And what were your command to make them appear flawed?

I plan to do some more testing once I'm back home.
As far as I can tell all the SYS:Documentation/C/ command docs have a formfeed near the beginning and at the end of the doc. The ^L characters appear whereever the formfeeds (HEX 0C) are located.
Example command:
more SYS:Documentation/C/Assign.doc
AmigaOne X1000 with 2GB memory - OS4.1 FE
Raziel

Re: Bug in shell/cli/console

Post by Raziel »

@xenic

Ok, so it could even be a bug in more then.

I'd like to try the commands in a vanilla shell from the 4.1 boot cd...if it doesnt break there, it can be considered a regression in today's shell at least.

But I'm not near my gear, so if anyone wants to do that quick test...
Post Reply