Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

How to run gui editor? #127

mxxcon opened this issue Oct 20, 2016 · 5 comments

How to run gui editor? #127

mxxcon opened this issue Oct 20, 2016 · 5 comments


Copy link

mxxcon commented Oct 20, 2016

It appears that I can't use gui-based editors such as Atom or Sublime with sops.
My .bash_profile contains export EDITOR=/usr/local/bin/atom
When I try to edit any sops-encrypted file I get something like:

mxx@MacBook-Pro:[~]: sops myfile.yaml
INFO: myfile.yaml doesn't exist, creating it.
INFO: generating and storing data encryption key
INFO: temp file created at /var/folders/b1/pwv5g6795fld3f0vt14kky_40000gp/T/tmpq6K2_D.yaml
PANIC: myfile.yaml has not been modified, exit without writing

A few sec later Atom opens up with that tmpq6K2_D.yaml file.
It is my understanding that this happens because gui editors open in a separate process outside of my terminal.
Regular terminal editors such vi/nano/mcedit work as expected.
How can I use gui editors with sops?

Copy link

sops will wait for the editor to exit. It looks like atom spawns a child process and then exits the main process. This will not work with sops. Atom has a -w command line flag that will wait for the main window to be closed before exiting. Create a /usr/local/bin/atom-blocking with

atom -w

And set EDITOR to that.

Copy link

jvehent commented Oct 21, 2016

How about adding this information to the README ?

Copy link

jvehent commented Oct 25, 2016

Could you add a note for this to the readme?

On Oct 20, 2016 3:28 PM, "Adrian Utrilla" wrote:

Closed #127 #127.

You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
#127 (comment), or mute the

Copy link

0xLeidenfrost commented Dec 15, 2020

On slightly more modern versions of atom, the same can be achieved without creating any scripts, but rather just by exporting editor as follows:export EDITOR="atom -w"

Copy link

patricknelson commented Dec 19, 2020

And for folks flexing Jetbrains IDEs, you can use the --wait flag. I'm on Windows, so to add a little diversity to the script examples:

@echo off
"C:\Program Files\JetBrains\PhpStorm 2019.3\bin\phpstorm64.exe" --wait %1

Drop that into a new batch file (e.g. phpstorm-blocking.bat) and just point the environment variable to that batch file. Of course, update the path as needed. Also note that, on Windows, you currently need to also do some interesting escaping to the path to this batch file if you really want it to work with sops. 😕

So in my case, the final value of EDITOR ends up becoming this for me (note that the value itself purposefully contains quotes and extra slashes, which can be confusing, but explained in issue #778 you can also use single quotes with forward slashes as well):

"C:\\Users\\patnelson\\Google Drive\\scripts\\phpstorm-blocking.bat"

However, after doing all this, it works like a charm in PhpStorm. 🎉

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
None yet

No branches or pull requests

5 participants