unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: Eli Zaretskii <eliz@gnu.org>, Drew Adams <drew.adams@oracle.com>
Cc: 41087@debbugs.gnu.org
Subject: bug#41087: 27.0.91; How to remove Emacs 27 changes to minibuffer?
Date: Mon, 4 May 2020 21:35:05 -0700 (PDT)	[thread overview]
Message-ID: <a1812925-7f61-4aa3-87fd-c673c06b97c3@default> (raw)
In-Reply-To: <<83lfm7m871.fsf@gnu.org>>

> > Emacs 27 is unfortunately _totally_ unusable for me.  Cannot do the
> > slightest thing.
> 
> Please provide at least some examples of the difficulties.  It's hard
> to say anything intelligent without that much.

I can't at this point.  I simply can't use it at all.
It will take a very long time, I expect, to figure
anything out about it.  I spent quite a while in the
Lisp debugger today, and didn't scratch the surface.

I don't have time for this now, I'm afraid.  I'll
have to hope that others encounter problems that are
related and later I'll perhaps get a pretest candidate
that I can use to further find out what's wrong.

If no one else runs into related problems then I'll
have to get into it at some point, no doubt.  But
I likely won't have the time to do that for quite
a while.  I don't want this to be the end of my use
of Emacs (e.g. staying forever with 26.3), but that
might need to be the case.

> > I think that some of the problems come from the changes to minibuffer
> > and echo-area behavior.

I really don't know that, so ignore that thought.
I do want to undo such changes, but I don't have
a clue whether they might be causing deeper problems.

> > Regardless of whether that is the case, I want
> > to undo those changes.  Is there an option for that? (I hope so.)  If
> > not, what changes do I need to make from Lisp, to get back the prior
> > behavior?
> 
> The NEWS mentions a few variables that should allow you to do that,
> but without knowing what you want to undo, it is hard to say more.

I didn't notice such variables.  Anyway, I'll worry
about that later, and just assume for now that it's
not at the root of the bigger problems I have.

But yes, I don't want minibuffer-message replacing
messge whenever the minibuffer is active, etc.  I
want the echo area as it was and minibuffer-message
and message as they were.

I realize that this bug report doesn't help anything
at this point.  I guess the message for now is that
my Emacs is completely broken - can't even begin to
use it for anything.  In particular, my *Completions*
buffer is shown in a separate frame, whose focus is
redirected to the minibuffer.  That's essentially
broken now.

There seems to be some additional handle-switch-frame,
which breaks that relation somehow (?), so typing in
the minibuffer, and then hitting TAB, which pops up
the *Completions* frame, takes input focus away from
the minibuffer frame (and gives it to the *Completions*
frame, which is read-only).

My setup works with each Emacs release, from 20 to 26.

I know this is all very vague.  Sorry.





       reply	other threads:[~2020-05-05  4:35 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <<da68d511-3682-4661-b1a1-4323d0ab50cb@default>
     [not found] ` <<83lfm7m871.fsf@gnu.org>
2020-05-05  4:35   ` Drew Adams [this message]
2020-05-05 14:23     ` bug#41087: 27.0.91; How to remove Emacs 27 changes to minibuffer? Eli Zaretskii
     [not found] ` <<85imhah1kt.fsf@gmail.com>
     [not found]   ` <<1b1632e1-2669-44c3-b6c1-1d8da519a91b@default>
     [not found]     ` <<87tv0klsvt.fsf@mail.linkov.net>
     [not found]       ` <<4575d23f-e3b5-4c44-8907-5ba8324dec91@default>
     [not found]         ` <<83r1vo7eqe.fsf@gnu.org>
2020-05-13  2:36           ` Drew Adams
2020-05-13 14:48             ` Eli Zaretskii
     [not found] <<<da68d511-3682-4661-b1a1-4323d0ab50cb@default>
     [not found] ` <<<83lfm7m871.fsf@gnu.org>
     [not found]   ` <<a1812925-7f61-4aa3-87fd-c673c06b97c3@default>
     [not found]     ` <<83bln2mpf8.fsf@gnu.org>
2020-05-05 17:46       ` Drew Adams
2020-05-04 21:07 Drew Adams
2020-05-05  2:22 ` Eli Zaretskii
2020-05-05 14:57 ` Noam Postavsky
2020-05-05 18:10   ` Drew Adams
2020-05-12 22:50     ` Juri Linkov
2020-05-12 23:56       ` Drew Adams
2020-05-13  2:09         ` Drew Adams
2020-05-13  2:25         ` Eli Zaretskii

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=a1812925-7f61-4aa3-87fd-c673c06b97c3@default \
    --to=drew.adams@oracle.com \
    --cc=41087@debbugs.gnu.org \
    --cc=eliz@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 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).