Doc keystrokes

57 views
Skip to first unread message

Mark Engelberg

unread,
Aug 17, 2012, 2:41:02 AM8/17/12
to clojured...@googlegroups.com
Are there key bindings to see the docstring or params for a given function?  (I see docstrings when I do auto-completion, but don't know how to access it when just browsing code).

Also, when looking at the stacktrace for an error, is there any easy way to jump to the source/line of the problem?  Are there ways to look at the values of the locals at the time of the crash?

Thanks,

Mark

Laurent PETIT

unread,
Aug 17, 2012, 12:54:50 PM8/17/12
to clojured...@googlegroups.com
Le 17 août 2012 à 10:10, Mark Engelberg <mark.en...@gmail.com> a écrit :

Are there key bindings to see the docstring or params for a given function?  (I see docstrings when I do auto-completion, but don't know how to access it when just browsing code).


In the beta channel, this feature exists and is activable via a shortcut similar to the one found in the java editor: cmd-alt-space on Mac, Ctrl-alt-space (or is it shit-alt-space ?) on Windows. 

Beta software update site: http://ccw.cgrand.net/updatesite-betas/

Also, when looking at the stacktrace for an error, is there any easy way to jump to the source/line of the problem?  Are there ways to look at the values of the locals at the time of the crash?

You can add a breakpoint triggered by the raise of an exception, and then use the debugger views to explore the stack locals. 

There is currently no hyperlink for jumping to the right file from the printed stack trace. 


Thanks,

Mark

--
You received this message because you are subscribed to the Google Groups "counterclockwise-users" group.
To view this discussion on the web visit https://groups.google.com/d/msg/clojuredev-users/-/KIqhVQprTNcJ.
To post to this group, send email to clojured...@googlegroups.com.
To unsubscribe from this group, send email to clojuredev-use...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/clojuredev-users?hl=en.

Clinton Foster

unread,
Dec 13, 2012, 12:13:22 PM12/13/12
to clojured...@googlegroups.com
Rather than requiring a special key shouldn't the docstring for a function be displayed when hovering over its name (similar to the way Javadoc is displayed for Java classes and methods)?

BTW, I tried using Cmd-Alt-Space but at least in Mountain Lion it seems to be mapped by the operating system to something else.

Laurent PETIT

unread,
Dec 15, 2012, 1:49:53 AM12/15/12
to clojured...@googlegroups.com
2012/12/13 Clinton Foster <clinton...@viasat.com>

Rather than requiring a special key shouldn't the docstring for a function be displayed when hovering over its name (similar to the way Javadoc is displayed for Java classes and methods)?

Sure. This feature keeps being postponed. Do you feel like opening a separate issue for it?
 
BTW, I tried using Cmd-Alt-Space but at least in Mountain Lion it seems to be mapped by the operating system to something else.

I just checked an in my Eclipse configuration, command "context information" when "In dialogs and windows" is bound to Shift+Ctrl+Space in OSX Lion (Eclipse > Preferences > General > Keys)
 

On Friday, August 17, 2012 9:54:50 AM UTC-7, laurent.petit wrote:
Le 17 août 2012 à 10:10, Mark Engelberg <mark.en...@gmail.com> a écrit :

Are there key bindings to see the docstring or params for a given function?  (I see docstrings when I do auto-completion, but don't know how to access it when just browsing code).


In the beta channel, this feature exists and is activable via a shortcut similar to the one found in the java editor: cmd-alt-space on Mac, Ctrl-alt-space (or is it shit-alt-space ?) on Windows. 

Beta software update site: http://ccw.cgrand.net/updatesite-betas/

Also, when looking at the stacktrace for an error, is there any easy way to jump to the source/line of the problem?  Are there ways to look at the values of the locals at the time of the crash?

You can add a breakpoint triggered by the raise of an exception, and then use the debugger views to explore the stack locals. 

There is currently no hyperlink for jumping to the right file from the printed stack trace. 


Thanks,

Mark

--
You received this message because you are subscribed to the Google Groups "counterclockwise-users" group.
To view this discussion on the web visit https://groups.google.com/d/msg/clojuredev-users/-/KIqhVQprTNcJ.
To post to this group, send email to clojured...@googlegroups.com.
To unsubscribe from this group, send email to clojuredev-use...@googlegroups.com.

For more options, visit this group at http://groups.google.com/group/clojuredev-users?hl=en.

--
You received this message because you are subscribed to the Google Groups "counterclockwise-users" group.
To view this discussion on the web visit https://groups.google.com/d/msg/clojuredev-users/-/yt1q-I6BdeEJ.

fmj...@gmail.com

unread,
Dec 16, 2012, 11:17:45 AM12/16/12
to clojured...@googlegroups.com

On Saturday, December 15, 2012 7:49:53 AM UTC+1, laurent.petit wrote:
2012/12/13 Clinton Foster <clinton...@viasat.com>
Rather than requiring a special key shouldn't the docstring for a function be displayed when hovering over its name (similar to the way Javadoc is displayed for Java classes and methods)?

Sure. This feature keeps being postponed. Do you feel like opening a separate issue for it?

I just did:
Issue 492 
Reply all
Reply to author
Forward
0 new messages