On Tuesday, February 9, 2016 at 2:01:43 AM UTC-6, Christian Brabandt wrote: > > Can you think of a command or situation where this patch provides a > > nice, useful solution? > > I think, it has come up in the past before: > - Catching E482/E484/E485 because /tmp got cleaned out would be > possible. > https://groups.google.com/d/msg/vim_use/qgRob9SWDv8/FAOFVVcDTv0J > - https://groups.google.com/d/msg/vim_dev/EbTWqBl2rdw/vT4fTaGFnMoJ > - and possibly others, which I don't remember currently. >
A couple more interesting ideas: Set 'nowrapscan' in the .vimrc, but catch an E385 (search hit bottom without match) and offer to wrap to the beginning (temporarily set wrapscan). Or, similar to the initial use of rebuilding tags if a tag is not found, modify 'path' if a file is not found for gf and friends. Does the autocmd work to catch things thrown by :throw? If so there could be all kinds of uses for that. Writes failing for files being readonly could prompt to retry with the sudo + tee trick. I'm sure clever plugin authors will find plenty more. -- -- You received this message from the "vim_dev" 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_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
