Hi,
I've noticed that the my current check out from the VCS now binds
CTRL-C to quitting the shell.
Is there anyway to disable this? It's highly frustrating when I type
CTRL-C to end a process, but sometimes the process ends before I push
the keys - leading to an inadvertent session end and me having to set
up my work space again.
CTRL-d is the usual key combo for a shell logout, which works just fine.
Cheers,
Joel
I've also noticed that I use CTRL-C to abort a command line and give
me a clean one (yet still leave what I typed previously on the
screen).
For a system that has it's roots in the command line, I feel this
change has had a significant impact on usability.
On Tue, Nov 3, 2009 at 2:25 PM, Joel Pitt <joel.pitt@gmail.com> wrote:
Hi,
I've noticed that the my current check out from the VCS now binds
CTRL-C to quitting the shell.Is there anyway to disable this? It's highly frustrating when I type
CTRL-C to end a process, but sometimes the process ends before I push
the keys - leading to an inadvertent session end and me having to set
up my work space again.CTRL-d is the usual key combo for a shell logout, which works just fine.
Cheers,
Joel
(Apologies for sorting your pots 
On Tue, Nov 3, 2009 at 2:25 PM, Joel Pitt <joel.pitt@gmail.com> wrote:
> Hi,
>
> I've noticed that the my current check out from the VCS now binds
> CTRL-C to quitting the shell.
>
> Is there anyway to disable this? It's highly frustrating when I type
> CTRL-C to end a process, but sometimes the process ends before I push
> the keys - leading to an inadvertent session end and me having to set
> up my work space again.
>
> CTRL-d is the usual key combo for a shell logout, which works just fine.
On Tue, 2009-11-03 at 15:06 +1300, Joel Pitt wrote:
I've also noticed that I use CTRL-C to abort a command line and give
me a clean one (yet still leave what I typed previously on the
screen).For a system that has it's roots in the command line, I feel this
change has had a significant impact on usability.
Maybe it's the same I described in my post "Access mapsets out of grass
(small problem when launching a grass session)" [1]?
I use very frequently Ctrl+C to just get a new line.
Nikos
[1] http://www.mail-archive.com/grass-user@lists.osgeo.org/msg10874.html
On Tue, 2009-11-03 at 03:58 +0100, Νίκος Αλεξανδρής wrote:
(Apologies for sorting your pots
posts... (heck the keyboard prints its own things
Hi Nikos,
2009/11/3 Νίκος Αλεξανδρής <nikos.alexandris@felis.uni-freiburg.de>:
Maybe it's the same I described in my post "Access mapsets out of grass
(small problem when launching a grass session)" [1]?I use very frequently Ctrl+C to just get a new line.
Nikos
[1] http://www.mail-archive.com/grass-user@lists.osgeo.org/msg10874.html
Yep, that looks like the same issue I'm having.. I'm guessing the
Grass init script is registering itself for the SIGINT signal. I could
investigate/fix this but as it seems to be a recent change, I wanted
to check if it was intentional or not.
J