I'm having the same issue with large python files with the exact same 
workaround:

> 1. open file
> 2. page down, OK
> 3. repeat 2 till the end of file, OK
> 4. go to first line, OK
> 5. go to last line, OK

I'm using vim 8 installed via homebrew on a mac.

VIM - Vi IMproved 8.0 (2016 Sep 12, compiled Feb 13 2018 12:01:25)
macOS version
Included patches: 1-1500
Compiled by Homebrew
Huge version without GUI.  Features included (+) or not (-):
+acl               +channel           +cryptv            +emacs_tags        
-footer            +lambda            +mksession         -mouse_sysmouse    
+path_extra        +reltime           +syntax            +textobjects       
+viminfo           -xpm
+arabic            +cindent           +cscope            +eval              
+fork()            +langmap           +modify_fname      +mouse_urxvt       
+perl              +rightleft         +tag_binary        +timers            
+vreplace          -xsmp
+autocmd           -clientserver      +cursorbind        +ex_extra          
-gettext           +libcall           +mouse             +mouse_xterm       
+persistent_undo   +ruby              +tag_old_static    +title             
+wildignore        -xterm_clipboard
-autoservername    +clipboard         +cursorshape       +extra_search      
-hangul_input      +linebreak         -mouseshape        +multi_byte        
+postscript        +scrollbind        -tag_any_white     -toolbar           
+wildmenu          -xterm_save
-balloon_eval      +cmdline_compl     +dialog_con        +farsi             
+iconv             +lispindent        +mouse_dec         +multi_lang        
+printer           +signs             -tcl               +user_commands     
+windows
+balloon_eval_term +cmdline_hist      +diff              +file_in_path      
+insert_expand     +listcmds          -mouse_gpm         -mzscheme          
+profile           +smartindent       +termguicolors     +vertsplit         
+writebackup
-browse            +cmdline_info      +digraphs          +find_in_path      
+job               +localmap          -mouse_jsbterm     +netbeans_intg     
+python            +startuptime       +terminal          +virtualedit       -X11
++builtin_terms    +comments          -dnd               +float             
+jumplist          -lua               +mouse_netterm     +num64             
-python3           +statusline        +terminfo          +visual            
-xfontset
+byte_offset       +conceal           -ebcdic            +folding           
+keymap            +menu              +mouse_sgr         +packages          
+quickfix          -sun_workshop      +termresponse      +visualextra       -xim
   system vimrc file: "$VIM/vimrc"
     user vimrc file: "$HOME/.vimrc"
 2nd user vimrc file: "~/.vim/vimrc"
      user exrc file: "$HOME/.exrc"
       defaults file: "$VIMRUNTIME/defaults.vim"
  fall-back for $VIM: "/usr/local/share/vim"
Compilation: clang -c -I. -Iproto -DHAVE_CONFIG_H   -DMACOS_X -DMACOS_X_DARWIN  
-g -O2 -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1
Linking: clang   -L. -fstack-protector -L/usr/local/lib 
-L/usr/local/opt/libyaml/lib -L/usr/local/opt/openssl/lib 
-L/usr/local/opt/readline/lib  -L/usr/local/lib -o vim        -lncurses -liconv 
-framework AppKit   -mmacosx-version-min=10.12 -fstack-protector-strong 
-L/usr/local/lib
-L/usr/local/Cellar/perl/5.26.1/lib/perl5/5.26.1/darwin-thread-multi-2level/CORE
 -lperl -lm -lutil -lc -F/usr/local/opt/python/Frameworks -framework Python   
-lruby.2.5.0 -lobjc

I don't experience this issue using vim 7.4 installed side-by-side (vim@7.4) on 
the same machine, using the same .vimrc.

Have you discovered any workaround for this issue?

-- 
-- 
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

--- 
You received this message because you are subscribed to the Google Groups 
"vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_use+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to