https://bugs.dragonflybsd.org/https://bugs.dragonflybsd.org/favicon.ico?16293952082006-03-10T01:55:10ZDragonFlyBSD bugtrackerDragonFlyBSD - Bug #106: emacs dired mode no longer workinghttps://bugs.dragonflybsd.org/issues/106?journal_id=3512006-03-10T01:55:10Zsteve.mynott
<ul></ul><p>I see no issue with emacs dired using "emacs-nox11-21.4anb2" from<br />pkgsrc running on 1.5.1-DEVELOPMENT.</p>
<p>Cheers Steve</p>
<p>On 3/9/06, Sascha Wildner <<a class="email" href="mailto:saw@online.de">saw@online.de</a>> wrote:</p>
<blockquote>
<p>Hi,</p>
<p>I've noticed that from some point in, say, the last 1.5 weeks the<br />directory edit mode of emacs no longer seems to work. When I try to open<br />a directory it just kinda freezes like in an infinite loop.</p>
<p>Here's a ktrace:</p>
<p><a class="external" href="http://yoyodyne.ath.cx/tmp/emacs.ktrace">http://yoyodyne.ath.cx/tmp/emacs.ktrace</a></p>
<p>It starts just after the dired-mode lisp code has been loaded. You'll<br />notice the large number of "CALL break()" lines starting in line 201,<br />only interrupted at the end by SIGHUP when I closed the ssh window.</p>
<p>Can anyone figure out what's going wrong here from that?</p>
<p>Sascha</p>
<p>--<br /><a class="external" href="http://yoyodyne.ath.cx">http://yoyodyne.ath.cx</a></p>
</blockquote> DragonFlyBSD - Bug #106: emacs dired mode no longer workinghttps://bugs.dragonflybsd.org/issues/106?journal_id=3522006-03-10T02:21:10Zswildner
<ul></ul><p>Steve Mynott wrote:</p>
<blockquote>
<p>I see no issue with emacs dired using "emacs-nox11-21.4anb2" from<br />pkgsrc running on 1.5.1-DEVELOPMENT.</p>
</blockquote>
<p>Strange, those are the versions I'm running here, too.</p>
<p>Sascha</p> DragonFlyBSD - Bug #106: emacs dired mode no longer workinghttps://bugs.dragonflybsd.org/issues/106?journal_id=13702006-10-02T20:30:59Zcorecode
<ul></ul><p>Is this fixed?</p> DragonFlyBSD - Bug #106: emacs dired mode no longer workinghttps://bugs.dragonflybsd.org/issues/106?journal_id=13902006-10-03T02:53:47Zswildner
<ul></ul><p>Kinda fixed. This issue occurs only on one box I have. As soon as I upgrade it,<br />I'll recheck.</p>