[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: ido-ubiquitous working everywhere EXCEPT find-bookmark
From: |
jmckitrick |
Subject: |
Re: ido-ubiquitous working everywhere EXCEPT find-bookmark |
Date: |
Sat, 10 Jun 2017 20:18:05 +0000 |
Aha!
My work machine uses melpa-stable, and my home machine uses melpa. So the
older version does not have the variable in question. I expect once that
version of ido-ubiquitous is 'stable' I'll get the same behavior at work as
well.
Which leads to the next 2 questions:
1. How can I force the preferred behavior the correct way?
2. Barring that, how can I make emacs complete bookmarks in
most-recently-used order first?
On Sat, Jun 10, 2017 at 4:02 PM <jmckitrick@gmail.com> wrote:
> If I set `ido-cr+-force-on-functional-collection' to non-nil, I get the
> result I want, like you said. But that value is not set anywhere in my
> setup.
> I am also using icomplete-mode. That's the mode that's giving me the
> {FOO|BAR} style completion. If I disable that, it's vanilla emacs
> completion choices.
>
> But I cannot figure out why my work machine works the way I want, and my
> home setup does not.
>
>
> On Sat, Jun 10, 2017 at 3:34 PM John Mastro <john.b.mastro@gmail.com>
> wrote:
>
>> <jmckitrick@gmail.com> wrote:
>> > the command is `bookmark-jump`, usually bound to C-x r b
>>
>> I also use ido-ubiquitous and ido-vertical, but I don't get ido
>> completion from `bookmark-jump' at all unless I set
>> `ido-cr+-force-on-functional-collection' to non-nil. If I do set that,
>> then I get vertical ido completion.
>>
>> Do you have that variable set?
>>
>> The only thing I can think of is if ido-ubiquitous is falling back to
>> another completion package (icomplete perhaps?).
>>
>> John
>>
> --
> Jonathon McKitrick
>
--
Jonathon McKitrick