Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

":write [z-a].txt" writes the file, but emits an E944 #5059

Closed
lkintact opened this issue Oct 15, 2019 · 4 comments
Closed

":write [z-a].txt" writes the file, but emits an E944 #5059

lkintact opened this issue Oct 15, 2019 · 4 comments

Comments

@lkintact
Copy link

  1. Run gvim --clean
  2. Execute :write [z-a].txt
  3. Gvim creates a file with the specified name, but displays an "E944: Reverse range in character class" error.

Gvim: https://github.com/vim/vim-win32-installer/releases/download/v8.1.2151/gvim_8.1.2151_x86_signed.zip,
Windows 10 Home 1803

@brammool
Copy link
Contributor

brammool commented Oct 15, 2019 via email

@lkintact
Copy link
Author

Sorry if I don't understand something, but since "[" and "]" are in 'isfname' by default on Windows systems, shouldn't Gvim just not make any attempts to expand the [z-a] part and write the file as is?

@eirnym
Copy link

eirnym commented Oct 18, 2019

I agree, there's no reason to expand a filename while saving.

brammool added a commit that referenced this issue Oct 19, 2019
Problem:    Error for bad regexp even though regexp is not used when writing
            a file. (Arseny Nasokin)
Solution:   Ignore regexp errors. (closes #5059)
@markuspeloquin
Copy link

cmdexpand.c:1979:19: error: use of undeclared identifier 'WILD_NOERROR'

It looks like the flag wasn't added to vim.h.

manuelschiller pushed a commit to manuelschiller/vim that referenced this issue Nov 10, 2019
Problem:    Error for bad regexp even though regexp is not used, when writing
            a file. (Arseny Nasokin)
Solution:   Ignore regexp errors. (closes vim#5059)
manuelschiller pushed a commit to manuelschiller/vim that referenced this issue Nov 10, 2019
Problem:    Error for bad regexp even though regexp is not used when writing
            a file. (Arseny Nasokin)
Solution:   Ignore regexp errors. (closes vim#5059)
janlazo added a commit to janlazo/neovim that referenced this issue Feb 13, 2020
Problem:    Error for bad regexp even though regexp is not used when writing
            a file. (Arseny Nasokin)
Solution:   Ignore regexp errors. (closes vim/vim#5059)
vim/vim@b40c257
janlazo added a commit to janlazo/neovim that referenced this issue Feb 14, 2020
Problem:    Error for bad regexp even though regexp is not used when writing
            a file. (Arseny Nasokin)
Solution:   Ignore regexp errors. (closes vim/vim#5059)
vim/vim@b40c257
janlazo added a commit to janlazo/neovim that referenced this issue Feb 14, 2020
Problem:    Error for bad regexp even though regexp is not used when writing
            a file. (Arseny Nasokin)
Solution:   Ignore regexp errors. (closes vim/vim#5059)
vim/vim@b40c257
janlazo added a commit to janlazo/neovim that referenced this issue Feb 15, 2020
Problem:    Error for bad regexp even though regexp is not used when writing
            a file. (Arseny Nasokin)
Solution:   Ignore regexp errors. (closes vim/vim#5059)
vim/vim@b40c257
janlazo added a commit to janlazo/neovim that referenced this issue Feb 15, 2020
Problem:    Error for bad regexp even though regexp is not used when writing
            a file. (Arseny Nasokin)
Solution:   Ignore regexp errors. (closes vim/vim#5059)
vim/vim@b40c257
janlazo added a commit to janlazo/neovim that referenced this issue Feb 15, 2020
Problem:    Error for bad regexp even though regexp is not used when writing
            a file. (Arseny Nasokin)
Solution:   Ignore regexp errors. (closes vim/vim#5059)
vim/vim@b40c257
janlazo added a commit to janlazo/neovim that referenced this issue Feb 16, 2020
Problem:    Error for bad regexp even though regexp is not used when writing
            a file. (Arseny Nasokin)
Solution:   Ignore regexp errors. (closes vim/vim#5059)
vim/vim@b40c257
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants