-
-
Notifications
You must be signed in to change notification settings - Fork 5.4k
-
-
Notifications
You must be signed in to change notification settings - Fork 5.4k
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
Comments
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
Normally [ and ] are not in 'isfname'. When expanding fails it may
still work, but probably not everywhere. You can use backslashes to
escape, but since MS-Windows uses backslash as a path separater this
often becomes confusing. Blame Microsoft...
…--
Lawmakers made it obligatory for everybody to take at least one bath
each week -- on Saturday night.
[real standing law in Vermont, United States of America]
/// Bram Moolenaar -- Bram@Moolenaar.net -- http://www.Moolenaar.net \\\
/// sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\
\\\ an exciting new programming language -- http://www.Zimbu.org ///
\\\ help me help AIDS victims -- http://ICCF-Holland.org ///
|
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 |
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)
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
gvim --clean
:write [z-a].txt
Gvim: https://github.com/vim/vim-win32-installer/releases/download/v8.1.2151/gvim_8.1.2151_x86_signed.zip,
Windows 10 Home 1803
The text was updated successfully, but these errors were encountered: