Mercurial > vim
view src/proto/ex_cmds2.pro @ 31287:fa309d9af73c v9.0.0977
patch 9.0.0977: it is not easy to see what client-server commands are doing
Commit: https://github.com/vim/vim/commit/4c5678ff0c376661d4a8183a5a074a1203413b9d
Author: Bram Moolenaar <Bram@vim.org>
Date: Wed Nov 30 18:12:19 2022 +0000
patch 9.0.0977: it is not easy to see what client-server commands are doing
Problem: It is not easy to see what client-server commands are doing.
Solution: Add channel log messages if ch_log() is available. Move the
channel logging and make it available with the +eval feature.
author | Bram Moolenaar <Bram@vim.org> |
---|---|
date | Wed, 30 Nov 2022 19:15:10 +0100 |
parents | b32b67a108f2 |
children |
line wrap: on
line source
/* ex_cmds2.c */ int autowrite(buf_T *buf, int forceit); void autowrite_all(void); int check_changed(buf_T *buf, int flags); void browse_save_fname(buf_T *buf); void dialog_changed(buf_T *buf, int checkall); int can_abandon(buf_T *buf, int forceit); int check_changed_any(int hidden, int unload); int check_fname(void); int buf_write_all(buf_T *buf, int forceit); void ex_listdo(exarg_T *eap); void ex_compiler(exarg_T *eap); void init_pyxversion(void); void ex_pyxfile(exarg_T *eap); void ex_pyx(exarg_T *eap); void ex_pyxdo(exarg_T *eap); void ex_checktime(exarg_T *eap); /* vim: set ft=c : */