Vim ошибка e37 - Решение и исправление самых разных ошибок на TopOshibok.ru

In this linux tutorial we will learn how to solve vi error — E37: No write since last change (add ! to override).

Contents of page >

Producing vi error — E37: No write since last change (add ! to override) in linux >
What does the — vi error — E37: No write since last change (add ! to override) means ?
Solution 1 to- vi error — E37: No write since last change (add ! to override) — quitting vi/Vim Editor without saving the file in linux >

Solution 1 in detail — quitting vi/Vim Editor without saving the file >

Solution 2 to- vi error — E37: No write since last change (add ! to override) — quitting vi/Vim Editor with saving the file in linux >

Producing vi error — E37: No write since last change (add ! to override) in linux >

Let’s say your file is opened and in vi/vim editor and you type ‘q’ and press Enter to exit the vi editor.

It will produce — vi error — E37: No write since last change (add ! to override)

What does the — vi error — E37: No write since last change (add ! to override) means ?

This vi error means that you are trying to exit/quit the vi editor after editing the file. It does not means that you cannot quit the editor without saving. For quitting the editor without saving ‘q’ is not enough you need to type ‘q!’ and press Enter.

Solution 1 to- vi error — E37: No write since last change (add ! to override) — quitting vi/Vim Editor without saving the file in linux >

Type ‘q!’ in place of ‘q’ and press Enter.

Solution 1 in detail — quitting vi/Vim Editor without saving the file >

STEP1 : How to quit/exit vi/Vim Editor without saving the file >

Press Esc key on keyboard

STEP2 : How to quit/exit vi/Vim Editor without saving the file >

Type ’:’ (colon)

STEP3 : How to quit/exit vi/Vim Editor without saving the file >

Type

‘q!’

STEP4 : How to quit/exit vi/Vim Editor without saving the file >

Press Enter

You will quit vi/Vim Editor without saving the file.

Solution 2 to- vi error — E37: No write since last change (add ! to override) — quitting vi/Vim Editor with saving the file in linux >

STEP1 : How to quit/exit vi/Vim Editor — saving the file >

Then press Esc key on keyboard

STEP2 : How to quit/exit vi/Vim Editor — saving the file >

Then type ’:’ (colon)

STEP3 : How to quit/exit vi/Vim Editor — saving the file >

Type

‘wq!’

STEP4 : How to quit/exit vi/Vim Editor — saving the file >

Press Enter

You will quit vi/Vim Editor saving the file.

Summary —

In this linux tutorial we solved vi error — E37: No write since last change (add ! to override).

Having any doubt? or you liked the tutorial! Please comment in below section.

How to edit file in vi/Vim Editor in linux — Save and quit

bash: ./yourScriptFile.sh: Permission denied Linux solved

Источник

Thank you for creating a very interesting plugin!
It did not work properly, so I will report it.

nvim --version: NVIM v0.5.0-dev+1384-gf2906a466
Operating system/version: Manjaro

Describe the bug

When I run vim.lsp.buf.formatting() without set hidden, I get the following error.

Error executing vim.schedule lua callback: …im/.plugged/plenary.nvim/lua/plenary/async_lib/async.lua:14: The coroutine failed with this message: …ig/nvim/.plugged/null-ls.nvim/lua/null-ls/formatting.lua:63: Vim(bufdo):E37: No write since last change (add ! to override)

To Reproduce using nvim -u mini.vim -i NONE

set encoding=utf-8

filetype plugin indent on
if has('vim_starting')
  let s:pluin_manager_dir='~/.config/nvim/.plugged/vim-plug'
  execute 'set runtimepath+=' . s:pluin_manager_dir
endif
call plug#begin('~/.config/nvim/.plugged')
Plug 'neovim/nvim-lspconfig'
Plug 'nvim-lua/plenary.nvim'
Plug 'jose-elias-alvarez/null-ls.nvim'
call plug#end()

set nobackup
set nowritebackup
set noswapfile
set updatecount=0
set backspace=indent,eol,start
language messages en_US.utf8

lua << EOF

local servers = require'xlsp.servers'
require'lspconfig'.sumneko_lua.setup{
  cmd = servers.get_cmd('sumneko_lua'),
}

require'null-ls'.setup {
  sources = {
    null_ls.builtins.formatting.stylua,
  }
}

EOF

Steps to reproduce the behavior:

nvim -u minvimrc -i NONE
:e sample.lua
edit
:w (hook BufWritePost)
error

Expected behavior

format is executed and the file is saved without error.

Thank you!

Источник

I closed the tutor in gVim yesterday.

So I wanted to continue the tutorial today.

I entered :e $VIMRUNTIME/tutor/tutor and got the error

«E37: No write since last change (use ! to override)»

So I checked the help, which said

Don’t forget to press <Enter> to finish the command. For those of you interested in the details, the three parts of this command are the colon (:), which enters Command-line mode; the q command, which tells the editor to quit; and the override command modifier (!). The override command modifier is needed because Vim is reluctant to throw away changes. If you were to just type «:q», Vim would display an error message and refuse to exit: E37: No write since last change (use ! to override) By specifying the override, you are in effect telling Vim, «I know that what I’m doing looks stupid, but I’m a big boy and really want to do this.» If you want to continue editing with Vim: The «:e!» command reloads the original version of the file.

But adding ! didn’t do anything. After entering

:e $VIMRUNTIME/tutor/tutor!

I got the same error:

E37: No write since last change (use ! to override)

Is this supposed to happen?

Источник

why you are obligated to save the file before exiting a TrueZen mode.

Actually, my comment was (partially) wrong. I’m not obligated to save it, and the modified contents actually appear in the original buffer when exiting a mode, but I still get an error. What I meant by «obligated to save the file» is that, to avoid the error, I have to save the file before exiting the mode, otherwise it occurs. It does not appear if I save before exiting.

I think I have the current version, as I’ve just ran :PlugUpdate. About the configs, I copied the default configs, but got the same result. I also removed everything else from my init.vim while testing, and ran :PlugClear to rule out the possibility of conflicts with other plugins. Here’s the whole init.vim for reference:

call plug#begin(stdpath('data') . '/plugged')
	Plug 'Pocco81/TrueZen.nvim'
call plug#end()

lua << EOF
local true_zen = require("true-zen")

true_zen.setup({
	ui = {
		bottom = {
			laststatus = 0,
			ruler = false,
			showmode = false,
			showcmd = false,
			cmdheight = 1,
		},
		top = {
			showtabline = 0,
		},
		left = {
			number = false,
			relativenumber = false,
			signcolumn = "no",
		},
	},
	modes = {
		ataraxis = {
			left_padding = 32,
			right_padding = 32,
			top_padding = 1,
			bottom_padding = 1,
			ideal_writing_area_width = {0},
			just_do_it_for_me = true,
			keep_default_fold_fillchars = true,
			custome_bg = "",
			bg_configuration = true,
			quit = "untoggle",
			affected_higroups = {NonText = {}, FoldColumn = {}, ColorColumn = {}, VertSplit = {}, StatusLine = {}, StatusLineNC = {}, SignColumn = {}}
		},
		focus = {
			margin_of_error = 5,
			focus_method = "experimental"
		},
	},
	integrations = {
		vim_gitgutter = false,
		galaxyline = false,
		tmux = false,
		gitsigns = false,
		nvim_bufferline = false,
		limelight = false,
		vim_airline = false,
		vim_powerline = false,
		vim_signify = false,
		express_line = false,
		lualine = false,
	},
	misc = {
		on_off_commands = false,
		ui_elements_commands = false,
		cursor_by_mode = false,
	}
})
EOF

Images

Here I ran :TZAtaraxis, typed abcde and tried to exit with :TZAtaraxis:

It’s also worth noting that, although it successfully exits Ataraxis, after this point, I cannot open it anymore. Running :TZAtaraxis doesn’t open the mode and yields the same error, with the additional message «Already only one window«:

Источник