<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">Hi Vaclav,<div class=""><br class=""></div><div class="">Thanks for this. My 2c is that the terminal should be made as optional because it can definitely be confusing and intimidating/off-putting for new users. <font color="#000000" class=""><span style="caret-color: rgb(0, 0, 0);" class="">Apologies if I’ve confused some of the options but here are my thoughts regarding the start-up options.</span></font></div><div class=""><br class=""></div><div class="">Unfortunately (in terms of complexity) option 5 would my preference. I like what it inherits from option 4, in that “grass —text” would always start with a terminal and just “grass” will *always* opens the full desktop application/GUI.</div><div class=""><br class=""></div><div class="">However, once in the GUI, ideally you would be able to launch a terminal session from a menu option, e.g. a bit like Rstudio or VScode. This is obviously how you want to launch an R or Jupyter session, and it was be unfortunate to have to exit GRASS and restart a session with a terminal just to do this. Also, what happens when the GRASS GUI crashes and you are not running a terminal? One of the aspects that I really like about GRASS is that even if any particular component of the application, like the GUI crashes, the session continues and modules/scripts keep on running, so everything is usually recoverable.</div><div class=""><br class=""></div><div class=""><font color="#000000" class=""><span style="caret-color: rgb(0, 0, 0);" class="">If the implementation of option (5) is problematic, then I guess mixing the startup options by </span></font><span style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0);" class=""> </span><font color="#000000" class=""><span style="caret-color: rgb(0, 0, 0);" class="">“grass —gui —shell” to open both the GUI and a terminal (like currently) would be possible although it is a bit cumbersome </span></font><span style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0);" class="">for all of the people who routinely punch GRASS commands into the terminal etc.</span></div><div class=""><span style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0);" class=""><br class=""></span></div><div class="">Steve</div><div class=""><div class=""><br class=""><div><br class=""><blockquote type="cite" class=""><div class="">On Sep 5, 2020, at 9:05 PM, Vaclav Petras <<a href="mailto:wenzeslaus@gmail.com" class="">wenzeslaus@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div style="caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none;" class="">4. Make the shell start only in the text mode (grass --text) or with a new additional option (--shell), i.e., you get it, only when you actually ask for it. In other words, with --text, GRASS GIS would behave more like R or Octave, without that (with --gui), it would behave more like QGIS or any other GUI application. (This includes the no terminal from desktop launchers from option 2.)<br class=""></div><div style="caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none;" class=""></div><br class="Apple-interchange-newline"></div></blockquote></div><br class=""></div></div></body></html>