mirror of
https://github.com/neovim/neovim.git
synced 2024-12-23 20:55:18 -07:00
docs: fix/remove invalid URLs #20647
This commit is contained in:
Justin M. Keyes
GitHub
parent
0a19c16778
commit
e5cb3104d0
@ -11,7 +11,7 @@ low-risk/isolated tasks:
|
||||
- Fix bugs found by [Clang](#clang-scan-build), [PVS](#pvs-studio) or
|
||||
[Coverity](#coverity).
|
||||
- [Improve documentation](#documenting)
|
||||
- [Merge a Vim patch] (familiarity with Vim is *strongly* recommended)
|
||||
- [Merge a Vim patch] (requires strong familiarity with Vim)
|
||||
|
||||
Reporting problems
|
||||
------------------
|
||||
|
||||
@ -8,7 +8,7 @@ Neovim's license follows:
|
||||
====
|
||||
Apache License
|
||||
Version 2.0, January 2004
|
||||
http://www.apache.org/licenses/
|
||||
https://www.apache.org/licenses/
|
||||
|
||||
TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
|
||||
|
||||
|
||||
@ -8,7 +8,7 @@ Nvim style guide *dev-style*
|
||||
|
||||
This is style guide for developers working on Nvim's source code.
|
||||
|
||||
License: CC-By 3.0 http://creativecommons.org/licenses/by/3.0/
|
||||
License: CC-By 3.0 https://creativecommons.org/licenses/by/3.0/
|
||||
|
||||
Type |gO| to see the table of contents.
|
||||
|
||||
|
||||
@ -401,7 +401,7 @@ to see more messages.
|
||||
|
||||
The self-installing Vim for MS-Windows includes a diff program. If you don't
|
||||
have it you might want to download a diff.exe. For example from
|
||||
http://gnuwin32.sourceforge.net/packages/diffutils.htm.
|
||||
https://gnuwin32.sourceforge.net/packages/diffutils.htm.
|
||||
|
||||
|
||||
USING PATCHES *diff-patchexpr*
|
||||
|
||||
@ -486,25 +486,25 @@ You can optionally install the following extra plug-ins. They work well with
|
||||
Ada and enhance the ability of the Ada mode:
|
||||
|
||||
backup.vim
|
||||
http://www.vim.org/scripts/script.php?script_id=1537
|
||||
https://www.vim.org/scripts/script.php?script_id=1537
|
||||
Keeps as many backups as you like so you don't have to.
|
||||
|
||||
rainbow_parenthesis.vim
|
||||
http://www.vim.org/scripts/script.php?script_id=1561
|
||||
https://www.vim.org/scripts/script.php?script_id=1561
|
||||
Very helpful since Ada uses only '(' and ')'.
|
||||
|
||||
nerd_comments.vim
|
||||
http://www.vim.org/scripts/script.php?script_id=1218
|
||||
https://www.vim.org/scripts/script.php?script_id=1218
|
||||
Excellent commenting and uncommenting support for almost any
|
||||
programming language.
|
||||
|
||||
matchit.vim
|
||||
http://www.vim.org/scripts/script.php?script_id=39
|
||||
https://www.vim.org/scripts/script.php?script_id=39
|
||||
'%' jumping for any language. The normal '%' jump only works for '{}'
|
||||
style languages. The Ada mode will set the needed search patterns.
|
||||
|
||||
taglist.vim
|
||||
http://www.vim.org/scripts/script.php?script_id=273
|
||||
https://www.vim.org/scripts/script.php?script_id=273
|
||||
Source code explorer sidebar. There is a patch for Ada available.
|
||||
|
||||
The GNU Ada Project distribution (http://gnuada.sourceforge.net) of Vim
|
||||
|
||||
@ -39,7 +39,7 @@ navigation.
|
||||
|
||||
1.1 Matchit *sql-matchit*
|
||||
-----------
|
||||
The matchit plugin (http://www.vim.org/scripts/script.php?script_id=39)
|
||||
The matchit plugin (https://www.vim.org/scripts/script.php?script_id=39)
|
||||
provides many additional features and can be customized for different
|
||||
languages. The matchit plugin is configured by defining a local
|
||||
buffer variable, b:match_words. Pressing the % key while on various
|
||||
@ -296,7 +296,7 @@ exist.
|
||||
3. Adding new SQL Dialects *sql-adding-dialects*
|
||||
|
||||
If you begin working with a SQL dialect which does not have any customizations
|
||||
available with the default Vim distribution you can check http://www.vim.org
|
||||
available with the default Vim distribution you can check https://www.vim.org
|
||||
to see if any customization currently exist. If not, you can begin by cloning
|
||||
an existing script. Read |filetype-plugins| for more details.
|
||||
|
||||
@ -403,7 +403,7 @@ Here are some examples of the entries which are pulled from the syntax files: >
|
||||
----------------
|
||||
Dynamic mode populates the popups with data directly from a database. In
|
||||
order for the dynamic feature to be enabled you must have the dbext.vim
|
||||
plugin installed, (http://vim.sourceforge.net/script.php?script_id=356).
|
||||
plugin installed, (https://vim.sourceforge.net/script.php?script_id=356).
|
||||
|
||||
Dynamic mode is used by several features of the SQL completion plugin.
|
||||
After installing the dbext plugin see the dbext-tutorial for additional
|
||||
@ -487,7 +487,7 @@ depending on the syntax file you are using. The SQL Anywhere syntax file
|
||||
Dynamic features
|
||||
----------------
|
||||
To take advantage of the dynamic features you must first install the
|
||||
dbext.vim plugin (http://vim.sourceforge.net/script.php?script_id=356). It
|
||||
dbext.vim plugin (https://vim.sourceforge.net/script.php?script_id=356). It
|
||||
also comes with a tutorial. From the SQL completion plugin's perspective,
|
||||
the main feature dbext provides is a connection to a database. dbext
|
||||
connection profiles are the most efficient mechanism to define connection
|
||||
|
||||
@ -251,7 +251,7 @@ At this moment translations are available for:
|
||||
Japanese - multiple authors
|
||||
Polish - translated by Mikolaj Machowski
|
||||
Russian - translated by Vassily Ragosin
|
||||
See the Vim website to find them: http://www.vim.org/translations.php
|
||||
See the Vim website to find them: https://www.vim.org/translations.php
|
||||
|
||||
A set of translated help files consists of these files:
|
||||
|
||||
|
||||
@ -7,7 +7,7 @@ The Ruby Interface to Vim *if_ruby* *ruby* *Ruby*
|
||||
|
||||
*E266* *E267* *E268* *E269* *E270* *E271* *E272* *E273*
|
||||
|
||||
The home page for ruby is http://www.ruby-lang.org/. You can find links for
|
||||
The home page for ruby is https://www.ruby-lang.org/. You can find links for
|
||||
downloading Ruby there.
|
||||
|
||||
Type |gO| to see the table of contents.
|
||||
|
||||
@ -724,7 +724,7 @@ Fortran with (possibly multiple) loops ending on a labelled executable
|
||||
statement of almost arbitrary type. Correct indentation requires
|
||||
compiler-quality parsing. Old code with do loops ending on labelled statements
|
||||
of arbitrary type can be indented with elaborate programs such as Tidy
|
||||
(http://www.unb.ca/chem/ajit/f_tidy.htm). Structured do/continue loops are
|
||||
(https://www.unb.ca/chem/ajit/f_tidy.htm). Structured do/continue loops are
|
||||
also left unindented because continue statements are also used for purposes
|
||||
other than ending a do loop. Programs such as Tidy can convert structured
|
||||
do/continue loops to the do/enddo form. Do loops of the do/enddo variety can
|
||||
|
||||
@ -1350,16 +1350,8 @@ Completion of C code requires a tags file. You should use Universal/
|
||||
Exuberant ctags, because it adds extra information that is needed for
|
||||
completion. You can find it here:
|
||||
Universal Ctags: https://ctags.io
|
||||
Exuberant Ctags: http://ctags.sourceforge.net
|
||||
|
||||
Universal Ctags is preferred, Exuberant Ctags is no longer being developed.
|
||||
|
||||
For Exuberant ctags, version 5.6 or later is recommended. For version 5.5.4
|
||||
you should add a patch that adds the "typename:" field:
|
||||
ftp://ftp.vim.org/pub/vim/unstable/patches/ctags-5.5.4.patch
|
||||
A compiled .exe for MS-Windows can be found at:
|
||||
http://ctags.sourceforge.net/
|
||||
https://github.com/universal-ctags/ctags-win32
|
||||
Universal Ctags is preferred, Exuberant Ctags is no longer maintained.
|
||||
|
||||
If you want to complete system functions you can do something like this. Use
|
||||
ctags to generate a tags file for all the system header files: >
|
||||
@ -1459,7 +1451,7 @@ DOM compatibility
|
||||
At the moment (beginning of 2006) there are two main browsers - MS Internet
|
||||
Explorer and Mozilla Firefox. These two applications are covering over 90% of
|
||||
market. Theoretically standards are created by W3C organisation
|
||||
(http://www.w3c.org) but they are not always followed/implemented.
|
||||
(https://www.w3.org/) but they are not always followed/implemented.
|
||||
|
||||
IE FF W3C Omni completion ~
|
||||
+/- +/- + + ~
|
||||
@ -1480,7 +1472,6 @@ external files and for class aware completion. You should use Universal/
|
||||
Exuberant ctags version 5.5.4 or newer. You can find it here:
|
||||
|
||||
Universal Ctags: https://ctags.io
|
||||
Exuberant Ctags: http://ctags.sourceforge.net
|
||||
|
||||
Script completes:
|
||||
|
||||
@ -1779,12 +1770,12 @@ DTD -> Vim *dtd2vim*
|
||||
On |www| is the script |dtd2vim| which parses DTD and creates an XML data file
|
||||
for Vim XML omni completion.
|
||||
|
||||
dtd2vim: http://www.vim.org/scripts/script.php?script_id=1462
|
||||
dtd2vim: https://www.vim.org/scripts/script.php?script_id=1462
|
||||
|
||||
Check the beginning of that file for usage details.
|
||||
The script requires perl and:
|
||||
|
||||
perlSGML: http://savannah.nongnu.org/projects/perlsgml
|
||||
perlSGML: https://savannah.nongnu.org/projects/perlsgml
|
||||
|
||||
|
||||
Commands
|
||||
|
||||
@ -792,22 +792,19 @@ start({config}, {opts}) *vim.lsp.start()*
|
||||
See |vim.lsp.start_client()| for all available options. The most important
|
||||
are:
|
||||
|
||||
`name` is an arbitrary name for the LSP client. It should be unique per
|
||||
language server.
|
||||
|
||||
`cmd` the command as list - used to start the language server. The command must
|
||||
be present in the `$PATH` environment variable or an absolute path to the executable. Shell
|
||||
constructs like `~` are NOT expanded.
|
||||
|
||||
`root_dir` path to the project root. By default this is used to decide if
|
||||
an existing client should be re-used. The example above uses
|
||||
|vim.fs.find()| and |vim.fs.dirname()| to detect the root by traversing
|
||||
the file system upwards starting from the current directory until either a
|
||||
`pyproject.toml` or `setup.py` file is found.
|
||||
|
||||
`workspace_folders` a list of { uri:string, name: string } tables. The
|
||||
project root folders used by the language server. If `nil` the property is
|
||||
derived from the `root_dir` for convenience.
|
||||
• `name` arbitrary name for the LSP client. Should be unique per language
|
||||
server.
|
||||
• `cmd` command (in list form) used to start the language server. Must be
|
||||
absolute, or found on `$PATH`. Shell constructs like `~` are not
|
||||
expanded.
|
||||
• `root_dir` path to the project root. By default this is used to decide
|
||||
if an existing client should be re-used. The example above uses
|
||||
|vim.fs.find()| and |vim.fs.dirname()| to detect the root by traversing
|
||||
the file system upwards starting from the current directory until either
|
||||
a `pyproject.toml` or `setup.py` file is found.
|
||||
• `workspace_folders` list of `{ uri:string, name: string }` tables
|
||||
specifying the project root folders used by the language server. If
|
||||
`nil` the property is derived from `root_dir` for convenience.
|
||||
|
||||
Language servers use this information to discover metadata like the
|
||||
dependencies of your project and they tend to index the contents within
|
||||
|
||||
@ -4831,7 +4831,7 @@ A BIBLIOGRAPHY *luaref-bibliography*
|
||||
This help file is a minor adaptation from this main reference:
|
||||
|
||||
- R. Ierusalimschy, L. H. de Figueiredo, and W. Celes.,
|
||||
"Lua: 5.1 reference manual", http://www.lua.org/manual/5.1/manual.html
|
||||
"Lua: 5.1 reference manual", https://www.lua.org/manual/5.1/manual.html
|
||||
|
||||
Lua is discussed in these references:
|
||||
|
||||
@ -4887,10 +4887,10 @@ a few exceptions and adaptations -- a copy of the Lua 5.1 Reference Manual
|
||||
|
||||
The main ideas and concepts on how to implement this reference were taken from
|
||||
Christian Habermann's CRefVim project
|
||||
(http://www.vim.org/scripts/script.php?script_id=614).
|
||||
(https://www.vim.org/scripts/script.php?script_id=614).
|
||||
|
||||
Adapted for bundled Nvim documentation; the original plugin can be found at
|
||||
http://www.vim.org/scripts/script.php?script_id=1291
|
||||
https://www.vim.org/scripts/script.php?script_id=1291
|
||||
|
||||
------------------------------------------------------------------------------
|
||||
vi:tw=78:ts=4:ft=help:norl:et
|
||||
|
||||
@ -97,7 +97,7 @@ used here to facilitate documenting consistent behavior:
|
||||
CONTENTS *luv-contents*
|
||||
|
||||
This documentation is mostly a retelling of the libuv API documentation
|
||||
(http://docs.libuv.org/en/v1.x/api.html) within the context of luv's Lua API.
|
||||
(https://docs.libuv.org/en/v1.x/api.html) within the context of luv's Lua API.
|
||||
Low-level implementation details and unexposed C functions and types are not
|
||||
documented here except for when they are relevant to behavior seen in the Lua
|
||||
module.
|
||||
@ -933,7 +933,7 @@ uv.async_send({async}, {...}) *uv.async_send()*
|
||||
|
||||
Poll handles are used to watch file descriptors for readability and
|
||||
writability, similar to the purpose of poll(2)
|
||||
(http://linux.die.net/man/2/poll).
|
||||
(https://linux.die.net/man/2/poll).
|
||||
|
||||
The purpose of poll handles is to enable integrating external libraries that
|
||||
rely on the event loop to signal it about the socket status changes, like
|
||||
|
||||
@ -341,34 +341,7 @@ Useful utilities for converting the charset:
|
||||
All: iconv
|
||||
GNU iconv can convert most encodings. Unicode is used as the
|
||||
intermediate encoding, which allows conversion from and to all other
|
||||
encodings. See http://www.gnu.org/directory/libiconv.html.
|
||||
|
||||
Japanese: nkf
|
||||
Nkf is "Network Kanji code conversion Filter". One of the most unique
|
||||
facility of nkf is the guess of the input Kanji code. So, you don't
|
||||
need to know what the inputting file's |charset| is. When convert to
|
||||
EUC-JP from ISO-2022-JP or Shift_JIS, simply do the following command
|
||||
in Vim:
|
||||
:%!nkf -e
|
||||
Nkf can be found at:
|
||||
http://www.sfc.wide.ad.jp/~max/FreeBSD/ports/distfiles/nkf-1.62.tar.gz
|
||||
|
||||
Chinese: hc
|
||||
Hc is "Hanzi Converter". Hc convert a GB file to a Big5 file, or Big5
|
||||
file to GB file. Hc can be found at:
|
||||
ftp://ftp.cuhk.hk/pub/chinese/ifcss/software/unix/convert/hc-30.tar.gz
|
||||
|
||||
Korean: hmconv
|
||||
Hmconv is Korean code conversion utility especially for E-mail. It can
|
||||
convert between EUC-KR and ISO-2022-KR. Hmconv can be found at:
|
||||
ftp://ftp.kaist.ac.kr/pub/hangul/code/hmconv/
|
||||
|
||||
Multilingual: lv
|
||||
Lv is a Powerful Multilingual File Viewer. And it can be worked as
|
||||
|charset| converter. Supported |charset|: ISO-2022-CN, ISO-2022-JP,
|
||||
ISO-2022-KR, EUC-CN, EUC-JP, EUC-KR, EUC-TW, UTF-7, UTF-8, ISO-8859
|
||||
series, Shift_JIS, Big5 and HZ. Lv can be found at:
|
||||
http://www.ff.iij4u.or.jp/~nrt/lv/index.html
|
||||
encodings. See https://directory.fsf.org/wiki/Libiconv.
|
||||
|
||||
|
||||
*mbyte-conversion*
|
||||
@ -404,17 +377,6 @@ is suitable for complex input, such as CJK.
|
||||
large overhead in communication, but it provides safe synchronization with
|
||||
no restrictions on applications.
|
||||
|
||||
For example, there are xwnmo and kinput2 Japanese |IM-server|, both are
|
||||
FrontEnd system. Xwnmo is distributed with Wnn (see below), kinput2 can be
|
||||
found at: ftp://ftp.sra.co.jp/pub/x11/kinput2/
|
||||
|
||||
For Chinese, there's a great XIM server named "xcin", you can input both
|
||||
Traditional and Simplified Chinese characters. And it can accept other
|
||||
locale if you make a correct input table. Xcin can be found at:
|
||||
http://cle.linux.org.tw/xcin/
|
||||
Others are scim: http://scim.freedesktop.org/ and fcitx:
|
||||
http://www.fcitx.org/
|
||||
|
||||
- Conversion Server
|
||||
*conversion-server*
|
||||
Some system needs additional server: conversion server. Most of Japanese
|
||||
|
||||
@ -573,9 +573,7 @@ when using ":w"), therefore Vim requires using a ! after the command, e.g.:
|
||||
VirtualBinding
|
||||
|
||||
Messages like this appear when starting up. This is not a Vim problem, your
|
||||
X11 configuration is wrong. You can find a hint on how to solve this here:
|
||||
http://groups.yahoo.com/group/solarisonintel/message/12179.
|
||||
[this URL is no longer valid]
|
||||
X11 configuration is wrong.
|
||||
|
||||
*W10* >
|
||||
Warning: Changing a readonly file
|
||||
|
||||
@ -92,27 +92,10 @@ use of "-" and "_".
|
||||
:lang mes en
|
||||
<
|
||||
|
||||
MS-WINDOWS MESSAGE TRANSLATIONS *win32-gettext*
|
||||
|
||||
If you used the self-installing .exe file, message translations should work
|
||||
already. Otherwise get the libintl.dll file if you don't have it yet:
|
||||
|
||||
http://sourceforge.net/projects/gettext
|
||||
Or:
|
||||
https://mlocati.github.io/gettext-iconv-windows/
|
||||
|
||||
This also contains tools xgettext, msgformat and others.
|
||||
|
||||
libintl.dll should be placed in same directory as (g)vim.exe, or one of the
|
||||
directories listed in the PATH environment value. Vim also looks for the
|
||||
alternate names "libintl-8.dll" and "intl.dll".
|
||||
|
||||
Message files (vim.mo) have to be placed in "$VIMRUNTIME/lang/xx/LC_MESSAGES",
|
||||
where "xx" is the abbreviation of the language (mostly two letters).
|
||||
|
||||
If you write your own translations you need to generate the .po file and
|
||||
convert it to a .mo file. You need to get the source distribution and read
|
||||
the file "src/po/README.txt".
|
||||
where "xx" is the abbreviation of the language (mostly two letters). If you
|
||||
write your own translations you need to generate the .po file and convert it
|
||||
to a .mo file.
|
||||
|
||||
To overrule the automatic choice of the language, set the $LANG variable to
|
||||
the language of your choice. use "en" to disable translations. >
|
||||
|
||||
@ -621,7 +621,7 @@ A jump table for the options with a short description can be found at |Q_op|.
|
||||
by Vim with the width of glyphs in the font. Perhaps it also has
|
||||
to be set to "double" under CJK MS-Windows when the system locale is
|
||||
set to one of CJK locales. See Unicode Standard Annex #11
|
||||
(http://www.unicode.org/reports/tr11).
|
||||
(https://www.unicode.org/reports/tr11).
|
||||
|
||||
*'autochdir'* *'acd'* *'noautochdir'* *'noacd'*
|
||||
'autochdir' 'acd' boolean (default off)
|
||||
@ -4536,7 +4536,7 @@ A jump table for the options with a short description can be found at |Q_op|.
|
||||
< - A directory name may end in a ':' or '/'.
|
||||
- Environment variables are expanded |:set_env|.
|
||||
- When using |netrw.vim| URLs can be used. For example, adding
|
||||
"http://www.vim.org" will make ":find index.html" work.
|
||||
"https://www.vim.org" will make ":find index.html" work.
|
||||
- Search upwards and downwards in a directory tree using "*", "**" and
|
||||
";". See |file-searching| for info and syntax.
|
||||
- Careful with '\' characters, type two to get one in the option: >
|
||||
|
||||
@ -413,7 +413,7 @@ you need to define your own PostScript font encoding vector. Details on how
|
||||
to define a font encoding vector is beyond the scope of this help file, but
|
||||
you can find details in the PostScript Language Reference Manual, 3rd Edition,
|
||||
published by Addison-Wesley and available in PDF form at
|
||||
http://www.adobe.com/. The following describes what you need to do for Vim to
|
||||
https://www.adobe.com/. The following describes what you need to do for Vim to
|
||||
locate and use your print character encoding.
|
||||
|
||||
i. Decide on a unique name for your encoding vector, one that does not clash
|
||||
@ -462,15 +462,6 @@ option allows you to specify different fonts to use when printing characters
|
||||
which are syntax highlighted with the font styles normal, italic, bold and
|
||||
bold-italic.
|
||||
|
||||
No CJK fonts are supplied with Vim. There are some free Korean, Japanese, and
|
||||
Traditional Chinese fonts available at:
|
||||
|
||||
http://examples.oreilly.com/cjkvinfo/adobe/samples/
|
||||
|
||||
You can find descriptions of the various fonts in the read me file at
|
||||
|
||||
http://examples.oreilly.de/english_examples/cjkvinfo/adobe/00README
|
||||
|
||||
Please read your printer documentation on how to install new fonts.
|
||||
|
||||
CJK fonts can be large containing several thousand glyphs, and it is not
|
||||
@ -491,7 +482,7 @@ It is possible to define your own multibyte character set although this
|
||||
should not be attempted lightly. A discussion on the process if beyond the
|
||||
scope of these help files. You can find details on CMap (character map) files
|
||||
in the document 'Adobe CMap and CIDFont Files Specification, Version 1.0',
|
||||
available from http://www.adobe.com as a PDF file.
|
||||
available from https://www.adobe.com as a PDF file.
|
||||
|
||||
==============================================================================
|
||||
6. PostScript Printing Troubleshooting *postscript-print-trouble*
|
||||
@ -548,23 +539,8 @@ Ghostscript is a PostScript and PDF interpreter that can be used to display
|
||||
and print on non-PostScript printers PostScript and PDF files. It can also
|
||||
generate PDF files from PostScript.
|
||||
|
||||
Ghostscript will run on a wide variety of platforms.
|
||||
|
||||
There are three available versions:
|
||||
|
||||
- AFPL Ghostscript (formerly Aladdin Ghostscript) which is free for
|
||||
non-commercial use. It can be obtained from:
|
||||
|
||||
http://www.cs.wisc.edu/~ghost/
|
||||
|
||||
- GNU Ghostscript which is available under the GNU General Public License. It
|
||||
can be obtained from:
|
||||
|
||||
ftp://mirror.cs.wisc.edu/pub/mirrors/ghost/gnu/
|
||||
|
||||
- A commercial version for inclusion in commercial products.
|
||||
|
||||
Additional information on Ghostscript can also be found at:
|
||||
Ghostscript will run on a wide variety of platforms. Information on
|
||||
Ghostscript can be found at:
|
||||
|
||||
http://www.ghostscript.com/
|
||||
|
||||
@ -580,79 +556,6 @@ ends have been created. These allow easier PostScript file selection,
|
||||
previewing at different zoom levels, and printing. Check supplied
|
||||
documentation for full details.
|
||||
|
||||
X11
|
||||
|
||||
- Ghostview. Obtainable from:
|
||||
|
||||
http://www.cs.wisc.edu/~ghost/gv/
|
||||
|
||||
- gv. Derived from Ghostview. Obtainable from:
|
||||
|
||||
http://wwwthep.physik.uni-mainz.de/~plass/gv/
|
||||
|
||||
Copies (possibly not the most recent) can be found at:
|
||||
|
||||
http://www.cs.wisc.edu/~ghost/gv/
|
||||
|
||||
MS-Windows
|
||||
|
||||
- GSview. Obtainable from:
|
||||
|
||||
http://www.cs.wisc.edu/~ghost/gsview/
|
||||
|
||||
Linux
|
||||
|
||||
- GSview. Linux version of the popular MS-Windows previewer.
|
||||
Obtainable from:
|
||||
|
||||
http://www.cs.wisc.edu/~ghost/gsview/
|
||||
|
||||
- BMV. Different from Ghostview and gv in that it doesn't use X but svgalib.
|
||||
Obtainable from:
|
||||
|
||||
ftp://sunsite.unc.edu/pub/Linux/apps/graphics/viewers/svga/bmv-1.2.tgz
|
||||
|
||||
|
||||
7.3 PSUtils
|
||||
|
||||
PSUtils is a collection of utility programs for manipulating PostScript
|
||||
documents. Binary distributions are available for many platforms, as well as
|
||||
the full source. PSUtils can be found at:
|
||||
|
||||
http://knackered.org/angus/psutils
|
||||
|
||||
The utilities of interest include:
|
||||
|
||||
- psnup. Convert PS files for N-up printing.
|
||||
- psselect. Select page range and order of printing.
|
||||
- psresize. Change the page size.
|
||||
- psbook. Reorder and lay out pages ready for making a book.
|
||||
|
||||
The output of one program can be used as the input to the next, allowing for
|
||||
complex print document creation.
|
||||
|
||||
|
||||
N-UP PRINTING
|
||||
|
||||
The psnup utility takes an existing PostScript file generated from Vim and
|
||||
convert it to an n-up version. The simplest way to create a 2-up printout is
|
||||
to first create a PostScript file with: >
|
||||
|
||||
:hardcopy > test.ps
|
||||
|
||||
Then on your command line execute: >
|
||||
|
||||
psnup -n 2 test.ps final.ps
|
||||
|
||||
Note: You may get warnings from some Ghostscript previewers for files produced
|
||||
by psnup - these may safely be ignored.
|
||||
|
||||
Finally print the file final.ps to your PostScript printer with your
|
||||
platform's print command. (You will need to delete the two PostScript files
|
||||
afterwards yourself.) 'printexpr' could be modified to perform this extra
|
||||
step before printing.
|
||||
|
||||
|
||||
ALTERNATE DUPLEX PRINTING
|
||||
|
||||
It is possible to achieve a poor man's version of duplex printing using the PS
|
||||
|
||||
@ -191,7 +191,7 @@ registers. Nvim looks for these clipboard tools, in order of priority:
|
||||
- xclip (if $DISPLAY is set)
|
||||
- xsel (if $DISPLAY is set)
|
||||
- lemonade (for SSH) https://github.com/pocke/lemonade
|
||||
- doitclient (for SSH) http://www.chiark.greenend.org.uk/~sgtatham/doit/
|
||||
- doitclient (for SSH) https://www.chiark.greenend.org.uk/~sgtatham/doit/
|
||||
- win32yank (Windows)
|
||||
- termux (via termux-clipboard-set, termux-clipboard-set)
|
||||
- tmux (if $TMUX is set)
|
||||
|
||||
@ -1287,7 +1287,7 @@ PYUNIT COMPILER *compiler-pyunit*
|
||||
This is not actually a compiler, but a unit testing framework for the
|
||||
Python language. It is included into standard Python distribution
|
||||
starting from version 2.0. For older versions, you can get it from
|
||||
http://pyunit.sourceforge.net.
|
||||
https://pyunit.sourceforge.net.
|
||||
|
||||
When you run your tests with the help of the framework, possible errors
|
||||
are parsed by Vim and presented for you in quick-fix mode.
|
||||
@ -1298,8 +1298,6 @@ Useful values for the 'makeprg' options therefore are:
|
||||
setlocal makeprg=./alltests.py " Run a testsuite
|
||||
setlocal makeprg=python\ %:S " Run a single testcase
|
||||
|
||||
Also see http://vim.sourceforge.net/tip_view.php?tip_id=280.
|
||||
|
||||
|
||||
TEX COMPILER *compiler-tex*
|
||||
|
||||
@ -1823,7 +1821,7 @@ In English, that sed script:
|
||||
it as a "continuation of a multi-line message."
|
||||
|
||||
*errorformat-ant*
|
||||
For ant (http://jakarta.apache.org/) the above errorformat has to be modified
|
||||
For ant (https://jakarta.apache.org/) the above errorformat has to be modified
|
||||
to honour the leading [javac] in front of each javac output line: >
|
||||
:set efm=%A\ %#[javac]\ %f:%l:\ %m,%-Z\ %#[javac]\ %p^,%-C%.%#
|
||||
|
||||
|
||||
@ -45,7 +45,7 @@ If you wish to use messages, help files, menus and other items translated to
|
||||
Russian, you will need to install the RuVim Language Pack, available in
|
||||
different codepages from
|
||||
|
||||
http://www.sourceforge.net/projects/ruvim/
|
||||
https://www.sourceforge.net/projects/ruvim/
|
||||
|
||||
After downloading an archive from RuVim project, unpack it into your
|
||||
$VIMRUNTIME directory. We recommend using UTF-8 archive.
|
||||
|
||||
@ -482,7 +482,7 @@ You can create a Vim spell file from the .aff and .dic files that Myspell
|
||||
uses. Myspell is used by OpenOffice.org and Mozilla. The OpenOffice .oxt
|
||||
files are zip files which contain the .aff and .dic files. You should be able
|
||||
to find them here:
|
||||
http://extensions.services.openoffice.org/dictionary
|
||||
https://extensions.services.openoffice.org/dictionary
|
||||
The older, OpenOffice 2 files may be used if this doesn't work:
|
||||
http://wiki.services.openoffice.org/wiki/Dictionaries
|
||||
You can also use a plain word list. The results are the same, the choice
|
||||
@ -764,13 +764,13 @@ them before the Vim word list is made. The tools for this can be found in the
|
||||
The format for the affix and word list files is based on what Myspell uses
|
||||
(the spell checker of Mozilla and OpenOffice.org). A description can be found
|
||||
here:
|
||||
http://lingucomponent.openoffice.org/affix.readme ~
|
||||
https://lingucomponent.openoffice.org/affix.readme ~
|
||||
Note that affixes are case sensitive, this isn't obvious from the description.
|
||||
|
||||
Vim supports quite a few extras. They are described below |spell-affix-vim|.
|
||||
Attempts have been made to keep this compatible with other spell checkers, so
|
||||
that the same files can often be used. One other project that offers more
|
||||
than Myspell is Hunspell ( http://hunspell.sf.net ).
|
||||
than Myspell is Hunspell ( https://hunspell.github.io ).
|
||||
|
||||
|
||||
WORD LIST FORMAT *spell-dic-format*
|
||||
@ -886,7 +886,7 @@ right encoding.
|
||||
*spell-AUTHOR* *spell-EMAIL* *spell-COPYRIGHT*
|
||||
NAME Name of the language
|
||||
VERSION 1.0.1 with fixes
|
||||
HOME http://www.myhome.eu
|
||||
HOME https://www.example.com
|
||||
AUTHOR John Doe
|
||||
EMAIL john AT Doe DOT net
|
||||
COPYRIGHT LGPL
|
||||
|
||||
@ -687,13 +687,13 @@ Automatic detection works for the encodings mentioned specifically by name in
|
||||
|encoding-names|, but TOhtml will only automatically use those encodings with
|
||||
wide browser support. However, you can override this to support specific
|
||||
encodings that may not be automatically detected by default (see options
|
||||
below). See http://www.iana.org/assignments/character-sets for the IANA names.
|
||||
below). See https://www.iana.org/assignments/character-sets for the IANA names.
|
||||
|
||||
Note: By default all Unicode encodings are converted to UTF-8 with no BOM in
|
||||
the generated HTML, as recommended by W3C:
|
||||
|
||||
http://www.w3.org/International/questions/qa-choosing-encodings
|
||||
http://www.w3.org/International/questions/qa-byte-order-mark
|
||||
https://www.w3.org/International/questions/qa-choosing-encodings
|
||||
https://www.w3.org/International/questions/qa-byte-order-mark
|
||||
|
||||
*g:html_use_encoding*
|
||||
Default: none, uses IANA name for current 'fileencoding' as above.
|
||||
@ -832,7 +832,7 @@ files are included:
|
||||
asm68k Motorola 680x0 assembly
|
||||
asmh8300 Hitachi H-8300 version of GNU assembly
|
||||
ia64 Intel Itanium 64
|
||||
fasm Flat assembly (http://flatassembler.net)
|
||||
fasm Flat assembly (https://flatassembler.net)
|
||||
masm Microsoft assembly (probably works for any 80x86)
|
||||
nasm Netwide assembly
|
||||
tasm Turbo Assembly (with opcodes 80x86 up to Pentium, and
|
||||
@ -1393,9 +1393,9 @@ Two syntax highlighting files exist for Euphoria. One for Euphoria
|
||||
version 3.1.1, which is the default syntax highlighting file, and one for
|
||||
Euphoria version 4.0.5 or later.
|
||||
|
||||
Euphoria version 3.1.1 (http://www.rapideuphoria.com/) is still necessary
|
||||
Euphoria version 3.1.1 (https://www.rapideuphoria.com/) is still necessary
|
||||
for developing applications for the DOS platform, which Euphoria version 4
|
||||
(http://www.openeuphoria.org/) does not support.
|
||||
(https://www.openeuphoria.org/) does not support.
|
||||
|
||||
The following file extensions are auto-detected as Euphoria file type:
|
||||
|
||||
@ -1452,7 +1452,7 @@ Elixir.
|
||||
|
||||
FLEXWIKI *flexwiki.vim* *ft-flexwiki-syntax*
|
||||
|
||||
FlexWiki is an ASP.NET-based wiki package available at http://www.flexwiki.com
|
||||
FlexWiki is an ASP.NET-based wiki package available at https://www.flexwiki.com
|
||||
NOTE: This site currently doesn't work, on Wikipedia is mentioned that
|
||||
development stopped in 2009.
|
||||
|
||||
@ -1808,7 +1808,7 @@ are read during initialization) >
|
||||
:let html_my_rendering=1
|
||||
|
||||
If you'd like to see an example download mysyntax.vim at
|
||||
http://www.fleiner.com/vim/download.html
|
||||
https://www.fleiner.com/vim/download.html
|
||||
|
||||
You can also disable this rendering by adding the following line to your
|
||||
vimrc file: >
|
||||
@ -1936,7 +1936,7 @@ highlight them use: >
|
||||
:let java_highlight_java_lang_ids=1
|
||||
|
||||
You can also highlight identifiers of most standard Java packages if you
|
||||
download the javaid.vim script at http://www.fleiner.com/vim/download.html.
|
||||
download the javaid.vim script at https://www.fleiner.com/vim/download.html.
|
||||
If you prefer to only highlight identifiers of a certain package, say java.io
|
||||
use the following: >
|
||||
:let java_highlight_java_io=1
|
||||
@ -3353,13 +3353,11 @@ of specialized LaTeX commands, syntax, and fonts. If you're using such a
|
||||
package you'll often wish that the distributed syntax/tex.vim would support
|
||||
it. However, clearly this is impractical. So please consider using the
|
||||
techniques in |mysyntaxfile-add| to extend or modify the highlighting provided
|
||||
by syntax/tex.vim. Please consider uploading any extensions that you write,
|
||||
which typically would go in $HOME/after/syntax/tex/[pkgname].vim, to
|
||||
http://vim.sf.net/.
|
||||
by syntax/tex.vim.
|
||||
|
||||
I've included some support for various popular packages on my website: >
|
||||
|
||||
http://www.drchip.org/astronaut/vim/index.html#LATEXPKGS
|
||||
https://www.drchip.org/astronaut/vim/index.html#LATEXPKGS
|
||||
<
|
||||
The syntax files there go into your .../after/syntax/tex/ directory.
|
||||
|
||||
@ -5397,8 +5395,7 @@ WARNING: The longer the tags file, the slower this will be, and the more
|
||||
memory Vim will consume.
|
||||
|
||||
Only highlighting typedefs, unions and structs can be done too. For this you
|
||||
must use Universal Ctags (found at https://ctags.io) or Exuberant ctags (found
|
||||
at http://ctags.sf.net).
|
||||
must use Universal Ctags (https://ctags.io) or Exuberant ctags.
|
||||
|
||||
Put these lines in your Makefile:
|
||||
|
||||
|
||||
@ -514,18 +514,13 @@ ctags As found on most Unix systems. Only supports C. Only
|
||||
universal ctags A maintained version of ctags based on exuberant
|
||||
ctags. See https://ctags.io.
|
||||
*Exuberant_ctags*
|
||||
exuberant ctags This is a very good one. It works for C, C++, Java,
|
||||
Fortran, Eiffel and others. It can generate tags for
|
||||
many items. See http://ctags.sourceforge.net.
|
||||
No new version since 2009.
|
||||
exuberant ctags Works for C, C++, Java, Fortran, Eiffel and others.
|
||||
See https://ctags.sourceforge.net. No new version
|
||||
since 2009.
|
||||
JTags For Java, in Java. It can be found at
|
||||
http://www.fleiner.com/jtags/.
|
||||
https://www.fleiner.com/jtags/.
|
||||
ptags.py For Python, in Python. Found in your Python source
|
||||
directory at Tools/scripts/ptags.py.
|
||||
ptags For Perl, in Perl. It can be found at
|
||||
http://www.eleves.ens.fr:8080/home/nthiery/Tags/.
|
||||
gnatxref For Ada. See http://www.gnuada.org/. gnatxref is
|
||||
part of the gnat package.
|
||||
|
||||
|
||||
The lines in the tags file must have one of these two formats:
|
||||
|
||||
@ -29,7 +29,7 @@ whole.
|
||||
Building your own terminfo is usually as simple as running this as
|
||||
a non-superuser:
|
||||
>
|
||||
curl -LO http://invisible-island.net/datafiles/current/terminfo.src.gz
|
||||
curl -LO https://invisible-island.net/datafiles/current/terminfo.src.gz
|
||||
gunzip terminfo.src.gz
|
||||
tic terminfo.src
|
||||
<
|
||||
|
||||
@ -8,7 +8,7 @@ Tips and ideas for using Vim *tips*
|
||||
|
||||
These are just a few that we thought would be helpful for many users.
|
||||
You can find many more tips on the wiki. The URL can be found on
|
||||
http://www.vim.org
|
||||
https://www.vim.org
|
||||
|
||||
Don't forget to browse the user manual, it also contains lots of useful tips
|
||||
|usr_toc.txt|.
|
||||
|
||||
@ -11,9 +11,9 @@ Vim is Charityware. You can use and copy it as much as you like, but you are
|
||||
encouraged to make a donation for needy children in Uganda. Please see |kcc|
|
||||
below or visit the ICCF web site, available at these URLs:
|
||||
|
||||
http://iccf-holland.org/
|
||||
http://www.vim.org/iccf/
|
||||
http://www.iccf.nl/
|
||||
https://iccf-holland.org/
|
||||
https://www.vim.org/iccf/
|
||||
https://www.iccf.nl/
|
||||
|
||||
You can also sponsor the development of Vim. Vim sponsors can vote for
|
||||
features. See |sponsor|. The money goes to Uganda anyway.
|
||||
@ -239,7 +239,7 @@ Holland: Transfer to the account of "Stichting ICCF Holland" in Lisse.
|
||||
|
||||
Germany: It is possible to make donations that allow for a tax return.
|
||||
Check the ICCF web site for the latest information:
|
||||
http://iccf-holland.org/germany.html
|
||||
https://iccf-holland.org/germany.html
|
||||
|
||||
World: Use a postal money order. That should be possible from any
|
||||
country, mostly from the post office. Use this name (which is
|
||||
|
||||
@ -28,12 +28,14 @@ with these (optional) keys:
|
||||
- `rgb` Decides the color format.
|
||||
- true: (default) 24-bit RGB colors
|
||||
- false: Terminal colors (8-bit, max 256)
|
||||
|
||||
*ui-override*
|
||||
- `override` Decides how UI capabilities are resolved.
|
||||
- true: Enable requested UI capabilities, even if not
|
||||
supported by all connected UIs (including |TUI|).
|
||||
- false: (default) Disable UI capabilities not
|
||||
supported by all connected UIs (including TUI).
|
||||
|
||||
*ui-ext-options*
|
||||
- `ext_cmdline` Externalize the cmdline. |ui-cmdline|
|
||||
- `ext_hlstate` Detailed highlight state. |ui-hlstate|
|
||||
@ -130,14 +132,18 @@ procedure:
|
||||
|
||||
1. Invoke |nvim_get_api_info()|, if needed to setup the client library and/or
|
||||
to get the list of supported UI extensions.
|
||||
|
||||
2. Do any configuration that should be happen before user config is loaded.
|
||||
Buffers and windows are not available at this point, but this could be used
|
||||
to set |g:| variables visible to init.vim
|
||||
|
||||
3. If the UI wants to do additional setup after user config is loaded,
|
||||
register a VimEnter autocmd: >
|
||||
nvim_command("autocmd VimEnter * call rpcrequest(1, 'vimenter')")
|
||||
<4. Now invoke |nvim_ui_attach()|. The UI must handle user input by now:
|
||||
|
||||
4. Now invoke |nvim_ui_attach()|. The UI must handle user input by now:
|
||||
sourcing init.vim and loading buffers might lead to blocking prompts.
|
||||
|
||||
5. If step 3 was used, Nvim will send a blocking "vimenter" request to the UI.
|
||||
Inside this request handler, the UI can safely do any initialization before
|
||||
entering normal mode, for example reading variables set by init.vim.
|
||||
|
||||
@ -85,7 +85,7 @@ The Vim user manual and reference manual are Copyright (c) 1988-2003 by Bram
|
||||
Moolenaar. This material may be distributed only subject to the terms and
|
||||
conditions set forth in the Open Publication License, v1.0 or later. The
|
||||
latest version is presently available at:
|
||||
http://www.opencontent.org/openpub/
|
||||
https://www.opencontent.org/openpub/
|
||||
|
||||
People who contribute to the manuals must agree with the above copyright
|
||||
notice.
|
||||
|
||||
@ -320,7 +320,7 @@ Where can you find plugins?
|
||||
- Some are always loaded, you can see them in the directory $VIMRUNTIME/plugin.
|
||||
- Some come with Vim. You can find them in the directory $VIMRUNTIME/macros
|
||||
and its sub-directories and under $VIM/vimfiles/pack/dist/opt/.
|
||||
- Download from the net. There is a large collection on http://www.vim.org.
|
||||
- Download from the net. There is a large collection on https://www.vim.org.
|
||||
- They are sometimes posted in a Vim maillist.
|
||||
- You could write one yourself, see |write-plugin|.
|
||||
|
||||
|
||||
@ -33,9 +33,8 @@ following command: >
|
||||
ctags *.c
|
||||
|
||||
"ctags" is a separate program. Most Unix systems already have it installed.
|
||||
If you do not have it yet, you can find Universal/Exuberant ctags at:
|
||||
http://ctags.io ~
|
||||
http://ctags.sf.net ~
|
||||
If you do not have it yet, you can find Universal ctags at:
|
||||
https://ctags.io ~
|
||||
|
||||
Universal ctags is preferred, Exuberant ctags is no longer being developed.
|
||||
|
||||
|
||||
@ -2623,7 +2623,7 @@ Further reading: |autoload|.
|
||||
==============================================================================
|
||||
*41.16* Distributing Vim scripts *distribute-script*
|
||||
|
||||
Vim users will look for scripts on the Vim website: http://www.vim.org.
|
||||
Vim users will look for scripts on the Vim website: https://www.vim.org.
|
||||
If you made something that is useful for others, share it!
|
||||
|
||||
Vim scripts can be used on any system. There might not be a tar or gzip
|
||||
|
||||
@ -71,8 +71,8 @@ directory src/po/README.txt.
|
||||
programmer. You must know both English and the language you are translating
|
||||
to, of course.
|
||||
When you are satisfied with the translation, consider making it available
|
||||
to others. Upload it at vim-online (http://vim.sf.net) or e-mail it to
|
||||
the Vim maintainer <maintainer@vim.org>. Or both.
|
||||
to others. Upload it to https://github.com/vim/vim or e-mail it to the Vim
|
||||
maintainer <maintainer@vim.org>. Or both.
|
||||
|
||||
==============================================================================
|
||||
*45.2* Language for Menus
|
||||
@ -166,10 +166,7 @@ script files, etc. You can regard 'encoding' as the setting for the internals
|
||||
of Vim.
|
||||
This example assumes you have this font on your system. The name in the
|
||||
example is for the X Window System. This font is in a package that is used to
|
||||
enhance xterm with Unicode support. If you don't have this font, you might
|
||||
find it here:
|
||||
|
||||
http://www.cl.cam.ac.uk/~mgk25/download/ucs-fonts.tar.gz ~
|
||||
enhance xterm with Unicode support.
|
||||
|
||||
For MS-Windows, some fonts have a limited number of Unicode characters. Try
|
||||
using the "Courier New" font. You can use the Edit/Select Font... menu to
|
||||
@ -178,10 +175,7 @@ though. Example: >
|
||||
|
||||
:set guifont=courier_new:h12
|
||||
|
||||
If it doesn't work well, try getting a fontpack. If Microsoft didn't move it,
|
||||
you can find it here:
|
||||
|
||||
http://www.microsoft.com/typography/fonts/default.aspx ~
|
||||
If it doesn't work well, try getting a fontpack.
|
||||
|
||||
Now you have told Vim to use Unicode internally and display text with a
|
||||
Unicode font.
|
||||
|
||||
@ -158,7 +158,7 @@ Working intuitively and consistently is a major goal of Nvim.
|
||||
- Nvim avoids features that cannot be provided on all platforms; instead that
|
||||
is delegated to external plugins/extensions. E.g. the `-X` platform-specific
|
||||
option is "sometimes" available in Vim (with potential surprises:
|
||||
http://stackoverflow.com/q/14635295).
|
||||
https://stackoverflow.com/q/14635295).
|
||||
|
||||
- Vim's internal test functions (test_autochdir(), test_settime(), etc.) are
|
||||
not exposed (nor implemented); instead Nvim has a robust API.
|
||||
|
||||
@ -824,23 +824,16 @@ end
|
||||
---
|
||||
--- See |vim.lsp.start_client()| for all available options. The most important are:
|
||||
---
|
||||
--- `name` is an arbitrary name for the LSP client. It should be unique per
|
||||
--- language server.
|
||||
---
|
||||
--- `cmd` the command as list - used to start the language server.
|
||||
--- The command must be present in the `$PATH` environment variable or an
|
||||
--- absolute path to the executable. Shell constructs like `~` are *NOT* expanded.
|
||||
---
|
||||
--- `root_dir` path to the project root.
|
||||
--- By default this is used to decide if an existing client should be re-used.
|
||||
--- The example above uses |vim.fs.find()| and |vim.fs.dirname()| to detect the
|
||||
--- root by traversing the file system upwards starting
|
||||
--- from the current directory until either a `pyproject.toml` or `setup.py`
|
||||
--- file is found.
|
||||
---
|
||||
--- `workspace_folders` a list of { uri:string, name: string } tables.
|
||||
--- The project root folders used by the language server.
|
||||
--- If `nil` the property is derived from the `root_dir` for convenience.
|
||||
--- - `name` arbitrary name for the LSP client. Should be unique per language server.
|
||||
--- - `cmd` command (in list form) used to start the language server. Must be absolute, or found on
|
||||
--- `$PATH`. Shell constructs like `~` are not expanded.
|
||||
--- - `root_dir` path to the project root. By default this is used to decide if an existing client
|
||||
--- should be re-used. The example above uses |vim.fs.find()| and |vim.fs.dirname()| to detect the
|
||||
--- root by traversing the file system upwards starting from the current directory until either
|
||||
--- a `pyproject.toml` or `setup.py` file is found.
|
||||
--- - `workspace_folders` list of `{ uri:string, name: string }` tables specifying the project root
|
||||
--- folders used by the language server. If `nil` the property is derived from `root_dir` for
|
||||
--- convenience.
|
||||
---
|
||||
--- Language servers use this information to discover metadata like the
|
||||
--- dependencies of your project and they tend to index the contents within the
|
||||
|
||||
14
runtime/pack/dist/opt/vimball/doc/vimball.txt
vendored
14
runtime/pack/dist/opt/vimball/doc/vimball.txt
vendored
@ -88,7 +88,7 @@ MAKING A VIMBALL *:MkVimball*
|
||||
If you wish to force slashes into the filename, that can also be done
|
||||
by using the exclamation mark (ie. :MkVimball! path/filename).
|
||||
|
||||
The tip at http://vim.wikia.com/wiki/Using_VimBall_with_%27Make%27
|
||||
The tip at https://vim.wikia.com/wiki/Using_VimBall_with_%27Make%27
|
||||
has a good idea on how to automate the production of vimballs using
|
||||
make.
|
||||
|
||||
@ -171,12 +171,12 @@ WINDOWS *vimball-windows*
|
||||
>
|
||||
Item Tool/Suite Free Website
|
||||
---- ---------- ---- -------
|
||||
7zip tool y http://www.7-zip.org/
|
||||
Winzip tool n http://www.winzip.com/downwz.htm
|
||||
unxutils suite y http://unxutils.sourceforge.net/
|
||||
cygwin suite y http://www.cygwin.com/
|
||||
GnuWin32 suite y http://gnuwin32.sourceforge.net/
|
||||
MinGW suite y http://www.mingw.org/
|
||||
7zip tool y https://www.7-zip.org/
|
||||
Winzip tool n https://www.winzip.com/downwz.htm
|
||||
unxutils suite y https://unxutils.sourceforge.net/
|
||||
cygwin suite y https://www.cygwin.com/
|
||||
GnuWin32 suite y https://gnuwin32.sourceforge.net/
|
||||
MinGW suite y https://www.mingw.org/
|
||||
<
|
||||
|
||||
==============================================================================
|
||||
|
||||
@ -319,6 +319,16 @@ local function validate_link(node, bufnr, fname)
|
||||
return helppage, tagname, ignored
|
||||
end
|
||||
|
||||
local function validate_url(text, fname)
|
||||
local ignored = false
|
||||
if vim.fs.basename(fname) == 'pi_netrw.txt' then
|
||||
ignored = true
|
||||
elseif text:find('http%:') then
|
||||
invalid_urls[text] = vim.fs.basename(fname)
|
||||
end
|
||||
return ignored
|
||||
end
|
||||
|
||||
-- Traverses the tree at `root` and checks that |tag| links point to valid helptags.
|
||||
local function visit_validate(root, level, lang_tree, opt, stats)
|
||||
level = level or 0
|
||||
@ -353,9 +363,7 @@ local function visit_validate(root, level, lang_tree, opt, stats)
|
||||
end
|
||||
end
|
||||
elseif node_name == 'url' then
|
||||
if text:find('http%:') then
|
||||
invalid_urls[text] = vim.fs.basename(opt.fname)
|
||||
end
|
||||
validate_url(text, opt.fname)
|
||||
elseif node_name == 'taglink' or node_name == 'optionlink' then
|
||||
local _, _, _ = validate_link(root, opt.buf, opt.fname)
|
||||
end
|
||||
|
||||
@ -12,15 +12,10 @@ Flow:
|
||||
update_params_map /
|
||||
render_node
|
||||
|
||||
This would be easier using lxml and XSLT, but:
|
||||
TODO: eliminate this script and use Lua+treesitter (requires parsers for C and
|
||||
Lua markdown-style docstrings).
|
||||
|
||||
1. This should avoid needing Python dependencies, especially ones that are
|
||||
C modules that have library dependencies (lxml requires libxml and
|
||||
libxslt).
|
||||
2. I wouldn't know how to deal with nested indentation in <para> tags using
|
||||
XSLT.
|
||||
|
||||
Each function :help block is formatted as follows:
|
||||
The generated :help text for each function is formatted as follows:
|
||||
|
||||
- Max width of 78 columns (`text_width`).
|
||||
- Indent with spaces (not tabs).
|
||||
|
||||
2
src/unicode/Copyright.txt
vendored
2
src/unicode/Copyright.txt
vendored
@ -2,7 +2,7 @@ COPYRIGHT AND PERMISSION NOTICE
|
||||
|
||||
Copyright © 1991-2015 Unicode, Inc. All rights reserved.
|
||||
Distributed under the Terms of Use in
|
||||
http://www.unicode.org/copyright.html.
|
||||
https://www.unicode.org/copyright.html.
|
||||
|
||||
Permission is hereby granted, free of charge, to any person obtaining
|
||||
a copy of the Unicode data files and any associated documentation
|
||||
|
||||
Loading…
Reference in New Issue
Block a user