Hi, 2019/11/4 Mon 20:37:24 UTC+9 James McCoy wrote: > > On Mon, Nov 4, 2019, 05:28 Bram Moolenaar <br...@moolenaar.net > <javascript:>> wrote: > >> >> > On Sun, Nov 03, 2019 at 09:20:20PM +0100, Bram Moolenaar wrote: >> > > >> > > Christian wrote: >> > > >> > > > On So, 03 Nov 2019, Bram Moolenaar wrote: >> > > > >> > > > > Right, "make vimtags" doesn't work. I'm not sure how widespread >> "type" >> > > > > is, I think "which" should be safer. >> > > > >> > > > type or command -v is the command one should use nowadays. For a >> really >> > > > deep dive into what to use, I suggest this great article: >> > > > >> > > > https://unix.stackexchange.com/a/85250/303213 >> > > >> > > Hmm, not that great. It doesn't list what command is available in >> which >> > > version of a shell. It does mention that "which" is widely available, >> > > while "type" is not. >> > >> > FWIW, "command -v ..." is specified in POSIX. "type" is as well, but as >> > an XSI extension. >> >> In tcsh: >> >> $ command -v vim >> command: Command not found. >> >> Perfect error message :-). >> > > Tcsh isn't /bin/sh, so I'm not sure why that's relevant. This is in the > context of a Makefile, which uses /bin/sh. > >> We already use "command -v" in src/po/Makefile. I think it can be also safely used in runtime/doc/Makefile.
Regards, Ken Takata -- -- 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 vim_dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/vim_dev/950f3960-a640-4229-ba0d-3c08fa3b9e1b%40googlegroups.com.
