unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Colin Baxter <m43cap@yandex.com>
To: Stefan Kangas <stefan@marxist.se>
Cc: , Emacs developers <emacs-devel@gnu.org>
Subject: Re: ibuffer-auto-mode
Date: Tue, 22 Jun 2021 07:14:22 +0100	[thread overview]
Message-ID: <87im264e9t.fsf@yandex.com> (raw)
In-Reply-To: <CADwFkmkv6aX9gRyNoHyzj6A8YHmAeEmwzsHbu9QRcykHoCmv6w@mail.gmail.com> (Stefan Kangas's message of "Mon, 21 Jun 2021 22:04:01 +0200")

Hello Stephan,
>>>>> Stefan Kangas <stefan@marxist.se> writes:

    > Colin Baxter <m43cap@yandex.com> writes:
    >> With emacs-28, I find I now have to set explicitly
    >> ibuffer-auto-mode to nil in my ~/.emacs in order for the menu
    >> popup <f10> to work in ibuffer. Otherwise I get a "void-variable
    >> ibuffer-auto-mode" error. This isn't needed for emacs-27. It
    >> isn't needed for "emacs-28 -Q" either; so presumably something
    >> about my setup triggers the void variable error, but I can't find
    >> anything that's obvious. I'd be grateful for suggestions as to
    >> where to look.
    >> 
    >> I know the def for the ibuffer-auto-mode has been changed, but
    >> even if I revert back to "nil nil nil" from ":lighter nil", the
    >> void-variable error is still triggered without the (setq
    >> ibuffer-auto-mode nil) setting.

    > (No reply here within 3 days.)

    > Nice bug report.  I would suggest sending this to
    > bug-gnu-emacs@gnu.org so we have a bug number and don't lose track
    > of it.

Good news. I've checked today and I now don't see the problem with the
latest emacs. So whatever it was, it's not there now.

Thanks.

Best wishes,

Colin.



      reply	other threads:[~2021-06-22  6:14 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-18  9:19 ibuffer-auto-mode Colin Baxter
2021-06-21 20:04 ` ibuffer-auto-mode Stefan Kangas
2021-06-22  6:14   ` Colin Baxter [this message]

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=87im264e9t.fsf@yandex.com \
    --to=m43cap@yandex.com \
    --cc=emacs-devel@gnu.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 public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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).