This is fantastic. This is why I think non-professional programmers could (and maybe sometimes should) learn to code - to solve little (or larger) problems bugging them.
You might be interested in Emacs, which is an environment for manipulating text and creating text-based workflows using a pretty nifty language called Emacs Lisp disguised as a text editor. ;-) (Full disclosure: I am an author of an Emacs Lisp textbook, and a long-time user and fan of Emacs.)
And here is a somewhat famous relevant quote from rms:
> Multics Emacs proved to be a great success—programming new editing commands was so convenient that even the secretaries in his office started learning how to use it. They used a manual someone had written which showed how to extend Emacs, but didn't say it was a programming. So the secretaries, who believed they couldn't do programming, weren't scared off. They read the manual, discovered they could do useful things and they learned to program. (https://www.gnu.org/gnu/rms-lisp.html)
You might be interested in Emacs, which is an environment for manipulating text and creating text-based workflows using a pretty nifty language called Emacs Lisp disguised as a text editor. ;-) (Full disclosure: I am an author of an Emacs Lisp textbook, and a long-time user and fan of Emacs.)
And here is a somewhat famous relevant quote from rms:
> Multics Emacs proved to be a great success—programming new editing commands was so convenient that even the secretaries in his office started learning how to use it. They used a manual someone had written which showed how to extend Emacs, but didn't say it was a programming. So the secretaries, who believed they couldn't do programming, weren't scared off. They read the manual, discovered they could do useful things and they learned to program. (https://www.gnu.org/gnu/rms-lisp.html)