Blog: 2023-07-10 - Revision history

Razzi at 23:48, 12 July 2023

2023-07-12T23:48:00Z

← Older revision		Revision as of 18:48, 12 July 2023
Line 34:		Line 34:

	cool. but that makes a split, how to open a normal edit session, that upon being closed, just goes back to the (vim) terminal?		cool. but that makes a split, how to open a normal edit session, that upon being closed, just goes back to the (vim) terminal?

			I think the solution is to use vim tabs, and make a custom vim terminal function to open the requested file in a new tab.

Razzi at 14:48, 12 July 2023

2023-07-12T14:48:12Z

← Older revision		Revision as of 09:48, 12 July 2023
Line 33:		Line 33:
	end		end

			cool. but that makes a split, how to open a normal edit session, that upon being closed, just goes back to the (vim) terminal?
	cool

Razzi at 14:31, 12 July 2023

2023-07-12T14:31:46Z

← Older revision		Revision as of 09:31, 12 July 2023
Line 28:		Line 28:
	vim '+term ++curwin' +term		vim '+term ++curwin' +term
	Now to figure out how to open vim in the original vim session:		Now to figure out how to open vim in the original vim session:

			function vdrop --argument file
			echo \x1b]'51;["drop", "'$file'"]'\x07
			end

			cool

Razzi at 04:37, 12 July 2023

2023-07-12T04:37:01Z

← Older revision		Revision as of 23:37, 11 July 2023
Line 8:		Line 8:

	https://superuser.com/questions/708245/re-compile-vim-with-options		https://superuser.com/questions/708245/re-compile-vim-with-options



Line 22:		Line 23:

	I tried this other terminal window manager zellij but its ui had these borders I couldn't figure out how to get rid of that were taking up a bunch of screen space.		I tried this other terminal window manager zellij but its ui had these borders I couldn't figure out how to get rid of that were taking up a bunch of screen space.


			At long last I have figured out how to open vim into 2 splits:
			vim '+term ++curwin' +term
			Now to figure out how to open vim in the original vim session:

Razzi at 22:30, 10 July 2023

2023-07-10T22:30:23Z

← Older revision		Revision as of 17:30, 10 July 2023
Line 14:		Line 14:
	Ok so here's the flow I want to be able to do. It's using my old tmux habits. Looks like this		Ok so here's the flow I want to be able to do. It's using my old tmux habits. Looks like this

	- start terminal and cd into project		* start terminal and cd into project
	- open editor / tmux		* open editor / tmux
	- open file in editor		* open file in editor
	- switch to terminal and build		* switch to terminal and build
	- switch back to file and edit		* switch back to file and edit
	etc.		etc.

Razzi: Created page with "Adding a control+b feature to fjord. As I do so I realize that the vim terminal opens a nested vim instance which makes the vim command line really confusing. Looks like one..."

2023-07-10T22:30:08Z

Created page with "Adding a control+b feature to fjord. As I do so I realize that the vim terminal opens a nested vim instance which makes the vim command line really confusing. Looks like one..."

New page

Adding a control+b feature to fjord. As I do so I realize that the vim terminal opens a nested vim instance which makes the vim command line really confusing.

Looks like one way around this is to use the vim clientserver functionality. Also something like the :drop command could be useful

But my vim doesn't come with clientserver (vim --version) so I'm installing vim from source:

$ sudo apt-get build-dep vim-gnome

https://superuser.com/questions/708245/re-compile-vim-with-options

Meanwhile I have neovim installed, but it doesn't have a termwinkey option. Huh...

Ok so here's the flow I want to be able to do. It's using my old tmux habits. Looks like this

- start terminal and cd into project
- open editor / tmux
- open file in editor
- switch to terminal and build
- switch back to file and edit
etc.

I tried this other terminal window manager zellij but its ui had these borders I couldn't figure out how to get rid of that were taking up a bunch of screen space.