summaryrefslogtreecommitdiff
path: root/doc/development/pry_debugging.md
diff options
context:
space:
mode:
Diffstat (limited to 'doc/development/pry_debugging.md')
-rw-r--r--doc/development/pry_debugging.md7
1 files changed, 5 insertions, 2 deletions
diff --git a/doc/development/pry_debugging.md b/doc/development/pry_debugging.md
index f29e0d403cd..d662e6bbc54 100644
--- a/doc/development/pry_debugging.md
+++ b/doc/development/pry_debugging.md
@@ -10,7 +10,10 @@ info: To determine the technical writer assigned to the Stage/Group associated w
To invoke the debugger, place `binding.pry` somewhere in your
code. When the Ruby interpreter hits that code, execution stops,
-and you can type in commands to debug the state of the program
+and you can type in commands to debug the state of the program.
+
+When debugging code in another process like Puma or Sidekiq, you can use `binding.remote_pry`.
+You can then connect to this session by running `pry-remote` from your terminal.
## `byebug` vs `binding.pry`
@@ -79,7 +82,7 @@ Similar to source browsing, is [Documentation browsing](https://github.com/pry/p
### Command history
-With **Ctrl+R** you can search your [command history](https://github.com/pry/pry/wiki/History).
+With <kbd>Control</kbd> + <kbd>R</kbd> you can search your [command history](https://github.com/pry/pry/wiki/History).
## Stepping