Project

pry-fkeys

0.0
No commit activity in last 3 years
No release in over 3 years
Help the user get to a place where the speedy F8/F10/F11/etc keys work. == Pry F-Keys [+F4+] ls -l (show all locally-defined variables and values) [+F5+] whereami (show the code context) [+F6+] up (a frame, depends on pry-stack_explorer, as does the next one) [+F7+] down [+F8+] continue (depends on pry-debugger, as do step/next/finish) [+Shift-F8+] try-again (restart from last 'raise', depends on pry-rescue) [+F10+] next (run the current statement) [+F11+] step (step into the next method call) [+Shift-F11+] finish (get back out of the last 'step')
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
2025
 Dependencies

Runtime

>= 0
 Project Readme

pry-fkeys¶ ↑

Help the user get to a place where the speedy F8/F10/F11/etc keys work.

At some point, it might be fully automated. For now, it just warns when:

  • The weaksauce ‘EditLine’ Readline is used instead of the GNU Readline one,

  • The F-key bindings are not in ~/.inputrc

The Shortcuts¶ ↑

F4

ls -l (show all locally-defined variables and values)

F5

whereami (show the code context)

F6

up (a frame, depends on pry-stack_explorer, as does the next one)

F7

down

F8

continue (depends on pry-debugger, as do step/next/finish)

Shift-F8

try-again (restart from last ‘raise’, depends on pry-rescue)

F10

next (run the current statement)

F11

step (step into the next method call)

Shift-F11

finish (get back out of the last ‘step’)

Why It’s Internals Are Ugly¶ ↑

Because it supports vi and emacs keys, in a few different terminal mappings.

Actually¶ ↑

It turns out you can configure EditLine. If anyone wants to tackle that, let me know and I’ll definitely include your work.