all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Tomas Nordin <tomasn@posteo.net>
To: "Charles A. Roelli" <charles@aurox.ch>
Cc: help-gnu-emacs@gnu.org
Subject: Re: dired-hide-details-mode have no effect suddenly
Date: Wed, 20 Sep 2017 22:49:06 +0200	[thread overview]
Message-ID: <87shfhumd9.fsf@fliptop> (raw)
In-Reply-To: <87377vllmq.fsf@fliptop>

Tomas Nordin <tomasn@posteo.net> writes:

> "Charles A. Roelli" <charles@aurox.ch> writes:
>
>> I had the same issue once.  I had mistakenly added to the global value
>> of the variable 'font-lock-extra-managed-props' in some of my own code
>> for a buffer-local minor mode, instead of making the variable
>> buffer-local.  That resulted in dired-hide-details-mode breaking (and
>> a month's worth of confusion).
>
> Ok, my value is nil of that variable in dired, will check it when I get
> the problem next time, thanks. But I never touched that variable as far
> as I am aware.

And now suddenly...

font-lock-extra-managed-props is a variable defined in ‘font-lock.el’.
Its value is (invisible composition)

... and problem is back. Who has changed it I don't know. I know that it
has happened around doing some magit.

Cool, resetting that variable to nil removes the problem. But still,
hmm, ehh.



  reply	other threads:[~2017-09-20 20:49 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
2017-09-05 19:10 ` Charles A. Roelli
2017-09-09 19:25   ` Tomas Nordin
2017-09-20 20:49     ` Tomas Nordin [this message]
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=87shfhumd9.fsf@fliptop \
    --to=tomasn@posteo.net \
    --cc=charles@aurox.ch \
    --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.