all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Juri Linkov <juri@linkov.net>
Cc: Stephen Berman <stephen.berman@gmx.net>, 8484@debbugs.gnu.org
Subject: bug#8484: 24.0.50; Dired problems with marking and hidden subdirs
Date: Wed, 16 Sep 2020 13:36:04 +0200	[thread overview]
Message-ID: <878sdarm1n.fsf@gnus.org> (raw)
In-Reply-To: <874knzosf6.fsf@mail.linkov.net> (Juri Linkov's message of "Tue,  15 Sep 2020 21:04:12 +0300")

Juri Linkov <juri@linkov.net> writes:

>> Stephen's patch seems to fix that example, so I've now applied it to the
>> trunk.  I had to move some utility functions from dired-aux to avoid
>> dired.el unconditionally loading dired-aux always (since this change is
>> in a very fundamental dired function).
>
> Ouch, this broke my configuration.  When the init file contains:
>
>   (add-hook 'dired-mode-hook 'dired-sort-toggle)
>
> trying to visit a Dired buffer fails with:
>
> Debugger entered--Lisp error: (error "No subdir-alist in tmp")
>   signal(error ("No subdir-alist in tmp"))
>   error("No subdir-alist in %s" #<buffer tmp>)
>   dired-current-directory()
>   dired-get-filename(nil t)

It looks like that function can't be called before a dired function is
properly set up, but dired-sort-toggle does so.  I've now made
dired-get-filename more robust again after the previous change to that
function.

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no





      reply	other threads:[~2020-09-16 11:36 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-12 11:58 bug#8484: 24.0.50; Dired problems with marking and hidden subdirs Stephen Berman
2016-01-22 20:55 ` Marcin Borkowski
2020-09-14 12:58 ` Lars Ingebrigtsen
2020-09-15 18:04   ` Juri Linkov
2020-09-16 11:36     ` Lars Ingebrigtsen [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=878sdarm1n.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=8484@debbugs.gnu.org \
    --cc=juri@linkov.net \
    --cc=stephen.berman@gmx.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.