Allow for customization of shell buffer names #121
Merged
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 change adds a new customizable variable, called kubel-shell-buffer-name-format. This variable defines the buffer name format for shell, ansi-term, eshell, and vterm buffers created through kubel-exec-popup. I frequently have to interact with multiple clusters and multiple namespaces in each cluster, so having the ability to add the Kubernetes context and namespace to the buffer name is useful. As explained in the documentation for kubel-shell-buffer-name-format, the following %-sequences are available:
%t: The shell type. Examples of this are
shell
andeshell
%c: The container name
%p: The pod name
%n: The current namespace
%C: The current context
I set the default format to
"kubel:%C:%n:%t:%c@%p"
, which updates the shell buffer name format to match the new buffer name format after the merge of #114.