On 25/10/2012 4:07 PM, Larry Hall (Cygwin) wrote:
On 10/25/2012 1:06 PM, ping wrote:
On 10/25/2012 12:54 PM, Eli Zaretskii wrote:
Date: Thu, 25 Oct 2012 09:01:40 -0600
From: Eric Blake
On 10/25/2012 08:55 AM, Ryan Johnson wrote:
http://debbugs.gnu.org/cgi/bugreport.cgi?bug=12697
I imagine i
On 10/25/2012 1:06 PM, ping wrote:
On 10/25/2012 12:54 PM, Eli Zaretskii wrote:
Date: Thu, 25 Oct 2012 09:01:40 -0600
From: Eric Blake
On 10/25/2012 08:55 AM, Ryan Johnson wrote:
http://debbugs.gnu.org/cgi/bugreport.cgi?bug=12697
I imagine it will be fixed before the release of Emacs 24.3
On 10/25/2012 12:54 PM, Eli Zaretskii wrote:
Date: Thu, 25 Oct 2012 09:01:40 -0600
From: Eric Blake
On 10/25/2012 08:55 AM, Ryan Johnson wrote:
http://debbugs.gnu.org/cgi/bugreport.cgi?bug=12697
I imagine it will be fixed before the release of Emacs 24.3.
Agree the initial part is emacs.
> Date: Thu, 25 Oct 2012 09:01:40 -0600
> From: Eric Blake
>
> On 10/25/2012 08:55 AM, Ryan Johnson wrote:
>
> http://debbugs.gnu.org/cgi/bugreport.cgi?bug=12697
>
> I imagine it will be fixed before the release of Emacs 24.3.
> >>> Agree the initial part is emacs. But I sus
On 25/10/2012 11:01 AM, Eric Blake wrote:
On 10/25/2012 08:55 AM, Ryan Johnson wrote:
http://debbugs.gnu.org/cgi/bugreport.cgi?bug=12697
I imagine it will be fixed before the release of Emacs 24.3.
Agree the initial part is emacs. But I suspect the confused bash
business is not. ^G should e
On 10/25/2012 08:55 AM, Ryan Johnson wrote:
http://debbugs.gnu.org/cgi/bugreport.cgi?bug=12697
I imagine it will be fixed before the release of Emacs 24.3.
>>> Agree the initial part is emacs. But I suspect the confused bash
>>> business is not. ^G should either send SIGINT or
On 25/10/2012 10:40 AM, Ken Brown wrote:
On 10/24/2012 5:26 PM, Ryan Johnson wrote:
On 24/10/2012 5:01 PM, Ken Brown wrote:
On 10/24/2012 9:09 AM, Ryan Johnson wrote:
On 01/10/2012 4:08 PM, Ryan Johnson wrote:
> On 01/10/2012 3:07 PM, Ken Brown wrote:
>> On 10/1/2012 2:51 PM, Ryan Johnson wr
On 10/24/2012 5:26 PM, Ryan Johnson wrote:
On 24/10/2012 5:01 PM, Ken Brown wrote:
On 10/24/2012 9:09 AM, Ryan Johnson wrote:
On 01/10/2012 4:08 PM, Ryan Johnson wrote:
> On 01/10/2012 3:07 PM, Ken Brown wrote:
>> On 10/1/2012 2:51 PM, Ryan Johnson wrote:
>>> I'm hitting a strange behavior w
On 24/10/2012 5:01 PM, Ken Brown wrote:
On 10/24/2012 9:09 AM, Ryan Johnson wrote:
On 01/10/2012 4:08 PM, Ryan Johnson wrote:
> On 01/10/2012 3:07 PM, Ken Brown wrote:
>> On 10/1/2012 2:51 PM, Ryan Johnson wrote:
>>> I'm hitting a strange behavior with emacs lately, where hitting
>>> C-x C-g
On 10/24/2012 9:09 AM, Ryan Johnson wrote:
On 01/10/2012 4:08 PM, Ryan Johnson wrote:
> On 01/10/2012 3:07 PM, Ken Brown wrote:
>> On 10/1/2012 2:51 PM, Ryan Johnson wrote:
>>> I'm hitting a strange behavior with emacs lately, where hitting
>>> C-x C-g [1] sometimes causes it to quit instantl
On 01/10/2012 4:08 PM, Ryan Johnson wrote:
> On 01/10/2012 3:07 PM, Ken Brown wrote:
>> On 10/1/2012 2:51 PM, Ryan Johnson wrote:
>>> I'm hitting a strange behavior with emacs lately, where hitting
>>> C-x C-g [1] sometimes causes it to quit instantly: no request to
>>> save files, no seg fault, n
On 01/10/2012 3:07 PM, Ken Brown wrote:
On 10/1/2012 2:51 PM, Ryan Johnson wrote:
I'm hitting a strange behavior with emacs lately, where hitting C-x C-g
[1] sometimes causes it to quit instantly: no request to save files, no
seg fault, no error message, just gone (have to reset the terminal to
On 10/1/2012 2:51 PM, Ryan Johnson wrote:
Hi all,
I'm hitting a strange behavior with emacs lately, where hitting C-x C-g
[1] sometimes causes it to quit instantly: no request to save files, no
seg fault, no error message, just gone (have to reset the terminal to
clear out emacs' ncurses setting
13 matches
Mail list logo