Blog: 2023-07-12 - Revision history

Razzi at 23:52, 12 July 2023

2023-07-12T23:52:16Z

← Older revision		Revision as of 18:52, 12 July 2023
Line 16:		Line 16:
	</pre>		</pre>
	The arguments have to be passed as a list and can't call arbitrary functions, since that'd be a security hole. Makes sense. So I'll have to bind my own terminal handler to open the file argument in a new tab.		The arguments have to be passed as a list and can't call arbitrary functions, since that'd be a security hole. Makes sense. So I'll have to bind my own terminal handler to open the file argument in a new tab.

			Meanwhile this mediawiki install is looking gaudy; would like to have dark mode - see https://phabricator.wikimedia.org/T26070

Razzi at 22:51, 12 July 2023

2023-07-12T22:51:54Z

← Older revision		Revision as of 17:51, 12 July 2023
Line 5:		Line 5:
	So there's a bit of a trickiness to the terminal->vim messaging - here's an example:		So there's a bit of a trickiness to the terminal->vim messaging - here's an example:

			<pre>
	function vim-client --argument file		function vim-client --argument file
	if string-empty $VIM_TERMINAL		if string-empty $VIM_TERMINAL
	echo not in vim terminal		echo not in vim terminal
	return 1
	~~end~~		return 1
		⚫	end

⚫	echo -e "\033]51;[\"drop\", \"$file\"]\007"
⚫	end

		⚫	echo -e "\033]51;[\"drop\", \"$file\"]\007"
			end
			</pre>
	The arguments have to be passed as a list and can't call arbitrary functions, since that'd be a security hole. Makes sense. So I'll have to bind my own terminal handler to open the file argument in a new tab.		The arguments have to be passed as a list and can't call arbitrary functions, since that'd be a security hole. Makes sense. So I'll have to bind my own terminal handler to open the file argument in a new tab.

Razzi at 22:51, 12 July 2023

2023-07-12T22:51:26Z

← Older revision		Revision as of 17:51, 12 July 2023
Line 2:		Line 2:

	This is a little different than the tmux flow I had before, where running vim would just open it fullscreen under tmux. Perhaps it's worth exploring whether when I have a single vim terminal open if it'd make sense just to open the file in the current window, potentially even exiting the terminal?		This is a little different than the tmux flow I had before, where running vim would just open it fullscreen under tmux. Perhaps it's worth exploring whether when I have a single vim terminal open if it'd make sense just to open the file in the current window, potentially even exiting the terminal?

			So there's a bit of a trickiness to the terminal->vim messaging - here's an example:

			function vim-client --argument file
			if string-empty $VIM_TERMINAL
			echo not in vim terminal
			return 1
			end

			echo -e "\033]51;[\"drop\", \"$file\"]\007"
			end

			The arguments have to be passed as a list and can't call arbitrary functions, since that'd be a security hole. Makes sense. So I'll have to bind my own terminal handler to open the file argument in a new tab.

Razzi: Created page with "Still hacking on vim as a terminal window manager. Think it'll work well enough to open a new file in a new tab, rather than in the same window as the terminal. Then when the..."

2023-07-12T22:48:41Z

Created page with "Still hacking on vim as a terminal window manager. Think it'll work well enough to open a new file in a new tab, rather than in the same window as the terminal. Then when the..."

New page

Still hacking on vim as a terminal window manager. Think it'll work well enough to open a new file in a new tab, rather than in the same window as the terminal. Then when the file is closed it'll go back to the terminal.

This is a little different than the tmux flow I had before, where running vim would just open it fullscreen under tmux. Perhaps it's worth exploring whether when I have a single vim terminal open if it'd make sense just to open the file in the current window, potentially even exiting the terminal?