CLI: Add support for ".edit" or "\e" #11447
Merged
+209
−0
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR adds support for using the
.edit
(or\e
for short) commands to open an editor to either (a) edit the previous history entry, or (b) edit the current buffer. The editor that is opened is by defaultvi
, but can be configured using either theDUCKDB_EDITOR
,EDITOR
orVISUAL
environment variables (in that order). When the command is used, the specified editor is opened with the current contents of the edit buffer. If the editor closes successfully (e.g.:wq
in vim) the edit buffer is replaced with the contents of the file and any queries within the file are executed. If the editor closes unsuccessfully (e.g.:q!
in vim) the previous buffer is kept around.Example usage: