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

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

[debbugs-tracker] bug#34089: closed (27.0.50; Substring icomplete broken


From: GNU bug Tracking System
Subject: [debbugs-tracker] bug#34089: closed (27.0.50; Substring icomplete broken for M-x switch-to-buffer)
Date: Wed, 16 Jan 2019 06:49:03 +0000

Your message dated Wed, 16 Jan 2019 06:48:25 +0000
with message-id <address@hidden>
and subject line Re: bug#34089: 27.0.50; Substring icomplete broken for M-x 
switch-to-buffer
has caused the debbugs.gnu.org bug report #34089,
regarding 27.0.50; Substring icomplete broken for M-x switch-to-buffer
to be marked as done.

(If you believe you have received this mail in error, please contact
address@hidden)


-- 
34089: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=34089
GNU Bug Tracking System
Contact address@hidden with problems
--- Begin Message --- Subject: 27.0.50; Substring icomplete broken for M-x switch-to-buffer Date: Wed, 16 Jan 2019 00:11:38 +0000 User-agent: Gnus/5.13 (Gnus v5.13) Emacs/27.0.50 (gnu/linux)
Hi maintainers,

In my newfound icomplete adventures, I've come across a very annoying
bug I just cannot catch:

    Emacs -Q
    M-x icomplete-mode
    M-: (setq completion-styles '(substring)) RET
    M-: (generate-new-buffer "Messages") RET
    C-x b

Now type "M".  The minibuffer suggest the buffer "Messages", but what
about "*Messages"?  Why isn't it considered?

If, instead of "M", I type "essa", then "Messages" and "*Messages*"
_are_ both considered, correctly.

Tracing completion-substring-try/all-completion shows that it is not
being called in the first situation: why???

João







--- End Message ---
--- Begin Message --- Subject: Re: bug#34089: 27.0.50; Substring icomplete broken for M-x switch-to-buffer Date: Wed, 16 Jan 2019 06:48:25 +0000
On Wed, Jan 16, 2019, 02:04 Stefan Monnier <address@hidden wrote:
Not sure how to write the code that combines category-default-styles and
global styles in order to get that behavior.

Delete everything and try again? 

I kid, I kid... :-) Thanks Stefan, I was hoping for such an easy answer!

BTW how do you debug this stuff?  Edebug is akward because of the minibuffer usage (and the second frame technique doesn't always work).

João

--- End Message ---

reply via email to

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