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

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

[debbugs-tracker] bug#17275: closed (emacs-24 crash in dired)


From: GNU bug Tracking System
Subject: [debbugs-tracker] bug#17275: closed (emacs-24 crash in dired)
Date: Thu, 17 Apr 2014 10:19:01 +0000

Your message dated Thu, 17 Apr 2014 13:18:20 +0300
with message-id <address@hidden>
and subject line Re: bug#17275: emacs-24 crash in dired
has caused the debbugs.gnu.org bug report #17275,
regarding emacs-24 crash in dired
to be marked as done.

(If you believe you have received this mail in error, please contact
address@hidden)


-- 
17275: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=17275
GNU Bug Tracking System
Contact address@hidden with problems
--- Begin Message --- Subject: emacs-24 crash in dired Date: Wed, 16 Apr 2014 11:24:14 +0100 User-agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0
Running emacs 24 on win7 64bit built from r116968 with mingw32 gcc 4.7.2.

From "emacs -Q"
1) Open a dired buffer:
   C-x C-f ~/.emacs.d RET

2) Switch to external 'ls' program
  (setq insert-directory-program "C:/cygwin/bin/ls.exe")
  (setq ls-lisp-use-insert-directory-program t)
  (setq dired-listing-switches "-al --group-directories-first")

3) Type 'g' in the dired buffer (bound to revert-buffer)
   Emacs shows the abort dialog.
   I have not managed to get gdb to emit a usable backtrace.

This is a recent regression (within the last week) as I build emacs from source daily. This bug does not manifest in current emacs trunk builds.



--- End Message ---
--- Begin Message --- Subject: Re: bug#17275: emacs-24 crash in dired Date: Thu, 17 Apr 2014 13:18:20 +0300
> From: Andy Moreton <address@hidden>
> Date: Thu, 17 Apr 2014 10:51:35 +0100
> 
> On Thu 17 Apr 2014, Eli Zaretskii wrote:
> > Please try the latest emacs-24 branch, I'd like to know if fixing
> > 17269 fixed this one as well.  If it did, the fix will appear on the
> > trunk soon enough.
> 
> Thanks Eli - that seems to have fixed it.

Great, closing.


--- End Message ---

reply via email to

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