diff options
| author | Bram Moolenaar <Bram@vim.org> | 2010-05-22 15:37:44 +0200 |
|---|---|---|
| committer | Bram Moolenaar <Bram@vim.org> | 2010-05-22 15:37:44 +0200 |
| commit | 06b5d5167a01c9fbf9661fb0c03bbd0a77cecae6 (patch) | |
| tree | 4e4054360a178c58b1fb4e48bb51955f984a6b66 /runtime/doc/pi_netrw.txt | |
| parent | db7c686ea58323f8e8550dea287eac7ea4964a55 (diff) | |
| download | vim-git-06b5d5167a01c9fbf9661fb0c03bbd0a77cecae6.tar.gz | |
Add the settabvar() and gettabvar() functions.
Various runtime file updates.
Diffstat (limited to 'runtime/doc/pi_netrw.txt')
| -rw-r--r-- | runtime/doc/pi_netrw.txt | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/runtime/doc/pi_netrw.txt b/runtime/doc/pi_netrw.txt index 41c6bd685..b57585be2 100644 --- a/runtime/doc/pi_netrw.txt +++ b/runtime/doc/pi_netrw.txt @@ -456,7 +456,7 @@ browsed remote directories, for example. On the other hand, thanks go to Jan M. for pointing out the many vulnerabilities that netrw (and vim itself) had had in handling "crafted" filenames. The |shellescape()| and |fnameescape()| functions were written in -response by Bram Moolenaar to handle these sort of problems, and netrw has +response by Bram Moolenaar to handle this sort of problems, and netrw has been modified to use them. Still, my advice is, if the "filename" looks like a vim command that you aren't comfortable with having executed, don't open it. |