Skip to content
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

Discrepancy between describe-function and counsel-describe-function #1330

Closed
jwiegley opened this issue Nov 29, 2017 · 8 comments
Closed

Discrepancy between describe-function and counsel-describe-function #1330

jwiegley opened this issue Nov 29, 2017 · 8 comments

Comments

@jwiegley
Copy link

@jwiegley jwiegley commented Nov 29, 2017

If my point is at the end of (find-file "hello" |, describe-function will describe the function, find-file; counsel-describe-function appears to select whatever function matches the regex given by the text of the word before point.

@basil-conto
Copy link
Collaborator

@basil-conto basil-conto commented Nov 29, 2017

I think this is intentional; see #1088 (comment).

@basil-conto
Copy link
Collaborator

@basil-conto basil-conto commented Nov 29, 2017

Having said that, it might be nice to make this configurable.

@abo-abo abo-abo closed this in 9967b2d Nov 29, 2017
@jwiegley
Copy link
Author

@jwiegley jwiegley commented Nov 29, 2017

I discovered it because I rely on the describe-function behavior, to understand the meaning of the "next argument" I'm about to type. Having to move point to avoid typing the function name at the prompt is inefficient enough that I'll just go back to describe-function, which still has the ivy completion.

@abo-abo
Copy link
Owner

@abo-abo abo-abo commented Nov 29, 2017

Thanks, it's customizable now: use (setq counsel-describe-function-preselect 'ivy-function-called-at-point) to test.

@jwiegley
Copy link
Author

@jwiegley jwiegley commented Nov 29, 2017

Great, @abo-abo, thank you!

@abo-abo
Copy link
Owner

@abo-abo abo-abo commented Nov 29, 2017

You're welcome.

I discovered it because I rely on the describe-function behavior, to understand the meaning of the "next argument" I'm about to type.

I see. I simply use C-1 for this with lispy.

@jwiegley
Copy link
Author

@jwiegley jwiegley commented Nov 29, 2017

I only recently installed lispy, so I've yet to build this into muscle memory.

@basil-conto
Copy link
Collaborator

@basil-conto basil-conto commented Nov 29, 2017

it's customizable now

Awesome, thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
3 participants