bug-gnu-emacs
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

bug#11047: 24.0.94; Hangs when creating buffer starting with multiple sp


From: Jan Djärv
Subject: bug#11047: 24.0.94; Hangs when creating buffer starting with multiple spaces and there exists buffers with multiple spaces
Date: Mon, 9 Apr 2012 12:57:27 +0200

Hello.

I can't reproduce this with OSX either.  Does it happen when Emacs is started 
with -Q?

        Jan D.

20 mar 2012 kl. 18:52 skrev Eli Zaretskii:

>> From: Charles Magid <address@hidden>
>> Date: Tue, 20 Mar 2012 09:37:11 -0400
>> 
>> 1. Started emacs on mac os x lion 10.7.3
>> 2. Started shell M-x shell
>> 3. Created buffer with very long text name starting with 4 spaces
>>   c-x b c-q spc c-q spc c-q spc c-q spc Now, start the server and you are 
>> ready to sign in and sign out. You can also block user access in any 
>> controller by calling authenticate_user! in a before filter. Just remember 
>> that, if you add the filter to your application controller, remember to skip 
>> the filter on the sessions controller, otherwise you won’t be able to sign 
>> in in the first place.
>> 4. confirm with a 'return'
>> 5. Repeat with slightly more spaces and complex buffer name
>>    c-x b c-q spc c-q spc c-q spc c-q spc c-q spc c-q spc You can now freely 
>> proceed to implement the other controllers and views in your application. 
>> Keep in mind that if you have devise :recoverable in your model, all the 
>> related methods like User.send_reset_password_instructions will already be 
>> available in your model, so you can use them straight away to implement your 
>> own reset password feature. Since Devise use all those methods internally, 
>> if you have any questions about implementing your own reset password 
>> feature, you can always take a look at Devise own controllers for some help.
>>     confirm by 'return'
>> 6. Emacs hangs using ~100% of cpu
> 
> FWIW, I cannot reproduce this on MS-Windows with yesterday's trunk.
> Emacs doesn't hang for me after doing all these steps.
> 
> 
> 






reply via email to

[Prev in Thread] Current Thread [Next in Thread]