all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / 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: Sat, 09 Sep 2017 21:34:29 +0200	[thread overview]
Message-ID: <87y3pnk6nu.fsf@fliptop> (raw)
In-Reply-To: <1381b9d9-cceb-4a5b-ab7f-d430e3753e74@default>

Drew Adams <drew.adams@oracle.com> 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



  reply	other threads:[~2017-09-09 19:34 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 [this message]
2017-09-09 22:48         ` Drew Adams
2017-09-12 20:40           ` Tomas Nordin
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

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

  git send-email \
    --in-reply-to=87y3pnk6nu.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.
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.