unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Tomas Nordin <tomasn@posteo.net>
To: Drew Adams <drew.adams@oracle.com>, help-gnu-emacs@gnu.org
Subject: RE: dired-hide-details-mode have no effect suddenly
Date: Tue, 12 Sep 2017 22:40:21 +0200	[thread overview]
Message-ID: <87poav3b2i.fsf@fliptop> (raw)
In-Reply-To: <bce7b145-c26f-453d-8fb3-e961df27f54d@default>

Drew Adams <drew.adams@oracle.com> writes:

> `C-h f dired-hide-details TAB' shows you these variables:
>
> dired-hide-details-hide-information-lines
> dired-hide-details-hide-symlink-targets
> dired-hide-details-mode
> dired-hide-details-mode-hook
>
> You might start with the last two, checking in your init
> file, `custom-file', or other code you might load.
>
> You can also put (debug-on-entry 'dired-hide-details-mode)
> in your init file, to find out what code is calling it.
> In the debugger, look at how it gets called, then use `c'
> to skip debugging.  Use `M-x cancel-debug-on-entry RET'
> to cancel such debugger entry.
>
> But it's probably easier to just grep for `dired-hide-details'
> in directories of customization and 3rd-party code you load.

Thanks for this suit of suggestions, I keep it in my back pocket. I
stored away the values of the variables (working condition), didn't grep
any results on `dired-hide-details' in my elpa directory.



  reply	other threads:[~2017-09-12 20:40 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-03 17:48 dired-hide-details-mode have no effect suddenly Tomas Nordin
2017-09-03 18:04 ` Drew Adams
2017-09-03 18:52   ` Tomas Nordin
2017-09-03 19:37     ` Drew Adams
2017-09-09 19:34       ` Tomas Nordin
2017-09-09 22:48         ` Drew Adams
2017-09-12 20:40           ` Tomas Nordin [this message]
2017-09-05 19:10 ` Charles A. Roelli
2017-09-09 19:25   ` Tomas Nordin
2017-09-20 20:49     ` Tomas Nordin
2017-09-21 18:30       ` Charles A. Roelli
2017-09-21 19:10         ` Tomas Nordin
2017-09-21 19:20           ` Tomas Nordin
2017-09-23  9:43             ` Charles A. Roelli
2017-09-24 15:49               ` Tomas Nordin

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

  List information: https://www.gnu.org/software/emacs/

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

  git send-email \
    --in-reply-to=87poav3b2i.fsf@fliptop \
    --to=tomasn@posteo.net \
    --cc=drew.adams@oracle.com \
    --cc=help-gnu-emacs@gnu.org \
    /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. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).