google / google/vim-codefmt

E484: Can't open file c:\Users\username~\AppData\Local\Temp\VIo7EE2.tmp

Open
#86 10 comments 1 reaction 0 assignees View on GitHub
bug
Dominant language
Vim Script
Stars
1.1k
Forks
102
PR merge metrics
No merged PRs in 30d

Description

On Windows 10, i am facing this issue. Unable to open the temp dir for writing.

My _vimrc file:

`let $TMPDIR = "C:/Users/Balasubramanian/.vim/temp"

" initial vundle configuration.
set rtp+=~/.vim/bundle/Vundle.vim
call vundle#begin()
"plugin installation
"vundle plugin

Plugin 'VundleVim/Vundle.vim'
Plugin 'scrooloose/nerdtree'
Plugin 'tpope/vim-surround'
Plugin 'kien/ctrlp.vim'
Plugin 'scrooloose/nerdcommenter'
Plugin 'DoxygenToolkit.vim'
"Plugin 'rip-rip/clang_complete'
Plugin 'valloric/youcompleteme'
Plugin 'brookhong/cscope.vim'
Plugin 'airblade/vim-rooter'
Plugin 'klen/python-mode'
Plugin 'nlknguyen/papercolor-theme'
Plugin 'google/vim-maktaba'
Plugin 'google/vim-codefmt'
Plugin 'google/vim-glaive'
Plugin 'flazz/vim-colorschemes'
Plugin 'altercation/vim-colors-solarized'
Plugin 'bling/vim-airline'
Plugin 'w0rp/ale'
Plugin 'cython/cython'

call vundle#end()
filetype plugin indent on
" the glaive#Install() should go after the "call vundle#end()"
call glaive#Install()
" Optional: Enable codefmt's default mappings on the = prefix.
Glaive codefmt plugin[mappings]
Glaive codefmt google_java_executable="java -jar C:/Users/Balasubramanian/.vim/bundle/vim-glaive/google-java-format-VERSION-all-deps.jar"
`

Can the community please help me ? every time i have to format the code, i am using a Visual Code to format it and i have to switch back to Vim for coding.

I have also disabled my "RealTime Scanner" , even then, get the same issue.

Thanks

Contributor guide

Open the contributing guide

Research direction

Start with the reported _vimrc configuration, especially the $TMPDIR setting and the google-java-format Glaive command, then reproduce formatting on Windows 10 to observe E484 for the temporary file. Confirm the issue is resolved when formatting can create and write its temporary file without requiring Visual Studio Code.

Written by the indexing model from the issue text.

Assessment

Tech stack
vim
Domain
tooling
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.