emacs-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

bug#64141: closed (27.1 newly has clunky type-break y-or-n-p)


From: GNU bug Tracking System
Subject: bug#64141: closed (27.1 newly has clunky type-break y-or-n-p)
Date: Sat, 02 Sep 2023 22:06:02 +0000

Your message dated Sat, 2 Sep 2023 15:04:47 -0700
with message-id 
<CADwFkmmF3J0XWrENV48h79Lf_7RH3vDLxDWvFmUNtrUxzjxi7g@mail.gmail.com>
and subject line Re: bug#64141: 27.1 newly has clunky type-break y-or-n-p
has caused the debbugs.gnu.org bug report #64141,
regarding 27.1 newly has clunky type-break y-or-n-p
to be marked as done.

(If you believe you have received this mail in error, please contact
help-debbugs@gnu.org.)


-- 
64141: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=64141
GNU Bug Tracking System
Contact help-debbugs@gnu.org with problems
--- Begin Message --- Subject: 27.1 newly has clunky type-break y-or-n-p Date: Sat, 17 Jun 2023 18:17:00 -0700
i upgraded to 27.1 and found that type-break is asking me about breaks
as follows:

when it asks in minibuffer

- point is in another window, requiring focus, changing point, and
tending to type-break
- home or page up key puts point at beg of message, where it will not
accept a reply
- it is generally more high-maintenane to get it to do a type-break or
to get it to postpone it
- it seems to arrive in the wrong place or at the wrong instant more
[this is subjective and please ignore if nonsensical]

apologies for bad bug report.  perhaps it will trigger a memory of a
code change or changelog/diff will make it obvious.

-- 
The Kafka Pandemic

A blog about science, health, human rights, and misopathy:
https://thekafkapandemic.blogspot.com



--- End Message ---
--- Begin Message --- Subject: Re: bug#64141: 27.1 newly has clunky type-break y-or-n-p Date: Sat, 2 Sep 2023 15:04:47 -0700
Juri Linkov <juri@linkov.net> writes:

>> i realize this isn't useful other than the stuff i have already
>> provided, but i find that type-break more often than not does the
>> wrong thing.  cursor in non-writable spot, or in a real buffer.  or in
>> middle of isearch.  probably various other things.
>>
>> is the idea that i would upgrade to a newer version of emacs?  i do
>> that by upgrading debian....
>
> Or you could take the old function `y-or-n-p' from 26.1
> and add it to your config for 27.1.

Having read this bug thread, it seems like there is nothing more to do
here.  I'm therefore closing this bug report.

If this conclusion is incorrect and this is still an issue, please reply
to this email (use "Reply to all" in your email client) and we can
reopen the bug report.


--- End Message ---

reply via email to

[Prev in Thread] Current Thread [Next in Thread]