On 14/02/2017 16:09, Stuart Levy wrote:
On Tuesday, January 31, 2017 at 4:28:17 PM UTC-6, Peter Shenkin wrote:
Could somebody please say what they have to do to trigger this crash? (I'm on Sierra 10.12.3 now, but 
never saw it earlier in 10.12.1.) Having said that, I usually just run "mvim <fname>", 
which brings MacVim up in its own window; but occasionally I do "vi" a file in a terminal 
window, but have never see this problem.


-P.

I found a small example which reliably crashes Terminal when running vim.

Repeatable crash in Terminal while typing in vim.   (Happens whether using 
macos-supplied vim, or a linux copy of vim run remotely via ssh.)

Repeat-by:

Make a Terminal window that’s not too wide, e.g. 120 columns.   (Doesn’t crash 
in a 150-column-wide terminal, but does crash with some variety of smaller 
widths.)

Run vim on the following plain ASCII text file (bracketed by ====’s, which 
should be removed i.e. they’re not part of the text file, which has exactly 5 
lines).  The file is also attached to this forum message:
====
/goldbaum2-7.bmv already exists; use -y to recreate
/des_surveyBuildup_11-7.bmv already exists; use -y to recreate
/lsst_telescope12-22.bmv 1-2660 
/fe0/deslsst/telescope/comps/lsst_obj_12-22_comp4k/lsst_obj_12-22_comp4k.%04d.png
img2bmv -f 30 -p 3 -N 6 -L 42  -t 512x360 -w 4096x2160  -w 3840x2160 -t 480x540 
 -o /fraid0/movies/ren400My_vars_grids_labels_11-8.bmv 1-2881 
/fe0/deslsst/renaissance/comps/ren400My_vars_grids_labels_3840_11-8/ren400My_vars_grids_labels_3840_11-8.%04d.png
Don't know how to make these movies:  -f 3
====

In vim, type:
   3jdfo
i.e., go down to the 4th line, then delete from start-of-line to the first “o”.
Terminal crashes reliably!  I'm running 10.12.3 also.

I can reproduce this in Terminal.app (also running macOS 10.12.3), with
both macOS's pre-built Vim and Vim 8.0.237 (from Homebrew). More
specifically, I can reproduce the crash if I run any of these:

    vim -u NONE
    vim -u NONE -N
    /usr/bin/vi -u NONE
    /usr/bin/vi -u NONE -N

but I *cannot* reproduce it if I run vim with my own .vimrc. I am still
trying to figure out which setting is the culprit.

The problem looks like a bug in Terminal.app to me. I cannot crash
MacVim or iTerm2, for example.

Life.

--
--
You received this message from the "vim_mac" 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_mac" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_mac+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to