search

Vimjas / vim-testbed

Docker image for testing Vim plugins
42 stars 6 forks source link

permissible directory #31

Open bounceme opened 7 years ago

bounceme commented 7 years ago

from what i can tell no files are editable or even openable. that makes testing harder for indent-scripts / editing plugins by requiring the full path to vim.

blueyed commented 7 years ago

Can you provide more information, e.g. logs?

I am not sure if it is worth supporting something older than 7.3 myself though.

bounceme commented 7 years ago

is this for #30 ? 7.2 works fine, maybe 7.1 is just too old. the failure was with ncurses i beleive

blueyed commented 7 years ago

Yes, I asked for #30.

What is this issue about exactly? Files should be editable, if you mount them using a Docker volume. How do you use vim-testbed?

bounceme commented 7 years ago 
FROM testbed/vim:latest
ENV IND master

RUN install_vim -tag v7.2 -name vim72 -build
RUN apk update
RUN apk add diffutils
RUN mkdir -p /home/vim/indent

ADD http://cdn.rawgit.com/pangloss/vim-javascript/${IND}/indent/javascript.vim /home/vim/indent/javascript.vim
ADD http://cdn.rawgit.com/sanctuary-js/sanctuary-def/779fc342b04f5d74778ec628a0b9bb80b204c8e5/index.js /testplugin/test.js

ENTRYPOINT vim-build/bin/vim72 -c "source /rtp.vim" -c "runtime indent/javascript.vim" -c \
           "set nocompatible" -c "syntax on" -c "filetype plugin indent on" /testplugin/test.js

I'm trying different vim's for compatibility issues, on some basic indentation script tests. unfortunately i can't set up automated builds at https://github.com/pangloss/vim-javascript . I'm actually using this interactively at the moment

blueyed commented 7 years ago

And what is the problem? That some dirs are not writable? Does the build already fail? btw: I am working on improving this in general in https://github.com/tweekmonster/vim-testbed/pull/33

bounceme commented 7 years ago

yea, run_vim.sh removes all permissions. nothing is editable or openable.

bounceme commented 7 years ago

i guess i could just use mkdir -m to as a fix for my use case

tinmarino commented 4 years ago

Did you find the source of your problem ? I get 

$ docker run -it --rm -e USER=root  -v $PWD/../:/testplugin -v $PWD/../test:/home vimwiki vim_7.4.1099 -u test/vimrc -i NONE

5df81d6da6ad:/testplugin$ cd /
5df81d6da6ad:/$ ls -l 
total 80
drwxr-xr-x    1 root     root          4096 Oct 24 15:35 bin
drwxr-xr-x    5 root     root           360 Dec 14 21:27 dev
drwxr-xr-x    1 root     root          4096 Dec 14 21:27 etc
drwxr-xr-x    5 1000     1000          4096 Dec 14 21:13 home
drwxr-xr-x    1 root     root          4096 Oct 24 15:44 lib
drwxr-xr-x    5 root     root          4096 Aug 20 10:30 media
drwxr-xr-x    2 root     root          4096 Aug 20 10:30 mnt
drwxr-xr-x    2 root     root          4096 Aug 20 10:30 opt
drwxr-xr-x    1 vimtest  vimtest       4096 Sep 18 22:24 plugins
dr-xr-xr-x  314 root     root             0 Dec 14 21:27 proc
drwx------    1 root     root          4096 Oct 24 15:44 root
-rw-r--r--    1 root     root           219 Sep 18 22:24 rtp.vim
drwxr-xr-x    2 root     root          4096 Aug 20 10:30 run
drwxr-xr-x    1 root     root          4096 Sep 18 22:24 sbin
drwxr-xr-x    2 root     root          4096 Aug 20 10:30 srv
dr-xr-xr-x   13 root     root             0 Dec 14 21:27 sys
drwxr-xr-x    9 1000     1000          4096 Dec 11 20:06 testplugin
drwxrwxrwt    1 root     root          4096 Oct 24 15:44 tmp
drwxr-xr-x    1 root     root          4096 Oct 24 15:44 usr
drwxr-xr-x   10 root     root          4096 Oct 24 15:36 vader
drwxr-xr-x    1 root     root          4096 Oct 24 15:36 var
drwxr-xr-x    1 root     root          4096 Oct 24 15:44 vim
drwxr-xr-x    1 root     root          4096 Oct 24 15:44 vim-build