Mercurial > vim

comparison runtime/doc/syntax.txt @ 2788:0877b8d6370e

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
Updated runtime files.
author Bram Moolenaar <bram@vim.org>
date Thu, 28 Apr 2011 19:02:44 +0200
parents b0d34143ebfc
children 3c7da93eb7f9
comparison
equal deleted inserted replaced
2787:52775cc91f18 2788:0877b8d6370e
1 *syntax.txt* For Vim version 7.3. Last change: 2011 Apr 01 1 *syntax.txt* For Vim version 7.3. Last change: 2011 Apr 06
2 2
3 3
4 VIM REFERENCE MANUAL by Bram Moolenaar 4 VIM REFERENCE MANUAL by Bram Moolenaar
5 5
6 6
466 :let g:html_hover_unfold = 1 466 :let g:html_hover_unfold = 1
467 467
468 Setting html_no_foldcolumn with html_dynamic_folds will automatically set 468 Setting html_no_foldcolumn with html_dynamic_folds will automatically set
469 html_hover_unfold, because otherwise the folds wouldn't be dynamic. 469 html_hover_unfold, because otherwise the folds wouldn't be dynamic.
470 470
471 By default "<pre>" and "</pre>" is used around the text. This makes it show 471 By default "<pre>" and "</pre>" are used around the text. When 'wrap' is set
472 up as you see it in Vim, but without wrapping. If you prefer wrapping, at the 472 in the window being converted, the CSS 2.0 "white-space:pre-wrap" value is
473 risk of making some things look a bit different, use: > 473 used to wrap the text. You can explicitly enable the wrapping with: >
474 :let g:html_pre_wrap = 1
475 or disable with >
476 :let g:html_pre_wrap = 0
477 This generates HTML that looks very close to the Vim window, but unfortunately
478 there can be minor differences such as the lack of a 'showbreak' option in in
479 the HTML, or where line breaks can occur.
480
481 Another way to obtain text wrapping in the HTML, at the risk of making some
482 things look even more different, is to use: >
474 :let g:html_no_pre = 1 483 :let g:html_no_pre = 1
475 This will use <br> at the end of each line and use "&nbsp;" for repeated 484 This will use <br> at the end of each line and use "&nbsp;" for repeated
476 spaces. 485 spaces. Doing it this way is more compatible with old browsers, but modern
477 486 browsers support the "white-space" method.
478 If you do use the "<pre>" tags, <Tab> characters in the text are included in 487
479 the generated output if they will have no effect on the appearance of the 488 If you do stick with the default "<pre>" tags, <Tab> characters in the text
480 text and it looks like they are in the document intentionally. This allows for 489 are included in the generated output if they will have no effect on the
481 the HTML output to be copied and pasted from a browser without losing the 490 appearance of the text and it looks like they are in the document
482 actual whitespace used in the document. 491 intentionally. This allows for the HTML output to be copied and pasted from a
492 browser without losing the actual whitespace used in the document.
483 493
484 Specifically, <Tab> characters will be included if the 'tabstop' option is set 494 Specifically, <Tab> characters will be included if the 'tabstop' option is set
485 to the default of 8, 'expandtab' is not set, and if neither the foldcolumn nor 495 to the default of 8, 'expandtab' is not set, and if neither the foldcolumn nor
486 the line numbers are included in the HTML output (see options above). When any 496 the line numbers are included in the HTML output (see options above). When any
487 of these conditions are not met, any <Tab> characters in the text are expanded 497 of these conditions are not met, any <Tab> characters in the text are expanded
500 mentioning the total number of inserted lines. If you prefer to see all the 510 mentioning the total number of inserted lines. If you prefer to see all the
501 inserted lines as with the side-by-side diff, use: > 511 inserted lines as with the side-by-side diff, use: >
502 :let g:html_whole_filler = 1 512 :let g:html_whole_filler = 1
503 And to go back to displaying up to three lines again: > 513 And to go back to displaying up to three lines again: >
504 :unlet g:html_whole_filler 514 :unlet g:html_whole_filler
505 < 515
506 TOhtml uses the current value of 'fileencoding' if set, or 'encoding' if not, 516 For most buffers, TOhtml uses the current value of 'fileencoding' if set, or
507 to determine the charset and 'fileencoding' of the HTML file. In general, this 517 'encoding' if not, to determine the charset and 'fileencoding' of the HTML
508 works for the encodings mentioned specifically by name in |encoding-names|, but 518 file. 'encoding' is always used for certain 'buftype' values. In general, this
509 TOhtml will only automatically use those encodings which are widely supported. 519 works for the encodings mentioned specifically by name in |encoding-names|,
510 However, you can override this to support specific encodings that may not be 520 but TOhtml will only automatically use those encodings which are widely
511 automatically detected by default. 521 supported. However, you can override this to support specific encodings that
522 may not be automatically detected by default.
512 523
513 To overrule all automatic charset detection, set g:html_use_encoding to the 524 To overrule all automatic charset detection, set g:html_use_encoding to the
514 name of the charset to be used. TOhtml will try to determine the appropriate 525 name of the charset to be used. TOhtml will try to determine the appropriate
515 'fileencoding' setting from the charset, but you may need to set it manually 526 'fileencoding' setting from the charset, but you may need to set it manually
516 if TOhtml cannot determine the encoding. It is recommended to set this 527 if TOhtml cannot determine the encoding. It is recommended to set this