You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, after launching the text editor, massren watches for the temporary file it created. If this file is modified, the renaming process starts, and then massren is closed.
However, if the file is not changed at all and simply closed, massren stays open and has to be closed with Ctrl + C.
In order to prevent this, we could watch the text editor process ID and, if it's gone, automatically exit massren. That would take care mainly of modal editors such as Vim. It still won't fix the issue with GUI editors though since they would usually remain open even if the file is closed.
The text was updated successfully, but these errors were encountered:
In order to prevent this, we could watch the text editor process ID and, if it's gone, automatically exit massren. That would take care mainly of modal editors such as Vim.
I guess that would cover Sublime Text as well (initiated by subl). git already does this on unchanged (unsaved) commit messages, using subl -nw.
Currently, after launching the text editor, massren watches for the temporary file it created. If this file is modified, the renaming process starts, and then massren is closed.
However, if the file is not changed at all and simply closed, massren stays open and has to be closed with Ctrl + C.
In order to prevent this, we could watch the text editor process ID and, if it's gone, automatically exit massren. That would take care mainly of modal editors such as Vim. It still won't fix the issue with GUI editors though since they would usually remain open even if the file is closed.
The text was updated successfully, but these errors were encountered: