Forum

Notifications
Clear all

Suggested Feature

0 Posts
3 Users
0 Reactions
219 Views
(@deriqat)
Active Member
Joined: 55 years ago
Posts: 9
Topic starter  

One thing that would be nice is a simple means to clear the current screen. For example, right-click on the screen and select "Clear" from the context menu. Maybe also have a toolbar button to do it.

This feature is useful when one is using Absolute Telnet as a simple terminal window. It's nice to be able to erase the screen between "sessions."


   
ReplyQuote
(@bpence)
Member Admin
Joined: 1 year ago
Posts: 1375
 

I'll consider that.


   
ReplyQuote
(@sscecina)
Active Member
Joined: 25 years ago
Posts: 7
 

I'd have to "second" this request. A simple way to clear the history/scroll buffer is all that's necessary. I don't know how many times a day I need to review the output of a long command and have trouble finding the beginning of the output. Being able to clear the buffer before running the command would be fantastic.


   
ReplyQuote
(@bpence)
Member Admin
Joined: 1 year ago
Posts: 1375
 

I've had the same issue, concerning long output. What I do is just hit enter a bunch of times to create a visual break between the output of the last command and the next command. It stands out visually, then, when you scroll back up.

Alternatively, you can use the unix 'clear' command or the AbsoluteTelnet 'Options->Reset Terminal' to clear the screen.

There's even the possibility to use the 'Options->Find' command to find some piece of text that's unique in your prompt string. For example, my prompt string includes my username and hostname like this: 'bpence@gateway' as well as the current directory. If I use the Options->find on the text 'bpence@gateway', not only will it highlight all of my prompts for me in bright blinking red, but now I can use the find previous and find next (alt-pgup and alt-pgdn) to quickly page to the beginning of each command I entered, regardless of how many there were or how big the output was.

Do any of these options fit your needs?

Brian


   
ReplyQuote
(@sscecina)
Active Member
Joined: 25 years ago
Posts: 7
 

Actually, I've used them all, many times. I find myself using the "hit enter a bunch of times" the most.

The problem with "clear" or "reset terminal" is that it only clears the contents of the window, not the history (which, btw, "clear" should NOT do 🙂 so, since the cursor is at the top of the window, when you start your command your output is right up against the history...

Personally I think "reset terminal" SHOULD wipeout the history... I almost suggested that it be the method of clearing the history when I originally posted.

- Scott


   
ReplyQuote
(@bpence)
Member Admin
Joined: 1 year ago
Posts: 1375
 

I don't believe there is anything formally defined as to what a terminal should or should not do in terms of the history buffer. Real terminals, you see, don't have a history buffer at all and the documentation describes only what happens on the visible screen.

Windows terminal apps have the added benefit of being able to display the terminal history, but the method by which it is maintained is largely defined by the implementor of the program.

I don't believe clear OR reset should clear the history. It's never been defined that way in the past and I'd almost assuredly upset too many users if this were to change.

If I do anything, it would be to add an option that would clear and reset the history buffer and current screen. I'll put this on my 'to consider' list.

Brian


   
ReplyQuote
Share: