You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Sep 9, 2024. It is now read-only.
Copy file name to clipboardExpand all lines: README.md
+10Lines changed: 10 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -19,6 +19,16 @@ Open up any .huff file and press `Load Interface` to prepare external functions,
19
19
20
20
The example above is for an erc721 mint function, entering from the function debugger will allow you to step through execution from the MAIN entrypoint. To select another function, click the drop down and select another function! The drop down will be populated with functions that are defined at the top of the file that you are currently debugging.
21
21
22
+
**Notice - *Relevant to WSL users***
23
+
To get the extension to run in wsl there is a workaround that you will have to make. Unfortunately, vscode extensions do not run in the same environment as your wsl shell so do not have access to the same path (even when mounted with wsl-remote). If the extension detects that you are working in a remote code space it will attempt to execute huffc and hevm within the wsl shell. The wsl api does not run the ~/.bashrc script (the file which huffup adds to the path), therefore to use this extension in wsl you will have to copy the following into your ~/.profile.
24
+
```
25
+
if [ -d "$HOME/.huff/bin" ]; then
26
+
PATH="$HOME/.huff/bin:$PATH"
27
+
fi
28
+
```
29
+
We will look to address this limitation in further releases of huffup.
30
+
31
+
22
32
### Macro Debugging
23
33
Macro debugging is the tool's most useful feature. Clicking `Load Macros` will load the macros of the currently open file.
24
34
If the macro has no `takes` arguments then the window will look like this:
0 commit comments