如何在PyCharm交互式Shell中快速将最后执行命令移至脚本？

Absolutely—this workflow is totally doable, and there are a few practical ways to set it up on your Mac without relying on manual copy-paste or digging through history panels. Here are tailored solutions to fit different tooling preferences:

Option 1: Automator Quick Action (No Third-Party Tools) #

Mac's built-in Automator lets you build a custom service to bridge your console and text editor with a single shortcut:

1. Open Automator and create a new Quick Action.
2. Set the workflow to receive no input in any application.
3. Add these actions in sequence:
   • Run AppleScript: Grab the last executed line from your terminal (adjust for Terminal or iTerm):

     tell application "Terminal"
         -- Fetch last command from history
         do script "history | tail -n 1 | sed 's/^[0-9]* //' | pbcopy" in front window
         delay 0.3 -- Give time for clipboard to update
     end tell
     

   • Run AppleScript: Append the clipboard content to your active editor window (example for VS Code; tweak for your editor):

     tell application "Visual Studio Code"
         activate
         tell application "System Events"
             keystroke "v" using {command down, option down} -- VS Code shortcut to paste at end of file
         end tell
     end tell
     

4. Save the Quick Action (name it something like "Append Last Console Line").
5. Head to System Preferences > Keyboard > Shortcuts > Services, find your new service, and assign a custom shortcut (e.g., Shift+Cmd+E).

Note: You’ll need to enable accessibility permissions for Automator in System Preferences > Security & Privacy > Privacy > Accessibility.

Option 2: Alfred Workflow (More Flexible, Third-Party) #

If you already use Alfred (a popular Mac productivity tool), this is a streamlined approach:

1. Open Alfred Preferences, go to Workflows, and create a blank workflow.
2. Add a Hotkey trigger and assign your desired shortcut.
3. Add a Run Script action with this bash code to capture the last command:

   last_cmd=$(history | tail -n 1 | sed 's/^[0-9]* //')
   echo "$last_cmd" | pbcopy
   

4. Add another Run Script action to paste the line into your editor (VS Code example):

   osascript -e 'tell application "Visual Studio Code" to activate' \
   -e 'tell application "System Events" to keystroke "v" using {command down, option down}'
   

5. Connect the trigger to both scripts, save the workflow, and test your shortcut.

Option 3: Custom Shell Function + Terminal Shortcut #

If you prefer staying in the terminal, define a shell function to send the last command directly to your editor:

1. Open your shell config file (e.g., ~/.zshrc for Zsh or ~/.bashrc for Bash).
2. Add this function (adjust the editor path/commands as needed):

   append_last_to_file() {
       last_cmd=$(history | tail -n 1 | sed 's/^[0-9]* //')
       # Send to active VS Code document
       echo "$last_cmd" >> "$(osascript -e 'tell application "Visual Studio Code" to get path of active document')"
   }
   

3. Source the config file (source ~/.zshrc), then assign a keyboard shortcut to run this function via your terminal’s shortcut settings.

All these methods eliminate the tedious steps you want to avoid, letting you append the last executed console line to your open file with a single keystroke. Pick the one that fits your existing workflow best!

内容的提问来源于stack exchange，提问作者Jae Carr