home.social

#autokey — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #autokey, aggregated by home.social.

fetched live
  1. #Espanso doesn't work correctly with the Flatpack version of KDE Kate text editor on Cinnamon Mint using X1 (at least for me). If I have a trigger of 'ofc' it should expand that to 'of course'. Except it's more likely to produce 'of cuor se' or 'ofc oseur'.

    #AutoKey (different from AutoHotKey) does the same if I choose "keyboard" as the entry method, but it has other methods to add text: three clipboard ones (Ctrl+V, Ctrl+Shift+V, Shift+Insert), plus Mouse Selection (which does nothing).

    Downside is that every text expansion I do then ends up cluttering the clipboard history utility I use, #CopyQ. So I had to define some hotkeys in that to toggle clipboard storing, and mostly run with CopyQ inactive until I needed it.

    And it's frankly a pain to add expansions to AutoKey.
    As an example:

    Ctrl+N to start a new entry
    type in "everyone" as its name
    click in the expansion box (can't even tab to it)
    Backspace out "Enter phrase contents"
    type in "everyone" as its contents
    Mouse down to Paste Using
    Select "Shift+Insert"
    Mouse down more to Abbreviations: Set
    Click "Add" in the popup
    type "e1" and hit Enter
    Click "Match phrase case to typed abbreviation"
    Click "OK"
    Ctrl+S to save entry

    That's thirteen steps to add an entry, compare to editing a single text file in Espanso and adding

    trigger: "e1"
    replace: "everyone"

    Though that basic entry would always produce "everyone" and not "Everyone" when I type "E1" instead of "e1".

    AutoKey does have text files, but it's one per entry, which is not remotely as convenient.

  2. #Espanso doesn't work correctly with the Flatpack version of KDE Kate text editor on Cinnamon Mint using X1 (at least for me). If I have a trigger of 'ofc' it should expand that to 'of course'. Except it's more likely to produce 'of cuor se' or 'ofc oseur'.

    #AutoKey (different from AutoHotKey) does the same if I choose "keyboard" as the entry method, but it has other methods to add text: three clipboard ones (Ctrl+V, Ctrl+Shift+V, Shift+Insert), plus Mouse Selection (which does nothing).

    Downside is that every text expansion I do then ends up cluttering the clipboard history utility I use, #CopyQ. So I had to define some hotkeys in that to toggle clipboard storing, and mostly run with CopyQ inactive until I needed it.

    And it's frankly a pain to add expansions to AutoKey.
    As an example:

    Ctrl+N to start a new entry
    type in "everyone" as its name
    click in the expansion box (can't even tab to it)
    Backspace out "Enter phrase contents"
    type in "everyone" as its contents
    Mouse down to Paste Using
    Select "Shift+Insert"
    Mouse down more to Abbreviations: Set
    Click "Add" in the popup
    type "e1" and hit Enter
    Click "Match phrase case to typed abbreviation"
    Click "OK"
    Ctrl+S to save entry

    That's thirteen steps to add an entry, compare to editing a single text file in Espanso and adding

    trigger: "e1"
    replace: "everyone"

    Though that basic entry would always produce "everyone" and not "Everyone" when I type "E1" instead of "e1".

    AutoKey does have text files, but it's one per entry, which is not remotely as convenient.

  3. #Espanso doesn't work correctly with the Flatpack version of KDE Kate text editor on Cinnamon Mint using X1 (at least for me). If I have a trigger of 'ofc' it should expand that to 'of course'. Except it's more likely to produce 'of cuor se' or 'ofc oseur'.

    #AutoKey (different from AutoHotKey) does the same if I choose "keyboard" as the entry method, but it has other methods to add text: three clipboard ones (Ctrl+V, Ctrl+Shift+V, Shift+Insert), plus Mouse Selection (which does nothing).

    Downside is that every text expansion I do then ends up cluttering the clipboard history utility I use, #CopyQ. So I had to define some hotkeys in that to toggle clipboard storing, and mostly run with CopyQ inactive until I needed it.

    And it's frankly a pain to add expansions to AutoKey.
    As an example:

    Ctrl+N to start a new entry
    type in "everyone" as its name
    click in the expansion box (can't even tab to it)
    Backspace out "Enter phrase contents"
    type in "everyone" as its contents
    Mouse down to Paste Using
    Select "Shift+Insert"
    Mouse down more to Abbreviations: Set
    Click "Add" in the popup
    type "e1" and hit Enter
    Click "Match phrase case to typed abbreviation"
    Click "OK"
    Ctrl+S to save entry

    That's thirteen steps to add an entry, compare to editing a single text file in Espanso and adding

    trigger: "e1"
    replace: "everyone"

    Though that basic entry would always produce "everyone" and not "Everyone" when I type "E1" instead of "e1".

    AutoKey does have text files, but it's one per entry, which is not remotely as convenient.

  4. #Espanso doesn't work correctly with the Flatpack version of KDE Kate text editor on Cinnamon Mint using X1 (at least for me). If I have a trigger of 'ofc' it should expand that to 'of course'. Except it's more likely to produce 'of cuor se' or 'ofc oseur'.

    #AutoKey (different from AutoHotKey) does the same if I choose "keyboard" as the entry method, but it has other methods to add text: three clipboard ones (Ctrl+V, Ctrl+Shift+V, Shift+Insert), plus Mouse Selection (which does nothing).

    Downside is that every text expansion I do then ends up cluttering the clipboard history utility I use, #CopyQ. So I had to define some hotkeys in that to toggle clipboard storing, and mostly run with CopyQ inactive until I needed it.

    And it's frankly a pain to add expansions to AutoKey.
    As an example:

    Ctrl+N to start a new entry
    type in "everyone" as its name
    click in the expansion box (can't even tab to it)
    Backspace out "Enter phrase contents"
    type in "everyone" as its contents
    Mouse down to Paste Using
    Select "Shift+Insert"
    Mouse down more to Abbreviations: Set
    Click "Add" in the popup
    type "e1" and hit Enter
    Click "Match phrase case to typed abbreviation"
    Click "OK"
    Ctrl+S to save entry

    That's thirteen steps to add an entry, compare to editing a single text file in Espanso and adding

    trigger: "e1"
    replace: "everyone"

    Though that basic entry would always produce "everyone" and not "Everyone" when I type "E1" instead of "e1".

    AutoKey does have text files, but it's one per entry, which is not remotely as convenient.

  5. #Espanso doesn't work correctly with the Flatpack version of KDE Kate text editor on Cinnamon Mint using X1 (at least for me). If I have a trigger of 'ofc' it should expand that to 'of course'. Except it's more likely to produce 'of cuor se' or 'ofc oseur'.

    #AutoKey (different from AutoHotKey) does the same if I choose "keyboard" as the entry method, but it has other methods to add text: three clipboard ones (Ctrl+V, Ctrl+Shift+V, Shift+Insert), plus Mouse Selection (which does nothing).

    Downside is that every text expansion I do then ends up cluttering the clipboard history utility I use, #CopyQ. So I had to define some hotkeys in that to toggle clipboard storing, and mostly run with CopyQ inactive until I needed it.

    And it's frankly a pain to add expansions to AutoKey.
    As an example:

    Ctrl+N to start a new entry
    type in "everyone" as its name
    click in the expansion box (can't even tab to it)
    Backspace out "Enter phrase contents"
    type in "everyone" as its contents
    Mouse down to Paste Using
    Select "Shift+Insert"
    Mouse down more to Abbreviations: Set
    Click "Add" in the popup
    type "e1" and hit Enter
    Click "Match phrase case to typed abbreviation"
    Click "OK"
    Ctrl+S to save entry

    That's thirteen steps to add an entry, compare to editing a single text file in Espanso and adding

    trigger: "e1"
    replace: "everyone"

    Though that basic entry would always produce "everyone" and not "Everyone" when I type "E1" instead of "e1".

    AutoKey does have text files, but it's one per entry, which is not remotely as convenient.

  6. @Zenie @jbaty Giving up #TextExpander was the final, biggest obstacle to transitioning to Linux from MacOS eight or ten years ago. #AutoKey did the job under X, mostly, and #Espanso works sometimes under Wayland but only after a sojourn in config hell. But neither has ever been reliable. It must be a difficult problem space because it just doesn't ever work.

    The vast majority of my snippets are for composing email, so I moved them to #yasnippet after I loved to #mu4e. And #Emacs has never let me down.

    But that leaves tons of stuff in the browser where one is left just to muddle through.

  7. @Zenie @jbaty Giving up #TextExpander was the final, biggest obstacle to transitioning to Linux from MacOS eight or ten years ago. #AutoKey did the job under X, mostly, and #Espanso works sometimes under Wayland but only after a sojourn in config hell. But neither has ever been reliable. It must be a difficult problem space because it just doesn't ever work.

    The vast majority of my snippets are for composing email, so I moved them to #yasnippet after I loved to #mu4e. And #Emacs has never let me down.

    But that leaves tons of stuff in the browser where one is left just to muddle through.

  8. @Zenie @jbaty Giving up #TextExpander was the final, biggest obstacle to transitioning to Linux from MacOS eight or ten years ago. #AutoKey did the job under X, mostly, and #Espanso works sometimes under Wayland but only after a sojourn in config hell. But neither has ever been reliable. It must be a difficult problem space because it just doesn't ever work.

    The vast majority of my snippets are for composing email, so I moved them to #yasnippet after I loved to #mu4e. And #Emacs has never let me down.

    But that leaves tons of stuff in the browser where one is left just to muddle through.

  9. @Zenie @jbaty Giving up #TextExpander was the final, biggest obstacle to transitioning to Linux from MacOS eight or ten years ago. #AutoKey did the job under X, mostly, and #Espanso works sometimes under Wayland but only after a sojourn in config hell. But neither has ever been reliable. It must be a difficult problem space because it just doesn't ever work.

    The vast majority of my snippets are for composing email, so I moved them to #yasnippet after I loved to #mu4e. And #Emacs has never let me down.

    But that leaves tons of stuff in the browser where one is left just to muddle through.

  10. @Zenie @jbaty Giving up #TextExpander was the final, biggest obstacle to transitioning to Linux from MacOS eight or ten years ago. #AutoKey did the job under X, mostly, and #Espanso works sometimes under Wayland but only after a sojourn in config hell. But neither has ever been reliable. It must be a difficult problem space because it just doesn't ever work.

    The vast majority of my snippets are for composing email, so I moved them to #yasnippet after I loved to #mu4e. And #Emacs has never let me down.

    But that leaves tons of stuff in the browser where one is left just to muddle through.

  11. #AutoKey

    Created a 'sqlite_bookbiz_readonly' as well as 'sqlite_bookbiz' scripts.

    Downloadable

    sqlite_bookbiz.py
    drive.proton.me/urls/NE5996N47

    sqlite_bookbiz_readonly.py
    drive.proton.me/urls/X4W3HBZ4Y

  12. #AutoKey

    Created a 'sqlite_bookbiz_readonly' as well as 'sqlite_bookbiz' scripts.

    Downloadable

    sqlite_bookbiz.py
    drive.proton.me/urls/NE5996N47

    sqlite_bookbiz_readonly.py
    drive.proton.me/urls/X4W3HBZ4Y

  13. I've summarized my settings and customization of my desktop using #GNOME48 (from #Debian13 #Trixie) on karl-voit.at/Gnome-Setup/

    Including:
    - my choice of #GNOME Extensions
    - custom scripts in "Files" (#Nautilus) incl. keyboard shortcuts
    - most settings can be easily set by gseetings in your shell without requiring Settings or Tweaks UI
    - list of current bugs relevant to me

    Still missing:
    - Working text snippets like #AutoKey or #AHK

    #publicvoit #PIM #Debian

  14. I've summarized my settings and customization of my desktop using #GNOME48 (from #Debian13 #Trixie) on karl-voit.at/Gnome-Setup/

    Including:
    - my choice of #GNOME Extensions
    - custom scripts in "Files" (#Nautilus) incl. keyboard shortcuts
    - most settings can be easily set by gseetings in your shell without requiring Settings or Tweaks UI
    - list of current bugs relevant to me

    Still missing:
    - Working text snippets like #AutoKey or #AHK

    #publicvoit #PIM #Debian

  15. I've summarized my settings and customization of my desktop using #GNOME48 (from #Debian13 #Trixie) on karl-voit.at/Gnome-Setup/

    Including:
    - my choice of #GNOME Extensions
    - custom scripts in "Files" (#Nautilus) incl. keyboard shortcuts
    - most settings can be easily set by gseetings in your shell without requiring Settings or Tweaks UI
    - list of current bugs relevant to me

    Still missing:
    - Working text snippets like #AutoKey or #AHK

    #publicvoit #PIM #Debian

  16. I've summarized my settings and customization of my desktop using #GNOME48 (from #Debian13 #Trixie) on karl-voit.at/Gnome-Setup/

    Including:
    - my choice of #GNOME Extensions
    - custom scripts in "Files" (#Nautilus) incl. keyboard shortcuts
    - most settings can be easily set by gseetings in your shell without requiring Settings or Tweaks UI
    - list of current bugs relevant to me

    Still missing:
    - Working text snippets like #AutoKey or #AHK

    #publicvoit #PIM #Debian

  17. I've summarized my settings and customization of my desktop using #GNOME48 (from #Debian13 #Trixie) on karl-voit.at/Gnome-Setup/

    Including:
    - my choice of #GNOME Extensions
    - custom scripts in "Files" (#Nautilus) incl. keyboard shortcuts
    - most settings can be easily set by gseetings in your shell without requiring Settings or Tweaks UI
    - list of current bugs relevant to me

    Still missing:
    - Working text snippets like #AutoKey or #AHK

    #publicvoit #PIM #Debian

  18. TRIUMPH! The LAST and FINAL thing holding me back from completely moving to #Wayland was replacing #AutoKey for text expansion.

    #espanso appears to replace all the functionality (at least that I use, although the scripting is not via Python). Happy!

    NOTE! DEBIAN USERS! If you follow the instructions on the installation page, you get an old release that has dependency issues. Download the LATEST RELEASE 2.2.3 of the Wayland .deb

    github.com/espanso/espanso/rel

    and then follow the installation instructions:

    espanso.org/docs/install/linux

  19. TRIUMPH! The LAST and FINAL thing holding me back from completely moving to #Wayland was replacing #AutoKey for text expansion.

    #espanso appears to replace all the functionality (at least that I use, although the scripting is not via Python). Happy!

    NOTE! DEBIAN USERS! If you follow the instructions on the installation page, you get an old release that has dependency issues. Download the LATEST RELEASE 2.2.3 of the Wayland .deb

    github.com/espanso/espanso/rel

    and then follow the installation instructions:

    espanso.org/docs/install/linux

  20. TRIUMPH! The LAST and FINAL thing holding me back from completely moving to #Wayland was replacing #AutoKey for text expansion.

    #espanso appears to replace all the functionality (at least that I use, although the scripting is not via Python). Happy!

    NOTE! DEBIAN USERS! If you follow the instructions on the installation page, you get an old release that has dependency issues. Download the LATEST RELEASE 2.2.3 of the Wayland .deb

    github.com/espanso/espanso/rel

    and then follow the installation instructions:

    espanso.org/docs/install/linux

  21. TRIUMPH! The LAST and FINAL thing holding me back from completely moving to #Wayland was replacing #AutoKey for text expansion.

    #espanso appears to replace all the functionality (at least that I use, although the scripting is not via Python). Happy!

    NOTE! DEBIAN USERS! If you follow the instructions on the installation page, you get an old release that has dependency issues. Download the LATEST RELEASE 2.2.3 of the Wayland .deb

    github.com/espanso/espanso/rel

    and then follow the installation instructions:

    espanso.org/docs/install/linux

  22. TRIUMPH! The LAST and FINAL thing holding me back from completely moving to #Wayland was replacing #AutoKey for text expansion.

    #espanso appears to replace all the functionality (at least that I use, although the scripting is not via Python). Happy!

    NOTE! DEBIAN USERS! If you follow the instructions on the installation page, you get an old release that has dependency issues. Download the LATEST RELEASE 2.2.3 of the Wayland .deb

    github.com/espanso/espanso/rel

    and then follow the installation instructions:

    espanso.org/docs/install/linux

  23. can someone tell me, how to get #AutoKey (installed appstream://autokey-gtk.desktop) from Discover working in all windows in #Neon #KDE?

    It works in Google Chrome, but not in #Thunderbird (which would be 95% of my usage) or Kate.

    #Linux #linuxproblems

  24. can someone tell me, how to get #AutoKey (installed appstream://autokey-gtk.desktop) from Discover working in all windows in #Neon #KDE?

    It works in Google Chrome, but not in #Thunderbird (which would be 95% of my usage) or Kate.

    #Linux #linuxproblems

  25. can someone tell me, how to get #AutoKey (installed appstream://autokey-gtk.desktop) from Discover working in all windows in #Neon #KDE?

    It works in Google Chrome, but not in #Thunderbird (which would be 95% of my usage) or Kate.

    #Linux #linuxproblems

  26. can someone tell me, how to get #AutoKey (installed appstream://autokey-gtk.desktop) from Discover working in all windows in #Neon #KDE?

    It works in Google Chrome, but not in #Thunderbird (which would be 95% of my usage) or Kate.

    #Linux #linuxproblems

  27. The PC is now running #Garuda #Linux, which means it's still running #ArchLinux. However, some oddities are annoying. #luakit doesn't want to learn other search engines, but what's particularly annoying is that abbreviations, or letter shortcuts, can no longer be defined with #autokey. When I click "OK" in the corresponding dialog window, nothing happens. Hotkeys, however, can be configured. I don't get it. #Arch

  28. The PC is now running #Garuda #Linux, which means it's still running #ArchLinux. However, some oddities are annoying. #luakit doesn't want to learn other search engines, but what's particularly annoying is that abbreviations, or letter shortcuts, can no longer be defined with #autokey. When I click "OK" in the corresponding dialog window, nothing happens. Hotkeys, however, can be configured. I don't get it. #Arch

  29. Der PC läuft nun mit #Garuda #Linux, also weiterhin mit #ArchLinux. Einige Merkwürdigkeiten nerven jedoch. #luakit will keine anderen Suchmaschinen lernen, aber besonders übel ist, dass sich bei #autokey keine Abbreviations, also Buchstabenkürzel, mehr definieren lassen. Beim Klick auf "OK" im zugehörigen Dialogfenster passiert einfach nichts. Hotkeys hingegen lassen sich einstellen. Kapiere ich nicht. #Arch

  30. Der PC läuft nun mit #Garuda #Linux, also weiterhin mit #ArchLinux. Einige Merkwürdigkeiten nerven jedoch. #luakit will keine anderen Suchmaschinen lernen, aber besonders übel ist, dass sich bei #autokey keine Abbreviations, also Buchstabenkürzel, mehr definieren lassen. Beim Klick auf "OK" im zugehörigen Dialogfenster passiert einfach nichts. Hotkeys hingegen lassen sich einstellen. Kapiere ich nicht. #Arch

  31. @bricabrac
    Ich nutze dafür, ebenfalls nach meinem Umstieg von Windows, seit Jahren #Autokey. Meines Wissen in allen Distributionen erhältlich. Es braucht als Basis autokey-common und dann je nach System autokey-qt oder autokey-gtk (nicht beides, sondern nur eins davon).

    github.com/autokey/autokey

  32. @bricabrac
    Ich nutze dafür, ebenfalls nach meinem Umstieg von Windows, seit Jahren #Autokey. Meines Wissen in allen Distributionen erhältlich. Es braucht als Basis autokey-common und dann je nach System autokey-qt oder autokey-gtk (nicht beides, sondern nur eins davon).

    github.com/autokey/autokey

  33. @bricabrac
    Ich nutze dafür, ebenfalls nach meinem Umstieg von Windows, seit Jahren #Autokey. Meines Wissen in allen Distributionen erhältlich. Es braucht als Basis autokey-common und dann je nach System autokey-qt oder autokey-gtk (nicht beides, sondern nur eins davon).

    github.com/autokey/autokey

  34. @maexchen1

    Okay, das ist dann eine generelle Textbausteinverwaltung, oder?

    Z.B. auf #Linux so etwas wie #AutoKey...

    @wikinaut

  35. @maexchen1

    Okay, das ist dann eine generelle Textbausteinverwaltung, oder?

    Z.B. auf #Linux so etwas wie #AutoKey...

    @wikinaut

  36. @maexchen1

    Okay, das ist dann eine generelle Textbausteinverwaltung, oder?

    Z.B. auf #Linux so etwas wie #AutoKey...

    @wikinaut

  37. @maexchen1

    Okay, das ist dann eine generelle Textbausteinverwaltung, oder?

    Z.B. auf #Linux so etwas wie #AutoKey...

    @wikinaut

  38. @maexchen1

    Okay, das ist dann eine generelle Textbausteinverwaltung, oder?

    Z.B. auf #Linux so etwas wie #AutoKey...

    @wikinaut

  39. 💡 #TIL there's another effort going on to bring inglorious

    #AutoHotkey to 🐧 GNU/‬#Linux!
    (#X11, that is.)

    Meet #AHK_X11 🥳

    🌐 github.com/phil294/AHK_X11
    📖 phil294.github.io/AHK_X11

    ☝️ Caveat: It only supports legacy #AHK 1.1 syntax and does not aim for 100% feature parity/compatibility, but should enable you to use most of your #hotkeys and #hotstrings #crossplattform! (Sync on your own).

    #scripting #automation #DesktopAutomation #KeyboardWarriors #xdotool #gtk #AutoIt #AutoKey #AlternativeTo

  40. 💡 #TIL there's another effort going on to bring inglorious

    #AutoHotkey to 🐧 GNU/‬#Linux!
    (#X11, that is.)

    Meet #AHK_X11 🥳

    🌐 github.com/phil294/AHK_X11
    📖 phil294.github.io/AHK_X11

    ☝️ Caveat: It only supports legacy #AHK 1.1 syntax and does not aim for 100% feature parity/compatibility, but should enable you to use most of your #hotkeys and #hotstrings #crossplattform! (Sync on your own).

    #scripting #automation #DesktopAutomation #KeyboardWarriors #xdotool #gtk #AutoIt #AutoKey #AlternativeTo

  41. 💡 #TIL there's another effort going on to bring inglorious

    #AutoHotkey to 🐧 GNU/‬#Linux!
    (#X11, that is.)

    Meet #AHK_X11 🥳

    🌐 github.com/phil294/AHK_X11
    📖 phil294.github.io/AHK_X11

    ☝️ Caveat: It only supports legacy #AHK 1.1 syntax and does not aim for 100% feature parity/compatibility, but should enable you to use most of your #hotkeys and #hotstrings #crossplattform! (Sync on your own).

    #scripting #automation #DesktopAutomation #KeyboardWarriors #xdotool #gtk #AutoIt #AutoKey #AlternativeTo

  42. 💡 #TIL there's another effort going on to bring inglorious

    #AutoHotkey to 🐧 GNU/‬#Linux!
    (#X11, that is.)

    Meet #AHK_X11 🥳

    🌐 github.com/phil294/AHK_X11
    📖 phil294.github.io/AHK_X11

    ☝️ Caveat: It only supports legacy #AHK 1.1 syntax and does not aim for 100% feature parity/compatibility, but should enable you to use most of your #hotkeys and #hotstrings #crossplattform! (Sync on your own).

    #scripting #automation #DesktopAutomation #KeyboardWarriors #xdotool #gtk #AutoIt #AutoKey #AlternativeTo

  43. 💡 #TIL there's another effort going on to bring inglorious

    #AutoHotkey to 🐧 GNU/‬#Linux!
    (#X11, that is.)

    Meet #AHK_X11 🥳

    🌐 github.com/phil294/AHK_X11
    📖 phil294.github.io/AHK_X11

    ☝️ Caveat: It only supports legacy #AHK 1.1 syntax and does not aim for 100% feature parity/compatibility, but should enable you to use most of your #hotkeys and #hotstrings #crossplattform! (Sync on your own).

    #scripting #automation #DesktopAutomation #KeyboardWarriors #xdotool #gtk #AutoIt #AutoKey #AlternativeTo

  44. Text Expander - Was ist das?

    Mit kurzen Phrasen und Hotkeys die tägliche Arbeit erleichtern. Ein Erfahrungsbericht.

    #Hotkey #Textersetzung #AutoKey #Espanso #Shortcut

    gnulinux.ch/text-expander-was-