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: Thu, 21 Sep 2017 21:20:36 +0200 [thread overview]
Message-ID: <87k20rvoxn.fsf@fliptop> (raw)
In-Reply-To: <87o9q3vpep.fsf@fliptop>
Tomas Nordin <tomasn@posteo.net> writes:
> "Charles A. Roelli" <charles@aurox.ch> writes:
>
>>> 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.
>>
>> Neat. Does M-x rgrep font-lock-extra-managed-props RET * RET
>> ~/.emacs.d/elpa/ show anything interesting?
>
> Yes, three. I think the relevant two are those:
>
> ./markdown-mode-20170610.602/markdown-mode.el:7783: (add-to-list 'font-lock-extra-managed-props 'composition)
> ./markdown-mode-20170610.602/markdown-mode.el:7789: (add-to-list 'font-lock-extra-managed-props 'invisible)
I have updated that package and now those variables are manipulated like this:
(setq-local font-lock-extra-managed-props
(append font-lock-extra-managed-props
'(composition display invisible)))
Is this a more proper way to do it? :)
next prev parent reply other threads:[~2017-09-21 19:20 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
2017-09-21 18:30 ` Charles A. Roelli
2017-09-21 19:10 ` Tomas Nordin
2017-09-21 19:20 ` Tomas Nordin [this message]
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=87k20rvoxn.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.
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).