From 53d1f3d50acf522394891dfbea67067ec578866f Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Davorin=20S=CC=8Cego?= <davorin.sego@gmail.com>
Date: Thu, 26 Oct 2023 14:53:17 +0200
Subject: [PATCH] Fix empty message in newer Sublime Text versions

The new_file.insert method was misusing the `edit` parameter.
Instead we can invoke a command to append text in the newly created window.

Context:

The edit parameter is not for new_file but for self.view.

Build 4158
https://www.sublimetext.com/dev
-  API: Fixed crash when an edit token is passed to the wrong view

(https://github.com/sublimehq/sublime_text/issues/6177)

API Docs:
https://www.sublimetext.com/docs/api_reference.html#sublime.Edit

> Edit objects are passed to TextCommands, and can not be created by the user. Using an invalid Edit object, or an Edit object from a different View, will cause the functions that require them to fail.
---
 GitCommitMsg.py | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/GitCommitMsg.py b/GitCommitMsg.py
index 65faa4c..d816145 100644
--- a/GitCommitMsg.py
+++ b/GitCommitMsg.py
@@ -73,7 +73,7 @@ class GitCommitMsgResultCommand(sublime_plugin.TextCommand):
   """
   def run(self, edit, file_name, start_line, end_line, result):
     new_file = self.view.window().new_file()
-    new_file.insert(edit, 0, result)
+    new_file.run_command("append", {"characters": result})
     new_file.set_scratch(True)
     new_file.set_read_only(True)
     syntax = "Packages/GitCommitMsg/GitCommitMsg.tmLanguage"