New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Document how to use -> to highlight the current selection #577

Closed
Wilfred opened this Issue Jul 11, 2016 · 5 comments

Comments

Projects
None yet
2 participants
@Wilfred
Contributor

Wilfred commented Jul 11, 2016

The docs at http://oremacs.com/swiper/#introduction say:

For example, adding a custom display function that points to a selected candidate with ->, instead of highlighting

However, I can't find any documentation for how to do this. I've found ivy-set-display-transformer, should I be using this? Is there sample code somewhere? The -> from ido-vertical is one of the very few things I miss when using ivy.

@abo-abo

This comment has been minimized.

Owner

abo-abo commented Jul 11, 2016

Use:

(setq ivy-format-function 'ivy-format-function-arrow)
@Wilfred

This comment has been minimized.

Contributor

Wilfred commented Jul 11, 2016

Thanks. Should I submit a PR for the docs, or does this belong elsewhere?

@abo-abo

This comment has been minimized.

Owner

abo-abo commented Jul 11, 2016

Editing the docs is better, especially since you have a CA. But putting more info on the wiki is always welcome as well.

Wilfred added a commit to Wilfred/swiper that referenced this issue Jul 11, 2016

@Wilfred

This comment has been minimized.

Contributor

Wilfred commented Jul 11, 2016

especially since you have a CA.

I do indeed! :) Is that public information somewhere, or have I said so at some point?

@abo-abo

This comment has been minimized.

Owner

abo-abo commented Jul 12, 2016

I do indeed! :) Is that public information somewhere, or have I said so at some point?

It's available to GNU devs via a file on GNU fencepost computer.

@Wilfred Wilfred referenced this issue Sep 13, 2016

Open

ELPA #44

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment