From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Drew Adams Newsgroups: gmane.emacs.help Subject: RE: dired-hide-details-mode have no effect suddenly Date: Sat, 9 Sep 2017 22:48:23 +0000 (UTC) Message-ID: References: <87d1774qr8.fsf@fliptop> <87d1778vjc.fsf@fliptop> <1381b9d9-cceb-4a5b-ab7f-d430e3753e74@default> <87y3pnk6nu.fsf@fliptop> NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Trace: blaine.gmane.org 1504997359 25842 195.159.176.226 (9 Sep 2017 22:49:19 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Sat, 9 Sep 2017 22:49:19 +0000 (UTC) To: Tomas Nordin , help-gnu-emacs@gnu.org Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Sun Sep 10 00:49:09 2017 Return-path: Envelope-to: geh-help-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1dqoYa-0005aC-Vo for geh-help-gnu-emacs@m.gmane.org; Sun, 10 Sep 2017 00:48:57 +0200 Original-Received: from localhost ([::1]:51098 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1dqoYg-0003Vc-Ei for geh-help-gnu-emacs@m.gmane.org; Sat, 09 Sep 2017 18:49:02 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:38903) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1dqoYG-0003VT-GK for help-gnu-emacs@gnu.org; Sat, 09 Sep 2017 18:48:37 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1dqoYD-0003n2-Bg for help-gnu-emacs@gnu.org; Sat, 09 Sep 2017 18:48:36 -0400 Original-Received: from userp1040.oracle.com ([156.151.31.81]:19108) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1dqoYD-0003me-1r for help-gnu-emacs@gnu.org; Sat, 09 Sep 2017 18:48:33 -0400 Original-Received: from userv0021.oracle.com (userv0021.oracle.com [156.151.31.71]) by userp1040.oracle.com (Sentrion-MTA-4.3.2/Sentrion-MTA-4.3.2) with ESMTP id v89MmSBi031308 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Sat, 9 Sep 2017 22:48:28 GMT Original-Received: from userv0121.oracle.com (userv0121.oracle.com [156.151.31.72]) by userv0021.oracle.com (8.14.4/8.14.4) with ESMTP id v89MmSll025504 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Sat, 9 Sep 2017 22:48:28 GMT Original-Received: from ubhmp0015.oracle.com (ubhmp0015.oracle.com [156.151.24.68]) by userv0121.oracle.com (8.14.4/8.13.8) with ESMTP id v89MmOkd016534; Sat, 9 Sep 2017 22:48:24 GMT In-Reply-To: <87y3pnk6nu.fsf@fliptop> X-Priority: 3 X-Mailer: Oracle Beehive Extensions for Outlook 2.0.1.9.1 (1003210) [OL 12.0.6774.5000 (x86)] X-Source-IP: userv0021.oracle.com [156.151.31.71] X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.4.x-2.6.x [generic] [fuzzy] X-Received-From: 156.151.31.81 X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Users list for the GNU Emacs text editor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Original-Sender: "help-gnu-emacs" Xref: news.gmane.org gmane.emacs.help:114220 Archived-At: > > Then recursively bisect your init file to find the culprit. >=20 > I am sure this is a proper suggestion. It's just that the workflow would > look something like, comment out half, use Emacs to a point in time when > I feel the problem should have occurred (but it didn't occur), > un-comment half of the first commented half plus the first un-commented > half and repeat using Emacs to a point in time when I feel that the > problem should have occurred and so on. I mean, it's just a bit tricky > when the problem is seemingly intermittent. Like now for example, Emacs > has been running for a couple of days and details hide as expected. >=20 > Could there be some variables to check while it's working as expected > and then check again when it's not working as expected? Or something > like that. `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.