From: Michael Heerdegen <michael_heerdegen@web.de>
To: Stefan Kangas <stefan@marxist.se>
Cc: 20841@debbugs.gnu.org, Lars Ingebrigtsen <larsi@gnus.org>
Subject: bug#20841: 25.0.50; Turning off `which-function-mode' does not remove its last effect from the minibuffer
Date: Sun, 04 Oct 2020 00:20:57 +0200 [thread overview]
Message-ID: <871rifdk8m.fsf@web.de> (raw)
In-Reply-To: <CADwFkm=TJiZpZZsz289wSStdyonF3xwxMK+03rKnL5E1QQoNrA@mail.gmail.com> (Stefan Kangas's message of "Mon, 31 Aug 2020 02:53:16 +0000")
Stefan Kangas <stefan@marxist.se> writes:
> > I don't understand. Did you read Michael Heerdegen's
> > mails in this thread? He explains the problem, no?
>
> Yes, I read his replies and looked into what he suggested. I can't see
> how his posts explain the problem.
>
> He was not clear over the difference between the confusingly named
> variables which-function-mode and which-func-mode. That confusion has
> nothing to do with the mode line not updating AFAICT.
No, I had understood the problem, but I guess it has been fixed in the
meantime - possibly
cbfb1295554 Stefan Monnier Improve disabling the mode
The problem had been that the mode var and the var used by the mode-line
to decide if there is anything to show were different and disabling the
mode didn't change the other var so the mode line display was not turned
off. After the above commit the mode line display is only on when both
variables are non-nil so I think he fixed it without knowing of this
report.
Michael.
next prev parent reply other threads:[~2020-10-03 22:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-18 1:25 bug#20841: 25.0.50; Turning off `which-function-mode' does not remove its last effect from the minibuffer Drew Adams
2016-04-30 20:01 ` Lars Ingebrigtsen
2016-04-30 20:41 ` Drew Adams
2016-05-07 12:44 ` Michael Heerdegen
2016-05-07 12:55 ` Michael Heerdegen
2020-08-31 2:11 ` Stefan Kangas
2020-08-31 2:26 ` Drew Adams
2020-08-31 2:53 ` Stefan Kangas
2020-10-03 22:20 ` Michael Heerdegen [this message]
2020-10-04 14:00 ` Lars Ingebrigtsen
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=871rifdk8m.fsf@web.de \
--to=michael_heerdegen@web.de \
--cc=20841@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=stefan@marxist.se \
/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.