From 20f28abb4754164f17867fe40dec547c9db94dba Mon Sep 17 00:00:00 2001 From: David Baker Date: Wed, 21 May 2025 13:00:45 +0100 Subject: [PATCH] prettier --- docs/debugging.md | 10 +++++++--- 1 file changed, 7 insertions(+), 3 deletions(-) diff --git a/docs/debugging.md b/docs/debugging.md index a028c88c..0cbab968 100644 --- a/docs/debugging.md +++ b/docs/debugging.md @@ -3,18 +3,22 @@ There are two parts of the desktop app that you might want to debug. ## The renderer process + This is the regular element-web codeand can be debugged by just selecting 'toggle developer tools' from the menu, even on ppackaged builds. This then works the same as chrome dev tools for element web. ## The main process + This is debugged as a node app, so: - 1. Open any chrome dev tools window - 1. Start element with the `--inspect-brk` flag - 1. Notice that you now have a little green icon in the top left of your chrome devtools window, click it. + +1. Open any chrome dev tools window +1. Start element with the `--inspect-brk` flag +1. Notice that you now have a little green icon in the top left of your chrome devtools window, click it. You are now debugging the code of the desktop app itself. ## The main process of a package app + When the app is shipped, electron's "fuses" are flipped, editing the electron binary itself to prevent certain features from being usable, one of which is debugging using `--inspect-brk` as above. You can flip the fuse back on Linux as follows: ```