#1

Integrated text expander has been a popular feature request in the community (1, 2, 3, etc.). I am glad to say it is no longer a feature request, as I implemented a plugin providing the requested functionality.

obsidian-text-expander-demo
obsidian-text-expander-demo600×658 3.17 MB

Currently, the plugin fully supports Linux and MacOS.

Features:

  • instant replacement on Tab hit
  • regex triggers, allowing triggers to have arbitrary format: arguments or any custom syntax
  • shell-powered, i.e. your scripts can do anything that shell supports, e.g. extract current clipboard or somehow parse your vault

Possible future features:

  • setting cursor positions after replacement
  • special syntax for render-time evaluation
  • at least partial Windows support
  • hotkeys as triggers
6 Likes
Shell commands plugin
#2

I thank @akaalias for his PoC version of text expander and Christian Vasquez for the Run Snippets plugin. I definitely borrowed some elements from both of the plugins.

(I met a link count restriction, so a separate post.)

1 Like
#3

Awesome! Thank you for the shout-out, will give your plugin a spin right away :smiley:

Mac: text replacements do not work in Obsidian
#4

Howdy!

I’ve been playing with your plugin and am banging my head on something that’s probably fairly obvious.

I’m trying to get a snippet to convert the current Obsidian note to a PDF using pandoc.

However, when I try anything that starts with {{shell:pandoc … }} all I get is an error “command not found”

The code works fine when I run it through the terminal, so I know I have pandoc installed correctly and am using the right syntax.

Am I missing something here?

Thank you!

#5

could you paste or share you’re complete call? it should be a simple problem with spaces, quotes or paths.