Would I miss any functionalities by using prompt.sh? I mean other than portability between OSs, does prompt.py provide other benefits? If there's nothing to lose in Unix by falling back to prompt.sh, I'd like to bring it into 7 and let the user choose. Maybe if the user is in Unix, there is no reason at all to use prompt.py?
I don't know about Windows, but what benefits would this python startup bring compared to native cmd.exe? Just wondering... On May 10, 2014 2:11 PM, "GRASS GIS" <[email protected]> wrote: > #2284: Keep pressing Ctrl+C in command line > > -------------------------+-------------------------------------------------- > Reporter: hcho | Owner: grass-dev@… > Type: enhancement | Status: new > Priority: normal | Milestone: 7.0.0 > Component: Startup | Version: svn-trunk > Keywords: | Platform: Linux > Cpu: x86-64 | > > -------------------------+-------------------------------------------------- > > Comment(by glynn): > > Replying to [ticket:2284 hcho]: > > > Can we fix this? Or can we opt to use the old init.sh, which I think is > gone now? > > There's no reason to revert to init.sh, but we could replace prompt.py > with the bash version (prompt.sh) from 6.x. The prompt script is only used > if you're using bash as your shell, so portability isn't an issue. > > You can disable the fancy prompt with "unset PROMPT_COMMAND". > > The error could probably be avoided by wrapping the entire prompt.py > script in a try/except block, but that wouldn't help with performance. > Ignoring the signal wouldn't work reliably, because you'd have to import > the signal module first, and any signal raised during that time would > still result in the KeyboardInterrupt exception. > > -- > Ticket URL: <http://trac.osgeo.org/grass/ticket/2284#comment:1> > GRASS GIS <http://grass.osgeo.org> > >
_______________________________________________ grass-dev mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/grass-dev
