view src/proto/cmdexpand.pro @ 19085:fd1070ff696b v8.2.0103

patch 8.2.0103: using null object with execute() has strange effects Commit: https://github.com/vim/vim/commit/e2a8f0773e91685843c062b1e48259712d5f2213 Author: Bram Moolenaar <Bram@vim.org> Date: Wed Jan 8 19:32:18 2020 +0100 patch 8.2.0103: using null object with execute() has strange effects Problem: Using null object with execute() has strange effects. Solution: Give an error message ofr Job and Channel.
author Bram Moolenaar <Bram@vim.org>
date Wed, 08 Jan 2020 19:45:04 +0100
parents cec4da73951a
children eb878f85967e
line wrap: on
line source

/* cmdexpand.c */
int nextwild(expand_T *xp, int type, int options, int escape);
char_u *ExpandOne(expand_T *xp, char_u *str, char_u *orig, int options, int mode);
void ExpandInit(expand_T *xp);
void ExpandCleanup(expand_T *xp);
int showmatches(expand_T *xp, int wildmenu);
char_u *sm_gettail(char_u *s);
char_u *addstar(char_u *fname, int len, int context);
void set_cmd_context(expand_T *xp, char_u *str, int len, int col, int use_ccline);
int expand_cmdline(expand_T *xp, char_u *str, int col, int *matchcount, char_u ***matches);
void globpath(char_u *path, char_u *file, garray_T *ga, int expand_options);
void f_getcompletion(typval_T *argvars, typval_T *rettv);
/* vim: set ft=c : */