Opened 4 years ago
Closed 4 years ago
#3849 closed enhancement (fixed)
Do we need to clear the screen when entering/exiting GRASS?
|Reported by:||pmav99||Owned by:|
Clearing the screen can often be problematic. More specifically, depending on the SHELL/terminal emulator you use you might lose the ability to scroll back which can be very annoying. Are there any objections in removing it?
Change History (5)
comment:1 by , 4 years ago
comment:2 by , 4 years ago
comment:3 by , 4 years ago
Can somebody second the removal from user perspective? Is terminal clearing important to you in some way or will you welcome not clearing?
comment:4 by , 4 years ago
Like Panos, I also feel that clearing the screen is rather unhelpful. Thus, I would vote for removing it as well.
comment:5 by , 4 years ago
|Status:||new → closed|
PR12 has been merged, closing.
Note: See TracTickets for help on using tickets.
No objections from me. It does not seem that other interpreters or environments are doing it (Python, R, Octave, Bash) even if they show a significant startup message by default (R, Octave). Although this ticket is about interactive use from command line, same is also needed to solve most if not all of #2639 which is about behaving as expected when stdin is provided (
grass --tmp-location XY --text < script.sh). I continue with a modification of my comment from https://github.com/OSGeo/grass/pull/4:
I see at least 3 different things happening:
Here we focus on the clearing only.
In #2639 I compared behavior to Python and R in case when standard input is provided. As for interactive use, Python (
python), R (
R), and Octave (
octave --no-gui) display banners (of different lengths), but none of them clears the terminal (at the beginning or the end). That suggests that
grassshould not do that either.
Copy-pasted command line when R, Octave, Python, and Bash are started and ended follows (newlines preserved, no clearing involved):