[ci skip] automated comment issue creation and tag+archive page generation

Author: y8z

_posts/2024-03-11-mac_mouse_gesture.md

@@ -0,0 +1,25 @@
+---
+layout: post
+title: Mouse gesture on Mac
+subtitle:
+tags: [Mac, software, tool]
+author: Yuanpeng Zhang
+comments: true
+use_math: true
+---
+
+On Windows, we have software like `AutoHotkey` with which we can define keyboard shortcut for running various actions in a convenient way. With `AutoHotkey`, we can also define mouse gestures to execute actions quickly. Here in Ref. [1] is provided a zip file containing the `AutoHotkey` files for some useful shortcuts and mouse gestures on Windows.
+
+> With `AutoHotkey`, one weird observation is that sometimes, if we define shortcuts involving the `Ctrl` key, the simulated or physically press of `Ctrl` key will not be released. I am still not finding the solution to this issue, so in the version of `AutoHotkey` file provided above, I am not including any definition of shortcuts involving the `Ctrl` key.
+
+On Mac, though, there is not such a single-shot solution to define mouse gestures in a convenient manner, at least I am not seeing any
+products on the market for such a purpose. However, there are some software, which, when put together, can realize somewhat what we need. The `Mac Mouse Fix` software [2] provides some tweaking capability for several of the alternative mouse buttons, including the middle button and some other available buttons on some mouse. The functionality is a bit limited but it can definitely make the use of normal mouse other than the Mac magic mouse more convenient and productive. Another useful software coming into the loop is called `MacGesture` [3], with which we can define some basic mouse operations, though, still limited, to realize some commonly executed actions, such as closing browser tab, moving forward and backward, scroll to the bottom and top of the page, etc. The combination of the two software mentioned here does make the using of normal mouse on Mac more convenient.
+
+References
+===
+
+[1] [https://yr.iris-home.net/mousegestureautohotkey](https://yr.iris-home.net/mousegestureautohotkey)
+
+[2] [https://macmousefix.com/](https://macmousefix.com/)
+
+[3] [https://github.com/MacGesture/MacGesture](https://github.com/MacGesture/MacGesture)

_posts/2024-03-11-vscode_python_debugger.md

@@ -0,0 +1,29 @@
+---
+layout: post
+title: Run Python Debugger in VSCode
+subtitle:
+tags: [IDE, software, tool, VSCode]
+author: Yuanpeng Zhang
+comments: true
+use_math: true
+---
+
+Running the debug mode for coding in IDE is a very convenient feature, as we can put in break points and check variables in our program without killing the running process. In `VSCode`, to run the debug mode - here I am taking Python as the example - we need to first download the debugger extension. For Python debugger, we can just search in the extension sore within `VSCode` and we should be able to find the Python debugger listed to be installed. Once installed, we can go to the `Run and Debug` option in the left sidebar and try to run the program in the debug mode. Initially, it will ask us to populate the configuration file, if we have never used the debug before, as shown [here](https://code.visualstudio.com/assets/docs/python/debugging/debug-start.png). Clicking on the link as shown in the picture, we will be brought up with the configuration JSON file to populate. We can put something like below in the file,
+
+```json
+{
+    "version": "0.2.0",
+    "configurations": [
+        {
+            "name": "Python Debugger: Current File",
+            "type": "debugpy",
+            "request": "launch",
+            "python": "/Users/y8z/opt/anaconda3/envs/g2python311/bin/python",
+            "program": "GSASII.py",
+            "console": "integratedTerminal"
+        }
+    ]
+}
+```
+
+Here, the `program` option will specify the relative path (with respective to the workspace folder) to the main Python file to be executed. By default, the `python` entry will not be created but it is actually necessary as it specifies the full path to the Python executable (which then determines which environment we will be using) to be used for running the Python script. Once all the entries above are populated properly, we can then hit the `Run` button in the `Run and Debug` option to start the debug mode. Here, we can first insert some breakpoints in our codes (by clicking on the left edge of the editor corresponding to a certain like and red circle will be shown to indicate the breakpoints). Then when the running program hits the breakpoint, it will bump into the debug mode, allowing us to bring up the command console -- we can use ``` ctrl+` ``` to bring up the terminal panel where we can find the `DEBUG CONSOLE` among the top option tabs in the terminal panel. We can also go to the top part of the editor to find the several options to control the flow of the debug mode, e.g., to move forward, i.e., to skip the current break point.