From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Tomas Nordin Newsgroups: gmane.emacs.help Subject: RE: dired-hide-details-mode have no effect suddenly Date: Sat, 09 Sep 2017 21:34:29 +0200 Message-ID: <87y3pnk6nu.fsf@fliptop> References: <87d1774qr8.fsf@fliptop> <87d1778vjc.fsf@fliptop> <1381b9d9-cceb-4a5b-ab7f-d430e3753e74@default> NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: blaine.gmane.org 1504985737 30175 195.159.176.226 (9 Sep 2017 19:35:37 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Sat, 9 Sep 2017 19:35:37 +0000 (UTC) To: Drew Adams , help-gnu-emacs@gnu.org Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Sat Sep 09 21:35:33 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 1dqlWy-0006QD-Mr for geh-help-gnu-emacs@m.gmane.org; Sat, 09 Sep 2017 21:35:04 +0200 Original-Received: from localhost ([::1]:50637 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1dqlX5-0005L1-SN for geh-help-gnu-emacs@m.gmane.org; Sat, 09 Sep 2017 15:35:11 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:33270) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1dqlWX-0005Ke-Dp for help-gnu-emacs@gnu.org; Sat, 09 Sep 2017 15:34:38 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1dqlWU-0003N0-B0 for help-gnu-emacs@gnu.org; Sat, 09 Sep 2017 15:34:37 -0400 Original-Received: from mout02.posteo.de ([185.67.36.66]:40412) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1dqlWU-0003M4-4M for help-gnu-emacs@gnu.org; Sat, 09 Sep 2017 15:34:34 -0400 Original-Received: from submission (posteo.de [89.146.220.130]) by mout02.posteo.de (Postfix) with ESMTPS id F004A20BBB for ; Sat, 9 Sep 2017 21:34:31 +0200 (CEST) Original-Received: from customer (localhost [127.0.0.1]) by submission (posteo.de) with ESMTPSA id 3xqPX61p3Sz10HY; Sat, 9 Sep 2017 21:34:30 +0200 (CEST) In-Reply-To: <1381b9d9-cceb-4a5b-ab7f-d430e3753e74@default> X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] [fuzzy] X-Received-From: 185.67.36.66 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:114217 Archived-At: Drew Adams writes: > Then recursively bisect your init file to find the culprit. 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. 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. -- Tomas