diff options
| author | Daniel Baumann <daniel.baumann@progress-linux.org> | 2024-04-07 08:50:33 +0000 |
|---|---|---|
| committer | Daniel Baumann <daniel.baumann@progress-linux.org> | 2024-04-07 08:50:33 +0000 |
| commit | 1333020b904a8714d01f4ae4789c5070e8ff90f2 (patch) | |
| tree | 338ef4570c790f46661f010deeebaaecc58c9bbc /debian | |
| parent | Adding upstream version 2:9.0.1378. (diff) | |
| download | vim-1333020b904a8714d01f4ae4789c5070e8ff90f2.tar.xz vim-1333020b904a8714d01f4ae4789c5070e8ff90f2.zip | |
Adding debian version 2:9.0.1378-2.debian/2%9.0.1378-2debian
Signed-off-by: Daniel Baumann <daniel.baumann@progress-linux.org>
Diffstat (limited to '')
78 files changed, 19512 insertions, 0 deletions
diff --git a/debian/FAQ b/debian/FAQ new file mode 100644 index 0000000..bf70b7e --- /dev/null +++ b/debian/FAQ @@ -0,0 +1,7700 @@ +vim:tw=75:wrap:fo=tcqn2:sw=4:sts=4:et + +This Vim FAQ is created from the questions and answers posted to the +vim@vim.org user mailing list and the comp.editors newsgroup. There are +several ways to solve a problem in Vim. This FAQ gives one of those several +possibilities. You can explore the other ways using the information and +links given in this FAQ. The credit for the answers in this FAQ goes to +Peppe, Benji, Charles Campbell and numerous others. + +INDEX + +SECTION 1 - GENERAL INFORMATION + 1.1. What is Vim? + 1.2. Who wrote Vim? + 1.3. Is Vim compatible with Vi? + 1.4. What are some of the improvements of Vim over Vi? + 1.5. Is Vim free? + +SECTION 2 - RESOURCES + 2.1. Where can I learn more about Vim? + 2.2. Is there a mailing list available? + 2.3. Is there an archive available for the Vim mailing lists? + 2.4. Where can I get the Vim user manual in HTML/PDF/PS format? + 2.5. I have a "xyz" (some) problem with Vim. How do I determine it is a + problem with my setup or with Vim? + 2.6. Where can I report bugs? + 2.7. Where can the FAQ be found? + 2.8. What if I don't find an answer in this FAQ? + 2.9. I have a patch for implementing a Vim feature. Where do I send the + patch? + 2.10. I have a Vim tip or developed a new Vim + syntax/indent/filetype/compiler plugin or developed a new script + or a colorscheme. Is there a public website where I can upload + this? + +SECTION 3 - AVAILABILITY + 3.1. What is the latest version of Vim? + 3.2. Where can I find the latest version of Vim? + 3.3. What platforms does it run on? + 3.4. Where can I download the latest version of the Vim runtime files? + +SECTION 4 - HELP + 4.1. How do I use the help files? + 4.2. How do I search for a keyword in the Vim help files? + 4.3. I am getting an error message E123, what did I do wrong? + 4.4. Where can I read about the various modes in Vim? + 4.5. How do I generate the Vim help tags file after adding a new Vim + help file? + 4.6. Can I use compressed versions of the help files? + +SECTION 5 - EDITING A FILE + 5.1. How do I load a file in Vim for editing? + 5.2. How do I save the current file in another name (save as) and edit + a new file? + 5.3. How do I change the current directory to the directory of the + current file? + 5.4. How do I write a file without the line feed (EOL) at the end of + the file? + 5.5. How do I configure Vim to open a file at the last edited location? + 5.6. When editing a file in Vim, which is being changed by an external + application, Vim opens a warning window (like the confirm dialog) + each time a change is detected. How do I disable this warning? + 5.7. How do I edit a file whose name is under the cursor? + 5.8. How do I reload/re-edit the current file? + 5.9. How do I autosave a file periodically? + 5.10. How do I open a file in read-only mode? + 5.11. How do I open a file for editing without saving the modifications + to the current file? + +SECTION 6 - EDITING MULTIPLE FILES + 6.1. How do I open multiple files at once from within Vim? + 6.2. How do I switch between multiple files/buffers in Vim? + 6.3. How do I open several files in Vim, with each file in a separate + window? + 6.4. How do I configure Vim to autoload several files at once similar + to "work-sets" or "projects"? + 6.5. Is it possible to open multiple top level windows in a single + instance of Vim similar to Nedit or emacs? + 6.6. How do I browse/explore directories from within Vim? + 6.7. How do I edit files over a network using ftp/scp/rcp/http? + +SECTION 7 - BACKUP + 7.1. When I edit and save files, Vim creates a file with the same name + as the original file and a "~" character at the end. How do I stop + Vim from creating this file (or) How do I disable the Vim backup + file feature? + 7.2. How do I configure Vim to store all the backup files in a + particular directory? + 7.3. When I save a file with Vim, the file permissions are changed. + How do I configure Vim to save a file without changing the file + permissions? + +SECTION 8 - BUFFERS + 8.1. I have made some modifications to a buffer. How do I edit another + buffer without saving the modified buffer and also without losing + the modifications? + 8.2. How do I configure Vim to auto-save a modified buffer when + switching to another buffer? + 8.3. How do I replace the buffer in the current window with a blank + buffer? + 8.4. Is there a keyboard shortcut to load a buffer by the buffer + number? + 8.5. How do I open all the current buffers in separate windows? + 8.6. How do I close (delete) a buffer without exiting Vim? + 8.7. I have several buffers opened with ":e filename". How do I close + one of the buffers without exiting Vim? + 8.8. When I use the command ":%bd" to delete all the buffers, not all + the buffers are deleted. Why? + 8.9. How do I display the buffer number of the current buffer/file? + 8.10. How do I delete a buffer without closing the window in which the + buffer is displayed? + 8.11. How do I map the tab key to cycle through and open all the + buffers? + +SECTION 9 - WINDOWS + 9.1. What is the difference between a Vim window and a buffer? + 9.2. How do I increase the width of a Vim window? + 9.3. How do I zoom into or out of a window? + 9.4. How do I execute an ex command on all the open buffers or open + windows or all the files in the argument list? + +SECTION 10 - MOTION + 10.1. How do I jump to the beginning (first line) or end (last line) of + a file? + 10.2. In insert mode, when I press the <Esc> key to go to command mode, + the cursor moves one character to the left (except when the cursor + is on the first character of the line). Is it possible to change + this behavior to keep the cursor at the same column? + 10.3. How do I configure Vim to maintain the horizontal cursor position + when scrolling with the <Page Up>, <Page Down>, etc keys? + 10.4. Some lines in a file are more than the screen width and they are + all wrapped. When I use the j, k keys to move from one line to the + next, the cursor is moved to the next line in the file instead of + the next line on the screen. How do I move from one screen line to + the next? + 10.5. What is the definition of a sentence, paragraph and section in + Vim? + 10.6. How do I jump to beginning or end of a sentence, paragraph or a + section? + 10.7. I have lines in a file that extends beyond the right extent of the + screen. How do I move the Vim view to the right to see the text + off the screen? + 10.8. How do I scroll two or more buffers simultaneously? + 10.9. When I use my arrow keys, Vim changes modes, inserts weird + characters in my document but doesn't move the cursor properly. + What's going on? + 10.10. How do I configure Vim to move the cursor to the end of the + previous line, when the left arrow key is pressed and the cursor + is currently at the beginning of a line? + 10.11. How do I configure Vim to stay only in insert mode (modeless + editing)? + 10.12. How do I display some context lines when scrolling text? + 10.13. How do I go back to previous cursor locations? + +SECTION 11 - SEARCHING TEXT + 11.1. After I searched for a text with a pattern, all the matched text + stays highlighted. How do I turn off the highlighting + temporarily/permanently? + 11.2. How do I enter a carriage return character in a search pattern? + 11.3. How do I search for the character ^M? + 11.4. How can I search/replace characters that display as '~R', '~S', + etc.? + 11.5. How do I highlight all the non-printable characters in a file? + 11.6. How do I search for whole words in a file? + 11.7. How do I search for the current word under the cursor? + 11.8. How do I search for a word without regard to the case (uppercase + or lowercase)? + 11.9. How do I search for words that occur twice consecutively? + 11.10. How do I count the number of times a particular word occurs in a + buffer? + 11.11. How do I place the cursor at the end of the matched word when + searching for a pattern? + 11.12. How do I search for an empty line? + 11.13. How do I search for a line containing only a single character? + 11.14. How do I search and replace a string in multiple files? + 11.15. I am using the ":s" substitute command in a mapping. When a + search for a pattern fails, the map terminates. I would like the + map to continue processing the next command, even if the + substitute command fails. How do I do this? + 11.16. How do I search for the n-th occurrence of a character in a + line? + 11.17. How do I replace a tab (or any other character) with a hard + return (newline) character? + 11.18. How do I search for a character by its ASCII value? + 11.19. How do I search for long lines? + 11.20. How do I display all the lines in the current buffer that + contain a specified pattern? + 11.21. How do I search for a text string that spans multiple lines? + 11.22. How do I search for a pattern only within a range of lines + in a buffer? + +SECTION 12 - CHANGING TEXT + 12.1. How do I delete all the trailing white space characters (SPACE + and TAB) at the end of all the lines in a file? + 12.2. How do I replace all the occurrences of multiple consecutive + space characters to a single space? + 12.3. How do I reduce a range of empty lines into one line only? + 12.4. How do I delete all blank lines in a file? How do I remove all + the lines containing only space characters? + 12.5. How do I copy/yank the current word? + 12.6. How do I yank text from one position to another position within a + line, without yanking the entire line? + 12.7. When I yank some text into a register, how do I append the text + to the current contents of the register? + 12.8. How do I yank a complete sentence that spans over more than one + line? + 12.9. How do I yank all the lines containing a pattern into a buffer? + 12.10. How do I delete all the lines in a file that does not contain a + pattern? + 12.11. How do I add a line before each line with "pattern" in it? + 12.12. Is there a way to operate on a line if the previous line + contains a particular pattern? + 12.13. How do I execute a command on all the lines containing a + pattern? + 12.14. Can I copy the character above the cursor to the current cursor + position? + 12.15. How do I insert a blank line above/below the current line + without entering insert mode? + 12.16. How do I insert the name of current file into the current + buffer? + 12.17. How do I insert the contents of a Vim register into the current + buffer? + 12.18. How do I move the cursor past the end of line and insert some + characters at some columns after the end of the line? + 12.19. How to replace the word under the cursor (say: junk) with + "foojunkbar" in Vim? + 12.20. How do I replace a particular text in all the files in a + directory? + 12.21. I have some numbers in a file. How do I increment or decrement + the numbers in the file? + 12.22. How do I reuse the last used search pattern in a ":substitute" + command? + 12.23. How do I change the case of a string using the ":substitute" + command? + 12.24. How do I enter characters that are not present in the keyboard? + 12.25. Is there a command to remove any or all digraphs? + 12.26. In insert mode, when I press the backspace key, it erases only + the characters entered in this instance of insert mode. How do I + erase previously entered characters in insert mode using the + backspace key? + 12.27. I have a file which has lines longer than 72 characters + terminated with "+" and wrapped to the next line. How can I + quickly join the lines? + 12.28. How do I paste characterwise yanked text into separate lines? + 12.29. How do I change the case (uppercase, lowercase) of a word or + a character or a block of text? + 12.30. How do I enter ASCII characters that are not present in the + keyboard? + 12.31. How do I replace non-printable characters in a file? + 12.32. How do I remove duplicate lines from a buffer? + 12.33. How do I prefix all the lines in a file with the corresponding + line numbers? + 12.34. How do I exchange (swap) two characters or words or lines? + 12.35. How do I change the characters used as word delimiters? + +SECTION 13 - COMPLETION IN INSERT MODE + 13.1. How do I complete words or lines in insert mode? + 13.2. How do I complete file names in insert mode? + 13.3. I am using CTRL-P/CTRL-N to complete words in insert mode. How do + I complete words that occur after the just completed word? + +SECTION 14 - TEXT FORMATTING + 14.1. How do I format a text paragraph so that a new line is inserted + at the end of each wrapped line? + 14.2. How do I format long lines in a file so that each line contains + less than 'n' characters? + 14.3. How do I join short lines to the form a paragraph? + 14.4. How do I format bulleted and numbered lists? + 14.5. How do I indent lines in insert mode? + 14.6. How do I format/indent an entire file? + 14.7. How do I increase or decrease the indentation of the current + line? + 14.8. How do I indent a block/group of lines? + 14.9. When I indent lines using the > or < key, the standard 8-tabstops + are used instead of the current 'tabstop' setting. Why? + 14.10. How do I turn off the automatic indentation of text? + 14.11. How do I configure Vim to automatically set the 'textwidth' + option to a particular value when I edit mails? + 14.12. Is there a way to make Vim auto-magically break lines? + 14.13. I am seeing a lot of ^M symbols in my file. I tried setting the + 'fileformat' option to 'dos' and then 'unix' and then 'mac'. + None of these helped. How can I hide these symbols? + 14.14. When I paste some text into a Vim buffer from another + application, the alignment (indentation) of the new text is + messed up. How do I fix this? + 14.15. When there is a very long wrapped line (wrap is "on") and a line + doesn't fit entirely on the screen it is not displayed at all. + There are blank lines beginning with '@' symbol instead of + wrapped line. If I scroll the screen to fit the line the '@' + symbols disappear and the line is displayed again. What Vim + setting control this behavior? + 14.16. How do I convert all the tab characters in a file to space + characters? + 14.17. What Vim options can I use to edit text that will later go to a + word processor? + 14.18. How do I join lines without adding or removing any space + characters? + +SECTION 15 - VISUAL MODE + 15.1. How do I do rectangular block copying? + 15.2. How do I delete or change a column of text in a file? + 15.3. How do I apply an ex-command on a set of visually selected lines? + 15.4. How do I execute an ex command on a column of text selected in + Visual block mode? + 15.5. How do I select the entire file in visual mode? + 15.6. When I visually select a set of lines and press the > key to + indent the selected lines, the visual mode ends. How can I + reselect the region for further operation? (or) How do I + re-select the last selected visual area again? + 15.7. How do I jump to the beginning/end of a visually selected region? + 15.8. When I select text with mouse and then press : to enter an ex + command, the selected text is replaced with the : character. How + do I execute an ex command on a text selected using the mouse + similar to the text selected using the visual mode? + 15.9. When I select a block of text using the mouse, Vim goes into + selection mode instead of Visual mode. Why? + +SECTION 16 - COMMAND-LINE MODE + 16.1. How do I use the name of the current file in the command mode or + an ex command line? + 16.2. How do I edit the text in the Vim command-line effectively? + 16.3. How do I switch from Vi mode to Ex mode? + 16.4. How do I copy the output from an ex-command into a buffer? + 16.5. When I press the tab key to complete the name of a file in the + command mode, if there are more than one matching file names, + then Vim completes the first matching file name and displays a + list of all matching filenames. How do I configure Vim to only + display the list of all the matching filenames and not complete + the first one? + 16.6. How do I copy text from a buffer to the command line and from the + command line to a buffer? + 16.7. How do I put a command onto the command history without executing + it? + 16.8. How do I increase the height of the command-line? + +SECTION 17 - VIMINFO + 17.1. When I invoke Vim, I get error messages about illegal characters + in the viminfo file. What should I do to get rid of these + messages? + 17.2. How do I disable the viminfo feature? + 17.3. How do I save and use Vim marks across Vim sessions? + +SECTION 18 - REMOTE EDITING + 18.1. How do I open a file with existing instance of gvim? What + happened to the Vim 5.x OpenWithVim.exe and SendToVim.exe files? + 18.2. How do I send a command to a Vim server to write all buffers to + disk? + 18.3. Where can I get the documentation about the Vim remote server + functionality? + +SECTION 19 - OPTIONS + 19.1. How do I configure Vim in a simple way? + 19.2. How do I toggle the value of an option? + 19.3. How do I set an option that affects only the current + buffer/window? + 19.4. How do I use space characters for a Vim option value? + 19.5. Can I add (embed) Vim option settings to the contents of a file? + 19.6. How do I display the line numbers of all the lines in a file? + 19.7. How do I change the width of the line numbers displayed using the + "number" option? + 19.8. How do I display (view) all the invisible characters like space, + tabs and newlines in a file? + 19.9. How do I configure Vim to always display the current line and + column number? + 19.10. How do I display the current Vim mode? + 19.11. How do I configure Vim to show pending/partial commands on the + status line? + 19.12. How do I configure the Vim status line to display different + settings/values? + 19.13. How do I configure Vim to display status line always? + 19.14. How do I make a Vim setting persistent across different Vim + invocations/instances/sessions? + 19.15. Why do I hear a beep (why does my window flash) about 1 second + after I hit the Escape key? + 19.16. How do I make the 'c' and 's' commands display a '$' instead of + deleting the characters I'm changing? + 19.17. How do I remove more than one flag using a single ":set" command + from a Vim option? + +SECTION 20 - MAPPING KEYS + 20.1. How do I know what a key is mapped to? + 20.2. How do list all the user-defined key mappings? + 20.3. How do I unmap a key? + 20.4. I am not able to create a mapping for the <xxx> key. What is + wrong? + 20.5. How do I map the numeric keypad keys? + 20.6. How do I create a mapping that works only in visual mode? + 20.7. In a Vim script, how do I know which keys to use for my mappings, + so that the mapped key will not collide with an already used key? + 20.8. How do I map the escape key? + 20.9. How do I map a key to perform nothing? + 20.10. I want to use the Tab key to indent a block of text and + Shift-Tab key to unindent a block of text. How do I map the keys + to do this? This behavior is similar to textpad, visual studio, + etc. + 20.11. In my mappings the special characters like <CR> are not + recognized. How can I configure Vim to recognize special + characters? + 20.12. How do I use the '|' to separate multiple commands in a map? + 20.13. If I have a mapping/abbreviation whose ending is the beginning of + another mapping/abbreviation, how do I keep the first from + expanding into the second one? + 20.14. Why does it take a second or more for Vim to process a key, + sometimes when I press a key? + 20.15. How do I map a key to run an external command using a visually + selected text? + 20.16. How do I map the Ctrl-I key while still retaining the + functionality of the <Tab> key? + +SECTION 21 - ABBREVIATIONS + 21.1. How do I auto correct misspelled words? + 21.2. How do I create multi-line abbreviations? + 21.3. When my abbreviations are expanded, an additional space character + is added at the end of the expanded text. How do I avoid this + character? + 21.4. How do I insert the current date/time stamp into the file? + 21.5. How do I prevent an abbreviation from expanding in insert mode? + +SECTION 22 - RECORD AND PLAYBACK + 22.1. How do I repeat an editing operation (insertion, deletion, paste, + etc)? + 22.2. How I record and repeat a set of key sequences? + 22.3. How do I edit/modify a recorded set of key sequences? + 22.4. How do I write recorded key sequences to a file? + 22.5. I am using register 0 to record my key sequences (i.e. q0 .... + q). In the recorded key sequences, I am yanking some text. After + the first replay of the recorded key sequence, I am no longer + able to play it back. + +SECTION 23 - AUTOCOMMANDS + 23.1. How do I execute a command when I try to modify a read-only file? + 23.2. How do I execute a command every time when entering a buffer? + 23.3. How do I execute a command every time when entering a window? + 23.4. From an autocmd, how can I determine the name of the file or the + buffer number for which the autocommand is executed? + 23.5. How do I automatically save all the changed buffers whenever Vim + loses focus? + 23.6. How do I execute/run a function when Vim exits to do some + cleanup? + +SECTION 24 - SYNTAX HIGHLIGHT + 24.1. How do I turn off/on syntax highlighting? + 24.2. How do I change the background and foreground colors used by Vim? + 24.3. How do I change the highlight colors to suit a dark/light + background? + 24.4. How do I change the color of the line numbers displayed when the + ":set number" command is used? + 24.5. How do I change the background color used for a Visually selected + block? + 24.6. How do I highlight the special characters (tabs, trailing spaces, + end of line, etc) displayed by the 'list' option? + 24.7. How do I specify a colorscheme in my .vimrc/.gvimrc file, so that + Vim uses the specified colorscheme everytime? + 24.8. Vim syntax highlighting is broken. When I am editing a file, some + parts of the file is not syntax highlighted or syntax highlighted + incorrectly. + 24.9. Is there a built-in function to syntax-highlight the + corresponding matching bracket? + 24.10. How do I turn off the C comment syntax highlighting? + 24.11. How do I add my own syntax extensions to the standard syntax + files supplied with Vim? + 24.12. How do I replace a standard syntax file that comes with the Vim + distribution with my own syntax file? + 24.13. How do I highlight all the characters after a particular column? + 24.14. How do I convert a source file (.c, .h, etc) with the Vim syntax + highlighting into a HTML file? + 24.15. How do I list the definition of all the current highlight + groups? + +SECTION 25 - VIM SCRIPT WRITING + 25.1. How do I list the names of all the scripts sourced by Vim? + 25.2. How do I debug Vim scripts? + 25.3. How do I locate the script/plugin which sets a Vim option? + 25.4. I am getting some error/informational messages from Vim (possibly + when running a script), the messages are cleared immediately. How + do I display the messages again? + 25.5. How do I save and restore a plugin specific information across + Vim invocations? + 25.6. How do I start insert mode from a Vim function? + 25.7. How do I change the cursor position from within a Vim function? + 25.8. How do I check the value of an environment variable in the .vimrc + file? + 25.9. How do I check whether an environment variable is set or not from + a Vim function? + 25.10. How do I call/use the Vim built-in functions? + 25.11. I am using some normal mode commands in my Vim script. How do I + avoid using the user-defined mappings for these normal mode + commands and use the standard Vim functionality for these normal + mode commands? + 25.12. How do I get a visually selected text into a Vim variable or + register? + 25.13. I have some text in a Vim variable 'myvar'. I would like to use + this variable in a ":s" substitute command to replace a text + 'mytext'. How do I do this? + 25.14. A Vim variable (bno) contains a buffer number. How do I use this + variable to open the corresponding buffer? + 25.15. How do I store the value of a Vim option into a Vim variable? + 25.16. I have copied and inserted some text into a buffer from a Vim + function. How do I indent the inserted text from the Vim + function? + 25.17. How do I get the character under the cursor from a Vim script? + 25.18. How do I get the name of the current file without the extension? + 25.19. How do I get the basename of the current file? + 25.20. How do I get the output from a Vim function into the current + buffer? + 25.21. How do I call external programs from a Vim function? + 25.22. How do I get the return status of a program executed using the + ":!" command? + 25.23. How do I determine whether the current buffer is modified or + not? + 25.24. I would like to use the carriage return character in a normal + command from a Vim script. How do I specify the carriage return + character? + 25.25. How do I split long lines in a Vim script? + 25.26. When I try to "execute" my function using the "execute 'echo + Myfunc()'" command, the cursor is moved to the top of the + current buffer. Why? + 25.27. How do I source/execute the contents of a register? + 25.28. After calling a Vim function or a mapping, when I press the 'u' + key to undo the last change, Vim undoes all the changes made by + the mapping/function. Why? + 25.29. How can I call a function defined with s: (script local + function) from another script/plugin? + 25.30. Is it possible to un-source a sourced script? In otherwords, + reverse all the commands executed by sourcing a script. + +SECTION 26 - PLUGINS + 26.1. How do I set different options for different types of files? + 26.2. I have downloaded a Vim plugin or a syntax file or a indent file, + or a color scheme or a filetype plugin from the web. Where should + I copy these files so that Vim will find them? + 26.3. How do I extend an existing filetype plugin? + 26.4. How do I turn off loading the Vim plugins? + 26.5. How do I turn on/off loading the filetype plugins? + 26.6. How do I override settings made in a file type plugin in the + global ftplugin directory for all the file types? + 26.7. How do I disable the Vim directory browser plugin? + 26.8. How do I set the filetype option for files with names matching a + particular pattern or depending on the file extension? + +SECTION 27 - EDITING PROGRAM FILES + 27.1. How do I enable automatic indentation for C/C++ files? + 27.2. How do I configure the indentation used for C/C++ files? + 27.3. How do I turn off the automatic indentation feature? + 27.4. How do I change the number of space characters used for the + automatic indentation? + 27.5. I am editing a C program using Vim. How do I display the + definition of a macro or a variable? + 27.6. I am editing a C program using Vim. How do I jump to the + beginning or end of a code block from within the block? + 27.7. Is there a way to turn off the "//" comment auto-insertion + behavior for C++ files? If I'm sitting on a line beginning with + "//", then I open a new line above or below it, Vim automatically + inserts new "//" chars. + 27.8. How do I add the comment character '#' to a set of lines at the + beginning of each line? + 27.9. How do I edit a header file with the same name as the + corresponding C source file? + 27.10. How do I automatically insert comment leaders while typing + comments? + +SECTION 28 - QUICKFIX + 28.1. How do I build programs from Vim? + 28.2. When I run the make command in Vim I get the errors listed as the + compiler compiles the program. When it finishes this list + disappears and I have to use the :clist command to see the error + message again. Is there any other way to see these error + messages? + +SECTION 29 - FOLDING + 29.1. How do I extend the Vim folding support? + 29.2. When I enable folding by setting the 'foldmethod' option, all the + folds are closed. How do I prevent this? + 29.3. How do I control how many folds will be opened when I start + editing a file? + 29.4. How do I open and close folds using the mouse? + 29.5. How do I change the text displayed for a closed fold? + 29.6. How do I store and restore manually created folds across + different Vim invocations? + +SECTION 30 - VIM WITH EXTERNAL APPLICATIONS + 30.1. Can I run a shell inside a Vim window? + 30.2. How do I pass the word under the cursor to an external command? + 30.3. How do I get the output of a shell command into a Vim buffer? + 30.4. How do I pipe the contents of the current buffer to an external + command and replace the contents of the buffer with the output + from the command? + 30.5. How do I sort a section of my file? + 30.6. Is there a step-by-step guide for using Vim with slrn? + 30.7. How do I use Vim as a pager? + 30.8. How do I view Unix man pages from inside Vim? + 30.9. How do I change the diff command used by the Vim diff support? + 30.10. How do I use the Vim diff mode without folding? + +SECTION 31 - GUI VIM + 31.1. How do I create buffer specific menus? + 31.2. How do I change the font used by GUI Vim? + 31.3. When starting GUI Vim, how do I specify the location of the GVIM + window? + 31.4. How do I add a horizontal scrollbar in GVim? + 31.5. How do I make the scrollbar appear in the left side by default? + 31.6. How do I remove the Vim menubar? + 31.7. I am using GUI Vim. When I press the ALT key and a letter, the + menu starting with that letter is selected. I don't want this + behavior as I want to map the ALT-<key> combination. How do I do + this? + 31.8. Is it possible to scroll the text by dragging the scrollbar so + that the cursor stays in the original location? + 31.9. How do I get gvim to start browsing files in a particular + directory when using the ":browse" command? + 31.10. For some questions, like when a file is changed outside of Vim, + Vim displays a GUI dialog box. How do I replace this GUI dialog + box with a console dialog box? + 31.11. I am trying to use GUI Vim as the editor for my xxx application. + When the xxx application launches GUI Vim to edit a file, the + control immediately returns to the xxx application. How do I + start GUI Vim, so that the control returns to the xxx + application only after I quit Vim? + 31.12. Why does the "Select Font" dialog doesn't show all the fonts + installed in my system? + 31.13. How do I use the mouse in Vim command-line mode? + 31.14. When I use the middle mouse button to scroll text, it pastes the + last copied text. How do I disable this behavior? + 31.15. How do I change the location and size of a GUI Vim window? + +SECTION 32 - VIM ON UNIX + 32.1. I am running Vim in a xterm. When I press the CTRL-S key, Vim + freezes. What should I do now? + 32.2. I am seeing weird screen update problems in Vim. What can I do to + solve this screen/display update problems? + 32.3. I am using the terminal/console version of Vim. In insertmode, + When I press the backspace key, the character before the cursor + is not erased. How do I configure Vim to do this? + 32.4. I am using Vim in a xterm. When I quit Vim, the screen contents + are restored back to the original contents. How do I disable + this? + 32.5. When I start Vim, it takes quite a few seconds to start. How do I + minimize the startup time? + 32.6. How can I make the cursor in gvim in unix stop blinking? + 32.7. How do I change the menu font on GTK Vim? + 32.8. How do I prevent <Ctrl-Z> from suspending Vim? + 32.9. When I kill the xterm running Vim, the Vim process continues to + run and takes up a lot of CPU (99%) time. Why is this happening? + 32.10. How do I get the Vim syntax highlighting to work in a Unix + terminal? + +SECTION 33 - VIM ON MS-WINDOWS + 33.1. In MS-Windows, CTRL-V doesn't start the blockwise visual mode. + What happened? + 33.2. When I press the CTRL-Y key, it acts like the CTRL-R key. How do + I configure Vim to treat CTRL-Y as CTRL-Y? + 33.3. How do I start GUI Vim in a maximized window always? + 33.4. After doing some editing operations, Vim freezes. The cursor + becomes an empty rectangle. I am not able enter any characters. + What is happening? + 33.5. I am using Windows XP, the display speed of maximized GVim is + very slow. What can I do to speed the display updates? + 33.6. What are the recommended settings for using Vim with cygwin? + 33.7. I am trying to use GNU diff with Vim diff mode. When I run the + diff from command line, it works. When I try to use the diff with + Vim it doesn't work. What should I do now? + 33.8. Is it possible to use Vim as an external editor for MS-Windows + Outlook email client? + 33.9. I am using Vim to edit HTML files. How do I start internet + explorer with the current file to preview the HTML file? + 33.10. I would like to use Vim with Microsoft Visual Studio. How do I + do this? + 33.11. Where do I place the _vimrc and _gvimrc files? + 33.12. Everytime I save a file, Vim warns about the file being changed + outside of Vim. Why? + +SECTION 34 - PRINTING + 34.1. How do I print a file along with line numbers for all the lines? + 34.2. How do I print a file with the Vim syntax highlighting colors? + +SECTION 35 - BUILDING VIM FROM SOURCE + 35.1. How do I build Vim from the sources on a Unix system? + 35.2. How do I install Vim in my home directory or a directory other + than the default installation directory in Unix? + 35.3. How do I build Vim from the sources on a MS-Windows system? + 35.4. The Vim help, syntax, indent files are missing from my Vim + installation. How do I install these files? + 35.5. I have built Vim from the source and installed the Vim package + using "make install". Do I need to keep the Vim source directory? + 35.6. How do I determine the Vim features which are enabled at compile + time? + 35.7. Can I build Vim without the GUI support? + 35.8. When building Vim on a Unix system, I am getting "undefined + reference to term_set_winsize' error. How do I resolve this + error? + 35.9. Vim configure keeps complaining about the lack of gtk-config + while trying to use GTK 2.03. This is correct, since in GTK 2 + they moved to using the generic pkg-config. I can get pkg-config + to list the various includes and libs for gtk, but for some + reason the configure script still isn't picking this up. + +SECTION 36 - VARIOUS + 36.1. How do I edit binary files with Vim? + 36.2. How do I disable the visual error flash and the error beep? + 36.3. How do I display the ascii value of a character displayed in a + buffer? + 36.4. Can I use zero as a count for a Vim command? + 36.5. How do I disable the Vim welcome screen? + 36.6. How do I avoid the "hit enter to continue" prompt? + 36.7. How do I invoke Vim from command line to run a group of commands + on a group of files? + 36.8. How do I use a normal mode command from insert mode without + leaving the insert mode? + 36.9. How do I start Vim in insert mode? + +SECTION 37 - UNICODE + 37.1. Is it possible to create Unicode files using Vim? + 37.2. Which Vim settings are particularly important for editing Unicode + files? + 37.3. What is the 'encoding' option? + 37.4. How does Vim name the various Unicode encodings? + 37.5. How does Vim specify the presence or absence of a byte-order + mark? + 37.6. What is the 'fileencoding' option? + 37.7. What is the 'fileencodings' option? + 37.8. What is the 'termencoding' option? + 37.9. What is the 'bomb' option? + 37.10. Where can I find an example of a typical use of all these + options? + 37.11. How can I insert Unicode characters into a file using Vim? + 37.12. How can I know which digraphs are defined and for which + characters? + + +============================================================================= + +SECTION 1 - GENERAL INFORMATION + + +1.1. What is Vim? + +Vim stands for Vi IMproved. It used to be Vi IMitation, but there are so +many improvements that a name change was appropriate. Vim is a text editor +which includes almost all the commands from the Unix program "Vi" and a lot +of new ones. All commands can be given with the keyboard. This has the +advantage that you can keep your fingers on the keyboard and your eyes on +the screen. For those who want it, there is mouse support and a GUI version +with scrollbars and menus. + +Vim is an editor, not a word processor. A word processor is used mainly to +do layout of text. This means positioning it, changing the way it appears +on output. More often than not, the final document is meant to be printed +or typeset or what have you, in order to present it in a pleasing manner to +others. Examples of word processors are Microsoft Word, WordPerfect, +FrameMaker, and AmiPro. + +An editor is simply for entering text. Any typesetting or laying out of the +document is secondary. With an editor, one's main concern is entering text, +not making the text look good. Examples of editors other than Vim and Vi +are Emacs, Crisp, Brief, and xedit. And Notepad. + +For more information, read + + :help intro + + +1.2. Who wrote Vim? + +Most of Vim was written by Bram Moolenar, with contributions from too many +people to mention here. See ":h credits" for a complete list. + +Vim is based on Stevie, worked on by Tim Thompson, Tony Andrews and G.R. +(Fred) Walter. + +For more information, read + + :help author + + +1.3. Is Vim compatible with Vi? + +Yes. Vim is very much compatible with Vi. You can use the "-C" +command-line flag to start Vim in Vi compatible mode: + + $ vim -C + +You can also use: + + $ vim -u NONE + +You can also set the 'compatible' option to enable Vi compatibility: + + :set compatible + +For more information, read + + :help -C + :help 'compatible' + :help compatible-default + + +1.4. What are some of the improvements of Vim over Vi? + +A short summary of the improvements of Vim over vi is listed below. The +list shows that Vim is a thoroughly modern and feature-packed editor. +Standard features of modern editors are implemented, and there is an equal +emphasis on general power-user features and features for programmers. + +Features to modernise Vi: + + Multi-level undo + Allows you to set the number of times you can undo your changes in a + file buffer. You can also redo an undone change. + Multiple windows and buffers + Each file can be displayed in its own window. You can move easily from + one window to another. Each file opened during a Vim session also has + an associated buffer and you can easily jump from one to the other. + Flexible insert mode + Vim allows you to use the arrow keys while in insert mode to move + around in the file. No more hitting <Esc>, moving around, then hitting + `i' or `a'. + Macros + Vim has a facility which allows you to record a sequence of typed + characters and repeat them any number of times. + Visual mode + You can highlight sections of text and execute operations on this + section of text only. + Block operators + Allow selection and highlighting of rectangular blocks of text in + order do execute specific operations on them. + Online help system + You can easily find help on any aspect of using Vim. Help is displayed + in its own window. + Command-line editing and history + History allows you to use the arrow keys to repeat or search for a + command that has already been typed. Allows you to match the beginning + of a command with the beginning of another similar command in the + history buffer. You can also edit a command to correct typos or change + a few values. + Command line completion. + Using the <Tab> key, you can complete commands, options, filenames, + etc. as needed. + Horizontal scrolling. + Long lines can be scrolled horizontally (with or without the GUI). + +Advanced user features: + + Text formatting. + With two keystrokes, you can format large sections of text, without + the use of external programs. + Word completion in Insert mode + Vim can complete words while you are typing, by matching the current + word with other similar words in the file. + Jump tags + Just like in an internet browser, you can jump back to previous parts + of the text you were editing, and then forward again. Your brain is + thus free to edit instead of navigate. + Automatic commands + Commands automatically executed when reading or writing a file, + jumping to another buffer, etc. + Viminfo + Allows storing of the command line history, marks and registers in a + file to be read on startup. Therefore, you can recall old search + patterns, macros, etc., in a new Vim session. + Mouse support + The mouse is supported in an xterm and for MS-DOS. It can be used to + position the cursor, select the visual area, paste a register, etc. + Graphical User Interface (GUI) + Just like any modern editor. Also, it's very easy to add your own + menus. Of course, console vim is still supported, and very widely + used. + Scripting language + Vim has a powerful scripting language so new commands can be created. + You can also use Perl, Python, TCL and Ruby to achieve the same thing! + Plugins + Extra functionality implemented via vim commands (regular commands or + the scripting language) that is automatically loaded on startup. + Examples: file explorer, network editing. More are being developed + and shared on VimOnline all the time. + Syntax highlighting for many programming languages + Syntax highlighting for hundreds of programming languages is + supported. Support for others can be added. + Extended regular expressions + Vim supports extended regular expressions which are similar in + functionality to that of perl regular expressions. + +Programming performance features: + + Edit-compile-edit speedup + You can compile within Vim and automatically jump to the location of + errors in the source code. + Indenting for many programming languages + C, C++, Java, Perl, XML and many other languages can be automatically + indented by vim while you type. Support for others can be added. + Searching for words in include files + Vim allows you to search for a match of the word under the cursor in + the current and included files. + Advance text objects + Instantly select, or delete, or copy, or indent, or format, or change + case, or ... to all the text between ( and ), or { and }, or < and >, + or [ and ]. Or a word, sentence, or paragraph. Very powerful. + Folding + Certain parts of the text can be "folded" away. The best example is + the body of a function. You can get an overview of the code, and then + open the fold of the function whose detail you need to see. + ctags and cscope integration + Using these two powerful programs, you can jump to a definition of a + function from a calling instance of it, and use other tricks to + navigate source code. + +For more information, read + + :help vi-differences + + +1.5. Is Vim free? + +Vim is Charityware. There are no restrictions on using or copying Vim, but +the author encourages you to make a donation to charity. A document +explaining how to do so is included in the distribution. + +For more information, read + + :help copyright + + +============================================================================= + +SECTION 2 - RESOURCES + + +2.1. Where can I learn more about Vim? + +You can post your Vim questions to the vim@vim.org mailing list. You can +post your Vim development related questions to the vim-dev@vim.org mailing +list. Vim does not have a newsgroup of its own. But the appropriate +newsgroup to post to is comp.editors. + +"VimOnline" is a web page that serves as a de facto homepage for vim, +although the main purpose of it is to gather tips and scripts from +everywhere. Get involved! The URL is vim.sourceforge.net or vim.sf.net. + +Finally, read the Vi FAQ: + + http://www.faqs.org/faqs/editor-faq/vi/part1/index.html + +For more information, read + + :help mail-list + :help internet + + +2.2. Is there a mailing list available? + +There are several: + + NAME DESCRIPTION + + vim-announce Announcements of new releases + vim General discussion + vim-dev Patches, bug reports, development discussions + vim-mac Macintosh discussion + vim-fr General discussion in French + vim-multibyte Multibyte development issues + vim-vms Development on VMS + +Of these, only vim and vim-dev are of general interest. vim-announce is +read-only to most people, and its messages are sent to the other lists as +well. The remaining four are very low volume. + +To subscribe: send an email to <NAME>-subscribe@vim.org +To unsubscribe: send an email to <NAME>-unsubscribe@vim.org +To get help: send an email to <NAME>-help@vim.org + + +2.3. Is there an archive available for the Vim mailing lists? + +Yes. Visit http://www.yahoogroups.com/list/<name>, where name is one of: +vimannounce, vim, vimdev, vim-fr, vim-mac, vim-multibyte, vim-vms. + +Alternatively, visit www.gmane.org to find out about GMANE, which allows +you to access the mailing lists as though they were newsgroups. This +offers some convenience to those who wish to browse the history or casually +observe the current threads. + + +2.4. Where can I get the Vim user manual in HTML/PDF/PS format? + +You can download the HTML/PDF/PS format of the Vim user manual from: + + http://vimdoc.sourceforge.net/ + + +2.5. I have a "xyz" (some) problem with Vim. How do I determine it is a + problem with my setup or with Vim? + +First, you have to determine that the problem is not with your .vimrc or +.gvimrc or system vimrc or your personal plugin files or in any of your +setup files. To do this, use + + $ vim -N -u NONE -U NONE + +This will start Vim in 'nocompatible" mode and will not source your +personal .vimrc and .gvimrc files. It will also not load your personal +plugins. In this invocation of Vim, try to reproduce your problem. If you +are not able to reproduce the problem, then the problem is related to some +setting in one of your local setup files or plugins. To locate the problem +in your setup files, you have to use trial and error and try commenting out +the lines in your setup files one by one. You can also use the -V command +line argument to Vim to get more debug information and analyze the problem: + + $ vim -V2 + +You can increase the value passed to the -V argument to get more debug +information. + +For more information, read + + :help -u + :help -U + :help -N + :help -V + :help 'verbose' + :help :verbose + :help set-verbose + + +2.6. Where can I report bugs? + +First collect the required information using the following command: + + :source $VIMRUNTIME/bugreport.vim + +Now send the resulting text from the above command to the bugs@vim.org +e-mail address. + +The Vim Development mailing list (see above) is a good place to discuss +general bugs. If the bug you find is with syntax highlighting or some +other "added feature" (i.e. not directly programmed into vim), attempt to +inform the maintainer of that feature. + +For more information, read + + :help bug-reports + + +2.7. Where can the FAQ be found? + +The FAQ can be found at VimOnline (vim.sf.net). Other places will be +decided in the future. + + +2.8. What if I don't find an answer in this FAQ? + +This FAQ covers mainly Vim-specific questions. You may find more +information suitable for most Vi clones by reading the Vi FAQ. It is posted +regularly on comp.editors. You can also find a copy at + + http://www.faqs.org/faqs/editor-faq/vi/part1/index.html + +Also, since Vim has gathered so many features in the last few years, +successfully documenting the frequently asked questions here is a +near-impossible task. To make it possible, please email the maintainer if +you have a good question. A good question is one that you've tried to +answer yourself (remember, Vim has great documentation) but struggled. + + +2.9. I have a patch for implementing a Vim feature. Where can I send this + patch? + +You can send your patches to the Vim developer mailing list +vim-dev@vim.org. + +For more information, read + + :help vim-dev + + +2.10. I have a Vim tip or developed a new Vim + syntax/indent/filetype/compiler plugin or developed a new script or a + colorscheme. Is there a public website where I can upload this? + +Yes. You can use the Vim Online website to upload your plugins/scripts, +colorschemes, tips, etc. The site is at http://vim.sourceforge.net + + +============================================================================= + +SECTION 3 - AVAILABILITY + + +3.1. What is the latest version of Vim? + +The latest version of Vim is 6.3 released on 8th June 2004. + +The release-history of different versions of Vim is below: + +Version 6.3 8th June 2004 +Version 6.2 1st June 2003 +Version 6.1 24th March 2002 +Version 6.0 27th September, 2001 +Version 5.8 31st May, 2001 +Version 5.7 24th June, 2000 +Version 5.6 16th January, 2000 +Version 5.5 21st September, 1999 +Version 5.4 26th July, 1999 +Version 5.3 31st August, 1998 +Version 5.2 24th August, 1998 +Version 5.1 7th April, 1998 +Version 5.0 19th February, 1998 +Version 4.6 13th March,1997 +Version 4.5 17th October, 1996 +Version 4.2 5th July,1996 +Version 4.0 21st May, 1996 +Version 3.0 16th August, 1994 +Version 2.0 21st December, 1993 +Version 1.27 23rd April, 1993 +Version 1.17 21st April, 1992 + + +3.2. Where can I find the latest version of Vim? + +You can download the sources for the latest version of Vim from the +VimOnline website. The URL for this site is +http://vim.sourceforge.net/download.php. + + +3.3. What platforms does it run on? + +All Unix platforms. +All Windows platforms. +Amiga, Atari, BeOS, DOS, Macintosh, MachTen, OS/2, RiscOS, VMS. + + +3.4. Where can I download the latest version of the Vim runtime files? + +You can download the latest version of the Vim runtime files (syntax files, +filetype plugins, compiler files, color schemes, documentation, indentation +files and keymaps) from the Vim ftp site from the +ftp://ftp.vim.org/pub/vim/runtime directory. + + +============================================================================= + +SECTION 4 - HELP + + +4.1. How do I use the help files? + +Help can be found for all functions of Vim. In order to use it, use the +":help" command. This will bring you to the main help page. On that first +page, you will find explanations on how to move around. Basically, you move +around in the help pages the same way you would in a read-only document. +You can jump to specific subjects by using tags. This can be done in two +ways: + + * Use the "<Ctrl-]>" command while standing on the name of a command or + option. This only works when the tag is a keyword. "<Ctrl-LeftMouse>" + and "g<LeftMouse>" work just like "<Ctrl-]>". + * use the ":tag <subject>" command. This works with all characters. + +Use "<Ctrl-T>" to jump back to previous positions in the help files. Use +":q" to close the help window. + +If you want to jump to a specific subject on the help pages, use ":help +{subject}". If you don't know what to look for, try ":help index" to get a +list of all available subjects. Use the standard search keys to locate the +information you want. You can abbreviate the ":help" command as ":h". + +For more information, read + + :help online-help + + +4.2. How do I search for a keyword in the Vim help files? + +You can press the CTRL-D key after typing the help keyword to get a list of +all the help keywords containing the supplied pattern. You can also use the +meta characters like *, \+, etc to specify the help search pattern: + + :help init<C-D> + :help str*()<C-D> + :help '*indent<C-D> + +You can press the Tab key after typing a partial help keyword to expand to +the matching keyword. You can continue to press the Tab key to see other +keyword matches. + +From the help window, you can use the ":tag" command to search for +keywords. For example, + + :tselect /window + +This command will list all the help keywords containing the text "window". +You can select one from the list and jump to it. + +You can use the ":helpgrep" command to search for the given text in all the +help files. The quickfix window will be opened with all the matching lines. + +For more information, read + + :help c_CTRL-D + :help c_<Tab> + :help :tselect + :help :help + :help :helpgrep + + +4.3. I am getting an error message E123, what did I do wrong? + +You can get more information about the error and the error message using: + + :help E123 + +For more information, read + + :help error-messages + + +4.4. Where can I read about the various modes in Vim? + +You can get information about the different modes in Vim by reading + + :help vim-modes + + +4.5. How do I generate the Vim help tags file after adding a new Vim help + file? + +You can use the ":helptags" command to regenerate the Vim help tag file. +For example: + + :cd $VIMRUNTIME/doc + :helptags . + +For more information, read + + :help :helptags + :help add-local-help + + +4.6. Can I use compressed versions of the help files? + +Yes. You can compress the help files and still be able to view them with +Vim. This makes accessing the help files a bit slower and requires the +"gzip" utility. Follow these steps to compress and use the Vim help files: + +- Compress all the help files using "gzip doc/*.txt". + +- Edit the "doc/tags" file and change the ".txt" to ".txt.gz" using + :%s=\(\t.*\.txt\)\t=\1.gz\t= + +- Add the following line to your vimrc: + set helpfile={dirname}/help.txt.gz + +Where {dirname} is the directory where the help files are. The gzip.vim +plugin supplied with the standard Vim distribution will take care of +decompressing the files. You must make sure that $VIMRUNTIME is set to +where the other Vim files are, when they are not in the same location as +the compressed "doc" directory. + +For more information, read + + :help gzip-helpfile + :help 'helpfile' + :help gzip + :help $VIMRUNTIME + + +============================================================================= + +SECTION 5 - EDITING A FILE + + +5.1. How do I load a file in Vim for editing? + +There are several ways to load a file for editing. The simplest is to +use the ":e" (:edit) command: + + :e <filename> + +You can also use the ":n" (:next) command to load files into Vim: + + :n <filename(s)> + +You can also use the ":args" command to load files into Vim: + + :args <filename(s)> + +For more information, read + + :help usr_07 + :help edit-files + :help :edit + :help :next_f + :help :args_f + + +5.2. How do I save the current file in another name (save as) and edit a + new file? + +You can use the ":saveas" command to save the current file in another name: + + :saveas <newfilename> + +Alternatively, you can also use the following commands: + + :w <newfilename> + :edit # + +You can also use the ":file" command, followed by ":w" command: + + :file <newfilename> + :w + +For more information, read + + :help 07.7 + :help :saveas + :help :file_f + :help :w + + +5.3. How do I change the current directory to the directory of the current + file? + +You can use the following command to change the current directory to the +directory of the current file: + + :cd %:p:h + +To automatically change the current directory to the directory of the +current file, use the following autocmd: + + :autocmd BufEnter * cd %:p:h + +For more information, read + + :help :cd + :help :lcd + :help filename-modifiers + :help autocommand + + +5.4. How do I write a file without the line feed (EOL) at the end of the + file? + +You can turn off the 'eol' option and turn on the 'binary' option to write +a file without the EOL at the end of the file: + + :set binary + :set noeol + :w + +For more information, read + + :help 'endofline' + :help 'binary' + :help 23.4 + + +5.5. How do I configure Vim to open a file at the last edited location? + +Vim stores the cursor position of the last edited location for each buffer +in the '"' register. You can use the following autocmd in your .vimrc or +.gvimrc file to open a file at the last edited location: + + au BufReadPost * if line("'\"") > 0 && line("'\"") <= line("$") | + \ exe "normal g'\"" | endif + +For more information, read + + :help '" + :help last-position-jump + + +5.6. When editing a file in Vim, which is being changed by an external + application, Vim opens a warning window (like the confirm dialog) each + time a change is detected. How do I disable this warning? + +You can set the Vim 'autoread' option to automatically read the file again +when it is changed outside of Vim: + + :set autoread + +You can also use the following autocommand: + + autocmd FileChangedShell * + \ echohl WarningMsg | + \ echo "File has been changed outside of vim." | + \ echohl None + +For more information, read + + :help 'autoread' + :help FileChangedShell + :help timestamp + :help :checktime + + +5.7. How do I edit a file whose name is under the cursor? + +You can use the gf command to edit a file whose name is under the cursor. +You can use the CTRL-W f command to edit the file in a new window. + +For more information, read + + :help gf + :help CTRL-W_f + :help 'isfname' + :help 'path' + :help 'suffixesadd' + :help 'includeexpr' + + +5.8. How do I reload/re-edit the current file? + +You can use the ":edit" command, without specifying a file name, to reload +the current file. If you have made modifications to the file, you can use +":edit!" to force the reload of the current file (you will lose your +modifications). + +For more information, read + + :help :edit + :help :edit! + :help 'confirm' + + +5.9. How do I autosave a file periodically? + +Vim doesn't support auto-saving a file periodically. + +For more information, read + + :help 'updatetime' + :help CursorHold + :help swap-file + + +5.10. How do I open a file in read-only mode? + +You can open a file in read-only mode using the ":view" command: + + :view <filename> + +This command sets the 'readonly' option for the opened buffer. You can also +use the "-R" command-line option to open a file in read-only mode: + + $ vim -R <filename> + +You can also use the symbolic link executable "view" to open a file in +read-only mode from the command-line: + + $ view <filename> + +For more information, read + + :help 07.6 + :help 'readonly' + :help 'modifiable' + :help :view + :help :sview + :help view + :help -R + :help -M + + +5.11. How do I open a file for editing without saving the modifications to + the current file? + +You can open a file for editing without saving the modifications to the +current file and without losing the changes using one of the following +methods: + + :split <new_filename> + :new <new_filename> + +You can also set the 'hidden' option and edit a new file: + + :set hidden + : e <new_filename> + +If you want to discard the changes made to the current file and load +another file for editing, then you can use the following command: + + :e! <new_filename> + +For more information, read + + :help :edit!_f + :help 'hidden' + :help :split + :help :new + + +============================================================================= + +SECTION 6 - EDITING MULTIPLE FILES + + +6.1. How do I open multiple files at once from within Vim? + +There are several ways to open multiple files at once from within Vim. You +can use the ":next" command to specify a group of files: + + :next f1.txt f2.txt + :next *.c + +You can use the :args command to specify a group of files as arguments: + + :args f1.txt f2.txt + :args *.c + +After loading the files, you can use the ":next" and ":prev" command to +switch between the files. + +For more information, read + + :help 07.2 + :help :next + :help :args_f + :help argument-list + + +6.2. How do I switch between multiple files/buffers in Vim? + +There are several ways to switch between multiple files. You can use the +":buffer" command to switch between multiple files. For example, + + :buffer file1 + :buffer file2 + +You can also use the CTRL-^ key to switch between buffers. By specifying a +count before pressing the key, you can edit the buffer with that number. +Without the count, you can edit the alternate buffer by pressing CTRL-^ + +You can also use the ":e #" command to edit a particular buffer: + + :e #5 + +For more information, read + + :help edit-files + :help :buffer + :help CTRL-^ + :help alternate-file + :help 22.4 + :help 07.3 + + +6.3. How do I open several files in Vim, with each file in a separate + window? + +You can use the -o and -O Vim command line arguments to open multiple files +in separate horizontally or vertically split Vim windows. For example: + + $ vim -o3 f1.txt f2.txt f3.txt + +The above command will open the files f1.txt, f2.txt and f3.txt in three +separate horizontally split Vim windows. + + $ vim -O3 f1.txt f2.txt f3.txt + +The above command will open the files f1.txt, f2.txt and f3.txt in three +separate vertically split Vim windows. + +For more information, read + + :help -o + :help -O + :help startup-options + + +6.4. How do I configure Vim to autoload several files at once similar to + "work-sets" or "projects"? + +You can use the ":mksession" and the ":mkview" commands to autoload several +files in Vim. + +The ":mksession" command creates a Vim script that restores the current +editing session. You can use the ":source" command to source the file +produced by the mksession command. + +The ":mkview" command creates a Vim script that restores the contents of +the current window. You can use the ":loadview" command to load the view +for the current file. + +For more information, read + + :help 21.4 + :help 21.5 + :help views-sessions + :help 'sessionoptions' + :help :mksession + :help :source + :help v:this_session + :help :mkview + :help :loadview + :help 'viewdir' + :help buffers + + +6.5. Is it possible to open multiple top level windows in a single instance + of Vim similar to Nedit or emacs? + +No. It is currently not possible to open multiple top-level windows in a +single instance of Vim. This feature is in the todo list. + + +6.6. How do I browse/explore directories from within Vim? + +You can use the explorer.vim plugin, supplied with the standard Vim +installation, to browse/explore directories from within Vim. You can start +the file explorer using one of the following commands: + + :e <directory> + :Explore + :SExplore + +From the file explorer, you can browse through directories, rename, delete +and edit files. + +For more information, read + + :help file-explorer + :help 22.1 + + +6.7. How do I edit files over a network using ftp/scp/rcp/http? + +You can use the netrw.vim plugin, supplied with the standard Vim package, +to edit files over a network using ftp/scp/rcp/http. Using this plugin, Vim +will transparently load and save the files over ftp/scp/rcp/http. For +example, to edit a file over ftp, you can use the following command: + + $ vim ftp://machine/path + +For more information, read + + :help netrw.vim + + +============================================================================= + +SECTION 7 - BACKUP + + +7.1. When I edit and save files, Vim creates a file with the same name as + the original file and a "~" character at the end. How do I stop Vim + from creating this file? (or) How do I disable the Vim backup file + feature? + +You have set the 'backup' option, so Vim creates a backup file when saving +the original file. You can stop Vim from creating the backup file, by +clearing the option: + + :set nobackup + +Note that, by default this option is turned off. You have explicitly +enabled the 'backup' option in one of the initialization files. You may +also have to turn off the 'writebackup' option: + + :set nowritebackup + +For more information, read + + :help 07.4 + :help backup-table + :help 'backup' + :help 'writebackup' + :help 'backupskip' + :help 'backupdir' + :help 'backupext' + :help 'backupcopy' + :help backup + + +7.2. How do I configure Vim to store all the backup files in a particular + directory? + +You can configure Vim to store all the backup files in a particular +directory using the 'backupdir' option. For example, to store all the +backup files in the ~/backup directory, you can use the following command: + + :set backupdir=~/backup + +For more information, read + + :help 07.4 + :help 'backupdir' + :help backup + + +7.3. When I save a file with Vim, the file permissions are changed. + How do I configure Vim to save a file without changing the file + permissions? + +This may happen, if the 'backupcopy' option is set to 'no' or 'auto'. Note +that the default value for this option is set in such a way that this will +correctly work in most of the cases. If the default doesn't work for you, +try setting the 'backupcopy' option to 'yes' to keep the file permission +when saving a file: + + :set backupcopy=yes + +This applies, only if you have configured Vim to make a backup whenever +overwriting a file. By default, Vim will not backup files. + +For more information, read + + :help 'backupcopy' + :help backup + :help 'backup' + :help 'writebackup' + + +============================================================================= + +SECTION 8 - BUFFERS + + +8.1. I have made some modifications to a buffer. How do I edit another + buffer without saving the modified buffer and also without losing the + modifications? + +You can set the 'hidden' option to edit a file without losing modifications +to the current file: + + :set hidden + +By setting the 'hidden' option, you can also save the modification history +(undo-history) for the buffer. Otherwise, as you switch between files, the +undo-history will be lost. + +For more information, read + + :help 'hidden' + :help hidden-quit + :help :hide + + +8.2. How do I configure Vim to auto-save a modified buffer when switching + to another buffer? + +You can set the 'autowrite' option to auto-save a modified buffer when +switching to another buffer: + + :set autowrite + +For more information, read + + :help 'autowrite' + :help 'autowriteall' + :help 'hidden' + + +8.3. How do I replace the buffer in the current window with a blank buffer? + +You can use the ":enew" command to load an empty buffer in place of the +buffer in the current window. + +For more information, read + + :help :enew + + +8.4. Is there a keyboard shortcut to load a buffer by the buffer number? + +You can use the CTRL-^ command to load a buffer by specifying the buffer +number. For example, to load buffer number 5, you have to use the 5 CTRL-^ +command. + +For more information, read + + :help CTRL-^ + + +8.5. How do I open all the current buffers in separate windows? + +You can use the ":ball" or ":sball" commands to open all the buffers +in the buffer list: + + :ball + +For more information, read + + :help :ball + + +8.6. How do I close (delete) a buffer without exiting Vim? + +You can use the ":bdelete" command to delete a buffer without exiting Vim. +For example: + + :bdelete file1 + +For more information, read + + :help :bdelete + :help :bwipeout + + +8.7. I have several buffers opened with :e filename. How do I close one of + the buffers without exiting Vim? + +You can use the ":bdelete <buffername>" command to close the buffer. + +For more information, read + + :help :bdelete + :help :bunload + :help :bwipeout + + +8.8. When I use the command ":%bd" to delete all the buffers, not all the + buffers are deleted. Why? + +In the ":%bd" command, the '%' range will be replaced with the starting and +ending line numbers in the current buffer. Instead of using '%' as the +range, you should specify numbers for the range. For example, to delete all +the buffers, you can use the command ":1,9999bd". + +For more information, read + + :help :bd + + +8.9. How do I display the buffer number of the current buffer/file? + +You can use 2<CTRL-G> command to display the buffer number for the current +file/buffer. Note the use of count before the CTRL-G command. If the count +is greater than 1, then Vim will display the buffer number. + +You can also use the following command to display the current buffer +number: + + :echo bufnr("%") + +You can also include the "%n" field to the 'statusline' option to display +the current buffer number on the statusline. + +For more information read, + + :help CTRL-G + :help bufnr() + :help :echo + :help 'statusline' + + +8.10. How do I delete a buffer without closing the window in which the + buffer is displayed? + +You can use the following command to open the next buffer and delete +the current buffer. + + :bnext | bdelete # + +For more information read, + + :help :bnext + :help :bdelete + :help :buffers + + +8.11. How do I map the tab key to cycle through and open all the buffers? + +You can use the following two map commands, to map the CTRL-Tab key to open +the next buffer and the CTRL-SHIFT-Tab key to open the previous buffer: + + :nnoremap <C-Tab> :bnext<CR> + :nnoremap <S-C-Tab> :bprevious<CR> + +For more information read, + + :help :bnext + :help :previous + + +============================================================================= + +SECTION 9 - WINDOWS + + +9.1. What is the difference between a Vim window and a buffer? + +A Vim buffer is a file loaded into memory for editing. The original file +remains unchanged until you write the buffer to the file. A Vim window is a +viewport onto a buffer. You can use multiple windows on one buffer or +several windows on different buffers. + +For more information, read + + :help usr_08.txt + :help 22.4 + :help windows-intro + :help Q_wi + + +9.2. How do I increase the width of a Vim window? + +You can increase the width of a Vim window using one of the following +commands: + + :vert resize +N + :vert resize -N + :vert resize N + +You can also use CTRL-W < or CTRL-W > or CTRL-W | commands. + +For more information, read + + :help vertical-resize + :help CTRL-W_> + :help CTRL-W_< + :help window-resize + + +9.3. How do I zoom into or out of a window? + +You can zoom into a window (close all the windows except the current +window) using the "CTRL-W o" command or the ":only" ex command. + +You can use the "CTRL-W _" command or the ":resize" ex command to increase +the current window height to the highest possible without closing other +windows. + +You can use the "CTRL-W |" command or the ":vertical resize" ex command to +increase the current window width to the highest possible without closing +other windows. + +You can use the "CTRL-W =" command to make the height and width of all the +windows equal. + +You can also set the following options to get better results with the above +commands: + +Method 1: +Set the 'winminheight' option to 0: + + :set winminheight=0 + +By default, this option is set to 1. +This option controls the minimum height of an inactive window (when it is +not the current window). When the 'winminheight' option is set to 0, only +the status line will be displayed for inactive windows. + +Method 2: +Set the 'noequalalways' option and set the 'winheight' option to a large +value (like 99999): + + :set noequalalways + :set winheight=99999 + +Now, the active window will always open to its maximum size, while the +other windows will stay present, but shrunken to just a status line. + +With any of the above mentioned methods, you cannot restore the window +layout after zooming into a window. If you want to restore the Vim window +layout after zooming into a window, you can use the ZoomWin plugin. You can +download this plugin from the Vim online website at: + +http://vim.sourceforge.net/scripts/script.php?script_id=508 + +For more information, read + + :help CTRL-W_o + :help window-resize + :help 'winminheight' + :help 'equalalways' + :help 'winheight' + :help 08.3 + + +9.4. How do I execute an ex command on all the open buffers or open windows + or all the files in the argument list? + +You can use the ":bufdo" command to execute an ex command on all the open +buffers. You can use the ":windo" command to execute an ex command on all +the open windows. You can use the ":argdo" command to execute an ex +command on all the files specified in the argument list. + +For more information, read + + :help :windo + :help :bufdo + :help :argdo + :help 26.3 + + +============================================================================= + +SECTION 10 - MOTION + + +10.1. How do I jump to the beginning (first line) or end (last line) of a + file? + +You can use 'G' command to jump to the last line in the file and the 'gg' +command to jump to the first line in the file. + +For more information, read + + :help G + :help gg + + +10.2. In insert mode, when I press the <Esc> key to go to command mode, the + cursor moves one character to the left (except when the cursor is on + the first character of the line). Is it possible to change this + behavior to keep the cursor at the same column? + +No. It is not possible to change this behavior. The cursor is *always* +positioned on a valid character (unless you have virtual-edit mode +enabled). So, if you are appending text to the end of a line, when you +return to command mode the cursor *must* drop back onto the last character +you typed. For consistency sake, the cursor drops back everywhere, even if +you are in the middle of a line. + +You can use the CTRL-O command in insert mode to execute a single ex +command and return back to insert mode without moving the cursor column. + +For more information, read + + :help 'virtual' + :help i_CTRL-O + + +10.3. How do I configure Vim to maintain the horizontal cursor position when + scrolling with the <Page Up>, <Page Down>, etc keys? + +You can reset the 'startofline' option to keep the cursor at the same +horizontal location when scrolling text: + + :set nostartofline + +For more information, read + + :help 'startofline' + + +10.4. Some lines in a file are more than the screen width and they are all + wrapped. When I use the j, k keys to move from one line to the next, + the cursor is moved to the next line in the file instead of the next + line on the screen. How do I move from one screen line to the next? + +You can use the gj and gk commands to move from one screen line to the +next/previous screen line. The j and k commands move the cursor from one +file line to the next file line. You can also avoid the line wrapping by +resetting the 'wrap' option: + + :set nowrap + +For more information, read + + :help gj + :help gk + :help 'wrap' + +You can use the following mappings: + + :map <Up> gk + :imap <Up> <C-o>gk + :map <Down> gj + :imap <Down> <C-o>gj + + +10.5. What is the definition of a sentence, paragraph and section in Vim? + +A sentence is defined as ending at a '.', '!' or '?' followed by either the +end of a line, or by a space (or two) or tab. Which characters and the +number of spaces needed to constitute a sentence ending is determined by +the 'joinspaces' and 'cpoptions' options. + +A paragraph begins after each empty line, and also at each of a set of +paragraph macros, specified by the pairs of characters in the 'paragraphs' +option. + +A section begins after a form-feed (<C-L>) in the first column and at each +of a set of section macros, specified by the pairs of characters in the +'sections' option. + +For more information, read + + :help sentence + :help 'joinspaces' + :help 'cpoptions' | /^\s*j\> + :help paragraph + :help section + :help word + + +10.6. How do I jump to beginning or end of a sentence, paragraph or a + section? + +You can use the following motion commands to jump to the beginning or end +of a sentence or a paragraph or a section: + + motion position where + ( beginning current sentence + ) end current sentence + { beginning current paragraph + } end current paragraph + [] end previous section + [[ beginning current section + ][ end current section + ]] beginning next section + +Each of these motions can be preceded by a number which will extend the +jump forward (or backward). + +For more information, read + + :help object-motions + + +10.7. I have lines in a file that extends beyond the right extent of the + screen. How do I move the Vim view to the right to see the text off + the screen? + +You can use one of the following commands to horizontally scroll the screen +to the left or right: + + zl - scroll to the left + zh - scroll to the right + zL - scroll half a screenwidth to the left + zH - scroll half a screenwidth to the right + zs - scroll to position the cursor at the start of the screen + ze - scroll to position the cursor at the end of the screen + +You can use the g0 command to move the cursor to the first character of the +screen line and the g$ command to move the cursor to the last character of +the screen line without scrolling the screen. + +For more information, read + + :help scroll-horizontal + + +10.8. How do I scroll two or more buffers simultaneously? + +You can set the "scrollbind" option for each of the buffer to scroll them +simultaneously. + +For more information, read + + :help 'scrollbind' + :help scroll-binding + :help 'scrollopt' + + +10.9. When I use my arrow keys, Vim changes modes, inserts weird characters + in my document but doesn't move the cursor properly. What's going on? + +There are a couple of things that could be going on: either you are using +Vim over a slow connection or Vim doesn't understand the key sequence that +your keyboard is generating. + +If you are working over a slow connection (such as a 2400 bps modem), you +can try to set the 'timeout' or 'ttimeout' option. These options, combined +with the 'timeoutlen' and 'ttimeoutlen' options, may fix the problem. + +The preceding procedure will not work correctly if your terminal sends key +codes that Vim does not understand. In this situation, your best option is +to map your key sequence to a matching cursor movement command and save +these mappings in a file. You can then ":source" the file whenever you work +from that terminal. + +For more information, read + + :help 'timeout' + :help 'ttimeout' + :help 'timeoutlen' + :help 'ttimeoutlen' + :help :map + :help vt100-cursor-keys + + +10.10. How do I configure Vim to move the cursor to the end of the previous + line, when the left arrow key is pressed and the cursor is currently + at the beginning of a line? + +You can add the '<' flag to the 'whichwrap' option to configure Vim to move +the cursor to the end of the previous line, when the left arrow key is +pressed and the cursor is currently at the beginning of a line: + + :set whichwrap+=< + +Similarly, to move the cursor the beginning of the next line, when the +right arrow key is pressed and the cursor is currently at the end of a +line, add the '>' flag to the 'whichwrap' option: + + :set whichwrap+=> + +The above will work only in normal and visual modes. To use this in insert +and replace modes, add the '[' and ']' flags respectively. + +For more information, read + + :help 'whichwrap' + :help 05.7 + + +10.11. How do I configure Vim to stay only in insert mode (modeless + editing)? + +You can set the 'insertmode' option to configure Vim to stay only in insert +mode: + + :set insertmode + +By setting this option, you can use Vim as a modeless editor. If you press +the <Esc> key, Vim will not go to the normal mode. To execute a single +normal mode command, you can press CTRL-O followed by the normal mode +command. To execute more than one normal command, you can use CTRL-L +followed by the commands. To return to insert mode, press the <Esc> key. To +disable this option, reset the 'insertmode' option: + + :set noinsertmode + +You can also start vim using the "evim" command or you can use "vim -y" to +use Vim as a modeless editor. + +You can also start Vim in insert mode using the ":startinsert" ex command. + +For more information, read + + :help 'insertmode' + :help :startinsert + :help :stopinsert + :help i_CTRL-O + :help i_CTRL-L + :help evim + :help evim-keys + + +10.12. How do I display some context lines when scrolling text? + +You can set the 'scrolloff' option to display a minimal number of screen +lines (context) above and below the cursor. + + :set scrolloff=10 + +For more information, read + + :help 'scrolloff' + :help 'sidescrolloff' + + +10.13. How do I go back to previous cursor locations? + +You can go back to the cursor location before the latest jump using the '' +or `` command. You can use the CTRL-O command to go back to older cursor +positions and the CTRL-I command to go to the newer cursor positions in the +jump list. + +For more information, read + + :help 03.10 + :help mark-motions + :help jump-motions + + +============================================================================= + +SECTION 11 - SEARCHING TEXT + + +11.1. After I searched for a text with a pattern, all the matched text + stays highlighted. How do I turn off the highlighting + temporarily/permanently? + +The 'hlsearch' option controls whether all the matches for the last +searched pattern are highlighted or not. By default, this option is not +enabled. If this option is set in a system-wide vimrc file, then you can +turn off the search highlighting by using the following command: + + :set nohlsearch + +To temporarily turn off the search highlighting, use + + :nohlsearch + +You can also clear the search highlighting, by searching for a pattern that +is not in the current file (for example, search for the pattern 'asdf'). + +For more information, read + + :help 'hlsearch' + :help :nohlsearch + + +11.2. How do I enter a carriage return character in a search pattern? + +You can either use '\r' or <CTRL-V><CTRL-M> to enter a carriage return +character in a pattern. In Vim scripts, it is better to use '\r' for the +carriage return character. + +For more information, read + + :help sub-replace-special + + +11.3. How do I search for the character ^M? + +You can enter the ^M character in a search command by first pressing the +CTRL-V key and then pressing the CTRL-M key. + + /^V^M + +You can also use the "\r" character. In Vim scripts, "\r" is preferred. + +For more information, read + + :help c_CTRL-V + :help using_CTRL-V + :help /\r + + +11.4. How can I search/replace characters that display as '~R', '~S', etc.? + +You can use the 'ga' command to display the ASCII value/code for the +special character. For example, let us say the ASCII value is 142. Then you +can use the following command to search for the special character: + + /^V142 + +where, ^V is entered by pressing CTRL-V. + +For more information, read + + :help ga + :help using_CTRL_V + :help 24.8 + + +11.5. How do I highlight all the non-printable characters in a file? + +You can use the following commands and search pattern to highlight all the +non-printable characters in a file: + + :set hlsearch + /\(\p\|$\)\@!. + +For more information, read + + :help /\p + :help /bar + :help /$ + :help /\( + :help /\@! + :help 'hlsearch' + + +11.6. How do I search for whole words in a file? + +You can search for whole words in a file using the \< and \> atoms. For +example: + + /\<myword\> + +The \< atom matches the beginning of the word and the \> atom matches the +end of the word. + +For more information, read + + :help /\< + :help /\> + + +11.7. How do I search for the current word under the cursor? + +You can press the * key to search forward for the current word under the +cursor. To search backward, you can press the # key. Note that only whole +keywords will be searched using these commands. + +For more information, read + + :help star + :help # + :help g* + :help g# + :help 03.8 + :help search-commands + + +11.8. How do I search for a word without regard to the case (uppercase or + lowercase)? + +To always ignore case while searching for a pattern, set the 'ignorecase' +option: + + :set ignorecase + +To ignore case only when searching a particular pattern, use the special \c +directive: + + /\c<pattern> + +For more information, read + + :help 'ignorecase' + :help /ignorecase + :help /\c + + +11.9. How do I search for words that occur twice consecutively? + +You can use one of the following search commands to locate words that occur +twice consecutively: + + /\(\<\w\+\)\_s\+\1\> + /\(\<\k\+\)\_s\+\1\> + +The main difference is the use of '\w' and '\k', where the latter is based +on the 'iskeyword' option which may include accented and other language +specific characters. + +For more information, read + + :help /\1 + :help /\( + :help /\) + :help /\< + :help /\> + :help /\w + :help /\k + :help /\+ + :help /\_x + :help 'iskeyword' + + +11.10. How do I count the number of times a particular word occurs in a + buffer? + +You can use the following set of commands to count the number of times a +particular word occurs in a buffer: + + :let cnt=0 + :g/\<your_word\>/let cnt=cnt+1 + :echo cnt + +This only counts the number of lines where the word occurs. You can also +use the following command: + + :%s/\<word\>/&/g + +To count the number of alphabetic words in a file, you can use + + :%s/\a\+/&/g + +To count the number of words made up of non-space characters, you can use + + :%s/\S\+/&/g + +For more information, read + + :help count-items + :help word-count + :help v_g_CTRL-G + :help 12.5 + + +11.11. How do I place the cursor at the end of the matched word when + searching for a pattern? + +You can use the 'e' offset to the search command to place the cursor at the +end of the matched word. For example + + /mypattern/e + +For more information about search offsets, read + + :help search-offset + :help / + + +11.12. How do I search for an empty line? + +You can search for an empty line using: + + /^$ + + or + + /^\s*$ + +For more information, read + + :help /^ + :help /$ + :help /\s + :help /* + :help search-commands + + +11.13. How do I search for a line containing only a single character? + +You can search for a line containing only a single character using: + + /^\s*\a\s*$ + +For more information, read + + :help /^ + :help /\a + :help /\s + :help /* + :help /$ + + +11.14. How do I search and replace a string in multiple files? + +You can use the 'argdo' or 'bufdo' or 'windo' commands to execute an ex +command on multiple files. For example: + + :argdo %s/foo/bar/g + +For more information, read + + :help :argdo + :help :bufdo + :help :windo + + +11.15. I am using the ":s" substitute command in a mapping. When a search + for a pattern fails, the map terminates. I would like the map to + continue processing the next command, even if the substitute command + fails. How do I do this? + +You can use the 'e' flag to the substitute command to continue processing +other commands in a map, when a pattern is not found. + +For more information, read + + :help :s_flags + + +11.16. How do I search for the n-th occurrence of a character in a line? + +To search for the n-th occurrence of a character in a line, you can prefix +the 'f' command with a number. For example, to search for the 5th +occurrence of the character @ in a line, you can use the command 5f@. This +assumes the cursor is at the beginning of the line - and that this first +character is not the one your are looking for. + +For more information, read + + :help f + :help F + :help t + :help T + :help ; + :help , + + +11.17. How do I replace a tab (or any other character) with a hard return + (newline) character? + +You can replace a tab (or any other character) with a hard return (newline) +character using the following command: + + :s/\t/\r/ + +Note that in the above command, if you use \n instead of \r, then the tab +characters will not be replaced by a new-line character. + +For more information, read + + :help sub-replace-special + :help NL-used-for-Nul + :help CR-used-for-NL + + +11.18. How do I search for a character by its ASCII value? + +You can search for a character by its ASCII value by pressing CTRL-V +followed by the decimal or hexadecimal or octal value of that character in +the search "/" command. To determine the ASCII value of a character you +can use the ":ascii" or the "ga" command. + +For more information, read + + :help i_CTRL-V_digit + :help :ascii + :help ga + + +11.19. How do I search for long lines? + +You can search for long lines or lines containing more than a specific +number of characters using the Vim regular-expressions in the search +command. For example, to search for all the lines containing more than 80 +characters, you can use one of the following commands: + + /^.\{80}.*$ + /^.*\%80c.*$ + +For more information, read + + :help /\{ + :help /\%c + + +11.20. How do I display all the lines in the current buffer that contain a + specified pattern? + +You can use the following command to display all the lines in the current +buffer that contain a specified pattern: + + :g/<pattern>/p + +For example, the following command will display all the lines in the +current buffer that contain "vim": + + :g/vim/p + +If you also want the corresponding line numbers, then you can use the +following command: + + :g/<pattern>/# + +For more information, read + + :help :global + :help :print + :help :number + + +11.21. How do I search for a text string that spans multiple lines? + +You can search for a text string that spans multiple lines using the \_x +regular expression atom. For example, to search for the text string "Hello +World", you can use the following search command: + + /Hello\_sWorld + +This will match the word "Hello" followed by a newline character and then +the word "World" at the beginning of the next line. This will also match +the word "Hello" immediately followed by a space character and then the +word "World". When searching for the "Hello World" string, to include the +space characters at the end and beginning of the line, you can use the +following search command: + + /Hello\_s\+World + +For more information, read + + :help 27.8 + :help pattern-atoms + :help /\_ + :help pattern-searches + + +11.22. How do I search for a pattern within the specified range of lines + in a buffer? + +You can search for a pattern within a range of lines using the \%>l +and \%<l regular expression atoms. + +For example, to search for the word 'white' between the lines 10 and 30 in +a buffer, you can use the following command: + + /white\%>10l\%<20l + +For more information, read + + :help /\%l + + +============================================================================= + +SECTION 12 - CHANGING TEXT + + +12.1. How do I delete all the trailing white space characters (SPACE and + TAB) at the end of all the lines in a file? + +You can use the ":substitute" command on the entire file to search and +remove all the trailing white space characters: + + :%s/\s\+$// + +For more information, read + + :help :% + :help :s + :help /\s + :help /\+ + :help /$ + + +12.2. How do I replace all the occurrences of multiple consecutive space + characters to a single space? + +You can use the following command to replace all the occurrences of +multiple consecutive space characters to a single space: + + :%s/ \{2,}/ /g + +For more information, read + + :help :% + :help :s + :help /\{ + :help :s_flags + + +12.3. How do I reduce a range of empty lines into one line only? + +You can use the following command to reduce a range of empty lines into one +line only: + + :v/./.,/./-1join + +The explanation for this command is below: + + :v/./ Execute the following command for all lines not + containing a character (empty lines). + ., Use the current line as the start of the range of + lines. + /./ Use the line containing a character as the last line. + -1 Adjust the range of lines to end with the line before + the last line. + j Join the lines in the range. + +Note that this will give an error message if the empty lines are at the end +of the file. To correct this, you have to add a temporary line at the end +of the file, execute the command and then remove the temporary line. + +For more information, read + + :help :v + :help :join + :help cmdline-ranges + :help collapse + + +12.4. How do I delete all blank lines in a file? How do I remove all the + lines containing only space characters? + +To remove all blank lines, use the following command: + + :g/^$/d + +To remove all lines with only whitespace (spaces or tabs) in them, use the +following command: + + :g/^\s\+$/d + +To remove all the lines with only whitespace, if anything, use the +following command: + + :g/^\s*$/d + + +12.5. How do I copy/yank the current word? + +You can use the "yiw" (yank inner word without whitespace) command or the +"yaw" (yank a word with whitespace) command to copy/yank the current +word. + +For more information, read + + :help 04.6 + :help 04.8 + :help iw + :help yank + :help text-objects + :help objects + + +12.6. How do I yank text from one position to another position within a + line, without yanking the entire line? + +You can specify a motion command with the yank operator (y) to yank text +from one position to another position within a line. For example, to yank +from the current cursor position till the next letter x, use yfx or Fx or +tx or Tx. To yank till the nth column, use n|. To yank till the next +occurrence of a 'word', use /word. To do a yank till the nth column on +another line, first mark the position using the 'ma' command, go to the +start of the yank position, and then yank till the mark using y`a (note the +direction of the quote) + +For more information, read + + :help yank + :help motion.txt + :help 4.6 + + +12.7. When I yank some text into a register, how do I append the text to + the current contents of the register? + +When you specify the register for some operation, if you use the upper-case +for the register name, then the new text will be appended to the existing +contents. For example, if you have some text in the register "a". If you +want to append some new text to this, you have to use the "A" register +name. If you use the lowercase register name, then the contents of the +register will be overwritten with the new text. + +For more information, read + + :help quote + :help quote_alpha + :help 10.1 + + +12.8. How do I yank a complete sentence that spans over more than one line? + +To yank a complete sentence that spans over more than one line you have to +use the yank operator followed by a motion command. For example: + + y) + +From inside the sentence you can use 'yi)' to yank the sentence. + +For more information, read + + :help yank + :help {motion} + :help object-motions + :help 4.6 + + +12.9. How do I yank all the lines containing a pattern into a buffer? + +You can use the ":global" command to yank all the lines containing the +pattern into a register and then paste the contents of the register into +the buffer: + + :let @a='' + :g/mypattern/y A + +The first command, clears the contents of the register "a". The second +command copies all the lines containing "mypattern" into the register "a". +Note that the capital letter "A" is used to append the matched lines. Now +you can paste the contents of register "a" to a buffer using "ap command. +For more information, read + + :help :g + :help :y + :help let-register + :help quote_alpha + :help put + :help registers + :help :registers + + +12.10. How do I delete all the lines in a file that does not contain a + pattern? + +You can use ":v" command to delete all the lines that does not contain a +pattern: + + :v/pattern/d + +or + + :g!/pattern/d + +For more information, read + + :help :v + :help :g + + +12.11. How do I add a line before each line with "pattern" in it? + +You can use the following command to add a line before each line with +"pattern" in it: + + :g/pattern/normal Oi<line of text goes here> + +Alternatively you can yank the line using the Y command and then insert the +line using the following command: + + :g/pattern/put! + +For more information, read + + :help :g + :help :put + :help insert + :help 0 + + +12.12. Is there a way to operate on a line if the previous line contains a + particular pattern? + +You can use the ":global" command to operate on a line, if the previous +line contains a particular pattern: + + :g/<pattern>/+{cmd} + +For more information, read + + :help :g + :help :range + + +12.13. How do I execute a command on all the lines containing a pattern? + +You can use the ":global" (:g) command to execute a command on all the +lines containing a pattern. + + :g/my pattern/d + +If you want to use a non-Ex command, then you can use the ":normal" +command: + + :g/my pattern/normal {command} + +Unless you want the normal mode commands to be remapped, consider using a +":normal!" command instead (note the "!"). + +For more information, read + + :help :global + :help :v + :help :normal + + +12.14. Can I copy the character above the cursor to the current cursor + position? + +In Insert mode, you can copy the character above the cursor to the current +cursor position by typing <Ctrl-Y>. The same can be done with the +characters below the cursor by typing <Ctrl-E>. + +For more information, read + + :help i_CTRL-Y + :help i_CTRL-E + + +12.15. How do I insert a blank line above/below the current line without + entering insert mode? + +You can use the ":put" ex command to insert blank lines. For example, try + + :put ='' + :put! ='' + +For more information, read + + :help :put + + +12.16. How do I insert the name of current file into the current buffer? + +There are several ways to insert the name of the current file into the +current buffer. In insert mode, you can use the <C-R>% or the +<C-R>=expand("%") command. In normal mode, you can use the ":put =@%" +command. + +For more information, read + + :help i_CTRL-R + :help expand() + :help !! + + +12.17. How do I insert the contents of a Vim register into the current + buffer? + +In insert mode, you can use the <C-R><register> command to insert the +contents of <register>. For example, use <C-R>a to insert the contents +of register "a" into the current buffer. + +In normal mode, you can use the ":put <register>" command to insert the +contents of <register>. For example, use the ":put d" command to insert +the contents of register "d" into the current buffer. + +For more information, read + + :help i_CTRL-R + :help :put + + +12.18. How do I move the cursor past the end of line and insert some + characters at some columns after the end of the line? + +You can set the "virtualedit" option to move the cursor past the +end-of-line and insert characters in a column after the end-of-line. To +start the virtual mode, use + + :set virtualedit=all + +For more information, read + + :help 'virtualedit' + + +12.19. How to replace the word under the cursor (say: junk) with + "foojunkbar" in Vim? + +There are several ways to do this. If the word is the first such word on +the line, use the following command: + + :exe "s/".expand("<cword>")."/foo&bar/" + +Too match specifically you could use a more complex substitution like this: + + :exe 's/\<'.expand("<cword>").'\%>'.(col(".")-1).'c\>/foo&bar/' + +You can also use the command: ciwfoo<C-R>"bar<Esc> + +For more information, read + + :help :substitute + :help expand() + :help col() + :help /\%c + + +12.20. How do I replace a particular text in all the files in a directory? + +You can use the "argdo" command to execute the substitute command on all +the files specified as arguments: + + :args * + :argdo %s/<your_text>/<replacement_text>/ge | update + +For more information, read + + :help :args_f + :help :argdo + :help :s_flags + + +12.21. I have some numbers in a file. How do I increment or decrement the + numbers in the file? + +You can use the CTRL-A key to increment the number and the CTRL-X key to +decrement the number. You can also specify the number to +increment/decrement from the number by specifying a count to the key. This +works for decimal, octal and hexadecimal numbers. You can change the base +used by Vim for this operation by modifying the 'nrformats' option. + +For more information, read + + :help 26.2 + :help CTRL-A + :help CTRL-X + :help 'nrformats' + + +12.22. How do I reuse the last used search pattern in a ":substitute" + command? + +To reuse the last used search pattern in a ":substitute" command, don't +specify a new search pattern: + + :s/pattern/newtext/ + :s//sometext/ + +In the second ":s" command, as a search pattern is not specified, the +pattern specified in the first ":s" command 'pattern' will be used. + +If you want to change the search pattern but repeat the substitution +pattern you can use the special right hand side, you can use the tilde +character: + + :s/newpattern/~/ + +For more information, read + + :help :s + :help :& + :help :~ + :help & + :help sub-replace-special + + +12.23. How do I change the case of a string using the ":substitute" + command? + +You can use special characters in the replacement string for a +":substitute" command to change the case of the matched string. For +example, to change the case of the string "MyString" to all uppercase, you +can use the following command: + + :%s/MyString/\U&/g + +To change the case to lowercase, you can use the following command: + + :%s/MyString/\L&/g + +To change the case of the first character in all the words in the current +line to uppercase, you can use the following command: + + :s/\<\(.\)\(\k*\)\>/\u\1\L\2/g + +For more information, read + + :help sub-replace-special + :help :substitute + :help \U + :help \L + :help \u + + +12.24. How do I enter characters that are not present in the keyboard? + +You can use digraphs to enter characters that are not present in the +keyboard. You can use the ":digraphs" command to display all the currently +defined digraphs. You can add a new digraph to the list using the +":digraphs" command. + +For more information, read + + :help digraphs + :help 'digraphs' + :help 24.9 + + +12.25. Is there a command to remove any or all digraphs? + +No. The digraphs table is defined at compile time. You can only add new +ones. Adding a command to remove digraphs is on the todo list. + + +12.26. In insert mode, when I press the backspace key, it erases only the + characters entered in this instance of insert mode. How do I erase + previously entered characters in insert mode using the backspace + key? + +You can set the 'backspace' option to erase previously entered characters +in insert mode: + + :set backspace=indent,eol,start + +For more information, read + + :help 'backspace' + :help i_backspacing + + +12.27. I have a file which has lines longer than 72 characters terminated + with "+" and wrapped to the next line. How can I quickly join the + lines? + +You can use the ":global" command to search and join the lines: + + :g/+$/j + +This will, however, only join every second line. A couple of more complex +examples which will join all consecutive lines with a "+" at the end are: + + :g/*$/,/\(^\|[^+]\)$/j + :g/+$/mark a | .,/\(^\|[^+]\)$/s/+$// | 'a,.j + +For more information, read + + :help :g + :help :j + :help :mark + + +12.28. How do I paste characterwise yanked text into separate lines? + +You can use the ":put" command to paste characterwise yanked text into new +lines: + + :put =@" + +For more information, read + + :help :put + :help quote_= + + +12.29. How do I change the case (uppercase, lowercase) of a word or a + character or a block of text? + +You can use the "~" command to switch the case of a character. + +You can change the case of the word under the cursor to uppercase using the +"gUiw" or "viwU" command and to lowercase using the "guiw" or "viwu" +command. + +You can switch the case (upper case to lower case and vice versa) of the +word under the cursor using the "viw~" or "g~iw" command. + +You can use the "gUgU" command to change the current line to uppercase and +the "gugu" command to change the current line to lowercase. + +You can use the "g~g~" command to switch the case of the current line. You +can use the "g~{motion}" or "{Visual}~" commands to switch the case of a +block of text. + +For more information, read + + :help case + + +12.30. How do I enter ASCII characters that are not present in the + keyboard? + +You can enter ASCII characters that are not present in the keyboard by +pressing CTRL-V and then the ASCII character number. You can also use +digraphs to enter special ASCII characters. + +For more information, read + + :help i_CTRL-V_digit + :help digraphs + :help 45.5 + + +12.31. How do I replace non-printable characters in a file? + +To replace a non-printable character, you have to first determine the ASCII +value for the character. You can use the ":ascii" ex command or the "ga" +normal-mode command to display the ASCII value of the character under the +cursor. + +You can enter the non-printable character by entering CTRL-V followed by +the decimal number 1-255 (with no leading zero), or by x and a hex number +00-FF, or by an octal number 0-0377 (with leading zero), or by u and a hex +number 0-FFFF, or by U and a hex number 0-7FFFFFFF + +Another alternative is to use the ":digraphs" ex command to display the +digraphs for all characters, together with their value in decimal and +alpha. You can enter a non-printable character by entering CTRL-K followed +by two alphanumeric characters (a digraph). + +For more information, read + + :help :ascii + :help i_CTRL-V + :help i_CTRL-V_digit + :help :digraphs + + +12.32. How do I remove duplicate lines from a buffer? + +You can use the following user-defined command to remove all the duplicate +lines from a buffer: + +:command -range=% Uniq <line1>,<line2>g/^\%<<line2>l\(.*\)\n\1$/d + +Add the above command to your .vimrc file and invoke ":Uniq" to remove all +the duplicate lines. + + +12.33. How do I prefix all the lines in a file with the corresponding line + numbers? + +You can prefix the lines with the corresponding line number in several +ways. Some of them are listed below: + + :%s/^/\=line('.'). ' ' + :%s/^/\=strpart(line(".")." ", 0, 5) + :g/^/exec "s/^/".strpart(line(".")." ", 0, 4) + +For more information, read + + :help sub-replace-special + :help line() + :help expr6 + :help strpart() + :help :execute + :help :global + + +12.34. How do I exchange (swap) two characters or words or lines? + +You can exchange two characters with the "xp" command sequence. The 'x' +will delete the character under the cursor and 'p' will paste the just +deleted character after the character under the cursor. This will result +in exchanging the two characters. + +You can exchange two words with the "deep" command sequence (start with the +cursor in the blank space before the first word). + +You can exchange two lines with the "ddp" command sequence. The 'dd' will +delete the current line and 'p' will paste the just deleted line after the +current line. This will result in exchanging the two lines. + +All of the above operations will change the " unnamed register. + +You can use the ":m +" ex command to exchange two lines without changing the +unnamed register. + +For more information, read + + :help x + :help p + :help dd + :help d + :help e + :help linewise-register + :help quotequote + :help :move + + +12.35. How do I change the characters used as word delimiters? + +Vim uses the characters specified by the 'iskeyword' option as word +delimitiers. The default setting for this option is "@,48-57,_,192-255". + +For example, to add ':' as a word delimitier, you can use + + :set iskeyword+=: + +To remove '_' as a word delimitier, you can use + + :set iskeyword-=_ + +For more information, read + + :help 'iskeyword' + :help word + + +============================================================================= + +SECTION 13 - COMPLETION IN INSERT MODE + + +13.1. How do I complete words or lines in insert mode? + +In insert mode, you can complete words using the CTRL-P and CTRL-N keys. +The CTRL-N command searches forward for the next matching keyword. +The CTRL-P command searches backwards for the next matching keyword. + +In insert mode, you can use the CTRL-X CTRL-L command sequence to complete +lines that starts with the same characters as in the current line before +the cursor. To get the next matching line, press the CTRL-P or CTRL-N keys. +There are a lot of other keys/ways available to complete words in insert +mode. + +Vim supports completion of the following items: + + CTRL-X CTRL-F file names + CTRL-X CTRL-L whole lines + CTRL-X CTRL-D macro definitions (also in included files) + CTRL-X CTRL-I current and included files + CTRL-X CTRL-K words from a dictionary + CTRL-X CTRL-T words from a thesaurus + CTRL-X CTRL-] tags + CTRL-X CTRL-V Vim command line + +For more information, read + + :help 24.3 + :help ins-completion + + +13.2. How do I complete file names in insert mode? + +In insert mode, you can use the CTRL-X CTRL-F command sequence to complete +filenames that start with the same characters as in the current line before +the cursor. + +For more information, read + + :help compl-filename + + +13.3. I am using CTRL-P/CTRL-N to complete words in insert mode. How do I + complete words that occur after the just completed word? + +You can use CTRL-X CTRL-N and CTRL-X CTRL-P keys to complete words that are +present after the just completed word. + +For more information, read + + :help i_CTRL-X_CTRL-P + :help i_CTRL-X_CTRL-N + :help ins-completion + + +============================================================================= + +SECTION 14 - TEXT FORMATTING + + +14.1. How do I format a text paragraph so that a new line is inserted at + the end of each wrapped line? + +You can use the 'gq' command to format a paragraph. This will format the +text according to the current 'textwidth' setting. + +Note that the gq operator can be used with a motion command to operate on a +range of text. For example: + + gqgq - Format the current line + gqap - Format current paragraph + gq3j - Format the current and the next 3 lines + +For more information, read + + :help gq + :help formatting + :help usr_25.txt + :help motion.txt + + +14.2. How do I format long lines in a file so that each line contains less + than 'n' characters? + +You can set the 'textwidth' option to control the number of characters that +can be present in a line. For example, to set the maximum width of a line +to 70 characters, you can use the following command: + + set textwidth=70 + +Now to break the long lines in a file to the length defined by the +'textwidth' option, you can use + + :g/./normal gqq + +For more information, read + + :help 'textwidth' + :help gq + + +14.3. How do I join short lines to form a paragraph? + +First, make sure the 'textwidth' option is set to a high value: + + :set textwidth=99999 + +Next, join the short lines to form a paragraph using the command: + + 1GgqG + +The above command will operate on the entire file. To do the formatting on +all paragraphs in a specific range, use: + + :'a,'bg/\S/normal gq} + +For more information, read + + :help gq + :help G + :help gqq + + +14.4. How do I format bulleted and numbered lists? + +You can configure Vim to format bulleted and numbered lists using the +'formatoptions' option. For example, you can format the list of the +following format: + + - this is a test. this is a test. this is a test. this is a test. + this is a test. + +into this format: + + - this is a test. this is a test. this is a test. this is a test. + this is a test. + +You can use the 'n' flag in the 'formatoptions' to align the text. + + :set fo+=n + +With this option, when formatting text, Vim will recognize numbered lists. +For this option to work, the 'autoindent' option also must be set. + +For more information, read + + :help 'formatoptions' + :help fo-table + :help format-comments + + +14.5. How do I indent lines in insert mode? + +In insert mode, you can press the CTRL-T key to insert one shiftwidth of +indent at the start of the current line. In insert mode, you can use the +CTRL-D key to delete on shiftwidth of indent at the start of the current +line. You can also use the CTRL-O >> and CTRL-O << commands to indent the +current line in insert mode. + +For more information, read + + :help i_CTRL-T + :help i_CTRL-D + :help i_0_CTRL-D + :help i_CTRL-O + :help >> + :help << + + +14.6. How do I format/indent an entire file? + +You can format/indent an entire file using the gg=G command, where + + gg - Goto the beginning of the file + = - apply indentation + G - till end of file + +For more information, read + + :help gg + :help = + :help G + :help 'formatprg' + :help C-indenting + + +14.7. How do I increase or decrease the indentation of the current line? + +You can use the '>>' and '<<' commands to increase or decrease the +indentation of the current line. + +For more information, read + + :help shift-left-right + :help >> + :help << + :help 'shiftwidth' + + +14.8. How do I indent a block/group of lines? + +You can visually select the group of lines and press the > or < key to +indent/unindent the lines. You can also use the following ex-command to +indent the lines + + :10,20> + +For more information, read + + :help shift-left-right + :help v_> + :help v_< + :help :< + :help :> + + +14.9. When I indent lines using the > or < key, the standard 8-tabstops are + used instead of the current 'tabstop' setting. Why? + +The number of spaces used when lines are indented using the ">" operator is +controlled by the 'shiftwidth' option. The 'tabstop' setting is not used +for indentation. To change the amount of spaces used for indentation, use +the command: + + :set shiftwidth=4 + +For more information, read + + :help 'shiftwidth' + :help >> + :help 'softtabstop' + + +14.10. How do I turn off the automatic indentation of text? + +By default, the automatic indentation of text is not turned on. Check the +configuration files (.vimrc, .gvimrc) for settings related to indentation. +Make sure the ":filetype indent on" command is not present. If it is +present, remove it. Also, depending on your preference, you may also want +to check the value of the 'autoindent', 'smartindent', 'cindent' and +'indentexpr' options and turn them off as needed. + +For more information, read + + :help :filetype-indent-off + :help 'autoindent' + :help 'smartindent' + :help 'cindent' + :help 'indentexpr' + + +14.11. How do I configure Vim to automatically set the 'textwidth' option + to a particular value when I edit mails? + +You can use the 'FileType' autocommand to set the 'textwidth' option: + + autocmd FileType mail set tw=<your_value> + +For more information, read + + :help :autocmd + :help FileType + :help usr_43.txt + + +14.12. Is there a way to make Vim auto-magically break lines? + +Yes. Set the 'textwidth' option to the preferred length for a line. Then +Vim will auto-magically break the newly entered lines. For example: + + :set textwidth=75 + +For more information, read + + :help 'textwidth' + :help ins-textwidth + :help 'formatoptions' + :help fo-table + :help formatting + + +14.13. I am seeing a lot of ^M symbols in my file. I tried setting the + 'fileformat' option to 'dos' and then 'unix' and then 'mac'. None of + these helped. How can I hide these symbols? + +When a file is loaded in Vim, the format of the file is determined as +below: + +- If all the lines end with a new line (<NL>), then the fileformat is + 'unix'. +- If all the lines end with a carriage return (<CR>) followed by a new line + (<NL>), then the fileformat is 'dos'. +- If all the lines end with carriage return (<CR>), then the fileformat is + 'mac'. + +If the file has some lines ending with <CR> and some lines ending with <CR> +followed by a <NL>, then the fileformat is set to 'unix'. + +You can change the format of the current file, by modifying the +'fileformat' option and then saving the file: + + :set fileformat=dos + :w + +To display the format of the current file, use + + :set fileformat? + +The above behavior is also controlled by the 'fileformats' option. You can +try the following commands: + + :set fileformats+=unix + :e <your_file> + :set fileformat=unix + :w + +To remove the carriage return (<CR>) character at the end of all the lines +in the current file, you can use the following command: + + :%s/\r$// + +To force Vim to use a particular file format, when editing a file, you can +use the following command: + + :e ++ff=dos filename + +For more information, read + + :help 'fileformats' + :help 'fileformat' + :help file-formats + :help DOS-format-write + :help Unix-format-write + :help Mac-format-write + :help dos-file-formats + :help 23.1 + :help ++ff + + +14.14. When I paste some text into a Vim buffer from another application, + the alignment (indentation) of the new text is messed up. How do I + fix this? + +The indentation of the text is messed up due to various Vim settings +related to indentation (like autoindent, smartindent, textwidth etc). +Before pasting text into Vim, you can set the 'paste' option: + + :set paste + +After pasting the text, you can turn off the option using: + + :set nopaste + +You can also toggle the paste option using: + + :set paste! + +If you can access the clipboard through the * register, then you can paste +the text without indentation using CTRL-R CTRL-O *. + +For more information, read + + :help 'paste' + :help 'pastetoggle' + :help i_CTRL-R_CTRL_O + :help clipboard + :help xterm-clipboard + :help gui-clipboard + + +14.15. When there is a very long wrapped line (wrap is "on") and a line + doesn't fit entirely on the screen it is not displayed at all. There + are blank lines beginning with '@' symbol instead of wrapped line. If + I scroll the screen to fit the line the '@' symbols disappear and the + line is displayed again. What Vim setting control this behavior? + +You can set the 'display' option to 'lastline' to display as much as +possible of the last line in a window instead of displaying the '@' +symbols. + + :set display=lastline + +For more information, read + + :help 'display' + + +14.16. How do I convert all the tab characters in a file to space + characters? + +You can use the ":retab" command to update all the tab characters in the +current file with the current setting of 'expandtab' and 'tabstop'. For +example, to convert all the tabs to white spaces, use + + :set expandtab + :retab + +For more information, read + + :help :retab + :help 'expandtab' + :help 'tabstop' + :help 25.3 + + +14.17. What Vim options can I use to edit text that will later go to a word + processor? + +You can set the following options to edit text that will later go into a +word processor: + + :set wrap + :set linebreak + :set textwidth=0 + :set showbreak=>>> + +You can use the 'gk' and 'gj' commands to move one screen line up and down. +For more information, read + + :help 'wrap' + :help 'linebreak' + :help 'textwidth' + :help 'showbreak' + :help gk + :help gj + + +14.18. How do I join lines without adding or removing any space characters? + +By default, when you join lines using the "J" or ":join" command, Vim will +replace the line break, leading white space and trailing white space with a +single space character. If there are space characters at the end of a line +or a line starts with the ')' character, then Vim will not add a space +character. + +To join lines without adding or removing any space characters, you can use +the gJ or ":join!" commands. + +For more information, read + + :help gJ + :help :join + :help J + :hep 10.5 + :help 'joinspaces' + :help 'cpoptions' + :help 'formatoptions' + + +============================================================================= + +SECTION 15 - VISUAL MODE + + +15.1. How do I do rectangular block copying? + +You can do rectangular block copying in Vim using the blockwise visual +mode. To start blockwise visual mode use the CTRL-V key. Move the cursor +using any of the motion commands and then use the y operator to yank to +visually selected text. + +If CTRL-V does not work as expected, it may have been remapped to CTRL-Q by +the mswin.vim script which is often sourced by a vimrc on Windows machines +to mimic some common short cuts from other programs. + +For more information, read + + :help 04.4 + :help blockwise-visual + :help visual-mode + :help Q_vi + + +15.2. How do I delete or change a column of text in a file? + +You can use the Vim block-wise visual mode to select the column of text and +apply an operator (delete, change, copy, etc) on it. + +For more information, read + + :help visual-block + :help visual-operators + + +15.3. How do I apply an ex-command on a set of visually selected lines? + +When you select a range of lines in visual mode, the < register is set to +the start of the visual region and the > register is set to the end of the +visual region. You can use these registers to specify the range for an ex +command. After visually selecting the lines, press ":" to go to the command +mode. Vim will automatically insert the visual range '<,'>. You can run +any ex-command on the visual range. + +For more information, read + + :help v_: + :help '< + :help '> + + +15.4. How do I execute an ex command on a column of text selected in Visual + block mode? + +All the ex commands operate on whole lines only. If you try to execute an +ex command on a column of text selected in visual block mode, Vim will +operate on all the selected lines (instead of the selected columns). You +can use the vis.vim plugin script from http://vim.sourceforge.net scripts +archive to do this. + +For more information, read + + :help cmdline-ranges + :help 10.3 + :help cmdline-lines + + +15.5. How do I select the entire file in visual mode? + +You can select the entire file in visual mode using ggVG. + + gg - go to the beginning of the file. + V - Start linewise visual mode + G - goto the end of the file. + +For more information, read + + :help gg + :help linewise-visual + :help G + + +15.6. When I visually select a set of lines and press the > key to indent + the selected lines, the visual mode ends. How can I reselect the + region for further operation? (or) How do I re-select the last + selected visual area again? + +You can use the 'gv' command to reselect the last selected visual area. You +can also use the marks '< and '> to jump to the beginning or the end of the +last selected visual area. + +For more information, read + + :help gv + :help '< + :help '> + + +15.7. How do I jump to the beginning/end of a visually selected region? + +You can use the 'o' command to jump to the beginning/end of a visually +selected region. + +For more information, read + + :help v_o + + +15.8. When I select text with mouse and then press : to enter an ex + command, the selected text is replaced with the : character. How do I + execute an ex command on a text selected using the mouse similar to + the text selected using the visual mode? + +This will happen if you have configured Vim to use select mode instead of +Visual mode by setting the 'selectmode' option. Check the value of this +option: + + :set selectmode? + +This mode is known as selectmode and is similar to the visual mode. This +option is also automatically set when you use the "behave mswin" command. +Select mode looks like visual mode, but it is similar to the selection mode +in MS-Windows. + +For more information, read + + :help Select-mode + :help 'selectmode' + :help 9.4 + :help :behave + + +15.9. When I select a block of text using the mouse, Vim goes into + selection mode instead of Visual mode. Why? + +The 'selectmode' option controls whether Select mode will be started when +selecting a block of text using the mouse. To start Visual mode when +selecting text using mouse, remove the 'mouse' value from the 'selectmode' +option: + + :set selectmode-=mouse + +Note that by default, the 'selectmode' option will be set to empty, so that +always visual mode is used. + +For more information, read + + :help 'selectmode' + :help Select-mode + :help :behave + + +15.10. How do I visually select the last copy/pasted text? + +You can use the '[ and '] marks to visually select the last copy/pasted +text. The '[ mark is set to the beginning of the last changed/yanked text +and the '] mark is set to the end of the last changed/yanked text. To +visually select this block of text use the command '[v'] + +For more information, read + + :help '[ + :help '] + :help `a + :help v + + +============================================================================= + +SECTION 16 - COMMAND-LINE MODE + + +16.1. How do I use the name of the current file in the command mode or an + ex command line? + +In the command line, the '%' character represents the name of the current +file. In some commands, you have to use expand("%") to get the filename: + + :!perl % + +For more information, read + + :help :_% + :help cmdline-special + :help expand() + + +16.2. How do I edit the text in the Vim command-line effectively? + +You can use the command-line window for editing Vim command-line text. To +open the Vim command-line window use the "q:" command in normal mode. In +command-line mode, use the CTRL-F key. In this window, the command line +history will be displayed. You can use normal Vim keys/commands to edit any +previous/new command line. To execute a command line, press the +enter/return key. + +In a similar vain, the search history can be edited with "q/" and "q?" +commands. + +For more information, read + + :help cmdline-window + + +16.3. How do I switch from Vi mode to Ex mode? + +You can use the Q command to switch from Vi mode to Ex mode. To switch from +Ex mode back to the Vi mode, use the :vi command. + +For more information, read + + :help Q + :help gQ + :help Ex-mode + :help :vi + + +16.4. How do I copy the output from an ex-command into a buffer? + +To copy the output from an ex-command into a buffer, you have to first get +the command output into a register. You can use the ":redir" command to get +the output into a register. For example, + + :redir @a + :g/HelloWord/p + :redir END + +Now the register 'a' will contain the output from the ex command +"g/HelloWord/p". Now you can paste the contents of the register 'a' into a +buffer. You can also send or append the output of an ex-command into a file +using the 'redir' command. + +You can prefix the ":global" command with ":silent", to avoid having the +lines printed to the screen. + +To redirect the output from an ex-command to a file, you can use the +following set of commands: + + :redir > myfile + :g/HelloWord/p + :redir END + +For more information, read + + :help :redir + :help :silent + + +16.5. When I press the tab key to complete the name of a file in the + command mode, if there are more than one matching file names, then + Vim completes the first matching file name and displays a list of all + matching filenames. How do I configure Vim to only display the list + of all the matching filenames and not complete the first one? + +You can modify the 'wildmode' option to configure the way Vim completes +filenames in the command mode. In this case, you can set the 'wildmode' +option to 'list': + + :set wildmode=list + +For more information, read + + :help 'wildmode' + + +16.6. How do I copy text from a buffer to the command line and from the + command line to a buffer? + +To copy text from a buffer to the command line, after yanking the text from +the buffer, use Ctrl-R 0 in the command line to paste the text. You can +also yank the text to a specific register and use CTRL-R <register> to +paste the text to the command line. You can use CTRL-R CTRL-W to paste the +word under the cursor in the command line. + +To copy text from the command line into a buffer, you can paste the +contents of the : register using the ":p command. The most recently +executed command line is stored in the : register. + +Another approach for copying and pasting text to and from the command line +is to open the command line window using q: from normal mode or CTRL-F from +the command-line mode. In the command line window you can use all the Vim +commands to edit the command line. + +For more information, read + + :help c_CTRL-R + :help quote_: + :help cmdline-window + + +16.7. How do I put a command onto the command history without executing it? + +To put a command onto the command history without executing it, press the +<Esc> key to cancel the command. + +For more information, read + + :help c_<Esc> + + +16.8. How do I increase the height of the command-line? + +You can increase the height of the command-line by changing the 'cmdheight' +option: + + :set cmdheight=2 + +For more information, read + + :help 'cmdheight' + :help hit-enter + :help 05.7 + + +============================================================================= + +SECTION 17 - VIMINFO + + +17.1. When I invoke Vim, I get error messages about illegal characters in + the viminfo file. What should I do to get rid of these messages? + +You can remove the $HOME/.viminfo or the $HOME/_viminfo file to get rid of +these error messages. + +For more information, read + + :help viminfo-errors + :help viminfo-file-name + :help viminfo + :help 21.3 + + +17.2. How do I disable the viminfo feature? + +By default, the viminfo feature is disabled. If the viminfo feature is +enabled by a system-wide vimrc file, then you can disable the viminfo +feature by setting the 'viminfo' option to an empty string in your local +.vimrc file: + + :set viminfo="" + +For more information, read + + :help 'viminfo' + + +17.3. How do I save and use Vim marks across Vim sessions? + +You can save and restore Vim marks across Vim sessions using the viminfo +file. To use the viminfo file, make sure the 'viminfo' option is not empty. +To save and restore Vim marks, the 'viminfo' option should not contain the +'f' flag or should have a value greater than zero for the 'f' option. + +For more information, read + + :help 21.3 + :help viminfo + :help 'viminfo' + :help :wviminfo + :help :rviminfo + + +============================================================================= + +SECTION 18 - REMOTE EDITING + + +18.1. How do I open a file with existing instance of gvim? What happened to + the Vim 5.x OpenWithVim.exe and SendToVim.exe files? + +Starting with Vim6, the OLE version of OpenWithVim.exe and SendToVim.exe +Vim utilities are replaced by the new client-server feature. To open the +file j.txt with an existing instance of Gvim (MyVim), use: + + $ gvim --servername MyVim --remote-silent j.txt + +To list the server names of all the currently running Vim instances, use + + $ vim --serverlist + +To get more information about client-server feature, read + + :help client-server + + +18.2. How do I send a command to a Vim server to write all buffers to disk? + +You can use the Vim remote server functionality to do this: + + $ gvim --servername myVIM --remote-send "<C-\><C-N>:wall<CR>" + +For more information, read + + :help client-server + :help CTRL-\_CTRL-N + :help :wall + + +18.3. Where can I get the documentation about the Vim remote server + functionality? + +You can get more information about the Vim remote server functionality by +reading + + :help client-server + + +============================================================================= + +SECTION 19 - OPTIONS + + +19.1. How do I configure Vim in a simple way? + +You can use the ":options" command to open the Vim option window: + + :options + +This window can be used for viewing and setting all the options. + +For more information, read + + :help :options + + +19.2. How do I toggle the value of an option? + +You can prefix the option with "inv" to toggle the value of the option: + + :set invignorecase + :set invhlsearch + +You can also suffix the option with "!" to toggle the value: + + :set ignorecase! + :set hlsearch! + +For more information, read + + :help set-option + + +19.3. How do I set an option that affects only the current buffer/window? + +Some of the Vim options can have a local or global value. A local value +applies only to a specific buffer or window. A global value applies to all +the buffers or windows. + +When a Vim option is modified using the ":set" command, both the global and +local values for the option are changed. You can use the ":setlocal" +command to modify only the local value for the option and the ":setglobal" +command to modify only the global value. + +You can use the ":setlocal" command to set an option that will affect only +the current file/buffer: + + :setlocal textwidth=70 + +Note that not all options can have a local value. You can use ":setlocal" +command to set an option locally to a buffer/window only if the option is +allowed to have a local value. + +You can also use the following command to set a option locally: + + :let &l:{option-name} = <value> + +For more information, read + + :help :setlocal + :help local-options + + +19.4. How do I use space characters for a Vim option value? + +To use space characters in a Vim option value, you have to escape the space +character. For example: + + :set tags=tags\ /usr/tags + +For more information, read + + :help option-backslash + + +19.5. Can I add (embed) Vim option settings to the contents of a file? + +You can use modelines to add Vim option settings to the contents of a file. +For example, in a C file, you can add the following line to the top or the +bottom of the file: + + /* vim:sw=4: */ + +This will set the 'shiftwidth' option to 4, when editing that C file. +For this to work, the 'modeline' option should be set. By default, the +'modeline' option is not set, for security reasons, in Debian. The +'modelines' settings specifies the number of lines that will be checked for +the Vim set commands. + +For more information, read + + :help 21.6 + :help modeline + :help auto-setting + :help 'modeline' + :help 'modelines' + + +19.6. How do I display the line numbers of all the lines in a file? + +You can set the 'number' option to display the line numbers for all the +lines. + + :set number + +For more information, read + + :help 'number' + + +19.7. How do I change the width of the line numbers displayed using the + "number" option? + +The width used for displaying the line numbers for the 'number' option is +hard-coded in Vim. It is not possible to change this width by setting some +option. + +The request and the patch to add an option to change the number of columns +used for the 'number' option is in the Vim todo list: + + "Add an option to set the width of the 'number' column. Eight + positions is often more than needed. Or adjust the width to the length + of the file? + Add patch that adds 'numberlen' option. (James Harvey) + Other patch with min and max from Emmanuel Renieris (2002 Jul 24) + Other patch without an option by Gilles Roy (2002 Jul 25)" + + +19.8. How do I display (view) all the invisible characters like space, tabs + and newlines in a file? + +You can set the 'list' option to see all the invisible characters in your +file. + + :set list + +With this option set, you can view space characters, tabs, newlines, +trailing space characters and wrapped lines. + +To not display the invisible characters (which is the default), you have to +reset the 'list' option: + + :set nolist + (or) + :set list! + +The ":set list!" command will toggle the current setting of the boolean +'list' option. + +You can modify the 'listchars' option to configure how and which invisible +characters are displayed. For example, with the following command all the +trailing space characters will be displayed with a '.' character. + + :set listchars=trail:. + +For more information, read + + :help 'listchars' + :help 'list' + + +19.9. How do I configure Vim to always display the current line and column + number? + +You can set the 'ruler' option to display current column and line number in +the status line: + + :set ruler + +For more information, read + + :help 'ruler' + + +19.10. How do I display the current Vim mode? + +You can set the 'showmode' option to display the current Vim mode. In +Insert, Replace and Visual modes, Vim will display the current mode on the +last line. + + :set showmode + +For more information, read + + :help 'showmode' + + +19.11. How do I configure Vim to show pending/partial commands on the + status line? + +You can set the 'showcmd' option to display pending/partial commands in the +status line: + + :set showcmd + +For more information, read + + :help 'showcmd' + + +19.12. How do I configure the Vim status line to display different + settings/values? + +You can set the 'statusline' option to display different values/settings in +the Vim status line. + +For more information, read + + :help 'statusline' + :help 'laststatus' + :help 'rulerformat' + :help 'ruler' + + +19.13. How do I configure Vim to display status line always? + +You can set the 'laststatus' option to 2 to display the status line always. + + :set laststatus=2 + +For more information, read + + :help 'laststatus' + + +19.14. How do I make a Vim setting persistent across different Vim + invocations/instances/sessions? + +To make a Vim option setting persistent across different Vim instances, add +your setting to the .vimrc or .gvimrc file. You can also use the ":mkvimrc" +command to generate a vimrc file for the current settings. + +For more information, read + + :help save-settings + :help vimrc + :help gvimrc + :help vimrc-intro + :help :mkvimrc + :help initialization + + +19.15. Why do I hear a beep (why does my window flash) about 1 second after + I hit the Escape key? + +This is normal behavior. If your window flashes, then you've got the visual +bell on. Otherwise, you should hear a beep. + +Vim needs a timeout to tell the difference between a simple escape and, +say, a cursor key sequence. When you press a key in normal mode (and even +in insert mode) and that key is the beginning of a mapping, Vim waits a +certain amount of time to see if the rest of the mapping sequence follows. +If the mapping sequence is completed before a given timeout period, the +mapping for that sequence of keys is applied. If you interrupt the mapping, +the normal actions associated with the keys are executed. + +For example, if you have a mapping defined as ":imap vvv Vim is great!!" +and you type "vvv" quickly, the "Vim is great!!" will be inserted into your +text. But if you type "vv v" then that is what will put into your text. +This is also true if you type "vvv" too slowly where "too slowly" is longer +than the value for the timeout option. Setting the timeout option to a +larger value can help alleviate problems that appear when using function +keys over a slow line. + +For more information, read + + :help ttimeout + + +19.16. How do I make the 'c' and 's' commands display a '$' instead of + deleting the characters I'm changing? + +To make the 'c' and 's' commands display a '$' instead of deleting the +characters, add the $ flag to the 'cpoptions' option: + + :set cpoptions+=$ + +For more information, read + + :help 'cpoptions' + + +19.17. How do I remove more than one flag using a single ":set" command + from a Vim option? + +You can remove more than one flag from a Vim option using a single ":set" +command, by specifying the flags in exactly the same order as they appear +in the option. For example, if you use the following command to remove the +'t' and 'n' flags from the 'formatoptions' option: + + :set formatoptions-=tn + +The 't' and 'n' flags will be removed from the 'formatoptions' option, only +if the 'formatoptions' option contains these flags in this order: 'tn'. +Otherwise, it will not remove the flags. To avoid this problem, you can +remove the flags one by one: + + :set formatoptions-=t formatoptions-=n + +For more information, read + + :help :set-= + + +============================================================================= + +SECTION 20 - MAPPING KEYS + + +20.1. How do I know what a key is mapped to? + +To see what a key is mapped to, use the following commands: + + :map <key> + :map! <key> + +You can also check the mappings in a particular mode using one of the +":cmap", ":nmap", ":vmap", ":imap", ":omap", etc commands. + +For more information, read + + :help map-listing + :help map-overview + + +20.2. How do list all the user-defined key mappings? + +You can list all the user-defined key mappings using: + + :map + +For more information, read + + :help map-listing + + +20.3. How do I unmap a previously mapped key? + +You can unmap a previously mapped key using the ":unmap" command: + + :unmap <key> + :unmap! <key> + +For mode specific mappings, you can use one of the +":nunmap/:vunmap/:ounmap/:iunmap/:lunmap/:cunmap" commands. + +The following command will fail to unmap a buffer-local mapped key: + + :unmap <key> + +To unmap a buffer-local mapped key, you have to use the <buffer> keyword in +the unmap command: + + :unmap <buffer> <key> + :unmap! <buffer> <key> + +For more information, read + + :help :unmap + :help map-modes + :help map-local + :help 'mapleader' + + +20.4. I am not able to create a mapping for the <xxx> key. What is wrong? + +First make sure that the key is passed to Vim. In insert mode, press CTRL-V +followed by the desired key. You should see the keycode corresponding to +the key . If you do see the keycode, then you can create a mapping for the +key using the following command: + + :map <C-V><xxx> <your_command_to_be_mapped> + +For more information, read + + :help map-keys-fails + :help :map-special-keys + :help key-codes + + +20.5. How do I map the numeric keypad keys? + +First make sure that the numeric keypad keys are passed to Vim. Next, you +can use the following command to map the numeric keypad keys: + + :map <kSomething> <your_command> + +where, <kSomething> can be kHome, kEnd, kPageUp, kPageDown, kPlus, kMinus, +kDivide, kMultiply, kEnter, etc. + +For more information, read + + :help key-codes + :help terminal-options + + +20.6. How do I create a mapping that works only in visual mode? + +You can create mappings that work only in specific mode (normal, command, +insert, visual, etc). To create a mapping that works only in the visual +mode, use the ":vmap" command: + + :vmap <F3> <your mapping here> + +For more information, read + + :help :vmap + :help map-modes + :help 40.1 + + +20.7. In a Vim script, how do I know which keys to use for my mappings, so + that the mapped key will not collide with an already used key? + +Vim uses most of the keys in the keyboard. You can use the <leader> prefix +in maps to define keys which will not overlap with Vim keys. For example: + + :map <leader>S <C-W>s + :map <leader>j <C-W>j + :map <leader>k <C-W>k + +where by default <leader> gets substituted with a backslash (\), so the +user would enter + + \s + \j + \k + +to invoke the above map commands. The user can change the mapleader +variable to be whatever they wanted: + + :let mapleader = "," + +When writing a plugin or other script, more often than not, it is advisable +to use :noremap instead of :map to avoid side effects from user defined +mappings. + +For more information, read + + :help <Leader> + :help <LocalLeader> + :help write-plugin + + +20.8. How do I map the escape key? + +You can map the Escape key to some other key using the ":map" command. For +example, the following command maps the escape key to CTRL-O. + + :map <C-O> <Esc> + + +20.9. How do I map a key to perform nothing? + +You can map a key to <Nop> to perform nothing when the key is pressed. For +example, with the following mappings, the <F7> key will do nothing when +pressed. + + :map <F7> <Nop> + :map! <F7> <Nop> + +For more information, read + + :help <Nop> + :help :map + :help :map! + :help map-modes + + +20.10. I want to use the Tab key to indent a block of text and Shift-Tab + key to unindent a block of text. How do I map the keys to do this? + This behavior is similar to textpad, visual studio, etc. + +Use the following mapping: + + :inoremap <S-Tab> <C-O><LT><LT> + :nnoremap <Tab> >> + :nnoremap <S-Tab> <LT><LT> + :vnoremap <Tab> > + :vnoremap <S-Tab> <LT> + +Note that, the <S-Tab> mapping will work only if Vim receives the correct +key sequence. This is mostly the case with GUI Vim. + +For more information, read + + :help :inoremap + :help :nnoremap + :help :vnoremap + :help <S-Tab> + :help i_CTRL-O + :help >> + :help << + :help <LT> + + +20.11. In my mappings the special characters like <CR> are not recognized. + How can I configure Vim to recognize special characters? + +Check the value of the 'cpoptions' option: + + :set cpoptions? + +If this option contains the '<' flag, then special characters will not be +recognized in mappings. Remove the '<' flag from 'cpoptions' option: + + :set cpo-=< + +Also, check the value of the 'compatible' option: + + :se compatible? + +The 'compatible' option must be reset: + + :se nocompatible + +For more information, read + + :help 'cpoptions' + :help 'compatible' + + +20.12. How do I use the '|' to separate multiple commands in a map? + +You can escape the '|' character using backslash (\) to use '|' in a map. + + :map _l :!ls \| more<CR> + +You can also try the following command: + + :map _l :!ls <bar> more<CR> + +There are also other ways to do this. + +For more information, read + + :help map_bar + + +20.13. If I have a mapping/abbreviation whose ending is the beginning of + another mapping/abbreviation, how do I keep the first from expanding + into the second one? + +Instead of using the ":map lhs rhs" command, use the ":noremap lhs rhs" +command. For abbreviations, use "noreabbrev lhs rhs". The "nore" prefix +prevents the mapping or abbreviation from being expanded again. + +For more information, read + + :help :noremap + :help :noreabbrev + + +20.14. Why does it take a second or more for Vim to process a key, + sometimes when I press a key? + +Make sure you have not defined a mapping for this key using the following +command: + + :map <key> + +If a mapping is defined for this key and the mapped key contains more than +one character, then Vim will wait for the next character to be pressed to +determine whether it is the mapped key or not. For example, if you have +mapped "ab", then if you press "a", Vim will wait for the next key to be +pressed. If the next key is "b", Vim will execute the mapped sequence. +Otherwise, Vim will proceed with the normal processing of "a" followed by +the next key. If the 'timeout' option is set (which is the default), then +Vim will timeout after waiting for the period specified with the +'timeoutlen' option (default is 1 second). + +For more information, read + + :help map-typing + :help 'timeoutlen' + :help 'ttimeoutlen' + :help 'timeout' + :help 'ttimeout' + :help vt100-cursor-keys + :help slow-fast-terminal + + +20.15. How do I map a key to run an external command using a visually + selected text? + +You can the ":vmap" command to map a key in the visual mode. In the mapped +command sequence, you have to first yank the text. The yanked text is +available in the '"' register. Now, you can use the contents of this +register to run the external command. For example, to run the external +command "perldoc" on a visually selected text, you can use the following +mapping: + + :vmap <F7> y:!exec "!perldoc '" . @" . "'"<CR> + +If you want the mapping to work in the visual mode, but not with the +highlighted text, you can use the following command: + + :vmap <F7> :<C-U>!perldoc <cword><CR> + +The above mapping will use the word under the cursor instead of the +highlighted text. Note the use of the <C-U> before invoking the "perldoc" +external command. The <C-U> is used to erase the range of text selected in +the visual mode and displayed on the command line. If the visual range is +not removed using <C-U>, then the output from the external command will +replace the visually selected text. + +For more information, read + + :help :vmap + :help quote_quote + :help let-register + :help c_CTRL-U + :help :!cmd + + +20.16. How do I map the Ctrl-I key while still retaining the functionality + of the <Tab> key? + +The Ctrl-I key and the <Tab> key produce the same keycode, so Vim cannot +distinguish between the Ctrl-I and the <Tab> key. When you map the Ctrl-I +key, the <Tab> key is also mapped (and vice versa). The same restriction +applies for the Ctrl-[ key and the <Esc> key. + +For more information, read + + :help keycodes + + +============================================================================= + +SECTION 21 - ABBREVIATIONS + + +21.1. How do I auto correct misspelled words? + +You can auto correct misspelled words using abbreviations. For example, the +following abbreviation can be used to correct "teh" with "the": + + :abbreviate teh the + +Vim supports abbreviations in insert mode, replace mode and command-line +mode. + +For more information, read + + :help 24.7 + :help abbreviations + :help Q_ab + + +21.2. How do I create multi-line abbreviations? + +You can create multi-line abbreviations by embedding the "<CR>" +key code in the text: + + iabbrev #c --------------<CR>-- Date:<CR>--<CR>--------- + +With the above abbreviation, when you type #c, it will be expanded to +the following text: + +-------------- +-- Date: +-- +--------- + +For more information, read + + :help abbreviations + + +21.3. When my abbreviations are expanded, an additional space character is + added at the end of the expanded text. How do I avoid this character? + +To avoid an additional space character at the end of the expanded text, you +can expand the abbreviation by pressing the CTRL-] key. The abbreviation +will be expanded without adding a space character at the end. + +Another alternative is to use the following function and command: + +function! Eatchar(pat) + let c = nr2char(getchar()) + return (c =~ a:pat) ? '' : c +endfunction +command! -nargs=+ Iabbr execute "iabbr" <q-args> . "<C-R>=Eatchar('\\s')<CR>" + +Now, define your abbreviations using the new "Iabbr" command instead of the +builtin "iabbrev" command. With this command, after expanding the +abbreviated text, the next typed space character will be discarded. + +For more information, read + + :help abbreviations + + +21.4. How do I insert the current date/time stamp into the file? + +You can use the strftime() function to insert the current data/time stamp +in a file. For example, you can use the following abbreviation: + + iabbrev dts <C-R>=strftime("%y/%m/%d %H:%M")<CR> + +With this abbreviation, when you type dts in insert mode, it will be +expanded to the date/time stamp. + +Some other forms of the above abbreviation are listed below: + + iabbrev mdyl <C-R>=strftime("%a %d %b %Y")<CR> + iabbrev mdys <C-R>=strftime("%y%m%d")<CR> + iabbrev mdyc <C-R>=strftime("%c")<CR> + iabbrev hml <C-R>=strftime("%d/%m/%y %H:%M:%S")<CR> + iabbrev hms <C-R>=strftime("%H:%M:%S")<CR> + +For more information, read + + :help strftime() + :help i_CTRL-R + + +21.5. How do I prevent an abbreviation from expanding in insert mode? + +You can prevent an abbreviation from expanding in insert mode by typing +CTRL-V before the character after the abrreviated word. + +For more information, read + + :help abbreviations + + +============================================================================= + +SECTION 22 - RECORD AND PLAYBACK + + +22.1. How do I repeat an editing operation (insertion, deletion, paste, + etc)? + +You can repeat the last editing operation using the '.' command. This will +repeat the last simple change like a insert, delete, change, paste, etc. + +For more information, read + + :help 04.3 + :help single-repeat + :help Q_re + + +22.2. How I record and repeat a set of key sequences? + +You can use the 'q' command in normal mode to record a set of key sequences +and store it in a register. For example, in the normal mode you can press q +followed by a register name {0-9a-bA-Z"} to start the recording. To +end/stop the recording press q again. You can playback/repeat the recorded +key sequences by pressing @ followed by the register name. e.g. @a. + +Another approach is to start Vim with the "-w" command-line argument. + + $ vim -w <file_name> + +Vim will record all the characters typed in the session in the +specified file "file_name". You can use the recorded file with the "-s" +command line argument to play it back: + + $ vim -s <file_name> + +For more information, read + + :help 10.1 + :help recording + :help -w + :help -s + + +22.3. How do I edit/modify a recorded set of key sequences? + +The recorded key sequences are stored in a register. You can paste the +contents of the register into a Vim buffer, edit the pasted text and again +yank the text into the register. You can also use the ":let" command to +modify the register. For example: + + :let @a = "iHello World\<Esc>" + +For more information, read + + :help recording + :help 10.1 + :help let-register + :help <> + :help 'cpoptions' + + +22.4. How do I write recorded key sequences to a file? + +The recorded key sequences are stored in a register. You can paste the +contents of the register into a Vim buffer. Now you can save the buffer +into a file. You can also modify the pasted text and again yank into the +register to modify the recorded key sequence. For example, if you record a +set of key sequences using qa ..... q. The recorded key sequences are +stored in the register 'a'. You can paste the contents of register 'a' +using "ap. + +For more information, read + + :help recording + :help 10.1 + + +22.5. I am using register 0 to record my key sequences (i.e. q0 .... q). + In the recorded key sequences, I am yanking some text. After the + first replay of the recorded key sequence, I am no longer able to + play it back. + +Register 0 contains the text from the last yank operation. In your recorded +key sequence, when the yank is performed, register 0 is overwritten with +the yanked text. So your recording stored in register 0 is lost. You have +to use some other register. + +For more information, read + + :help registers + + +============================================================================= + +SECTION 23 - AUTOCOMMANDS + + +23.1. How do I execute a command when I try to modify a read-only file? + +You can use the FileChangedRO autocommand event to execute a command when a +read-only file modified. For example, you can use this event to checkout a +read-only file: + + :autocmd FileChangedRO * call MyCheckoutFunction() + +For more information, read + + :help FileChangedRO + + +23.2. How do I execute a command every time when entering a buffer? + +You can use the BufEnter autocommand event to execute a command every time +when entering a buffer. For example: + + :autocmd BufEnter *.c set formatoptions=croqt + +For more information, read + + :help BufEnter + + +23.3. How do I execute a command every time when entering a window? + +You can use the WinEnter autocommand event to execute a command every time +when entering a window. For example: + + :autocmd WinEnter *.c call MyFunction() + +For more information, read + + :help WinEnter + + +23.4. From an autocmd, how can I determine the name of the file or the + buffer number for which the autocommand is executed? + +You can use the special words <afile> or <abuf> in an autocmd to get the +name of the file or the buffer number for which the autocommand is +executed. + +For more information, read + + :help :<afile> + :help :<abuf> + :help :<amatch> + + +23.5. How do I automatically save all the changed buffers whenever Vim + loses focus? + +You can define an autocommand for the FocusLost event which will save all +the modified buffers whenever Vim loses focus: + + :autocmd FocusLost * wall + +For more information, read + + :help FocusLost + :help :wall + + +23.6. How do I execute/run a function when Vim exits to do some cleanup? + +You can use VimLeave autocmd event to execute a function just before Vim +exists. For example, + + :autocmd VimLeave * call MyCleanupFunction() + +For more information, read + + :help VimLeave + + +============================================================================= + +SECTION 24 - SYNTAX HIGHLIGHT + + +24.1. How do I turn off/on syntax highlighting? + +By default, the Vim syntax highlighting is turned off. To enable the syntax +highlighting, you can use one of the following commands: + + :syntax enable + + or + + :syntax on + +To disable the syntax highlighting, you can use the following command: + + :syntax off + +For more information, read + + :help 06.1 + :help 06.4 + :help :syntax-enable + :help :syntax-on + :help :syn-clear + + +24.2. How do I change the background and foreground colors used by Vim? + +Vim uses the "Normal" highlight group for the background and foreground +colors. To change the foreground/background colors, you have to modify the +"Normal" highlight group. For example, to set the background color to blue +and foreground color to white, you can use + + :highlight Normal ctermbg=blue ctermfg=white guibg=blue guifg=white + +If you are using the Motif or the Athena version of the GUI Vim, then you +can modify the foreground and background resource names in the .Xdefaults +files to change the colors: + + Vim.foreground: Black + Vim.backround: Wheat + +You can also use the "-foreground" and "-background" command-line arguments +to specify the foreground and background colors. These arguments are +supported only in the Motif or Athena versions: + + $ gvim -foreground Black -background Wheat + +For more information, read + + :help :highlight + :help .Xdefaults + :help -gui + + +24.3. How do I change the highlight colors to suit a dark/light background? + +You can set the 'background' option to either 'dark' or 'light' to change +the highlight colors to suit a dark/light background: + + :set background=dark + +For more information, read + + :help 'background' + :help 6.2 + + +24.4. How do I change the color of the line numbers displayed when the + ":set number" command is used? + +The line numbers displayed use the LineNr highlighting group. To display +the current colors used, use + + :hi LineNr + +To change the color modify the LineNr highlight group. For example: + + :hi linenr guifg=red guibg=black + +This will give red numbers on a black background in GVIM. + +For more information, read + + :help :highlight + + +24.5. How do I change the background color used for a Visually selected + block? + +You can modify the 'Visual' highlight group to change the color used for a +visually selected block: + + :highlight Visual guibg=red + +For more information, read + + :help :highlight + :help hl-Visual + + +24.6. How do I highlight the special characters (tabs, trailing spaces, end + of line, etc) displayed by the 'list' option? + +You can modify the "NonText" and "SpecialKey" highlight groups to highlight +the special characters displayed by the 'list' option: + + :highlight NonText guibg=red + :highlight SpecialKey guibg=green + +The "NonText" highlighting group is used for "eol", "extends" and +"precedes" settings in the "listchars" option. The "SpecialKey" +highlighting group is used for the "tab" and "trail" settings. + +For more information, read + + :help 'listchars' + :help hl-NonText + :help hl-SpecialKey + + +24.7. How do I specify a colorscheme in my .vimrc/.gvimrc file, so that Vim + uses the specified colorscheme everytime? + +You can specify the color scheme using the ":colorscheme" command in your +.vimrc or .gvimrc file: + + colorschme evening + +For more information, read + + :help :colorscheme + + +24.8. Vim syntax highlighting is broken. When I am editing a file, some + parts of the file is not syntax highlighted or syntax highlighted + incorrectly. + +Vim doesn't read the whole file to parse the text for syntax highlighting. +It starts parsing wherever you are viewing the file. That saves a lot of +time, but sometimes the colors are wrong. A simple fix is refreshing the +screen using the CTRL-L key. Or scroll back a bit and then forward again. +You can also use the command: + + :syntax sync fromstart + +Note that this might considerably slow down the screen refreshing. + +For more information, read + + :help :syn-sync + :help :syn-sync-first + + +24.9. Is there a built-in function to syntax-highlight the corresponding + matching bracket? + +No. Vim doesn't support syntax-highlighting matching brackets. You can try +using the plugin developed by Charles Campbell: + + http://vim.sourceforge.net/tips/tip.php?tip_id=177 + +You can jump to a matching bracket using the '%' key. You can set the +'showmatch' option to temporarily jump to a matching bracket when in insert +mode. + +For more information, read + + :help % + :help 'showmatch' + :help 'matchtime' + :help 'matchpairs' + + +24.10. How do I turn off the C comment syntax highlighting? + +You can use the following command to turn off C comment syntax +highlighting: + + :highlight clear comment + +For more information, read + + :help c-syntax + + +24.11. How do I add my own syntax extensions to the standard syntax files + supplied with Vim? + +You should not modify the syntax files supplied with Vim to add your +extensions. When you install the next version of Vim, you will lose your +changes. Instead you should create a file under the ~/.vim/after/syntax +directory with the same name as the original syntax file and add your +additions to this file. + +For more information, read + + :help mysyntaxfile-add + :help 'runtimepath' + + +24.12. How do I replace a standard syntax file that comes with the Vim + distribution with my own syntax file? + +You can replace a standary syntax file that comes with the Vim distribution +by creating a file with the same name as the original syntax file and +placing it in the vim runtime syntax (~/.vim/syntax) directory. For +example, to replace the c.vim syntax file in a Unix system, place the new +c.vim in the ~/.vim/syntax directory. In a MS-Windows system, place the new +syntax file in the $HOME/vimfiles/syntax or $VIM/vimfiles/syntax directory. + +For more information, read + + :help mysyntaxfile-replace + :help 44.11 + :help mysyntaxfile + + +24.13. How do I highlight all the characters after a particular column? + +You can use the ":match" command to highlight all the characters after a +particular column: + + :match Todo '\%>75v.\+' + +This will highlight all the characters after the 75th column. + +For more information, read + + :help :match + :help /\%v + :help /\+ + :help /. + + +24.14. How do I convert a source file (.c, .h, etc) with the Vim syntax + highlighting into a HTML file? + +You can use the 2html.vim script to convert a source file into a HTML file +with the Vim syntax highlighting. Use the following command: + + :runtime! syntax/2html.vim + +For more information, read + + :help convert-to-HTML + + +24.15. How do I list the definition of all the current highlight groups? + +You can list the definition of all the current highlight groups using the +":highlight" (without any arguments) ex command. + +For more information, read + + :help :highlight + + +============================================================================= + +SECTION 25 - VIM SCRIPT WRITING + + +25.1. How do I list the names of all the scripts sourced by Vim? + +You can use the ":scriptnames" command to list the names of all the scripts +sourced by Vim: + + :scriptnames + +For more information, read + + :help :scriptnames + + +25.2. How do I debug Vim scripts? + +Vim has built-in support for a primitive debugger to debug Vim plugins and +scripts. Using this debugger you can set breakpoints and step through the +plugin functions. + +For more information, read + + :help debug-scripts + :help -D + + +25.3. How do I locate the script/plugin which sets a Vim option? + +You can use the ":verbose" command to locate the plugin/script which last +modified a Vim option. For example: + + :verbose set textwidth? + +For more information, read + + :help :set-verbose + :help :verbose + + +25.4. I am getting some error/informational messages from Vim (possibly + when running a script), the messages are cleared immediately. How do + I display the messages again? + +You can use the ":messages" command to display the previous messages. + + :messages + +For more information, read + + :help :messages + :help :echoerr + :help :echomsg + :help message-history + + +25.5. How do I save and restore a plugin specific information across Vim + invocations? + +Vim will save and restore global variables that start with an uppercase +letter and don't contain a lower case letter. For this to work, the +'viminfo' option must contain the '!' flag. Vim will store the variables in +the viminfo file. + +For more information, read + + :help 'viminfo' + :help viminfo-file + :help variables + + +25.6. How do I start insert mode from a Vim function? + +You can use the ":startinsert" command to start the insert mode from inside +a Vim function. + +For more information, read + + :help :startinsert + + +25.7. How do I change the cursor position from within a Vim function? + +You can use the cursor() function to position the cursor. + + call cursor(lnum, col) + +You can also use the following command to change the cursor position: + + exe "normal! " . lnum . "G" . col . "|" + +For more information, read + + :help cursor() + :help bar + + +25.8. How do I check the value of an environment variable in the .vimrc + file? + +You can use prefix the environment variable name with the '$' character to +use it from a Vim script/function. You can refer to the value of an +environment variable using the $env_var syntax: + + if $EDITOR == 'vi' + endif + +For more information, read + + :help expr-env + + +25.9. How do I check whether an environment variable is set or not from a + Vim function? + +You can use the exists() function to check for the existence of a +environment variable. + + if exists("$MY_ENV_VAR") + endif + +For more information, read + + :help exists() + :help expr-env + + +25.10. How do I call/use the Vim built-in functions? + +You can use the ":call" command to invoke a Vim built-in function: + + :call cursor(10,20) + +You can use the ":echo" command to echo the value returned by a function: + + :echo char2nr('a') + +You can use the ":let" command to assign the value returned by a function +to a variable: + + :let a = getline('.') + +To store the return value from a function into a Vim register, you can use +the following command: + + :let @a = system('ls') + +The above command will store the return value from the 'ls' command into +the register 'a'. + +For more information, read + + :help :call + :help :echo + :help :let + :help :let-register + :help user-functions + :help usr_41.txt + + +25.11. I am using some normal mode commands in my Vim script. How do I + avoid using the user-defined mappings for these normal mode commands + and use the standard Vim functionality for these normal mode + commands? + +You can use the "normal!" command in your script to invoke a normal-mode +command. This will use the standard functionality of the normal mode +command and will not use the user-defined mapping. + +For more information, read + + :help :normal + + +25.12. How do I get the current visually selected text into a Vim variable + or register? + +You can get the current visually selected text into a Vim variable by +yanking the text into Vim register and then assigning the contents of the +register into the variable: + + :normal! gvy + :let myvar = @" + +The above command copies the visually selected text into the variable +"myvar". + +You can also use the command: + + :normal! gv"*y + +In the above command, gv reselects the last visually selected text and the +rest of the command copies the selected text into the * (clipboard) +register. Alternatively, you can set the 'a' flag in the 'guioptions' +option to automatically copy a visually selected text into the * register. +To do this as part of a visual map, you can use a command similar to the +one shown below: + + :vmap <F3> "*y:call ... + +For more information, read + + :help gv + :help :normal + :help let-@ + :help quotestar + :help clipboard + :help registers + + +25.13. I have some text in a Vim variable 'myvar'. I would like to use this + variable in a ":s" substitute command to replace a text 'mytext'. + How do I do this? + +You can use the 'execute' command to evaluate the variable: + + :execute '%s/mytext/' . myvar . '/' + +For more information, read + + :help :execute + +You can also use "\=" in the substitute command to evaluate the variable: + + :%s/mytext/\=myvar/ + +For more information, read + + :help sub-replace-special + + +25.14. A Vim variable (bno) contains a buffer number. How do I use this + variable to open the corresponding buffer? + +The :buffer command will not accept a variable name. It accepts only a +buffer number or buffer name. You have to use the ":execute" command to +evaluate the variable into the corresponding value. For example: + + :execute "buffer " . bno + +For more information, read + + :help :execute + + +25.15. How do I store the value of a Vim option into a Vim variable? + +You can prefix the option name with the '&' character and assign the option +value to a Vim variable using the "let" command. For example, to store the +value of the 'textwidth' option into the Vim variable "old_tw", you can use +the following command: + + :let old_tw = &tw + +To do the opposite, to set the 'textwidth' option with the value stored in +the 'old_tw' variable, you can use the following command: + + :let &tw = old_tw + +For more information, read + + :help expr-option + :help let-option + + +25.16. I have copied and inserted some text into a buffer from a Vim + function. How do I indent the inserted text from the Vim function? + +You can use the following command to format the just inserted text: + + :normal '[='] + +For more information, read + + :help '[ + :help '] + :help = + :help :normal + + +25.17. How do I get the character under the cursor from a Vim script? + +You can use the getline() function and use string index [] to get the +character: + + :echo getline(".")[col(".") - 1] + +In the above command, getline(".") returns the text in the current line. +The indexing of the string starts at zero, and you can get a single +character in a string by its index with the "string[index]" notation. The +col(".") returns the column of the cursor position; the adjustment is to +get the right character of the string. + +Alternatively, you can use the following sequence of commands to get the +character under the cursor: + + normal! vy + let ch=@" + +Note that the above commands will change the '< and '> marks. + +For more information, read + + :help getline() + :help col() + :help expr-[] + + +25.18. How do I get the name of the current file without the extension? + +You can get the name of the current file without the extension using: + + :echo expand("%:r") + +With some commands, you can use the file name modifiers directly: + + :cd %:p:h + :!gcc -o %:r.o % + +For more information, read + + :help filename-modifiers + :help expand() + :help cmdline-special + :help fnamemodify() + + +25.19. How do I get the basename of the current file? + +You can use the :t filename modifier to get the basename of the current +file: + + :echo expand("%:t") + +For more information, read + + :help filename-modifiers + + +25.20. How do I get the output from a Vim function into the current buffer? + +You can insert the return value from a function using the following command +in insert mode: + + <C-R>=MyFunc() + +Note that this will only insert the return value of the function. + +For more information, read + + :help i_CTRL-R + :help i_CTRL-R_CTRL-R + :help i_CTRL-R_CTRL-O + :help expression + + +25.21. How do I call external programs from a Vim function? + +There are several ways to call external programs from a Vim function. You +can use the builtin system() function to invoke external programs and get +the result: + + :let output = system("ls") + +You can also use "!" ex-command to run an external command. + +For more information, read + + :help system() + :help :! + :help 10.9 + + +25.22. How do I get the return status of a program executed using the ":!" + command? + +You can use the predefined Vim v:shell_error variable to get the return +status of the last run shell command. + +For more information, read + + :help v:shell_error + + +25.23. How do I determine whether the current buffer is modified or not? + +You can check the value of the 'modified' option to determine whether the +current buffer is modified: + + :set modified? + +From a Vim script, you can check the value of the 'modified' option: + + if &modified + echo "File is modified" + endif + +For more information, read + + :help 'modified' + + +25.24. I would like to use the carriage return character in a normal + command from a Vim script. How do I specify the carriage return + character? + +You can use the ":execute" command to specify the special (control) +character in a normal mode command: + + :execute "normal \<CR>" + :execute "normal ixxx\<Esc>" + +For more information, read + + :help :execute + :help expr-quote + + +25.25. How do I split long lines in a Vim script? + +You can split long lines in a Vim script by inserting the backslash +character ("\") at the start of the next line. For example, + +For more information, read + + :help line-continuation + + +25.26. When I try to "execute" my function using the "execute 'echo + Myfunc()'" command, the cursor is moved to the top of the current + buffer. Why? + +The ":execute" command runs the normal mode command specified by the +argument. In the case of the following command: + + :execute "echo Myfunc()" + +The call to "echo Myfunc()" will return 0. The ":execute" command will run +the normal mode command "0", which moves the cursor to the top of the file. +To call a Vim function, you should use the ":call" command instead of the +":execute" command: + + :call Myfunc() + +For more information, read + + :help :call + :help :execute + :help :echo + :help user-functions + :help 41.5 + :help 41.6 + + +25.27. How do I source/execute the contents of a register? + +If you have yanked a set of Vim commands into a Vim register (for example +register 'a'), then you can source the contents of the register using one +of the following commands: + + :@a +or + :exe @a + +For more information, read + + :help :@ + + +25.28. After calling a Vim function or a mapping, when I press the 'u' + key to undo the last change, Vim undoes all the changes made by + the mapping/function. Why? + +When you call a function or a mapping, all the operations performed by the +function/mapping are treated as one single operation. When you undo the +last operation by pressing 'u', all the changes made by the +function/mapping are reversed. + +For more information, read + + :help undo-redo + :help map-undo + + +25.29. How can I call a function defined with s: (script local function) + from another script/plugin? + +The s: prefix for a Vim function name is used to create a script local +function. A script local function can be called only from within that +script and cannot be called from other scripts. To define a function in a +script/plugin, so that it can be called from other plugins/scripts, define +the function without the s: prefix. + +For more information, read + + :help script-variable + :help script-local + :help :scriptnames + + +25.30. Is it possible to un-source a sourced script? In otherwords, reverse + all the commands executed by sourcing a script. + +No. It is not possible to reverse or undo all the commands executed by +sourcing a script. + +For more information, read + + :help :source + + +============================================================================= + +SECTION 26 - PLUGINS + + +26.1. How do I set different options for different types of files? + +You can create filetype plugins to set different options for different +types of files. You should first enable filetype plugins using the command: + + :filetype plugin on + +A filetype plugin is a vim script that is loaded whenever Vim opens or +creates a file of that type. For example, to ensure that the 'textwidth' +option is set to 80 when editing a C program (filetype 'c'), create one of +the following files: + + ~/.vim/ftplugin/c.vim (Unix) + %HOME%\vimfiles\ftplugin\c.vim (Windows) + +with the following text in it: + + setlocal textwidth=80 + +You can also use autocommands to set specific options when editing specific +type of files. For example, to set the 'textwidth' option to 75 for only +*.txt files, you can use the following autocmd: + + autocmd BufRead *.txt setlocal textwidth=80 + +For more information, read + + :help filetype-plugin + :help add-filetype-plugin + :help autocmd + :help 40.3 + + +26.2. I have downloaded a Vim plugin or a syntax file or a indent file, or + a color scheme or a filetype plugin from the web. Where should I copy + these files so that Vim will find them? + +You can place the Vim runtime files (plugins, syntax files, indent files, +color schemes, filetype plugins, etc) under one of the directories +specified in the 'runtimepath' option. To determine the current value of +the 'runtimepath' option, use the following command: + + :set runtimepath + +For Unix systems, this is usally the "$HOME/.vim" directory. For MS-Windows +systems, this is usually the $VIM\vimfiles or $HOME\vimfiles directory. +Depending on the type of the runtime file, you have to place it under a +specific directory under the above runtime directory. The names of the +directories are listed below: + + colors/ - color scheme files + compiler/ - compiler files + doc/ - documentation + ftplugin/ - filetype plugins + indent/ - indent scripts + keymap/ - key mapping files + lang/ - menu translations + plugin/ - plugin scripts + syntax/ - syntax files + tutor/ - files for vimtutor + +For more information, read + + :help your-runtime-dir + :help 'runtimepath' + :help :runtime + + +26.3. How do I extend an existing filetype plugin? + +You can extend an existing filetype plugin by creating a file under either +the $VIMRTUNTIME/after/ftplugin or the $VIMRTUNTIME/ftplugin directory. The +name of the file should be the same as the name of the existing filetype +plugin file. You can place your additions to the new file. + +If you placed the file in the after/ftplugin runtime directory, then Vim +will first source the existing filetype plugin file and then will source +the new file. If you placed the file in the $VIMRTUNTIME/ftplugin runtime +directory, then Vim will first source the new file and then will source the +existing filetype plugin file. + +For more information, read + + :help ftplugin-overrule + :help filetype-plugin + :help add-filetype-plugin + :help 'runtimepath' + + +26.4. How do I turn off loading the Vim plugins? + +You can reset the 'loadplugins' option to turn off loading the plugins: + + :set noloadplugins + +You can also specify the "--noplugin" command line argument to stop loading +the plugins: + + $ vim --noplugin + +For more information, read + + :help 'loadplugins' + :help --noplugin + :help load-plugins + + +26.5. How do I turn on/off loading the filetype plugins? + +By default, Vim will not load the filetype plugins. You can configure Vim +to load filetype plugins using the command: + + filetype plugin on + +You can turn off loading the filetype plugins using: + + filetype plugin off + +For more information, read + + :help filetype-plugin-on + :help filetype-plugin-off + :help :filetype + + +26.6. How do I override settings made in a file type plugin in the global + ftplugin directory for all the file types? + +You can use an autocommand triggered on the FileType event: + + au Filetype * set formatoptions=xyz + +This should at least be after "filetype on" in your vimrc. Best is to put +it in your "myfiletypefile" file, so that it's always last. + +If you want to override a setting for a particular filetype, then create a +file with the same name as the original filetype plugin in the +~/.vim/after/ftplugin directory For example, to override a setting in the +c.vim filetype plugin, create a c.vim file in the ~/.vim/after/ftplugin +directory and add your preferences in this file. + +For more information, read + + :help ftplugin-overrule + :help ftplugins + :help myfiletypefile + + +26.7. How do I disable the Vim directory browser plugin? + +To disable the directory browsing Vim plugin, add the following line to +your .vimrc file: + + let loaded_explorer = 1 + +For more information, read + + :help file-explorer + + +26.8. How do I set the filetype option for files with names matching a + particular pattern or depending on the file extension? + +You can set the 'filetype' option for files with names matching a +particular pattern using an autocmd. For example, to set the 'filetype' +option to 'c' for all files with extension '.x', you can use the following +autocmd: + + autocmd! BufRead,BufNewFile *.x setfiletype c + +A better alternative to the above approach is to create a filetype.vim file +in the ~/.vim directory (or in one of the directories specified in the +'runtimepath' option) and add the following lines: + + " my filetype file + if exists("did_load_filetypes") + finish + endif + augroup filetypedetect + au! BufRead,BufNewFile *.x setfiletype c + augroup END + +For more information, read + + :help new-filetype + :help 43.2 + :help :setfiletype + + +============================================================================= + +SECTION 27 - EDITING PROGRAM FILES + + +27.1. How do I enable automatic indentation for C/C++ files? + +You can enable file-type based indentation using: + + :filetype indent on + +If you want to only enable automatic C indentation, then use: + + :set cindent + +For more information, read + + :help 'cindent' + :help C-indenting + :help filetype + + +27.2. How do I configure the indentation used for C/C++ files? + +You can configure the Vim C indentation by modifying the value of the +'cinoptions', 'cinkeys' and 'cinwords' options. + +For more information, read + + :help 'cindent' + :help 'cinoptions' + :help 'cinkeys' + :help 'cinwords' + :help C-indenting + :help cinoptions-values + :help 'smartindent' + + +27.3. How do I turn off the automatic indentation feature? + +By default, the automatic indentation is not turned on. You must have +configured Vim to do automatic indentation in either .vimrc or .gvimrc +files. You can disable automatic indentation using either, + + :filetype indent off + +or + + :set nocindent + +Also, check the setting for the following options: + + :set autoindent? + :set smartindent? + :set indentexpr? + +For more information, read + + :help 'cindent' + :help filetype-indent-off + :help 'autoindent' + :help 'smartindent' + :help 'indentexpr' + + +27.4. How do I change the number of space characters used for the automatic + indentation? + +You can modify the 'shiftwidth' option to change the number of space +characters used for the automatic indentation: + + :set shiftwidth=4 + +For more information, read + + :help 'shiftwidth' + + +27.5. I am editing a C program using Vim. How do I display the definition + of a macro or a variable? + +You can use the [d command to display the definition of a macro and the [i +command to display the definition of a variable. + +For more information, read + + :help [d + :help [i + :help include-search + :help 29.4 + :help 29.5 + + +27.6. I am editing a C program using Vim. How do I jump to the beginning or + end of a code block from within the block? + +You can use '[{' command to jump to the beginning of the code block and ']} +to jump to the end of the code block from inside the block. + +For more information, read + + :help [{ + :help ]} + :help various-motions + + +27.7. Is there a way to turn off the "//" comment auto-insertion behavior + for C++ files? If I'm sitting on a line beginning with "//", then I + open a new line above or below it, Vim automatically inserts new "//" + chars. + +You can modify the value of the 'comments' option to stop Vim from +inserting the C++ comment character ("//") automatically. For example: + + :set comments=sr:/*,mb:*,el:*/ + +For more information, read + + :help 'comments' + :help format-comments + + +27.8. How do I add the comment character '#' to a set of lines at the + beginning of each line? + +First, select the first character in all the lines using visual block mode +(CTRL-V). Press 'I' to start inserting characters at the beginning of the +line. Enter the comment character and then stop the insert mode by pressing +<Esc>. Vim will automatically insert the entered characters at the +beginning of all the selected lines. + +For more information, read + + :help visual-block + :help blockwise-operators + :help v_b_I + + +27.9. How do I edit a header file with the same name as the corresponding C + source file? + +You can use the following command to edit a header file with the same name +as the corresponding C source file: + + :e %:t:r.h + +You can use the following command to edit the file in a new split window: + + :sp %:t:r.h + +In the above commands, the percent sign expands to the name of the current +file. The ":t" modifier extracts the tail (last component) of the +filename. The ":r" modifier extracts the root of the filename. The .h is +appended to the resulting name to get the header filename. + +Another approach is to use the following command: + + :sfind %:t:r.h + +This command will search for the header file in the directories specified +in the 'path' option. + +For more information, read + + :help cmdline-special + :help filename-modifiers + :help :sfind + :help 'path' + + +27.10. How do I automatically insert comment leaders while typing comments? + +To automatically insert comment leaders while typing comments, add the 'r' +and 'o' flags to the 'formatoptions' option. + + :set formatoptions+=ro + +You may also want to add the 'c' flag to auto-wrap comments using the +'textwidth' option setting and the 'q' flag to format comments with the +"gq" command: + + :set formatoptions=croq + +For more information, read + + :help 30.6 + :help format-comments + :help 'comments' + :help fo-table + + +============================================================================= + +SECTION 28 - QUICKFIX + + +28.1. How do I build programs from Vim? + +You can use the ":make" command to build programs from Vim. The ":make" +command runs the program specified by the 'makeprg' option. + +For more information, read + + :help 30.1 + :help make_makeprg + :help 'makeprg' + :help 'makeef' + :help :make + :help quickfix + + +28.2. When I run the make command in Vim I get the errors listed as the + compiler compiles the program. When it finishes this list disappears + and I have to use the :clist command to see the error message again. + Is there any other way to see these error messages? + +You can use the ":copen" or ":cwindow" command to open the quickfix window +that contains the compiler output. You can select different error lines +from this window and jump to the corresponding line in the source code. + +For more information, read + + :help :copen + :help :cwindow + :help quickfix + + +============================================================================= + +SECTION 29 - FOLDING + + +29.1. How do I extend the Vim folding support? + +You can use the 'foldexpr' option to fold using an user specified function. +For example, to fold subroutines of the following form into a single line: + + sub foo { + my $barf; + $barf = 3; + return $barf; + } + +You can use the following commands: + + set foldmethod=expr + set foldexpr=MyFoldExpr(v:lnum) + fun! MyFoldExpr(line) + let str = getline(a:line) + if str =~ '^sub\>' + return '1' + elseif str =~ '^}' + return '<1' + else + return foldlevel(a:line - 1) + endif + endfun + +For more information, read + + :help 'foldexpr' + :help fold-expr + + +29.2. When I enable folding by setting the 'foldmethod' option, all the + folds are closed. How do I prevent this? + +You can set the 'foldlevelstart' option to a particular value to close only +folds above the specified value. + + :set foldlevelstart=99 + +For more information, read + + :help 'foldlevelstart' + :help 'foldlevel' + :help fold-foldlevel + + +29.3. How do I control how many folds will be opened when I start editing a + file? + +You can modify the 'foldlevelstart' option to control the number of folds +that will be opened when you start editing a file. To start editing with +all the folds closed: + + :set foldlevelstart=0 + +To start editing with all the folds opened, you can use + + :set foldlevelstart=999 + +For more information, read + + :help 'foldlevelstart' + + +29.4. How do I open and close folds using the mouse? + +You can click on the + and - characters displayed at the leftmost column to +open and close fold. For this to work, you have to set the 'foldcolumn' +to a value greater than zero: + + :set foldcolumn=2 + +For more information, read + + :help 'foldcolumn' + + +29.5. How do I change the text displayed for a closed fold? + +You can use the 'foldtext' option to change the text displayed for a closed +fold. + +For more information, read + + :help 'foldtext' + :help fold-foldtext + :help 'fillchars' + + +29.6. How do I store and restore manually created folds across different + Vim invocations? + +You can use the ":mkview" command to store manually created folds. Later, +you can use the ":loadview" command to restore the folds. For this to work, +the 'viewoptions' must contain "folds". + +For more information, read + + :help 28.4 + :help :mkview + :help :loadview + :help 'viewoptions' + :help 'viewdir' + :help :mksession + :help 'sessionoptions' + + +============================================================================= + +SECTION 30 - VIM WITH EXTERNAL APPLICATIONS + + +30.1. Can I run a shell inside a Vim window? + +Currently Vim doesn't have support for running shell and other external +commands inside a Vim window. + +For more information, read + + :help shell-window + +Alternatively, you can try using the Unix "screen" utility or the 'splitvt' +program. + +You can also use the vimsh plugin by Brian Sturk to run a shell in a Vim +window. To use this you need to have Vim built with python support. For +more information visit the following URL: + + http://vim.sourceforge.net/scripts/script.php?script_id=165 + + +30.2. How do I pass the word under the cursor to an external command? + +You can use the special keyword <cword> to pass the word under the cursor +to an external command. For example: + + :!dict <cword> + +For more information, read + + :help <cword> + + +30.3. How do I get the output of a shell command into a Vim buffer? + +You can use the ":r !" command to get the output of a shell command into a +Vim buffer. For example, to insert the output of the "ls" shell command, +you can use the following command: + + :r !ls + +To insert the output of the shell command above the first line use the +following command: + + :0r !ls + +For more information, read + + :help :r! + + +30.4. How do I pipe the contents of the current buffer to an external + command and replace the contents of the buffer with the output from + the command? + +You can use the :! command to pipe the contents of the current buffer to a +external command and replace the contents of the buffer with the output +from the command. For example, to sort the contents of the current buffer, +using the Unix sort command, you can use the following command: + + :%!sort + +To sort only lines 10-20, you can use the following command + + :10,20!sort + +Also, if you want to pipe a buffer to an external command but not put the +results back in the buffer, you can use + + :w !sort + +The above command will pipe the entire buffer to the sort command. Note +that the space between the 'w' and the '!' is critical. To pipe only a +range of lines, you can use + + :10,20w !sort + +The above command will pipe the lines 10-20 to the sort command. + +For more information, read + + :help :range! + :help 10.9 + :help :w_c + + +30.5. How do I sort a section of my file? + +You can pipe a section of the file to the Unix "sort" utility to sort the +file. For example: + + :5,100!sort + +You can also use a visual block, and use the "!sort" command on the +selected block. + +To sort using visual blocks (sort based on a column or sort just the column +itself), read the following tip from the Vim online web page: + +http://vim.sourceforge.net/tips/tip.php?tip_id=588 + + +30.6. Is there a step-by-step guide for using Vim with slrn? + +Visit the following link to get information about using Vim with Slrn: + + http://thingy.apana.org.au/~fun/slrn/ + + +30.7. How do I use Vim as a pager? + +You can use Vim as a pager using the $VIMRUNTIME/macros/less.sh shell +script, supplied as part of the standard Vim distribution. This shell +script uses the $VIMRUNTIME/macros/less.vim Vim script to provide less like +key bindings. + +For more information, read + + :help less + + +30.8. How do I view Unix man pages from inside Vim? + +You can view Unix man pages, inside Vim, using the man.vim plugin supplied +as part of the standard Vim distribution. To use this plugin, add the +following line to your startup vimrc file: + + runtime ftplugin/man.vim + +You can also press the K key to run the program specified by the +'keywordprg' option with the keyword under the cursor. By default, +'keywordprg' is set to run man on the keyword under the cursor. + +For more information, read + + :help man-plugin + :help K + :help 'keywordprg' + + +30.9. How do I change the diff command used by the Vim diff support? + +By default, the Vim diff support uses the 'diff' command. You can change +this by changing the 'diffexpr' option. + +For more information, read + + :help diff-diffexpr + :help 'diffexpr' + + +30.10. How do I use the Vim diff mode without folding? + +You can use the following command-line to start Vim with two filenames +and use the diff mode without folding: + + $ vim -o file1 file2 "+windo set diff scrollbind scrollopt+=hor nowrap" + +If you like vertically split windows, then replace "-o" with "-O". + +For more information, read + + :help vimdiff + + +============================================================================= + +SECTION 31 - GUI VIM + + +31.1. How do I create buffer specific menus? + +Adding support for buffer specific menus is in the Vim TODO list. In the +mean time, you can try Michael Geddes's plugin, buffermenu.vim: + + http://vim.sourceforge.net/scripts/script.php?script_id=246 + + +31.2. How do I change the font used by GUI Vim? + +You can change the 'guifont' option to change the font used by GUI Vim. To +display the current value of this option, you can use + + :set guifont? + +You can add the displayed font name to the .vimrc file to use the font +across Vim sessions. For example, add the following line to the .vimrc file +to use Andale Mono font. + + set guifont=Andale_Mono:h10:cANSI + +For Win32, GTK and Photon version of Vim, you can use the following command +to bringup a dialog which will help you in changing the guifont: + + :set guifont=* + +You can also use the -font Vim command line option to specify the font used +for normal text. + +For more information, read + + :help 'guifont' + :help 'guifontset' + :help 'guifontwide' + :help font-sizes + :help -font + :help -boldfont + :help -italicfont + :help -menufont + :help -menufontset + + +31.3. When starting GUI Vim, how do I specify the location of the GVIM + window? + +You can use the "-geometry" command line argument to specify the location +of the GUI Vim window. For example: + + $ gvim -geometry 80x25+100+300 + +For more information, read + + :help 31.4 + :help -geom + + +31.4. How do I add a horizontal scrollbar in GVim? + +You can enable the horizontal scrollbar by modifying the 'guioptions' +option: + + :set guioptions+=b + +For more information, read + + :help 'guioptions' + :help gui-horiz-scroll + + +31.5. How do I make the scrollbar appear in the left side by default? + +You can add the 'l' flag to the 'guioptions' option to make the scrollbar +appear in the left side. + + :set guioptions+=l + :set guioptions-=r + +For more information, read + + :help 'guioptions' + :help gui-scrollbars + + +31.6. How do I remove the Vim menubar? + +You can remove the Vim menubar by removing the 'm' flag from the +'guioptions' option: + + :set guioptions-=m + +For more information, read + + :help 'guioptions' + + +31.7. I am using GUI Vim. When I press the ALT key and a letter, the menu + starting with that letter is selected. I don't want this behavior as + I want to map the ALT-<key> combination. How do I do this? + +You can use the 'winaltkeys' option to disable the use of the ALT key to +select a menu item: + + :set winaltkeys=no + +For more information, read + + :help 'winaltkeys' + :help :simalt + + +31.8. Is it possible to scroll the text by dragging the scrollbar so that + the cursor stays in the original location? + +The way Vim is designed, the cursor position has to be in a visible spot in +normal, visual, select and insert mode. This cannot be changed without +modifying Vim. When the scrollbar is used, the cursor will be moved so that +it is always visible. Another approach to solving this problem is to use +the Vim marks. You can mark the current cursor position using ma. Then +scroll to a different part of the text and jump back to the old position +using `a. You can also try the following suggestion from the Vim Online +website: + + http://www.vim.org/tip_view.php?tip_id=320 + +For more information, read + + :help mark-motions + + +31.9. How do I get gvim to start browsing files in a particular directory + when using the ":browse" command? + +You can set the 'browsedir' option to the default directory to use for the +":browse" command. + + :set browsedir='<your_dir>' + +For more information, read + + :help 'browsedir' + + +31.10. For some questions, like when a file is changed outside of Vim, Vim + displays a GUI dialog box. How do I replace this GUI dialog box with + a console dialog box? + +You can set the 'c' flag in the 'guioptions' option to configure Vim to use +console dialogs instead of GUI dialogs: + + :set guioptions+=c + +For more information, read + + :help 'guioptions' + + +31.11. I am trying to use GUI Vim as the editor for my xxx application. + When the xxx application launches GUI Vim to edit a file, the + control immediately returns to the xxx application. How do I start + GUI Vim, so that the control returns to the xxx application only + after I quit Vim? + +You have to start GUI Vim with the '-f' (foreground) command line option: + + $ gvim -f + +By default, GUI Vim will disconnect from the program that started Vim. With +the '-f' option, GUI Vim will not disconnect from the program that started +it. + +For more information, read + + :help gui-fork + :help -f + + +31.12. Why does the "Select Font" dialog doesn't show all the fonts + installed in my system? + +Vim supports only fixed width (mono-spaced) fonts. Proportional fonts are +not supported. In the "Select Font" dialog, only fixed width fonts will be +displayed. + +For more information, read + + :help font-sizes + :help 'guifont' + + +31.13. How do I use the mouse in Vim command-line mode? + +You can set the 'c' flag in the 'mouse' option to use mouse in the Vim +command-line mode: + + :set mouse+=c + +For more information, read + + :help mouse-using + :help gui-mouse + :help 09.2 + + +31.14. When I use the middle mouse button to scroll text, it pastes the + last copied text. How do I disable this behavior? + +You can map the middle mouse button to <Nop> to disable the middle mouse +button: + + :map <MiddleMouse> <Nop> + :map! <MiddleMouse> <Nop> + +For more information, read + + :help gui-mouse-mapping + :help <Nop> + + +31.15. How do I change the location and size of a GUI Vim window? + +You can use the "winpos" command to change the Vim window position. To +change the size of the window, you can modify the "lines" and "columns" +options. + +For example, the following commands will position the GUI Vim window at the +X,Y co-ordinates 50,50 and set the number of lines to 50 and the number of +columsn to 80. + + :winpos 50 50 + :set lines=50 + :set columns=80 + +The arguments to the 'winpos' command specify the pixel co-ordinates of the +Vim window. The 'lines' and 'columns' options specify the number of lines +and characters to use for the height and the width of the window +respectively. + +For more information, read + + :help 31.4 + :help :winpos + :help 'lines' + :help 'columns' + :help GUIEnter + + +============================================================================= + +SECTION 32 - VIM ON UNIX + + +32.1. I am running Vim in a xterm. When I press the CTRL-S key, Vim + freezes. What should I do now? + +Many terminal emulators and real terminal drivers use the CTRL-S key to +stop the data from arriving so that you can stop a fast scrolling display +to look at it (also allowed older terminals to slow down the computer so +that it did not get buffer overflows). You can start the output again by +pressing the CTRL-Q key. + +When you press the CTRL-S key, the terminal driver will stop sending the +output data. As a result of this, it will look like Vim is hung. If you +press the CTRL-Q key, then everything will be back to normal. + +You can turn off the terminal driver flow control using the 'stty' command: + + $ stty -ixon -ixoff + +or, you can change the keys used for the terminal flow control, using the +following commands: + + $ stty stop <char> + $ stty start <char> + + +32.2. I am seeing weird screen update problems in Vim. What can I do to + solve this screen/display update problems? + +You have to use a proper terminal emulator like xterm with correct TERM +settings (TERM=xterm) and a correct terminfo/termcap file. +For more information, read + + :help 'term' + + +32.3. I am using the terminal/console version of Vim. In insertmode, When I + press the backspace key, the character before the cursor is not + erased. How do I configure Vim to do this? + +You have to make sure that Vim gets the correct keycode for the backpspace +key. You can try using the command: + + :fixdel + +Make sure the TERM environment variable is set to the correct terminal +name. You can try using the 'stty' command: + + $ stty erase ^H + +where, you have to enter the ^H character by pressing the CTRL-V key and +then the CTRL-H key. + +For more information, read + + :help :fixdel + :help Linux-backspace + :help NetBSD-backspace + + +32.4. I am using Vim in a xterm. When I quit Vim, the screen contents are + restored back to the original contents. How do I disable this? + +The xterm has a capability called "alternate screen". If this capability +is present, vim switches to that alternate screen upon startup and back on +exit, thus restoring the original screen contents. To disable this +feature, add the following line to your .vimrc file: + + :set t_ti= t_te= + +For more information, read + + :help restorescreen + :help xterm-screens + + +32.5. When I start Vim, it takes quite a few seconds to start. How do I + minimize the startup time? + +This may be related to Vim opening the X display for setting the xterm +title and using the X clipboard. Make sure the DISPLAY variable is set to +point to the correct host. Try using the command line: + + $ vim -X + +This will prevent Vim from opening the X display. With this command-line +option, the X clipboard cannot be used and also Vim will not be able to +change the xterm title. + +You can also set the 'clipboard' option to + + :set clipboard=exclude:.* + +This has the same effect as using the -X command-line argument. + +For more information, read + + :help -X + :help 'clipboard' + + +32.6. How can I make the cursor in gvim in unix stop blinking? + +You can modify the 'guicursor' option, to stop the cursor from blinking. +For example: + + :set guicursor=a:blinkon0 + +For more information, read + + :help 'guicursor' + + +32.7. How do I change the menu font on GTK Vim? + +You can modify the ~/.gtkrc file to change the menu font on GTK Vim. For +example: + + style "default" + { font ="smooth09" } + class "*" style "default" + +The last line changes the font of all widgets. + +For more information, read + + :help gui-gtk + + +32.8. How do I prevent <Ctrl-Z> from suspending Vim? + +You can map <Ctrl-Z> to prevent the suspending. Here are some suggestions: + +- Make <Ctrl-Z> do nothing: + + :map <C-Z> <Nop> + +- Make <Ctrl-Z> start a shell: + + :map <C-Z> :shell<CR> + +- Make <Ctrl-Z> give an error message: + + :map <C-Z> :"suspending disabled<CR> + +For the last example, the double quote is necessary in order to keep the +message on the status line. + + +32.9. When I kill the xterm running Vim, the Vim process continues to run + and takes up a lot of CPU (99%) time. Why is this happening? + +When Vim is built with support for Python interface, you will have this +problem. This is a known problem with the python thread library and Vim. To +solve this problem, use a Vim binary built without the Python interface. + +For more information, read + + :help +python + :help python + + +32.10. How do I get the Vim syntax highlighting to work in a Unix terminal? + +The easiest and simplest way to get Vim syntax highlighting is to use the +GUI version of Vim (GVIM). To get syntax highlighting to work in the +console/terminal version of Vim, you have to run a terminal emulator (like +Xfree86 xterm or rxvt or dtterm) that supports color. Note that if a +terminal emulator supports changing the background and foreground colors, +that does not mean that it also supports ANSI escape sequences for changing +the color. You can download the latest version of Xfree86 xterm from +http://dickey.his.com/xterm/xterm.html. You can download the latest version +of rxvt from http://www.rxvt.org. You have to install the terminfo/termcap +file that supports colors for the terminal emulator. Also, set the TERM +environment variable to the correct name of the term that supports colors. + +You can use the colortest.vim script supplied with the Vim runtime +package to test the color setup. To use this script, follow these steps: + + :e $VIMRUNTIME/syntax/colortest.vim + :source % + +For more information, read + + :help 06.2 + :help terminal-colors + :help termcap-colors + :help startup-terminal + :help xterm-color + :help colortest.vim + + +============================================================================= + +SECTION 33 - VIM ON MS-WINDOWS + + +33.1. In MS-Windows, CTRL-V doesn't start the blockwise visual mode. What + happened? + +The mswin.vim script provides key mappings and options to make Vim behave +like a MS-Windows application. One of the keys mapped is CTRL-V which is +used for pasting text in MS-Windows applications. This will disable the use +of CTRL-V to start the blockwise visual mode. The mswin.vim script maps +CTRL-Q for staring the blockwise visual mode. So you can use CTRL-Q instead +of CTRL-V. + +For more information, read + + :help CTRL-V + :help CTRl-V-alternative + :help CTRL-Q + :help 10.5 + + +33.2. When I press the CTRL-Y key, it acts like the CTRL-R key. How do I + configure Vim to treat CTRL-Y as CTRL-Y? + +The mapping of the CTRL-Y key to the CTRL-R key is done by the mswin.vim +script. The mswin.vim script maps CTRL-Y to make Vim behave like a standard +MS-Windows application. This is explained in ":help CTRL-Y". You can either +comment out the line in mswin.vim that maps the CTRL-Y key or you can +remove the line in your .vimrc file that sources the mswin.vim script. + + +33.3. How do I start GUI Vim in a maximized window always? + +You can use the "simalt" command to maximize the Vim window. You can use +the GUIEnter autocmd to maximize the Vim window on startup: + + autocmd GUIEnter * simalt ~x + +For more information, read + + :help :simalt + :help GUIEnter + :help gui-win32-maximized + + +33.4. After doing some editing operations, Vim freezes. The cursor becomes + an empty rectangle. I am not able enter any characters. What is + happening? + +Most probably, you used the mouse wheel to scroll the text in Vim. There is +a known problem in using intellimouse mouse wheel with Vim. To avoid this +problem, disable Universal scrolling support for Vim. + +For more information, read + + :help intellimouse-wheel-problems + + +33.5. I am using Windows XP, the display speed of maximized GVim is very + slow. What can I do to speed the display updates? + +This may be due to the fact that you have enabled 'Smooth edges of screen +fonts' in the display properties. Try turning off font smoothing or try +changing the smoothing method to "Standard". + + +33.6. What are the recommended settings for using Vim with cygwin? + +You may want to set the following shell related Vim settings: + + :set shellcmdflag=-c + :set shellquote= + :set shellslash " Use the forward slash for expansion. + :set shellxquote=\" + :set shell=d:\cygwin\bin\bash.exe " Use the bash shell + :set shellpipe=2>&1| tee + :set shellredir=>%s 2>&1 + + +33.7. I am trying to use GNU diff with Vim diff mode. When I run the diff + from command line, it works. When I try to use the diff with Vim it + doesn't work. What should I do now? + +There is a problem with using GNU diff with Vim. You can try using the +GNU diff.exe built by Ron Aaron from the following link: + + http://www.mossbayeng.com/~ron/vim/builds.html + + +33.8. Is it possible to use Vim as an external editor for MS-Windows + Outlook email client? + +You can use the "cubiclevim" COM Add-In to use Vim as an external editor +for MS-Windows Outlook email client. Visit the following URL for more +information: + + http://sourceforge.net/projects/cubiclevim + +Note that currently this works only with MS-Office 2000 and XP. + + +33.9. I am using Vim to edit HTML files. How do I start internet explorer + with the current file to preview the HTML file? + +You can use the following command: + + :!start c:\progra~1\intern~1\iexplore.exe file://%:p<CR> + + +33.10. I would like to use Vim with Microsoft Visual Studio. How do I do + this? + +You have to download and use the OLE version of Vim (for example: +gvim61ole.zip). This file also contains instructions on how to use Vim with +Visual Studio. + +For more information, read + + :help MSVisualStudio + + +33.11. Where do I place the _vimrc and _gvimrc files? + +You can place the _vimrc and _gvimrc files under the directory pointed to +by the VIM environment variable. If you are sharing this system with other +users, then you can place the files in a directory and set the HOME +environment variable to this directory. + +For more information, read + + :help $HOME-use + :help _vimrc + + +33.12. Everytime I save a file, Vim warns about the file being changed + outside of Vim. Why? + +If you get the following warning message, everytime you save a file: + + WARNING: The file has been changed since reading it!!! + Do you really want to write to it (y/n)? + +then this problem could be related to a bug in MS-Windows on the day +daylight saving time starts. Vim remembers the timestamp of the file after +it was written. Just before the next write the timestamp is obtained again +to check if the file was changed outside of Vim. This works correctly, +except on the day daylight saving time starts. + +This problem will go away the next day after the day the daylight saving +time starts. + +For more information, read + + :help W11 + + +============================================================================= + +SECTION 34 - PRINTING + + +34.1. How do I print a file along with line numbers for all the lines? + +You can set the 'printoptions' option and use the ":hardcopy" command to +print your file: + + :set printoptions=number:y + :hardcopy + +For more information, read + + :help 'printoptions' + :help :hardcopy + + +34.2. How do I print a file with the Vim syntax highlighting colors? + +You can use the ":hardcopy" command to print a file with the Vim syntax +highlighting colors. You can also convert your file to a HTML file using +the 2html.vim script and print the HTML file. + +For more information, read + + :help syntax-printing + :help 2html.vim + :help :hardcopy + :help printing + + +============================================================================= + +SECTION 35 - BUILDING VIM FROM SOURCE + + +35.1. How do I build Vim from the sources on a Unix system? + +For a Unix system, follow these steps to build Vim from the sources: + +- Download the source and run-time files archive (vim-##.tar.bz2) from the + ftp://ftp.vim.org/pub/vim/unix directory. +- Extract the archive using the bzip2 and tar utilities using the command: + + $ bunzip2 -c <filename> | tar -xf - + +- Run the 'make' command to configure and build Vim with the default + configuration. +- Run 'make install' command to install Vim in the default directory. + +To enable/disable various Vim features, before running the 'make' command +you can run the 'configure' command with different flags to include/exclude +the various Vim features. To list all the available options for the +'configure' command, use: + + $ configure -help + +For more information, read + + :help install + + +35.2. How do I install Vim in my home directory or a directory other + than the default installation directory in Unix? + +To install Vim in a directory other than the default installation +directory, you have to specify the directory using the --prefix option +while running the configure script. + + $ ./configure --prefix=/users/xyz + +You can enable/disable various Vim feature by supplying different arguments +to the configure script. For more information about all these options, run + + $ ./configure --help + +For more information, read + + :help install-home + :help install + + +35.3. How do I build Vim from the sources on a MS-Windows system? + +For a MS-Windows system, Vim can be built using either the Visual C++ +compiler or the Borland C++ compiler or the Ming GCC compiler or the cygwin +gcc compiler. Follow these steps to build Vim from the sources for +MS-Windows: + +- Download the source (vim##src.zip), runtime (vim##rt.zip) and the extra + (vim-##-extra.tar.gz) archives from the ftp://ftp.vim.org/pub/vim/pc + directory. +- Extract the archives into a directory (for example, c:\vimsrc) +- Depending on the installed compiler, you can use the corresponding + makefile to build the Vim sources. For Visual C++ use the Make_mvc.mak + makefile, for borland C++ use the Make_bc5.mak makefile, for ming GCC use + the Make_ming.mak makefile, for cygwin gcc use the Make_cyg.mak makefile. + +Depending on whether you want to build the GUI version of Vim or the +console version of Vim, you have to pass different arguments to the +makefiles. After successfully building the sources, you can copy the +vim.exe or gvim.exe file to the desired directory along with the files from +the runtime archive. + +You can visit the following site for extensive information about building +Vim on a MS-Windows system using the various compilers: + + http://mywebpage.netscape.com/SharpPeople/vim/howto/index.html + +For more information, read + + :help install + + +35.4. The Vim help, syntax, indent files are missing from my Vim + installation. How do I install these files? + +The Vim help, syntax, indent and other runtime files are part of the Vim +runtime package. You need to download and install the Vim runtime package. +For example, for MS-Windows, the name of the Vim 6.1 runtime package is +vim61rt.zip. + +For more information, read + + :help install + + +35.5. I have built Vim from the source and installed the Vim package using + "make install". Do I need to keep the Vim source directory? + +No. Once you have built and installed Vim in some directory other than the +original source directory (for example, /usr/bin or /usr/local/bin), then +you can remove the source directory. + + +35.6. How do I determine the Vim features which are enabled at compile + time? + +You can use the ":version" command to determine the Vim features that are +enabled at compile time. The features that are enabled will be prefixed +with a "+". The features that are not enabled will be prefixed with a "-". + +If you want to test for a feature in a script, you can use the has() +function: + + if has("menu") + " Set up some menus + endif + +For more information, read + + :help :version + :help +feature-list + :help has() + + +35.7. Can I build Vim without the GUI support? + +Yes. You can build Vim by optionally enabling/disabling many of the +features including GUI. + +For more information, read + + :help install + + +35.8. When building Vim on a Unix system, I am getting "undefined reference + to term_set_winsize' error. How do I resolve this error? + +You will get this error when the build process is not able to locate the +termlib, termcap or ncurses library. You have to install the ncurses-dev +package to resolve this error. + + +35.9. Vim configure keeps complaining about the lack of gtk-config while + trying to use GTK 2.03. This is correct, since in GTK 2 they moved to + using the generic pkg-config. I can get pkg-config to list the + various includes and libs for gtk, but for some reason the configure + script still isn't picking this up. + +Use the following shell script named gtk-config: + + #!/bin/sh + pkg-config gtk+-2.0 $1 $2 + + +============================================================================= + +SECTION 36 - VARIOUS + + +36.1. How do I edit binary files with Vim? + +You can set the following options to edit binary files in Vim: + + :set binary + :set display=uhex + +You can also use the "-b" command-line option to edit a binary file: + + $ vim -b <binary_file_name> + +You can also use the xxd utility (part of the Vim distribution) to edit +binary files. + +For more information, read + + :help 23.4 + :help edit-binary + :help hex-editing + :help -b + :help 'binary' + :help 'endofline' + :help 'display' + + +36.2. How do I disable the visual error flash and the error beep? + +You can disable both the visual error flash and the error beep using the +following command: + + :set visualbell t_vb= + +For more information, read + + :help 'visualbell' + :help 'errorbells' + :help t_vb + + +36.3. How do I display the ascii value of a character displayed in a + buffer? + +You can use the 'ga' command to display the ascii value of a displayed +character. + +For more information, read + + :help ga + :help :ascii + + +36.4. Can I use zero as a count for a Vim command? + +You cannot use zero as a count for a Vim command, as "0" is a command on +its own, moving to the first column of the line. + +For more information, read + + :help 0 + :help count + + +36.5. How do I disable the Vim welcome screen? + +You can disable the Vim welcome screen, by adding the 'I' flag to the +'shortmess' option: + + :set shortmess+=I + +For more information, read + + :help :intro + :help 'shortmess' + + +36.6. How do I avoid the "hit enter to continue" prompt? + +Vim will prompt you with the "hit enter to continue" prompt, if there are +some messages on the screen for you to read and the screen is about to be +redrawn. You can add the 'T' flag to the 'shortmess' option to truncate +all messages. This will help in avoiding the hit-enter prompt: + + :set shortmess+=T + +You can also increase the command height by setting the 'cmdheight' option: + + :set cmdheight=2 + +For more information, read + + :help hit-enter + :help avoid-hit-enter + :help 'shortmess' + :help 'cmdheight' + + +36.7. How do I invoke Vim from command line to run a group of commands on a + group of files? + +There are several ways to invoke Vim from command line to run a group of +commands on a group of files. You can use a set of "-c" command line +options to specify a group of commands: + + $ vim -c "<ex_command_1>" -c "<ex_command_2>" *.txt + +Each of the ex-command specified with the "-c" command line option is +executed one by one sequentially. You can also use a single "-c" command +line option and the "|" character to separate the ex commands: + + $ vim -c "<ex_command_1> | <ex_command_2>" *.txt + +In the above command, if an ex command fails, then all the remaining ex +commands will not be executed. + +For example, to replace "ABC" with "DEF" in a file from the command-line, +you can use the following command: + + $ vim -c "%s/ABC/DEF/ge | update" myfile.txt + +To replace "ABC" with "DEF" in multiple files from the command-line, +you can use the following command: + + $ vim -c "argdo %s/ABC/DEF/ge | update" *.txt + +You can store the group of commands into a file and use the "-s" command +line option to run the commands on a set of files. For example, if the +group of commands are stored in the file mycmds.txt, then you can use the +following command: + + $ vim -s mycmds.txt *.pl + +For more information, read + + :help -c + :help -s + + +36.8. How do I use a normal mode command from insert mode without leaving + the insert mode? + +You can use a normal command from insert mode, without leaving the insert +mode, by first pressing the CTRL-O key and then follow that with a single +normal mode command. + +To execute more than one normal mode command, press the CTRL-L key, +followed by any number of normal mode commands and then press <Esc> to get +back to the insert mode. + +For more information, read + + :help i_CTRL-O + :help i_CTRL-L + + +36.9. How do I start Vim in insert mode? + +You can start Vim in insert mode using the ":startinsert" ex command. + + $ vim +startinsert myfile.txt + +The above command will open the file "myfile.txt" and start insert mode +with the cursor in front of the first character on the first line. To open +the file and start appending after the last character on the last line, +you can use the following command: + + $ vim + +startinsert! myfile.txt + +For more information, read + + :help :startinsert + + +============================================================================= + +SECTION 37 - UNICODE +Author: Tony Mechelynck <antoine.mechelynck AT belgacom.net> + + +37.1. Is it possible to create Unicode files using Vim? + +Yes. It may be more or less complicated depending on the keyboard and fonts +available to you, but it is always possible to encode any possible Unicode +codepoint (and some illegal ones) into a file. To create a Unicode file +using Vim, you should have compiled Vim with the "+multi_byte" compile-time +option. You can get more information about Unicode from the following +sites: + + http://www.unicode.org + http://www.cl.cam.ac.uk/~mgk25/unicode.html + +For more information, read + + :help multibyte + :help usr_45.txt + + +37.2. Which Vim settings are particularly important for editing Unicode + files? + +The most important are the various "encoding" options, i.e., 'encoding', +'fileencoding', 'fileencodings' and 'termencoding'. The boolean option +'bomb' is also significant. + +For more information, read + + :help 'encoding' + :help 'fileencoding' + :help 'fileencodings' + :help 'termencoding' + :help 'bomb' + + +37.3. What is the 'encoding' option? + +Basically, the 'encoding' option defines how Vim will represent your data +internally. However, all Unicode encodings are represented internally as +utf-8 and converted (if necessary) when reading and writing. + +For more information, read + + :help 'encoding' + + +37.4. How does Vim name the various Unicode encodings? + +Utf-8 is called utf-8 or utf8; utf-16 is called ucs-2 or ucs2; utf-32 is +called ucs-4 or ucs4. Also, you may specify endianness (except for utf-8 +which does not vary for endianness) by appending le for little-endian or be +for big-endian. If you create a file with an encoding of ucs-2 or ucs-4 +without specifying endianness, Vim will use what is typical of your +machine. + +For more information, read + + :help encoding-names + :help encoding-values + :help encoding-table + + +37.5. How does Vim specify the presence or absence of a byte-order mark? + +When reading a file, if the 'fileencodings' option includes "ucs-bom", Vim +will check for a byte-order mark. When writing a file, if the 'bomb' option +is set, Vim will write a byte-order mark on files whose encoding warrants +it. + +For more information, read + + :help 'fileencodings' + :help 'bomb' + + +37.6. What is the 'fileencoding' option? + +The 'fileencoding' option defines the particular encoding which Vim will +use to write a file. If empty, then the value of the 'encoding' option is +the default. + +For more information, read + + :help 'fileencoding' + + +37.7. What is the 'fileencodings' option? + +The 'fileencodings' option defines the heuristics used by Vim when opening +an existing file. It is a comma separated list of encodings. A special +name, "ucs-bom" is used to indicate that Vim should check for the presence +of a byte-order mark; however, it will not be recognised if it comes after +"utf-8". Normally, "ucs-bom" (if present) should be first in the list. + +When Vim opens a file, it checks it against the encodings listed in +'fileencodings'. The first one that matches is used. If there is no match, +then Vim sets 'fileencoding' to the null string, i.e., the value of +'encoding' will be used. + +For more information, read + + :help 'fileencodings' + :help 'encoding' + + +37.8. What is the 'termencoding' option? + +The 'termencoding' option defines how your keyboard encodes the data you +type. If empty, Vim assumes that it has the same value as 'encoding'. +Usually it should be set to something that matches your locale. + +For more information, read + + :help 'termencoding' + :help locale + + +37.9. What is the 'bomb' option? + +When reading a file with "ucs-bom" present in the 'fileencodings' option, +Vim will set the 'bomb' option on or off depending on the presence or +absence of a byte-order mark at the start of the file. When writing, Vim +will write a byte-order mark if the 'bomb' option is set. You may set or +unset it manually do make Vim write, or not write, the b.o.m. + +For more information, read + + :help 'bomb' + + +37.10. Where can I find an example of a typical use of all these options? + +There is a "tip", with explains them in different words with an example, at +http://vim.sourceforge.net/tip_view.php?tip_id=246 . + + +37.11. How can I insert Unicode characters into a file using Vim? + +Several methods are available: + +- Characters present on your keyboard can be typed in the usual way, even + those which require a "dead-key" prefix, like (for instance) the + circumflex on French keyboards. +- Characters for which a digraph is defined can be typed as two characters + prefixed by <Ctrl-K>. +- If you have set the 'digraph' option, you can enter the characters for + which a digrph is defined as <char1><BS><char2>. +- Any character can be entered by using a <Ctrl-V> prefix (or <Ctrl-Q> if + <Ctrl-V> is remapped to paste from the clipboard). + +For more information, read + + :help digraphs + :help 'digraph' + :help i_CTRL-V_digit + + +37.12. How can I know which digraphs are defined and for which characters? + +First set the 'encoding' option properly (for instance, to utf-8), then use +the :digraphs command to list the currently defined digraphs. + +For more information, read + + :help :digraphs + :help 'encoding' + + +============================================================================= + +Current Maintainer: Yegappan Lakshmanan +Last updated on: 2 January 2005 + diff --git a/debian/NEWS b/debian/NEWS new file mode 100644 index 0000000..51c7c4b --- /dev/null +++ b/debian/NEWS @@ -0,0 +1,15 @@ +vim (2:8.0.0022-1) unstable; urgency=medium + + Vim now ships with a defaults.vim file which, when the user has no vimrc, + enables some options that have historically been disabled by default. This + is described in more detail at ":help defaults.vim". + + Since defaults.vim is loaded when the user's vimrc would typically be + loaded, it will override any settings in /etc/vim/vimrc(.local). In order + to disable the loading of defaults.vim, add + + let g:skip_defaults_vim = 1 + + to /etc/vim/vimrc(.local). + + -- James McCoy <jamessan@debian.org> Tue, 04 Oct 2016 20:28:02 -0400 diff --git a/debian/README.Debian b/debian/README.Debian new file mode 100644 index 0000000..64a577e --- /dev/null +++ b/debian/README.Debian @@ -0,0 +1,56 @@ +Vim for Debian +--------------- + +1. The current Debian Vim scripts policy can be found in the vim-doc package + under /usr/share/doc/vim and <https://vim-team.pages.debian.net/vim/>. + +2. Before reporting bugs, check if the bug also exists if you run vim + with "vim --clean". If not, make sure that the "bug" is not + a result of a setting in your ~/.vimrc before reporting it. + +defaults.vim +------------ + +Vim provides $VIMRUNTIME/defaults.vim to improve the default Vim experience for +a user with no vimrc file. It enables commonly useful functionality that +wasn't historically enabled by default, like syntax highlighting and filetype +plugins. + +However, the defaults.vim script is ONLY loaded when a user does NOT have their +own vimrc file. If you create a vimrc file and want to build on top of +defaults.vim, add these lines to the top of your vimrc file: + + unlet! g:skip_defaults_vim + source $VIMRUNTIME/defaults.vim + +When defaults.vim is loaded implicitly for a user, that happens _after_ the +system vimrc file has been loaded. Therefore, defaults.vim will override +settings in the system vimrc. To change that, one can either + +a) Explicitly load defaults.vim in the system vimrc, as described above, and + then define your customizations +b) Explicitly opt out of defaults.vim by adding the line below to + the system vimrc + + let g:skip_defaults_vim = 1 + +Modeline support disabled by default +------------------------------------ + +Modelines have historically been a source of security/resource vulnerabilities +and are therefore disabled by default in $VIMRUNTIME/debian.vim. + +You can enable them in ~/.vimrc or /etc/vim/vimrc with "set modeline". + +In order to mimic Vim's default setting (modelines disabled when root, enabled +otherwise), you may instead want to use the following snippet: + + if $USER != 'root' + set modeline + else + set nomodeline + endif + +The securemodelines script from vim.org (and in the vim-scripts package) may +also be of interest as it provides a way to whitelist exactly which options +may be set from a modeline. diff --git a/debian/README.source b/debian/README.source new file mode 100644 index 0000000..f4d85a1 --- /dev/null +++ b/debian/README.source @@ -0,0 +1,41 @@ +If you are reading this from a Debian source package, you can stop now; +this package should build normally after extracting with dpkg-source -x. +The rest of this file gives some hints about generating source packages +from the packaging git repository. + +This repository maintains patches to upstream source using gbp-pq. These +patches are serialized to debian/patches/. + +In order to modify an existing patch, simply run “gbp pq import”. This will +create a local branch with the commits that were used to create the patches. +Edit or amend the commits as necessary. + +In order to create a new patch, switch to the patch using “gbp pq import” as +before. If a patch file exists, use “gbp pg apply --topic={upstream,debian} +patchfile” to apply the patch (works like “git am”). If the patch is intended +to be upstreamed, it should be applied before any Debian-specific patches and +use the "upstream" topic. Alternatively, if the patch is not intended to be +upstreamed, it should use the "debian" topic and be applied after any upstream +patches. + +When updating to a new version of upstream code, the patches need to be rebased +on the new upstream code. The process is + +* Create the patch-queue branch -- gbp pq import +* Switch back to the packaging branch -- gbp pq switch +* Merge the upstream tag -- git merge vX.Y.ZZZZ +* Rebase the patches -- gbp pq rebase + * Make any adjustments/fixups, as necessary +* Switch back to the packaging branch -- gbp pq switch +* Export the patches -- gbp pq export + +Whenever the patch queue branch is modified, those changes need to be exported +back to the packaging branch. “gbp pq switch” will change from the patch queue +branch to the packaging branch. At that point, “gbp pq export” will update +debian/patches/ with the current state of the patch queue. This needs to be +commited just like any other change. + +There are hooks setup in the git repo to avoid pushing the patch queue +branches, but it's also wise to remove the local branch when done with the +changes. The repository's configuration is set to delete the branch +automatically after running “gbp pq export” in order to help enforce this. diff --git a/debian/bug-presubj b/debian/bug-presubj new file mode 100644 index 0000000..87c3e13 --- /dev/null +++ b/debian/bug-presubj @@ -0,0 +1,6 @@ +Before filing a bug, please ensure that your configuration is not the cause of +the bug. At the very least, this can help narrow down exactly where the bug +exists or what option is causing the behavior. + +Start Vim with the "--clean" option and provide specific steps on reproducing +the bug from there. diff --git a/debian/bug-script b/debian/bug-script new file mode 100644 index 0000000..58911de --- /dev/null +++ b/debian/bug-script @@ -0,0 +1,8 @@ +#!/bin/sh + +printf "\n--- real paths of main Vim binaries ---\n" >&3 +for f in vi vim gvim; do + if [ -L "/usr/bin/$f" ]; then + printf "/usr/bin/$f is $(readlink -f /usr/bin/$f)\n" >&3 + fi +done diff --git a/debian/changelog b/debian/changelog new file mode 100644 index 0000000..101999b --- /dev/null +++ b/debian/changelog @@ -0,0 +1,7338 @@ +vim (2:9.0.1378-2) unstable; urgency=medium + + * Backport 9.0.1499 to fix CVE-2023-2426 (Closes: #1035323) + * Backport fix for indenting of Perl subroutines (Closes: #1034529) + + -- James McCoy <jamessan@debian.org> Thu, 04 May 2023 06:24:44 -0400 + +vim (2:9.0.1378-1) unstable; urgency=medium + + * Merge upstream patch v9.0.1378 + + Vulnerability fixes + - 9.0.1143: Invalid memory access with bad 'statusline' value, + CVE-2023-0049 + - 9.0.1144: Reading beyond text, CVE-2023-0051 + - 9.0.1145: Invalid memory access with recursive substitute expression, + (Closes: #1031875, CVE-2023-0054) + - 9.0.1189: Invalid memory access with folding and using "L", + CVE-2023-0288 + - 9.0.1225: Reading past the end of a line when formatting text, + CVE-2023-0433 + - 9.0.1247: Divide by zero with 'smoothscroll' set and a narrow window, + CVE-2023-0512 + - 9.0.1367: Divide by zero in zero-width window, CVE-2023-1127 + - 9.0.1376: Accessing invalid memory with put in Visual block mode, + CVE-2023-1170 + + 9.0.1073, 9.0.1080: Fix keyboard input/mapping support for some + terminals (e.g., foot and kitty). (Closes: #1029049) + + 9.0.1213: Fix inconsistent behavior when adding text after a fold at the + end of the buffer (Closes: #868252) + + syntax/2html.vim: Fix reference to undefined s:settings_no_doc variable + (Closes: #1030151) + + syntax/debcontrol.vim, syntax/debsources.vim: Add support for + non-free-firmware. (Closes: #1029986) + + -- James McCoy <jamessan@debian.org> Sat, 04 Mar 2023 14:41:33 -0500 + +vim (2:9.0.1000-4) unstable; urgency=medium + + * Backport patch to fix tests on IPv6-only hosts (Closes: #1027824) + + -- James McCoy <jamessan@debian.org> Tue, 10 Jan 2023 22:16:36 -0500 + +vim (2:9.0.1000-3) unstable; urgency=medium + + * Fix substitution of VIMCUR in vim-common.install (Closes: #1027766) + * Backport v9.0.1129 to fix sporadic Test_range failure + + -- James McCoy <jamessan@debian.org> Tue, 03 Jan 2023 10:15:51 -0500 + +vim (2:9.0.1000-2) unstable; urgency=medium + + * Restore man page translations for da, de, and ja (Closes: #1027318) + * Update to debhelper-compat 13 + * Remove obsolete maintscript files for versions earlier than oldstable + * Remove PER_VARIANT_FILES handling in debian/rules + * Add future=+lfs to DEB_BUILD_MAINT_OPTIONS + * Backport v9.0.1118 to fix sporadic test failures + * ci: Run tests against installed xxd + * ci: Install python3 for vim tests + * Backport v9.0.1117 to fix bracketed paste with new ncurses + (Closes: #1027674) + + -- James McCoy <jamessan@debian.org> Mon, 02 Jan 2023 06:31:55 -0500 + +vim (2:9.0.1000-1) unstable; urgency=medium + + * Merge upstream patch v9.0.1000 + + Security fixes + - 9.0.0882: using freed memory after SpellFileMissing autocmd uses + bwipe, CVE-2022-4292 + - 9.0.0947: invalid memory access in substitute with function that goes + to another file (Closes: #1027146, CVE-2022-4141) + * Backport v9.0.1087 to fix test_autocmd flakiness + + -- James McCoy <jamessan@debian.org> Wed, 28 Dec 2022 11:51:10 -0500 + +vim (2:9.0.0813-1) unstable; urgency=medium + + * Merge upstream patch v9.0.0813 + + syntax/markdown.vim: Fix performance of markdownLinkText highlighting. + (Closes: #994209) + + -- James McCoy <jamessan@debian.org> Sun, 30 Oct 2022 16:59:44 -0400 + +vim (2:9.0.0626-1) unstable; urgency=medium + + * Merge upstream patch v9.0.0626 + + Various CVE fixes (Closes: #1019590) + - 9.0.0246: using freed memory when 'tagfunc' deletes the buffer, + CVE-2022-2946 + - 9.0.0260: using freed memory when using 'quickfixtextfunc' + recursively, CVE-2022-2982 + - 9.0.0322: crash when no errors and 'quickfixtextfunc' is set, + CVE-2022-3037 + - 9.0.0360: crash when invalid line number on :for is ignored, + CVE-2022-3099 + - 9.0.0389: crash when 'tagfunc' closes the window, CVE-2022-3134 + - 9.0.0483: illegal memory access when replacing in virtualedit mode, + CVE-2022-3234 + - 9.0.0490: using freed memory with cmdwin and BufEnter autocmd, + CVE-2022-3235 + - 9.0.0530: using freed memory when autocmd changes mark, CVE-2022-3256 + - 9.0.0577: buffer underflow with unexpected :finally, CVE-2022-3296 + - 9.0.0598: using negative array index with negative width window, + CVE-2022-3324 + - 9.0.0614: CVE-2022-3352 + + 9.0.0509: confusing error for "saveas" command with "nofile" buffer + (Closes: #796872) + + -- James McCoy <jamessan@debian.org> Fri, 30 Sep 2022 00:38:50 -0400 + +vim (2:9.0.0242-1) unstable; urgency=medium + + * Merge upstream patch v9.0.0242 + + 9.0.241/242: Install the shared syntax files (Closes: #1017856) + * Add historic changelog entry for #947120 fix + * Adjust lintian overrides for new []-format + * Declare compliance with Policy 4.6.1, no changes needed + + -- James McCoy <jamessan@debian.org> Mon, 22 Aug 2022 22:46:33 -0400 + +vim (2:9.0.0229-1) unstable; urgency=medium + + * Merge upstream patch v9.0.0229 + + Various CVE fixes + - 9.0.0211: invalid memory access when compiling :lockvar, CVE-2022-2819 + - 9.0.0212: invalid memory access when compiling :unlet, CVE-2022-2816 + - 9.0.0213: using freed memory with error in assert argument, + CVE-2022-2817 + - 9.0.0218: reading before the start of the line, CVE-2022-2845 + - 9.0.0220: invalid memory access with for loop over NULL string, + CVE-2022-2849 + - 9.0.0221: accessing freed memory if compiling nested function fails, + CVE-2022-2862 + - 9.0.0225: using freed memory with multiple line breaks in expression, + CVE-2022-2889 + * Add Recommends: xxd to vim-common + * Minor fixes for vim-tiny's fake help file (Closes: #1017715) + * Revert "Temporarily skip Test_Debugger_breakadd_expr", test fixed upstream + + -- James McCoy <jamessan@debian.org> Sat, 20 Aug 2022 09:56:52 -0400 + +vim (2:9.0.0135-1) unstable; urgency=medium + + * Merge upstream patch v8.2.5172 + + ftplugin/perl.vim: Only add : to 'isfname' in Perl buffers. (Closes: + #761800) + + ftplugin/tap.vim: Set fold-related options local to the buffer. (Closes: + #954113) + + syntax/debcontrol.vim: Fix highlighting of sections with a slash (e.g., + "non-free/utils"). (Closes: #1010839) + + syntax/tap.vim: Match TODO/SKIP markers case-insensitively. (Closes: + #954016) + + syntax/perl.vim: Properly highlight code on the same line as the start + of a here-doc block. (Closes: #136455) + + Various CVE fixes (Closes: #1015984, #1016068) + - 8.2.5043: can open a cmdline window from a substitute expression, + CVE-2022-1942 + - 8.2.5050: using freed memory when searching for pattern in path, + CVE-2022-1968 + - 8.2.5063: error for a command may go over the end of IObuff, + CVE-2022-2000 + - 8.2.5120: searching for quotes may go over the end of the line, + CVE-2022-2124 + - 8.2.5122: lisp indenting may run over the end of the line, + CVE-2022-2125 + - 8.2.5123: using invalid index when looking for spell suggestions, + CVE-2022-2126 + - 8.2.5126: substitute may overrun destination buffer, CVE-2022-2129 + - 9.0.0018: going over the end of the typeahead, CVE-2022-2285 + - 9.0.0025: accessing beyond allocated memory with the cmdline window, + CVE-2022-2288 + - 9.0.0035: spell dump may go beyond end of an array, CVE-2022-2304 + - 8.2.5162: reading before the start of the line with BS in Replace + mode, CVE-2022-2207 + - 8.2.4895: buffer overflow with invalid command with composing chars, + CVE-2022-1616 + - 8.2.4899: with latin1 encoding CTRL-W might go before the cmdline, + CVE-2022-1619 + - 8.2.4919: can add invalid bytes with :spellgood, CVE-2022-1621 + - 8.2.4956: reading past end of line with "gf" in Visual block mode, + CVE-2022-1720 + - 8.2.4977: memory access error when substitute expression changes + window, CVE-2022-1785 + - 8.2.5013: after text formatting cursor may be in an invalid position, + CVE-2022-1851 + - 8.2.5023: substitute overwrites allocated buffer, CVE-2022-1897 + - 8.2.5024: using freed memory with "]d", CVE-2022-1898 + - 9.0.0060: accessing uninitialized memory when completing long line, + CVE-2022-2522 + * Temporarily skip Test_Debugger_breakadd_expr + * Remove "Depends: xxd" from vim-common (Closes: #1007887) + * Suppress error about missing defaults.vim in vim-tiny (Closes: #1004118) + + -- James McCoy <jamessan@debian.org> Wed, 03 Aug 2022 19:00:35 -0400 + +vim (2:8.2.4793-1) unstable; urgency=medium + + * Merge upstream patch v8.2.4793 + + -- James McCoy <jamessan@debian.org> Wed, 20 Apr 2022 20:23:54 -0400 + +vim (2:8.2.4659-1) unstable; urgency=medium + + * Merge upstream patch v8.2.4659 + + 8.2.4151: reading beyond end of a line (Closes: #1004859, CVE-2022-0318) + + autoload/phpcomplete.vim: Fix E565 error in omni-completion (Closes: + #1008710) + * Remove outdated NEWS and README.Debian entries + * README.Debian: Fix links to vim-policy + * Improve docs about purpose and effect of defaults.vim (Closes: #856273) + * Define system (g)vimrc location as /etc/vim/(g)vimrc, rather than + symlinking from /usr/share/vim/(g)vimrc -> /etc/vim/(g)vimrc. + * Replace vim-athena with vim-motif, Athena GUI deprecated upstream + * Remove lintian override for rgb.txt, removed upstream + * Declare compliance with Policy 4.6.0, no changes needed + * Remove vim-gtk transitional package + + -- James McCoy <jamessan@debian.org> Sun, 03 Apr 2022 10:44:13 -0400 + +vim (2:8.2.3995-1) unstable; urgency=medium + + * Merge upstream patch v8.2.3918 + + 8.2.3610: crash when ModeChanged triggered too early (Closes: #1001900, + CVE-2021-3968) + + 8.2.3611: crash when using CTRL-W f without finding a file name (Closes: + #1001899, CVE-2021-3973) + + 8.2.3612: using freed memory with regexp using a mark (Closes: #1001897, + CVE-2021-3974) + + 8.2.3625: illegal memory access when C-indenting (Closes: #1001896, + CVE-2021-3984) + + 8.2.3847: illegal memory access when using a lambda with an error + (Closes: #1002534, CVE-2021-4136) + + autoload/zip.vim: Use URI syntax for pseudo-filename to avoid empty + buffer after 8.2.3468 (Closes: #1000767) + * Revert "Disable Test_very_large_count since it fails on 32-bit systems", + fixed upstream + + -- James McCoy <jamessan@debian.org> Mon, 03 Jan 2022 17:57:10 -0500 + +vim (2:8.2.3565-1) unstable; urgency=medium + + * Merge upstream patch v8.2.3565 + + 8.2.3489: ml_get error after search with range (Closes: #996593, + CVE-2021-3875) + + syntax/{debchangelog,debsources}.vim: Add jammy as a recognized Ubuntu + release (Closes: #996760) + * Drop patches applied upstream + + Fix test_recover.vim's checks for endianness and size of long + + Use explicitly signed type for tt_min_argcount to fix unsigned char + systems + * Revert "Temporarily depend on xxd for build tests/autopkgtests" + * Disable Test_very_large_count since it fails on 32-bit systems + + -- James McCoy <jamessan@debian.org> Sat, 30 Oct 2021 10:56:38 -0400 + +vim (2:8.2.3455-2) unstable; urgency=medium + + * Fix test_recover.vim's checks for endianness and size of long + * Use explicitly signed type for tt_min_argcount to fix unsigned char systems + + -- James McCoy <jamessan@debian.org> Sun, 03 Oct 2021 09:17:57 -0400 + +vim (2:8.2.3455-1) unstable; urgency=medium + + * Merge upstream patch v8.2.3455 + + 8.2.2761: Don't add current_syn_inc_tag to topgrp. (Closes: #947120) + + 8.2.3022: Add support for xchacha20 encryption, using libsodium + + 8.2.3068: Update Unicode support to Unicode 13 + + 8.2.3402, 8.2.3403: invalid memory access when using :retab with large + value (Closes: CVE-2021-3770, #994076) + + 8.2.3409: reading beyond end of line with invalid utf-8 character + (Closes: CVE-2021-3778, #994498) + + 8.2.3428: using freed memory when replacing (Closes: CVE-2021-3796, + #994497) + + 8.2.3430: Add the ModeChanged autocommand event + + ftplugin/scala.vim: Fix syntax of includeexpr option (Closes: #895629) + + syntax/{debchangelog,debsources}.vim: Add impish as a recognized Ubuntu + release (Closes: #995151) + * Vim addons policy + + Automatically publish policy to https://vim-team.pages.debian.net/vim/ + (Closes: #989223) + + Rewrite policy to document use of dh_vim-addon instead of + vim-addon-manager + * Explicitly Depend on lynx to ensure docbook2txt works + * Build against libsodium for non-tiny builds + * Define a writable $HOME for the tests + * Temporarily depend on xxd for build tests/autopkgtests, otherwise + new tests for the xchacha20 encryption fail. + * Switch to salsa-ci-team pipeline for CI + + -- James McCoy <jamessan@debian.org> Thu, 30 Sep 2021 12:54:53 -0400 + +vim (2:8.2.2434-3) unstable; urgency=medium + + * Add pkg.vim.noruby Build-Profile + * Disable ruby interpreter on alpha and ia64 (Closes: #983308) + * Re-enable ruby for vim-gtk3 on Ubuntu, since it is no longer in main + + -- James McCoy <jamessan@debian.org> Mon, 01 Mar 2021 21:58:09 -0500 + +vim (2:8.2.2434-2) unstable; urgency=medium + + * Only enable sound support for GUI builds (Closes: #982856) + + -- James McCoy <jamessan@debian.org> Sat, 20 Feb 2021 13:46:51 -0500 + +vim (2:8.2.2434-1) unstable; urgency=medium + + * Merge upstream patch v8.2.2434 + + 8.2.2428: Fix handling of focus events when 'ttymouse' is unset. + (Closes: #980449) + + -- James McCoy <jamessan@debian.org> Sat, 30 Jan 2021 23:47:07 -0500 + +vim (2:8.2.2367-1) unstable; urgency=medium + + * Merge upstream patch v8.2.2367 + + 8.2.2367: Fix test failures on armel/armhf/mipsel + + -- James McCoy <jamessan@debian.org> Sun, 17 Jan 2021 10:53:54 -0500 + +vim (2:8.2.2344-2) unstable; urgency=medium + + * rules: Add dummy command to test target to fix make error when + DEB_BUILD_OPTIONS=nocheck + + -- James McCoy <jamessan@debian.org> Thu, 14 Jan 2021 22:25:21 -0500 + +vim (2:8.2.2344-1) unstable; urgency=medium + + * Merge upstream patch v8.2.2344 + + ftplugin/spec.vim: Fix missing ":let" (Closes: #977429) + + syntax/cabal.vim: Add build-tools-depends keyword (Closes: #973548) + * rules: Sanitize locale-related environment variables (Closes: #973943) + + -- James McCoy <jamessan@debian.org> Thu, 14 Jan 2021 21:40:26 -0500 + +vim (2:8.2.1913-1) unstable; urgency=medium + + [ James McCoy ] + * Merge upstream tag v8.2.1913 + + syntax/sh.vim: Highlight "local var" appropriately when /bin/sh is dash. + (Closes: #796282) + + plugin/netrwPlugin.vim: Fix directory navigation with + g:netrw_liststyle=3 and g:netrw_list_hide='^\..*'. (Closes: #942549) + + 8.2.1909: Remove the limit on items in 'statusline' (Closes: #688258) + + 8.2.1912: Fix test failures with Python 3 >= 3.9 (Closes: #972777) + * rules: Provide path to vim when building vim.pot + * Add procps and cscope to (autopkg)test Depends + * d/tests: Use dpkg-query rather than dpkg-parsechangelog to get upstream version + * d/tests: Use runtime/ from source tree + * d/tests: Force TERM=xterm when running upstreamtest + * Stop installing vim2html.pl + * Stop installing README.txt files in vim-runtime + * Lintian + + Add national-encoding overrides for files intentionally in non-UTF8 + encodings + + Add package-contains-documentation-outside-usr-share-doc overrides for + builtin help + + Rename binary-without-manpage override to no-manual-page + + Rename manpage-without-executable override to spare-manual-page + + Override repeated-path-segment for dvorak plugin + + Add package-contains-documentation-outside-usr-share-doc override for + rgb.txt + + [ Pino Toscano ] + * Remove unused XPM icons. + * Remove do not ship gvim.svg in /usr/share/pixmaps. + + -- James McCoy <jamessan@debian.org> Tue, 27 Oct 2020 21:38:24 -0400 + +vim (2:8.2.0716-3) unstable; urgency=medium + + * Version the vim/gvim/etc Provides for the vim binary packages. This + allows versioned Depends on vim to be satisfied by any of the binary + packages instead of trying to install Package: vim. (Closes: #960119) + + -- James McCoy <jamessan@debian.org> Mon, 11 May 2020 22:37:13 -0400 + +vim (2:8.2.0716-2) unstable; urgency=medium + + * Build vim-basic for arch-all builds, needed for install targets + + -- James McCoy <jamessan@debian.org> Sat, 09 May 2020 11:27:39 -0400 + +vim (2:8.2.0716-1) unstable; urgency=medium + + * Merge upstream tag v8.2.0716 + + syntax/make.vim: Fix mis-highlighting of targets that start with the + word "overrule". (Closes: #958993) + * rules: Switch to dh + * Remove src/po/vim.pot during clean + + -- James McCoy <jamessan@debian.org> Sat, 09 May 2020 09:20:09 -0400 + +vim (2:8.2.0510-1) unstable; urgency=medium + + * Merge upstream tag v8.2.0510 + + 8.2.0444: Improve reliability of Test_swap_prompt_splitwin + + 8.2.0447: Improve reliability of Test_terminal_scroll + + 8.2.0454: Improve reliability of Test_state + + 8.2.0456, 8.2.0461, 8.2.0470: Improve reliability of Test_confirm_cmd + + 8.2.0462: Fix invalid assertion in Test_popup_and_previewwindow_dump + + 8.2.0474: Allow ":write" to overwrite an existing file when used via + BufWriteCmd, fixing breakage of plugins like vim-gnupg + * Add lintian overrides for manpage-without-executable + * Remove obsolete vim-common.preinst + + -- James McCoy <jamessan@debian.org> Sat, 04 Apr 2020 23:20:13 -0400 + +vim (2:8.2.0439-1) unstable; urgency=medium + + * Merge upstream tag v8.2.0439 + + 8.2.0398: Fix FTBFS due to Test_profile_func() failure + + 8.2.0436: Fix FTBFS in test_vim9_disassemble.vim due to type mismatches + in format strings + + -- James McCoy <jamessan@debian.org> Mon, 23 Mar 2020 23:21:40 -0400 + +vim (2:8.2.0397-1) unstable; urgency=medium + + * Merge upstream tag v8.2.0397 + + 8.2.0382: Fix Test_terminal_in_popup failures by disabling the ruler + + syntax/resolv.vim: Refresh list of known options. (Closes: #626371) + + -- James McCoy <jamessan@debian.org> Tue, 17 Mar 2020 08:31:45 -0400 + +vim (2:8.2.0378-1) unstable; urgency=medium + + * Merge upstream tag v8.2.0378 + + 8.2.0374: Fix test failures on 32-bit archs. (Closes: #953742) + + -- James McCoy <jamessan@debian.org> Fri, 13 Mar 2020 23:40:47 -0400 + +vim (2:8.2.0368-1) unstable; urgency=medium + + * Merge upstream patch v8.2.0368 + + New "vim9script" syntax available for scripts, c.f. ":help vim9-script" + + syntax/debchangelog.vim: Stop highlighting space before "UNRELEASED" as + an error (Closes: #944781) + + syntax/markdown.vim: Don't treat a bare "<" as the start of an HTML tag. + (Closes: #892172) + + syntax/resolv.vim: Highlight IPv6 addresses (Closes: #626371) + + 8.2.0271: Correctly format 64-bit numbers for status messages in + vim-tiny on 32-bit systems (Closes: #951380) + * Declare compliance with Policy 4.5.0, no changes needed + * Build-Depend on debhelper-compat (= 12) + + -- James McCoy <jamessan@debian.org> Tue, 10 Mar 2020 22:54:00 -0400 + +vim (2:8.1.2269-1) unstable; urgency=medium + + * Merge upstream patch v8.1.2269 + + 8.1.2261: Disable modifyOtherKeys while in Insert mode when 'noesckeys' + is set. (Closes: #944132) + + -- James McCoy <jamessan@debian.org> Sat, 09 Nov 2019 07:59:40 -0500 + +vim (2:8.1.2244-1) unstable; urgency=medium + + * Merge upstream patch v8.1.2244 + + syntax/debchangelog.vim: Highlight unsupported releases differently than + supported releases. (Closes: #847933) + + "mouse" feature is now always enabled. + + Improve support for chorded mappings in xterm, when xterm's + modifyOtherKeys mode is enabled, c.f. :help modifyOtherKeys. + * Revert "Move /usr/bin/vim.* into /usr/libexec/vim/" + (Closes: #943328, #942225). The change broke user preferences for + alternatives and sensible-editor. + * Add /var/lib/addons to 'runtimepath' at build time (Closes: #943967) + * Use dh_missing instead of dh_install --list-missing (Closes: #942277) + + -- James McCoy <jamessan@debian.org> Sun, 03 Nov 2019 20:52:36 -0500 + +vim (2:8.1.2136-1) unstable; urgency=medium + + * Merge upstream patch v8.1.2136 + + Farsi support was removed + + syntax/debcontrol.vim: Recognize "Files-Excluded(-<component>)" fields + (Closes: #932894) + + Swap files are automatically deleted if the file was unmodified and the + process which generated the swap file isn't running. (Closes: #375989) + + Fix incorrect over-indenting when auto-indent is enabled for XML files. + (Closes: #918672) + + Fix indentation of bash scripts with nested if blocks. (Closes: + #939369) + + New popup window support, via the "popup_*()" APIs + + New sound support, via the "sound_*()" APIs + + "localmap", "visual", "visualextra", "visualedit", "user_commands", + "multi_byte", "cmdline_compl", "insert_expand", "modify_fname", + and "comments" features are now always enabled. + + Fix test_compiler.vim failure when locale isn't available. (Closes: + #917859) + * control: + + Remove obsolete versioned Build-Depends on dpkg-dev + * rules: + + Use dh_install --list-missing + * Turn vim-gtk into a transitional package to vim-gtk3 (Closes: #930576 + since the IA__gdk_drawable_get_size assertions don't happen in the GTK3 + build) + * Declare compliance with Policy 4.4.1, no changes needed + * Move /usr/bin/vim.* into /usr/libexec/vim/ + * autopkgtest: + + Mark the "$variant --version" tests superficial + + Add new tests which run the build time tests against the installed + binary/runtime. Mark it flaky for now, since there are some tests which + are more prone to fail in the LXC environment. + + Run autopkgtests as a dedicated user, to avoid false negative failures + with upstream tests which check permissions + + -- James McCoy <jamessan@debian.org> Fri, 11 Oct 2019 21:37:58 -0400 + +vim (2:8.1.0875-5) unstable; urgency=medium + + * gbp.conf: Set debian-tag to debian/%(version)s + * Backport 'modelineexpr' patches to further restrict modelines + + 8.1.1366: Using expressions in a modeline is unsafe + + 8.1.1367: can set 'modelineexpr' in modeline + + 8.1.1368: Modeline test fails with python but without pythonhome + + 8.1.1382: Error when editing test file + + 8.1.1401: misspelled mkspellmem as makespellmem (test fix) + + -- James McCoy <jamessan@debian.org> Sat, 15 Jun 2019 12:41:15 -0400 + +vim (2:8.1.0875-4) unstable; urgency=high + + * Backport 8.1.1046 and 8.1.1365 to fix CVE-2019-12735 (Closes: #930020) + + 8.1.1365: source command doesn't check for the sandbox + + -- James McCoy <jamessan@debian.org> Fri, 07 Jun 2019 06:49:19 -0400 + +vim (2:8.1.0875-3) unstable; urgency=medium + + * syntax/deb{changelog,sources}: Update release names for Debian/Ubuntu + (Closes: #927167) + + -- James McCoy <jamessan@debian.org> Sun, 05 May 2019 23:41:10 -0400 + +vim (2:8.1.0875-2) unstable; urgency=medium + + * Backport 8.1.0878 and 8.1.0884 to fix test failures on kFreeBSD. + * Backport 8.1.0948 to avoid enabling filetype detection when the +eval + feature isn't present. (Closes: #922106) + + -- James McCoy <jamessan@debian.org> Fri, 22 Feb 2019 07:55:04 -0500 + +vim (2:8.1.0875-1) unstable; urgency=medium + + * Merge upstream patch v8.1.0875 + + "autocmd", "multi_byte", "virtualedit", and "visualextra" features are + now always enabled. + + New Blob type, for working with raw bytes. + + Support a 3rd character for the "tab" setting in the 'listchars' option. + + *.com files under /etc/apache2/sites-* are properly recognized as apache + filetype. (Closes: #740387) + + syntax/debchangelog.vim: Recognize "emergency" as a valid urgency. + (Closes: #920522) + + Support 64-bit offsets for xxd. (Closes: #771456) + * rules: + + Remove --enable-multibyte since it is always enabled + * debian.vim: + + Remove has('autocmd') checks since it is always enabled + * gvimrc: + + Adapt gui check to work for gtk2/gtk3 + + -- James McCoy <jamessan@debian.org> Mon, 04 Feb 2019 23:11:09 -0500 + +vim (2:8.1.0693-2) unstable; urgency=medium + + * Separate /etc/vim and /usr/share/vim/vimfiles. The former should be for + the sysadmin, while the latter is used by packages. + + Make /usr/share/vim/vimfiles a directory, not a symlink to /etc/vim + + Add /etc/vim to the default 'runtimepath' + + -- James McCoy <jamessan@debian.org> Sat, 05 Jan 2019 15:53:12 -0500 + +vim (2:8.1.0693-1) unstable; urgency=medium + + * Merge upstream tag v8.1.0693 + * control: + + Remove obsolete vim-gnome package + + Remove ${shlibs:Depends} from vim-common, since it is Arch: all + + Build-Depend on libtool-bin to run libterm tests + + Replace libtinfo-dev Build-Depends with libncurses-dev + + Change Homepage to https://www.vim.org/ + * Use debian/clean to cleanup files/directories + * rules: + + Rename stamp files so dh_clean deletes them automatically + + Ensure helptags are generated before running tests + * Declare compliance with Policy 4.3.0, no changes needed + + -- James McCoy <jamessan@debian.org> Sat, 05 Jan 2019 12:34:12 -0500 + +vim (2:8.1.0549-1) unstable; urgency=medium + + * Merge upstream tag v8.1.0549 + + Built-in support for performing diffs, via the libxdiff library, which + allows setting the diff algorithm (:help 'diffopt'). + + Fix formatting of example output in translated xxd man pages. (Closes: + #909217) + * gitlab-ci.yml: Run build as non-root user + * Mark vim-common Multi-Arch: foreign (Closes: #910732) + + -- James McCoy <jamessan@debian.org> Tue, 27 Nov 2018 20:38:28 -0500 + +vim (2:8.1.0320-1) unstable; urgency=medium + + * Merge upstream tag v8.1.0320 + - syntax/debcontrol.vim: + + Recognize riscv64 as an architecture (Closes: #905435) + - syntax/sh.vim: + + Fix syntax highlighting of curly braces inside parameter expansion + (Closes: #904875) + * rules: + + Stop using --dbgsym-migration + + Stop overriding default dpkg-deb compression + * Declare compliance with Policy 4.2.0, no changes needed + * control: Add cscope to Build-Depends to test cscope integration + + -- James McCoy <jamessan@debian.org> Wed, 22 Aug 2018 19:46:39 -0400 + +vim (2:8.1.0229-1) unstable; urgency=medium + + [ upstream ] + * Unicode 11 support + * New options ('vartabstop'/'varsofttabstop') to define variable width tab + stops. + * Danish translation + + [ James McCoy ] + * Change "Compiled by" string to team+vim@tracker.d.o + * rules: + + Only run scratch target, not distclean, in autoconf-stamp to avoid FTBFS + with parallel builds. + + Allow defining VARIANT from the environment. Thanks to Guillem Jover + for the suggestion (Closes: #903927) + * Change vim-python Provides to vim-python3. While Vim only supports py2 or + py3, Neovim supports both so the change in provides allows + python(3)-neovim to differentiate the supported Python version. + + -- James McCoy <jamessan@debian.org> Thu, 02 Aug 2018 21:44:43 -0400 + +vim (2:8.1.0089-1) unstable; urgency=medium + + * New upstream release + + New syntax highlighting for machine-readable debian/copyright files. + (Closes: #869965) + + Fix mis-highlighting of architectures in debian/control files. (Closes: + #900476) + * Change Maintainer to team+vim@tracker.debian.org + * Add wildcard to binaries-have-file-conflict override between + vim-tiny/vim-runtime to account for upstream releases. + + -- James McCoy <jamessan@debian.org> Tue, 19 Jun 2018 22:44:05 -0400 + +vim (2:8.0.1766-1) unstable; urgency=medium + + [ David Rabel ] + * d/copyright: Fix path to tee.c + + [ upstream ] + * 8.0.1477: Avoid cursor flicker when changing (de)focusing the terminal. + (Closes: #890642) + * 8.0.1491: New 'pumwidth' option allows controlling the width of the popup + menu. (Closes: #450481) + * 8.0.1744: Skip Test_writefile_sync_dev_stdout when /dev/stdout isn't + writable. (Closes: #894565) + * syntax/config.vim: Fix highlighting matching paren for AC_MSG_* syntax + items. (Closes: #881654) + * syntax/debcontrol.vim: Recognize Testsuite and Testsuite-Triggers fields. + (Closes: #886230) + * syntax/sh.vim: Do not highlight substring processing as an error for POSIX + sh. (Closes: #885938) + + [ James McCoy ] + * watch: Track git tags instead of major releases + * Declare compliance with Policy 4.1.4, no changes needed + * control: Use 11~ for minimum debhelper version to ease backporting + * rules: + + Fold config.mk handling into autoconf-stamp target + + Use C.UTF-8 locale when running tests to avoid an upstream bug in the + tests. When not run in a UTF-8 locale, a child Vim used by the tests + displays some unicode characters incorrectly, breaking the test. + + -- James McCoy <jamessan@debian.org> Thu, 26 Apr 2018 22:08:08 -0400 + +vim (2:8.0.1453-1) unstable; urgency=medium + + [ upstream ] + * 8.0.1452: terminal test fails on some systems + + This should fix the massive FTBFS on the buildds + * 8.0.1453: terminal test fails on some slow terminals + + -- James McCoy <jamessan@debian.org> Fri, 02 Feb 2018 15:37:32 -0500 + +vim (2:8.0.1451-1) unstable; urgency=medium + + [ David Rabel ] + * Update Standards-Version to 4.1.3 + + [ upstream ] + * 8.0.1444: missing -D_FILE_OFFSET_BITS=64 may cause problems + This should work around the inconsistent handling of large file support in + glibc (#888566), which closes: #827319. + + [ James McCoy ] + * Re-enable Perl bindings on kFreeBSD + * Change Vcs-* to salsa.d.o + * Bump debhelper compat to 11 + * Set R³ to no + * d/control: Use https URL for Homepage + * vim-doc: Move documentation under /usr/share/doc/vim, per §12.3 + * Remove doc/<arch pkg> → doc/<all pkg> symlinks + * d/rules: Set .NOTPARALLEL to avoid dh_prep clobbering each other + + -- James McCoy <jamessan@debian.org> Thu, 01 Feb 2018 19:07:29 -0500 + +vim (2:8.0.1401-2) unstable; urgency=medium + + * debian.vim: Move a function definition inside an :if so it doesn't cause + vim-tiny to spew lots of errors. (Closes: #885073) + + -- James McCoy <jamessan@debian.org> Sun, 24 Dec 2017 08:21:33 -0500 + +vim (2:8.0.1401-1) unstable; urgency=medium + + [ upstream ] + * syntax/sh.vim: + + Fix syntax highlighting of $() when the /bin/sh is detected as + POSIX-compliant. (Closes: #848663) + + Correctly highlight escaped single-quotes inside test expressions. + (Closes: #761064) + + [ James McCoy ] + * runtime/debian.vim: + + Fix mechanism used to check for <S-Insert> mappings, since maparg() + doesn't understand multiple modes in the {mode} argument. Thanks to + Sergey Vlasov for the patch! (Closes: #883422) + * syntax/debcontrol.vim: + + Fix highlighting of "Section: javascript" … again. (Closes: #884495) + + -- James McCoy <jamessan@debian.org> Sun, 17 Dec 2017 22:32:25 -0500 + +vim (2:8.0.1257-2) unstable; urgency=medium + + * Add patch to fix flakiness in test_search.vim + * syntax/debcontrol.vim: + + Recognize golang section. Thanks to Guillem Jover. (Closes: #880698) + + -- James McCoy <jamessan@debian.org> Sat, 04 Nov 2017 00:17:46 -0400 + +vim (2:8.0.1257-1) unstable; urgency=medium + + [ upstream ] + * 8.0.1246: Fix flaky popup test, which should fix the various FTBFS from + the last upload. + + [ James McCoy ] + * syntax/debsources.vim: + + Fix syntax error in definition of unsupported releases. Thanks to Josh + Triplett. (Closes: #879986) + * Declare compliance with Policy 4.1.1, no changes needed. + + -- James McCoy <jamessan@debian.org> Thu, 02 Nov 2017 21:27:13 -0400 + +vim (2:8.0.1226-1) unstable; urgency=medium + + [ upstream ] + * 8.0.1154: Fix indentation when 'indentkeys' is in use. (Closes: #877262) + + [ James McCoy ] + * syntax/debcontrol.vim: + + Add support for all fields in deb-src-control(5). (Closes: #878970) + * syntax/deb{sources,changelog}.vim: + + Add bionic release and mark yakkety & squeeze unsupported. + + -- James McCoy <jamessan@debian.org> Fri, 27 Oct 2017 08:27:27 -0400 + +vim (2:8.0.1144-1) unstable; urgency=medium + + [ upstream ] + * Fix detection/enabling of cursor blink state. (Closes: #872302) + * ftplugin/perl.vim: Set 'iskeyword' local to the buffer so it doesn't + affect subsequently opened buffers. (Closes: #873755) + * syntax/mason.vim: Correctly highlight mason files again. (Closes: + #700016) + + [ James McCoy ] + * debcontrol.vim: + + Recognize Testsuite field (Closes: #872360) + + Treat tabs as valid whitespace (Closes: #872557) + * Declare compliance with Policy 4.1.0, no changes needed + * Add basic autopkgtests + * Add missing postrm for symlink_to_dir maintscripts + + -- James McCoy <jamessan@debian.org> Sun, 24 Sep 2017 22:02:28 -0400 + +vim (2:8.0.0946-1) unstable; urgency=medium + + [ upstream ] + * 8.0.0939, 8.0.0940: Handle flakiness in terminal tests. (Closes: #872164) + * 8.0.0944: test_profile: Accept a match when self and total time are the + same. + * 8.0.0946: Don't rely on PATH_MAX. Fixes FTBFS on hurd. + + -- James McCoy <jamessan@debian.org> Mon, 14 Aug 2017 22:41:29 -0400 + +vim (2:8.0.0937-1) unstable; urgency=medium + + [ upstream ] + * 8.0.0210 et.al.: Add support for bracketed paste. (Closes: #504244) + * 8.0.0421: Fix display in diff mode when adding a line at the end of a + buffer. (Closes: #846993) + * 8.0.0693 et.al.: Implement a terminal emulator. + * 8.0.0698: Fix a crash on exit when using a Python function from a timer. + (Closes: #868767) + * 8.0.0737: Crash when X11 selection is very big (Closes: #606957) + + [ James McCoy ] + * vim-policy: + + Specify the "addon", not "name", field is used to declare the addon. + Thanks to Reiner Herrmann. + * Merge changes from Ubuntu, dependent on DEB_VENDOR=Ubuntu: + + Remove --disable-python3interp on Ubuntu for vim-basic + + Disable ruby for vim-gtk3 + * d/rules: + + Remove src/po/vim.pot and *.pyc during clean + + Remove explicit setting of SOURCE_DATE_EPOCH since dpkg's pkg-info.mk + provides it. + * debcontrol.vim: + + Add highlighting for Build-(Depends|Conflicts)-Arch + + Fix syntax highlighting of "javascript" section. (Closes: #867307) + * Rewrite d/copyright in machine readable format. (Closes: #819734) + + Properly document xxd's license. (Closes: #776191) + * Mark vim-doc and xxd Multi-Arch: foreign. Thanks to Helmut Grohne for the + patch. (Closes: #852722) + * Declare compliance with policy 4.0.1 + + Change Priority: extra packages to optional + * Reference Python 3 instead of Python in long descriptions. (Closes: + #868020) + * Bump debhelper compat to 10. + * debian/control: + + Remove version constraints that are satisifed in oldstable. + + -- James McCoy <jamessan@debian.org> Sun, 13 Aug 2017 16:06:37 -0400 + +vim (2:8.0.0197-5) unstable; urgency=high + + * Backport upstream patches to fix CVE-2017-11109 (Closes: #867720) + + 8.0.0703: Illegal memory access with empty :doau command + + 8.0.0706: Crash when cancelling the cmdline window in Ex mode + + 8.0.0707: Freeing wrong memory when manipulating buffers in autocommands + + -- James McCoy <jamessan@debian.org> Tue, 11 Jul 2017 23:11:25 -0400 + +vim (2:8.0.0197-4) unstable; urgency=medium + + * Backport upstream patch v8.0.0550 to fix a regression in tag lookups for + ctags-generated emacs style tags files. (Closes: #859426) + * Add Artful Aardvark, jessie-backports-sloppy, and + stretch-backports/security to deb{changelog,sources} syntax files. + * debsources.vim: Require word boundaries around distribution name. + (Closes: #859247) + * Set $TERM to a known sane value when running tests to avoid test failures + due to an unknown $TERM. + + -- James McCoy <jamessan@debian.org> Sun, 23 Apr 2017 08:10:29 -0400 + +vim (2:8.0.0197-3) unstable; urgency=high + + * Backport upstream patches v8.0.0377 & v8.0.0378, to fix buffer overflows + when reading corrupted undo files. (Closes: #856266, CVE-2017-6349, + CVE-2017-6350) + + -- James McCoy <jamessan@debian.org> Mon, 06 Mar 2017 22:33:23 -0500 + +vim (2:8.0.0197-2) unstable; urgency=high + + * Backport upstream patch v8.0.0322, to fix buffer overflow if a spellfile + has an invalid length in it. (Closes: #854969, CVE-2017-5953) + + -- James McCoy <jamessan@debian.org> Sun, 12 Feb 2017 19:56:16 -0500 + +vim (2:8.0.0197-1) unstable; urgency=medium + + [ upstream ] + * 8.0.0190: Improve performance of tag lookup (Closes: #673130) + + -- James McCoy <jamessan@debian.org> Mon, 16 Jan 2017 20:26:10 -0500 + +vim (2:8.0.0134-1) unstable; urgency=medium + + * Merge upstream tag v8.0.0134 + * Bump minimum version of debhelper for --dbgsym-migration option. (Closes: + #846183) + * debian/rules: Remove '=' from "define" directive to maintain compatibility + with make < 3.82. (Closes: #846312) + * syntax/debcontrol.vim: Add sections for Rust and JavaScript. Thanks to + Josh Triplett for the patch! (Closes: #847539) + * Add an (old) NEWS.Debian entry describing the switch from py2 -> py3 for + Vim's python language bindings. + + -- James McCoy <jamessan@debian.org> Wed, 14 Dec 2016 22:33:53 -0500 + +vim (2:8.0.0095-1) unstable; urgency=high + + * Merge upstream tag v8.0.0095 + + 8.0.0056: Only allow valid characters in 'filetype', 'syntax' and + 'keymap'. (CVE-2016-1248) + + 8.0.0089: Fix problems with Gtk 3.22.2. This replaces the proposed + patches applied earlier. (#842070) + + -- James McCoy <jamessan@debian.org> Tue, 22 Nov 2016 13:23:07 -0500 + +vim (2:8.0.0049-1) unstable; urgency=medium + + * Merge upstream tag v8.0.0049 + + 8.0.0038: Define OPEN_CHR_FILES for kFreeBSD to fix Test_read_fifo_utf8 + test failure. (Part of #827319) + * Disable Perl bindings for kfreebsd-* until #827319 is resolved since the + FTBFS was blocking bootstrapping of kfreebsd systems. + * Add Zesty Zapus to deb{changelog,sources} syntax files + * Cherry-pick two proposed patches to fix vim-gtk3's widget sizing, while + upstream Vim and Gtk figure out what the right fix is. (Related to + #842070) + + -- James McCoy <jamessan@debian.org> Sat, 12 Nov 2016 13:17:06 -0500 + +vim (2:8.0.0022-1) unstable; urgency=medium + + * syntax/debsources: Recognize https URLs. Thanks to Joe Stein for the + patch! + * Add information about defaults.vim to NEWS.Debian and /etc/vim/vimrc. + (Closes: #837761) + * Update vim-tiny patch to not source defaults.vim when vim.tiny is invoked + as vi. + * Bump priority of vim-tiny's vi alternative, so it's higher than e3vi. + (Closes: #839265) + + -- James McCoy <jamessan@debian.org> Tue, 04 Oct 2016 23:34:23 -0400 + +vim (2:8.0.0003-1) unstable; urgency=medium + + [ upstream ] + * Vim 8 released! + * v8.0.0003: Fix test failures on big-endian architectures. + + -- James McCoy <jamessan@debian.org> Mon, 12 Sep 2016 21:54:12 -0400 + +vim (2:7.4.2347-1) unstable; urgency=medium + + [ upstream ] + * Fix test failure due to relying on modelines. (Closes: #837130) + + [ James McCoy ] + * Move xxd into its own package. This allows other packages to express a + relationship on xxd itself, rather than vim-common, and also enables + turning vim-common into an Arch: all package. + * Remove dpkg-dev Build-Depends, since the version is satisifed prior to + oldstable. + + -- James McCoy <jamessan@debian.org> Sat, 10 Sep 2016 23:35:08 -0400 + +vim (2:7.4.2330-1) unstable; urgency=medium + + [ upstream ] + * Highlighted changes: + + 7.4.1976: Support 64-bit number variables in VimL. Use has('num64') to + test for presence of the functionality. (Closes: #788055) + + runtime/ftplugin/man.vim: + - Use the width of the current window when formatting a man page. + (Closes: #827634) + + runtime/syntax/rst.vim: + - Use underline for emphasized text. (Closes: #547537) + + runtime/tutor/tutor.es: + - Fix misspelling of seguido. (Closes: #834336) + + [ James McCoy ] + * Switch from Python2 to Python3 language bindings. All packaged + addons which use Python support both 2 & 3. (Closes: #729924) + * Add mips64el as a recognized architecture in debcontrol files. Thanks to + Reiner Herrmann for the patch. (Closes: #830545) + * Update supported Ubuntu releases in debsources files. + * Remove vim-gnome (which uses deprecated gnome2 libraries) in favor of + vim-gtk3. (Closes: #820239) + * Run tests during build targets to avoid test failures related to running + as (fake)root. + + -- James McCoy <jamessan@debian.org> Wed, 07 Sep 2016 22:12:11 -0400 + +vim (2:7.4.1829-1) unstable; urgency=medium + + * Merge upstream tag v7.4.1829 + + 7.4.1713: Force use of X11 backend under Wayland. (Closes: #819954) + + 7.4.1802: Improve handling of long lines in quickfix lists. (Closes: + #815976) + + LogiPat plugin's :ELP command renamed to :LPE, so it doesn't shadow :E. + (Closes: #796075) + + -- James McCoy <jamessan@debian.org> Mon, 09 May 2016 23:06:14 -0400 + +vim (2:7.4.1689-3) unstable; urgency=medium + + * helpztags: Fix regression in previous upload where the doc file isn't + opened, so no tags file is generated. (Closes: #820313) + + -- James McCoy <jamessan@debian.org> Thu, 07 Apr 2016 22:37:20 -0400 + +vim (2:7.4.1689-2) unstable; urgency=medium + + * Stop installing a dangling symlink at + /usr/share/vim/addons/doc/matchit.txt. (Closes: #819796) + * Lintian: + + Provide more details in vim-doc's long description. Thanks to Elimar + Riesebieter for the patch. (Closes: #819733) + * helpztags: + + Don't try to read a file if it can't be opened. (Closes: #819764) + + Don't error if the specified directory doesn't exist. (Closes: #819809) + * Generate vim-policy in a consistent locale. + + -- James McCoy <jamessan@debian.org> Sun, 03 Apr 2016 09:25:18 -0400 + +vim (2:7.4.1689-1) unstable; urgency=medium + + * Merge upstream tag v7.4.1689. + + Highlighted changes: + - 7.4.1142: “:syn iskeyword” command to define the set of keyword + characters for syntax highlighting, rather than changing the buffer's + 'iskeyword' option. + - 7.4.1154 et.al.: Support converting between JSON + and VimL. See json_decode(), json_encode(), js_decode(), and + js_encode(). + - 7.4.1169 et.al.: Support async communication with external processes + using the new channel and job features. + - 7.4.1384 et.al.: Provide native support for managing Vim + addons/packages with the :packadd command and 'packpath' option. + - 7.4.1402: GTK3 GUI support + - 7.4.1578: Support running a function on a periodic basis with the + timer_start()/timer_start() functions. + - runtime/syntax/sh.vim + + Fix incorrect highlighting when case/esac are embedded in a word. + (Closes: #818137) + - runtime/syntax/sshdconfig.vim + + Update with recent keywords, including VersionAddendum. (Closes: + #776834) + * Add a vim-gtk3 package. (Closes: #815750) + * Improve reproducibility of Vim builds. (Closes: #787327) + + Use $SOURCE_DATE_EPOCH to set the compilation time displayed in :version + + Set a static value for configure's --with-compiledby argument + * Migrate to automatic -dbgsym packages + * Declare compliance with Policy 3.9.7, no changes needed. + * Stop installing empty icon directories in vim-common. Thanks to Elimar + Riesebieter for the patch. (Closes: #819653) + + -- James McCoy <jamessan@debian.org> Thu, 31 Mar 2016 21:57:48 -0400 + +vim (2:7.4.963-1) unstable; urgency=medium + + * Merge upstream tag v7.4.963. + + Remove merged patches: + - Typo in Spanish translation of swapfile recovery. + + Highlighted changes: + - 7.4.849: New Insert mode command to maintain the undo sequence across + cursor movements (c.f., :help i_CTRL-G_U). + - 7.4.858: New quickfix-related commands (:ldo, :lfdo, :cdo, and :cfdo). + - indent/yaml.vim: Maintain indent of mapping key when mapping is + contained in a list. (Closes: #713066) + - 7.4.941: New 'tagcase' option to control whether tag searches are case + insensitive. + * Rewrite vim-tiny's help.txt. + + Clarify the reasoning for the package and why the help isn't available. + + Explicitly mention what the more featureful Vim packages are. + + Point to vimhelp.appspot.com for online help, since it is better kept + updated. + * Update Vcs-* URLs to point to Git. + * Install upstream's patchlist as the changelog. (Closes: #622827) + * Fix a typo in vim-policy. Thanks to Jakuyo Friel for the patch. (Closes: + #773531) + * Fix FTBFS when running “dpkg-buildpackage -A”. (Closes: #806875) + * Stop installing menu files. + * Install upstream's desktop files and drop the ones from debian/. + * Mark vim-runtime/vim-gui-common as Multi-Arch: foreign. (Closes: #806535) + + -- James McCoy <jamessan@debian.org> Wed, 09 Dec 2015 23:31:36 -0500 + +vim (2:7.4.826-1) unstable; urgency=medium + + * Merge upstream tag v7-4-826. Remove merged patches. + + Recognize bash completion files for syntax highlighting. (Closes: + #628494) + + Update declared license for xxd. (Closes: #776191) + * Enable <S-Insert> mappings when gvim is started via “:gui”. Based on a + patch from Daniel Shahaf. (Closes: #793781) + + -- James McCoy <jamessan@debian.org> Sun, 16 Aug 2015 22:17:45 -0400 + +vim (2:7.4.712-3) unstable; urgency=medium + + * Change Suggests: ttf-dejavu → fonts-dejavu. (Closes: #783969) + * Welcome, wily werewolf. + * Remove vim-lesstif transitional package. + * Remove obsolete Breaks/Replaces from vim-gui-common. + * Lintian: + + Add override to vim-common for desktop-command-not-in-package, since vim + is provided by the other binary packages. + + Remove spelling-error-in-binary overrides for tEH + + Remove empty /usr/share/pixmaps directory from vim-gui-common + * Declare compliance with policy 3.9.6 + * Fix FTBFS with newer ghostscript by using ps2write device. (Closes: + #785221) + * Make build resilient to changes in the default tcl version. + * Update description of vim-tiny to clarify it only exists to provide the vi + binary for the base install. (Closes: #784268) + + -- James McCoy <jamessan@debian.org> Sat, 13 Jun 2015 01:16:02 -0400 + +vim (2:7.4.712-2) unstable; urgency=medium + + * Add stretch to Debian syntax files. (Closes: #783506) + * syntax/debsources.vim: Recognize all Debian/Ubuntu releases, but highlight + unsupported releases differently. + * Add patch upstream/lcs_space-overflow.patch, which fixes an integer + overflow when determining whether to apply listchar's space setting. This + fixes the test_listchars failure on certain architectures when PIE is + enabled. + + -- James McCoy <jamessan@debian.org> Thu, 30 Apr 2015 20:25:42 -0400 + +vim (2:7.4.712-1) unstable; urgency=medium + + * Merge upstream tag v7-4-712 + + 7.4.586: Remove a cyclic dependency when generating documentation, which + results in unreproducible builds. (Closes: #775562) + + 7.4.609: Use a stack of dicts and lists to be marked for garbage + collection, thus making it iterative instead of recursive. Fixes crash + with some plugins written in other languages (e.g., lua). (Closes: + #778821) + + runtime/syntax/registry.vim: Correct highlighting of comments. (Closes: + #687199) + + runtime/syntax/strace.vim: Highlight 2-digit escape sequences the same + as 1 or 3-digit escape sequences. (Closes: #775113) + * Remove backported patches upstream/v7-4-576.patch and + upstream/netrwSavePosn.patch. + * Add a Build-Conflict for autoconf2.13 to avoid a FTBFS if it's installed. + (Closes: #781031) + + -- James McCoy <jamessan@debian.org> Sat, 25 Apr 2015 09:00:09 -0400 + +vim (2:7.4.488-7) unstable; urgency=medium + + * Backport patch 7.4.576 to fix jarring toggling of 'linebreak' option when + using the c command to change the buffer. (Closes: #774492) + * Backport upstream fix for call to unknown function in NetRW plugin. + (Closes: #768467) + + -- James McCoy <jamessan@debian.org> Tue, 31 Mar 2015 19:30:17 -0400 + +vim (2:7.4.488-6) unstable; urgency=medium + + * Build vim logo from the eps instead of pdf so the svg has the correct + bounding box. Thanks to Simon McVittie for the idea! (Closes: #778477) + * syntax/debchangelog.vim: + + Recognize jessie, jessie-backports, and sid targets + + Recognize binary-only=yes key value in debchangelogHeader + + -- James McCoy <jamessan@debian.org> Sat, 21 Mar 2015 14:24:01 -0400 + +vim (2:7.4.488-5) unstable; urgency=medium + + * Install icons to the proper directory. dh_install doesn't rename files, + even though the last upload pretended it does. + - Use upstream's icons and remove the ones in debian/ + - Add Build-Depends: pdf2svg to create a scalable icon + + -- James McCoy <jamessan@debian.org> Wed, 11 Feb 2015 21:38:10 -0500 + +vim (2:7.4.488-4) unstable; urgency=medium + + * Move vim icon from vim-gui-common to vim-common since both vim.desktop and + gvim.desktop use it. (Closes: #773930) + + -- James McCoy <jamessan@debian.org> Mon, 29 Dec 2014 23:13:17 -0500 + +vim (2:7.4.488-3) unstable; urgency=medium + + * Install icons to /usr/share/icons/hicolor to work around #765069. + (Closes: #768256) + + -- James McCoy <jamessan@debian.org> Sun, 30 Nov 2014 15:08:09 -0500 + +vim (2:7.4.488-2) unstable; urgency=medium + + * Actually fix the Name in vim.desktop. (Closes: #769575) + + -- James McCoy <jamessan@debian.org> Fri, 14 Nov 2014 21:06:27 -0500 + +vim (2:7.4.488-1) unstable; urgency=medium + + * Merge upstream tag v7-4-488 + * Fix the Name in vim.desktop. + + -- James McCoy <jamessan@debian.org> Wed, 22 Oct 2014 21:07:59 -0400 + +vim (2:7.4.481-1) unstable; urgency=medium + + * Merge upstream tag v7-4-481 + + Updated Russian translation of vimtutor. (Closes: #722673) + * syntax/debcontrol.vim: Recognize https URLs for Vcs-Git. (Closes: + #763553) + * debian/rules: Request all hardening features, other than fortify, from + dpkg-buildflags. + * Add codename for Ubuntu's next release, vivid. + * Install a .desktop file for terminal vim. (Closes: #760512) + + -- James McCoy <jamessan@debian.org> Mon, 20 Oct 2014 23:26:20 -0400 + +vim (2:7.4.430-1) unstable; urgency=medium + + * Merge upstream tag v7-4-430 + + 7.4.397: Fix paren matching in zsh scripts. (Closes: #754507) + + Runtime updates: + - Improve highlighting of Python's \N{…} sequences. (Closes: #749175) + * Add jessie release and remove EOLed saucy release from Debian runtime + files. (Closes: #753823) + + -- James McCoy <jamessan@debian.org> Mon, 01 Sep 2014 04:11:24 -0400 + +vim (2:7.4.335-1) unstable; urgency=medium + + * Merge upstream tag v7-4-335 + + Avoid setting buftype=nofile for scp buffers. (Closes: #743136) + + Properly handle scp://user@host/ URLs (Closes: #744111) + * Remove EOLed Quantal release from Debian runtime files. + * Transition from Lua 5.1 to Lua 5.2 + + -- James McCoy <jamessan@debian.org> Thu, 19 Jun 2014 23:02:17 -0400 + +vim (2:7.4.273-2) unstable; urgency=medium + + * syntax/debcontrol.vim: + + Fix architecture orders to work with left-most regex matching. + + -- James McCoy <jamessan@debian.org> Fri, 02 May 2014 00:17:48 -0400 + +vim (2:7.4.273-1) unstable; urgency=medium + + * Merge upstream tag v7-4-273 + * syntax/debcontrol.vim: + + Correctly highlight any-x32 in Architecture field + + Add ppc64el architecture + * syntax/deb{changelog,sources}.vim: + + Add codenames for Ubuntu's development release (devel, utopic) + + -- James McCoy <jamessan@debian.org> Thu, 01 May 2014 21:50:24 -0400 + +vim (2:7.4.253-1) unstable; urgency=medium + + * Merge upstream tag v7-4-253 + + 7.4.252: Clear blink timer after removing it to avoid GLib-CRITICAL + error. (Closes: #743668) + * rules: Explicitly disable SMACK on Linux, in favor of SELinux. + + -- James McCoy <jamessan@debian.org> Mon, 07 Apr 2014 22:47:57 -0400 + +vim (2:7.4.225-1) unstable; urgency=medium + + * Merge upstream tag v7-4-225 + + Patches merged upstream: + - upstream/python-ftplugin-include.patch and + upstream/shadowdir-tests.diff + + netrw: Don't try to access the clipboard when support isn't enabled. + (Closes: #737530) + + 7.4.209: Escape a repeated command when storing it for redo. (Closes: + #739656) + + 7.4.222: Use RbConfig::CONFIG['rubyarchhdrdir'] to allow building Vim + against Ruby 2.x. (Closes: #739125) + + -- James McCoy <jamessan@debian.org> Thu, 27 Mar 2014 22:13:31 -0400 + +vim (2:7.4.161-1) unstable; urgency=medium + + * Merge upstream tag v7-4-161 + + Fix loading of NetRW when editing a directory. (Closes: #732091) + * Update Ubuntu releases in Debian syntax files. + * Add more debian-ports architectures to debcontrol syntax file. (Closes: + #722313) + * ftplugin/debchangelog: Allow changing distribution from UNRELEASED. + (Closes: #734267) + * control: Bump Standards-Version to 3.9.5, no changes needed. + * Add shadowdir-tests.diff to fix building in a shadow build directory. + + -- James McCoy <jamessan@debian.org> Sun, 02 Feb 2014 19:27:58 -0500 + +vim (2:7.4.052-1) unstable; urgency=low + + * Merge upstream tag v7-4-052 + - Remove upstream/python-ftplugin-keywordprg.patch, merged upstream + * debian/watch: Use the pasv option. + * debian/control: Version the ruby1.8{,-dev} Build-Conflicts now that the + Provides: have been dropped. + + -- James McCoy <jamessan@debian.org> Wed, 09 Oct 2013 00:06:41 -0400 + +vim (2:7.4.027-1) unstable; urgency=low + + * Merge upstream tag v7-4-027 + + 7.4.003: Refresh a stale pointer in new regex engine to avoid + dereferencing a freed pointer. (Closes: #722081) + + 7.4.024: Read an undo file owned by the current user, even if that + differs from the owner of the edited file. (Closes: #721944) + + Use old regex engine for yamlBlockMappingKey highlighting to workaround + performance problem with new engine. (Closes: #719510) + + -- James McCoy <jamessan@debian.org> Tue, 17 Sep 2013 20:29:24 -0400 + +vim (2:7.4.000-1) unstable; urgency=low + + * New upstream release. + * Upload to unstable. + * Stop providing /usr/share/vim/vimcurrent. It shouldn't be used by + anything, since it's Debian specific, and the Vim packaging hasn't used it + (other than documenting the location of debian.vim) for years. + * Override spelling-error-in-binary … tEH the. + + -- James McCoy <jamessan@debian.org> Sat, 10 Aug 2013 21:24:02 -0400 + +vim (2:7.4b.004-1) experimental; urgency=low + + * Merge upstream tag v7-4b-004 + + 7.4a.044: Clear window from b_wininfo in win_free(). (Closes: #717529) + * debian/rules: Install Japanese translations of man pages. + * Update path in binaries-have-file-conflict lintian override. + * Use canonical URI for Vcs-*. + + -- James McCoy <jamessan@debian.org> Fri, 02 Aug 2013 22:58:04 -0400 + +vim (2:7.4a.012-1) experimental; urgency=low + + * Merge upstream tag v7-4a-012 + + New NFA regex engine. Vim automatically determines whether to use the + new or old engine based on the pattern. A specific engine can be + forced with the 'regexengine' option or within a pattern using the \%#= + atom. + + Updated Perl syntax files + - Adds support for Perl 5.10 syntax. (Closes: #681606) + - Fixes syntax highlighting when qq{} contains a } character. (Closes: + #598197) + + Fix display of an empty entry in NetRW directory listing. (Closes: + #709101) + + Recognize Ikiwiki's *.mdwn as markdown filetype. (Closes: #672597) + + 7.3.985: Call g_set_prgname() on startup to set a proper WM_CLASS. + (Closes: #639925) + + Source ~/.vim/vimrc or ~/.vim/gvimrc in favor of ~/.vimrc or ~/.gvimrc. + + Update sh syntax file + - Recognize when sh is dash and change the default behavior highlighting + to be POSIX instead of Bourne. (Closes: #712657, #699172) + - Correctly highlight text after a "--". (Closes: #713922) + * debian/rules: Simplify version handling and bump for the pre-release. + * Add shadowdir-fixes.patch, to fix test failures when building in a + shadow directory. + + -- James McCoy <jamessan@debian.org> Fri, 12 Jul 2013 22:30:28 -0400 + +vim (2:7.3.923-3) unstable; urgency=low + + * Build-Conflict against ruby1.8{,-dev} to work around incorrect ruby{,-dev} + Provides (c.f., #710022). + + -- James McCoy <jamessan@debian.org> Sun, 23 Jun 2013 22:12:29 -0400 + +vim (2:7.3.923-2) unstable; urgency=low + + * Fix FTBFS with M-A Python. (Closes: #701513) + + -- James McCoy <jamessan@debian.org> Sun, 26 May 2013 22:18:36 -0400 + +vim (2:7.3.923-1) unstable; urgency=low + + * Merge upstream tag v7-3-923 + + Updated documentation for Python syntax file. (Closes: #613038) + + NetRW no longer creates files in ~/.vim (or ~/.vim itself) if + g:netrw_dirhistmax <= 0. (Closes: #635984) + * Remove EOLed Oneiric and Hardy releases from Debian runtime files. Add + Saucy and wheezy-backports. + * Bump Standards-Version to 3.9.4, no changes needed. + * Recognize “-b $branch” as part of a Vcs-Git field. (Closes: #702751) + + -- James McCoy <jamessan@debian.org> Sun, 05 May 2013 23:07:27 -0400 + +vim (2:7.3.831-1) experimental; urgency=low + + * Merge upstream tag v7-3-831 + + Merged patches: + - upstream/debian-runtime-spell.patch, upstream/if_py-crash.patch, + upstream/netrw-syntax-fix.patch, upstream/remove-py_config.patch + + 7.3.607: Swap fg and bg colors for completion menu. (Closes: #680772) + + 7.3.750: Fix off-by-one error in justify macro. (Closes: #620106) + + 7.3.751: Retry test61 once if it fails. + - Remove the explicit ignoring of test61 failures in debian/rules + * Mark "DM-Upload-Allowed" in debian/control files as an "Error", since the + field is no longer supported by the Debian archives. + * Re-enable vim-gnome on m68k. + * Update Ubuntu release names in Debian runtime files. + + -- James McCoy <jamessan@debian.org> Thu, 21 Feb 2013 22:13:43 -0500 + +vim (2:7.3.547-7) unstable; urgency=low + + * Add vim-lesstif.preinst to handle transitioning /usr/share/doc/vim-lesstif + from a symlink to a directory. (Closes: #700069) + * Add clarification to short description of vim-nox. (Closes: #699780) + + -- James McCoy <jamessan@debian.org> Sat, 09 Feb 2013 18:43:57 -0500 + +vim (2:7.3.547-6) unstable; urgency=low + + * Always enable ACL support. (Closes: #693462) + + -- James McCoy <jamessan@debian.org> Thu, 22 Nov 2012 09:37:52 -0500 + +vim (2:7.3.547-5) unstable; urgency=low + + * Use xz compression for all binary packages. (Closes: #687265) + * Backport patches 7.3.652 and 7.3.661 to fix crash in Python bindings when + GCC 4.7 is used to build Vim. (Closes: #678122) + + -- James McCoy <jamessan@debian.org> Sat, 15 Sep 2012 23:59:18 -0400 + +vim (2:7.3.547-4) unstable; urgency=low + + * Add remove-py_config.patch, removing the dependence on Python's config.c. + (Closes: #681599) + + -- James McCoy <jamessan@debian.org> Mon, 23 Jul 2012 22:55:51 -0400 + +vim (2:7.3.547-3) unstable; urgency=low + + * Add netrw-syntax-fix.patch to fix a syntax error in NetRead's ftp + handling. (Closes: #678513) + + -- James McCoy <jamessan@debian.org> Tue, 26 Jun 2012 19:14:28 -0400 + +vim (2:7.3.547-2) unstable; urgency=low + + * Work around GCC 4.7 optimization bug, #678122, by explicitly using gcc-4.6 + + -- James McCoy <jamessan@debian.org> Thu, 21 Jun 2012 22:28:51 -0400 + +vim (2:7.3.547-1) unstable; urgency=low + + * Merge upstream tag v7-3-547 + * Change ruby(-dev) Build-Depends to use unversioned package names in order + to build with the default ruby version. + * Add spell-check support to Debian control syntax file. + + -- James McCoy <jamessan@debian.org> Wed, 06 Jun 2012 20:20:05 -0400 + +vim (2:7.3.524-1) unstable; urgency=low + + * Merge upstream tag v7-3-524 + + Recognize git commit files in submodules. (Closes: #663735) + + Fix NetRW's munging of options when opening files. (Closes: #661720) + + 7.3.485: Use environment's LDFLAGS when building xxd. (Closes: #663605) + + Update recognized keywords for dircolors syntax. (Closes: #660632) + * Exclude the tools directory from the install. + + Stop shipping scripts which use Perl4 functionality. (Closes: #659431) + + Remove lintian overrides for csh scripts. + + Remove patch debian/awk-shebang.patch + * Remove EOLed Lenny/Maverick releases, add Quantal release to runtime + files. + * Remove upstream/po-syntax-cpo.patch, merged upstream. + * Remove upstream/debian-runtime-*.patch, merged upstream. + * Remove upstream/fr-manpage-fixes.patch, merged upstream. + * Remove upstream/xdefaults-syntax-define.patch, merged upstream. + * Add lintian override for binaries-have-file-conflict. vim-runtime diverts + vim-tiny's doc/help.txt and doc/tags. + * Remove unused menu-icon-missing override. + + -- James McCoy <jamessan@debian.org> Thu, 24 May 2012 21:37:40 -0400 + +vim (2:7.3.429-2) unstable; urgency=low + + * Ignore failures in test61 since it is highly sensitive to timing. + Slow/heavily loaded systems will cause the test to fail. (Closes: + #625941) + * Install bug scripts with correct permissions. + + Use dh_bugfiles to simplify process + + Bump debhelper B-D to >= 7.2.3~ + + -- James McCoy <jamessan@debian.org> Fri, 10 Feb 2012 22:47:19 -0500 + +vim (2:7.3.429-1) unstable; urgency=low + + * Pull upstream tag v7-3-429 + + Updated sshconfig syntax file. (Closes: #594296) + + 7.3.365: Fix crash when using a large Unicode character with syntax + highlighting. (Closes: #657777) + + Updated java indent file handles indentation of annotations. (Closes: + #519240) + * Add new education and introspection sections to debcontrol syntax file. + (Closes: #651381) + * Update vim-common's mime information to handle only having vim-tiny + installed. (Closes: #654674) + + Add test -x /usr/bin/vim for the vim entries. + + Add lower-priority vi entries. + * Use new --enable-fail-if-missing flag to make configure fail if an + interpreter is enabled but configure test fails. + * Add bug script to show what binaries the vi/vim/gvim symlinks point to. + * Only use /u/s/dpkg/default.mk when available. + + Reduce versioned B-D on dpkg-dev + + Manually set relevant makefile variables if file isn't present + * Add alternate libncurses5-dev B-D to ease backporting. + + -- James McCoy <jamessan@debian.org> Sat, 04 Feb 2012 22:04:06 -0500 + +vim (2:7.3.363-1) unstable; urgency=low + + * Pull upstream tag v7-3-363 + + 7.3.358: Fix mouse handling since urxvt support. (Closes: #647055) + * Set vim-lesstif's section to oldlibs, as suggested by + transitional-package-should-be-oldlibs-extra. + + -- James McCoy <jamessan@debian.org> Wed, 30 Nov 2011 21:53:43 -0500 + +vim (2:7.3.346-1) unstable; urgency=low + + * Pull upstream tag v7-3-346 + + 7.3.337: Redraw the screen after resizing the terminal. (Closes: + #644668) + + 7.3.343: Add mouse support for urxvt. + + 7.3.344: Use read()/write() instead of fputs()/fread() to detect when + the child GUI process has started. (Closes: #644639) + * Don't build vim-gnome on m68k, since the dependencies aren't available. + * Update Debian runtime files for Precise Pangolin. (Closes: #644489) + * Use correct DEB_VERSION_* make variable for update-orig target. + * Also use CPPFLAGS and LDFLAGS from /u/s/dpkg/buildflags.mk + * Change libncurses5-dev B-D to libtinfo-dev. + * Remove patch de.po-lesen.patch, merged upstream. + * Set DEB_BUILD_MAINT_OPTIONS=hardening=-fortify so we don't override + upstream's handling. + * Bump Standards-Version to 3.9.2, no changes needed. + + -- James McCoy <jamessan@debian.org> Thu, 20 Oct 2011 22:17:16 -0400 + +vim (2:7.3.333-1) unstable; urgency=low + + * Pull upstream tag v7-3-333 + + 7.3.318: Fix behavior of C on empty last line. (Closes: #642432) + + 7.3.323: Recognize a few more patterns for GCC error messages. (Closes: + #621693) + + 7.3.333: Handle multi-byte characters when using `.' to repeat a + command. (Closes: #632542) + * debian/rules: Remove debian/lintian/vim in clean-vim-basic + * debian/rules: Include makefiles from dpkg-dev. + + Bump dpkg-dev versioned B-D >= 1.16.1 + + -- James Vega <jamessan@debian.org> Tue, 04 Oct 2011 21:48:44 -0400 + +vim (2:7.3.315-1) unstable; urgency=low + + * Pull upstream tag v7-3-315. + + 7.3.295: When select() is interrupted loop and try again. (Closes: + #627376) + + 7.3.300: Python doesn't parse multi-byte argument correctly. (Closes: + #638375) + * Recognize armhf as an architecture in debcontrol files. (Closes: #638873) + * Fix typo in vim policy. Thanks to Jakub Wilk for the patch. (Closes: + #640042) + * Add GenericName field to desktop file. (Closes: #641037) + * Use versioned ruby binary name to ensure we're getting the correct build + flags. + + -- James Vega <jamessan@debian.org> Sun, 18 Sep 2011 22:17:17 -0400 + +vim (2:7.3.280-1) unstable; urgency=low + + * Pull upstream tag v7-3-280. + + Remove patches/crontab-syntax-case-ignore, merged upstream. + + Remove patches/debcontrol-syntax-multiarch, merged upstream + + Remove patches/dosini-syntax-hash, merged upstream + + 7.3.261: Parse GCC 4.5+ "In file included from" messages correctly when + using quickfix. (Closes: #621693) + * debian/control: + + Add vim-lua Provides to packages which are built with lua bindings. + + Add Lua to long description for the packages which provide the bindings. + * Drop +hg~$hash from the version string now that upstream is tagging the + minor updates. + * Update Debian/Ubuntu codenames in debchangelog/debsources syntax files. + (Closes: #624686) + * Add support for architecture wildcards in debcontrol syntax file. Thanks + to Jakub Wilk for the patch. (Closes: #624805) + * Remove path and extension from Icon key in the desktop file. Thanks to + Michael Bienia for the patch. (Closes: #624688, LP: #740842) + * debian/watch: Change dversionmangle to just drop the patch version. + * Make the leading XC- optional for the Package-Type header in debcontrol + syntax file. Thanks to Guillem Jover for the patch. (Closes: #628763) + * Improve syntax highlighting for automake files. Based on a patch by + Guillem Jover. (Closes: #628759) + + -- James Vega <jamessan@debian.org> Mon, 15 Aug 2011 06:35:08 -0400 + +vim (2:7.3.154+hg~74503f6ee649-2) unstable; urgency=low + + * Remove upstream/Makefile-parallel.patch as many parallel invocations of + upstream's Makefile may result in multiple instances of cp trying to + exclusively open src/auto/config.mk. + * debian/rules: Add a src/auto/config.mk target which all configure-* + targets have as a pre-requisite. + + -- James Vega <jamessan@debian.org> Sun, 10 Apr 2011 17:43:21 -0400 + +vim (2:7.3.154+hg~74503f6ee649-1) unstable; urgency=low + + * Pull patches 036 - 154. (Closes: #608390) + + 7.3.042: Clear the spell checking info only when clearing the options + for a buffer. (Closes: #600688) + + 7.3.088: Fix a sporadic crash when using Ruby bindings. (Closes: + #614336) + + 7.3.091: Don't write special K_IGNORE codes when recording a Vim + session. (Closes: #608242) + * debian/watch: Adjust dversionmangle to handle the hg naming. + * Add upstream/es.po-recover.patch, which corrects the translation of the + swap file recovery prompt. Thanks to Vicente Couce Díaz for the patch. + (Closes: #606947) + * debian/rules: + + Remove -Wl,--as-needed since upstream now uses that when available. + + Disable dynamic loading of language bindings until a more robust method + of handling their dependencies is determined. (Closes: #611573) + * Remove vim-lesstif package in favor of the new vim-athena package. + * Add upstream/pythoncomplete-autoload-init.patch, which ensures PyParser's + parserline variable is initialized. Thanks to John Eikenberry for the + patch. (Closes: #608420) + * Bump debhelper compatibility to 7. + + Use dh_prep instead of dh_clean -k. + + Bump debhelper Build-Depends to >= 7. + * debian.vim: Remove BufRead autocmd which was incorrectly setting + filetype=mail for reportbug.conf. Reportbug's temp files are always + reportbug-*. (Closes: #621798) + * Add upstream/debcontrol-syntax-multiarch.patch, which adds syntax + highlighting of Multi-Arch fields in debian/control. Thanks to Thomas + Preud'homme for the patch. (Closes: #621098) + * debian/control: + + Remove python3-dev Build-Depends since python3interp can only be enabled + if dynamically loading the language binding libraries. + + Change ruby Build-Depends to ruby1.8 since the unversioned packages are + going away. + * Add upstream/Makefile-parallel.patch, which adds the "shadow" target to + the top-level Makefile so src/config.mk.dist is properly copied to + src/auto/config.mk before invoking src/Makefile. This fixes parallel + builds since config.mk.dist was introduced. + + Update Lintian overrides for the consistent path names in 2.5.0. + + -- James Vega <jamessan@debian.org> Sat, 09 Apr 2011 19:18:27 -0400 + +vim (2:7.3.035+hg~8fdc12103333-1) unstable; urgency=low + + * Pull patches 001 - 035. + + More robust YAML highlighting. (Closes: #535682) + * debian/rules: + + Stop overriding CFLAGS on the command-line when invoking make. Upstream + enforces an upper-limit of 1 for _FORTIFY_SOURCE due to the use of + flexible arrays in nested structs, which improperly cause Vim to crash + with _FORTIFY_SOURCE=2. + + Use DEB_HOST_ARCH_OS instead of DEB_HOST_GNU_SYSTEM to determine whether + Linux-specific functionality is enabled. + + Use dpkg-vendor to change build configuration when building on Ubuntu. + Thanks to Michael Bienia for the patch. + * Make helpztags capable of generating tags files for non-English help + files. (Closes: #600248) + * Debian runtime: + + Add natty as a recognized distribution. (Closes: #600560) + + Add metapackages as a recognized section. (Closes: #600562) + + Remove etch as a recognized distribution. + * debian/control: Add dpkg-dev (>= 1.15.1) Build-Depends for dpkg-vendor. + + -- James Vega <jamessan@debian.org> Mon, 25 Oct 2010 00:48:58 -0400 + +vim (2:7.3.000+hg~ee53a39d5896-1) unstable; urgency=low + + * New upstream release. + * debian/rules: + + Explicitly use the dynamic loading Python interfaces. + + Remove cleanup from clean target which are now properly handled by + upstream's Makefile. + * Update version information in documentation. + + -- James Vega <jamessan@debian.org> Sun, 15 Aug 2010 17:34:02 -0400 + +vim (2:7.3f.20100812+hg~20e83abf88b1-1) experimental; urgency=low + + * Merge latest 7.3f pre-release. + + Correctly restore multi-byte terminal titles when exiting Vim. (Closes: + #558153) + + Highlight text inside math zones correctly for tex files. (Closes: + #509908) + + Recognize nested cite regions in tex files. (Closes: #444288) + + Support syntax highlighting of bash's $"". (Closes: #473736) + * Patches merged upstream: + + perl-indent-block.patch + + logcheck-ftplugin.patch + + tex-syntax-verbatim-spell.patch + * Enable Lua scripting. + + Add liblua5.1-0-dev and lua5.1 to Build-Depends. + + Enable lua interface via dynamic loading. + * Switch Perl interface to dynamic loading. + * debian/rules: Prefer running tests with the vim-nox binary if it's + available. + * Bump Standards-Version to 3.9.1.0 -- no changes needed. + + -- James Vega <jamessan@debian.org> Thu, 12 Aug 2010 20:01:43 -0400 + +vim (2:7.3b.20100720+hg~7b7508ee56f1-1) experimental; urgency=low + + * Merge 7.3b pre-release. + + Don't run autocommands when being killed to avoid overrunning the stack. + (Closes: #580961) + + Detect when the recovered buffer matches the on-disk file and notify the + user. (Closes: #89359) + + Update CMake runtime files. (Closes: #463715) + + Correctly set timestamp for X selection transfers. (Closes: #577035) + + Improve 'cindent's handling of javascript. (Closes: #588875) + + Correctly displays characters inserted via digraph sequences which wrap + to a new line. (Closes: #442184) + * Patches merged upstream: + + it-manpage-fixes.patch + + lang-breaks-floating-point.patch + + python-modlibs.patch: + - Remove autoconf Build-Depends as configure.in isn't being patched + anymore. + - Remove autoconf-stamp pre-requisite for configure-stamp-% target. + * Update debian/rules to handle the snapshot versioning. + * Enable Python3 language interface. + + Add python3-dev to Build-Depends. + + Pass --enable-python3interp to configure when building variants with + language interfaces enabled. + + -- James Vega <jamessan@debian.org> Wed, 21 Jul 2010 00:12:19 -0400 + +vim (2:7.2.445+hg~cb94c42c0e1a-1) unstable; urgency=low + + * debian/control: + + Use Breaks instead of Conflicts for the gvimtutor move. + + Use linux-any wildcards for linux-specific Build-Depends. (Closes: + #587866) + + Bump Standards-Version to 3.9.0.0. + * Pull patches 439 - 445. + * runtime/ftplugin/debchangelog.vim: Use “silent!” to avoid errors when + disabling the menu. Thanks to Jan Christoph Ebersbach for the patch. + + -- James Vega <jamessan@debian.org> Sun, 11 Jul 2010 22:14:53 -0400 + +vim (2:7.2.438+hg~d44112feb815-5) unstable; urgency=low + + * Rework the diversion handling again. + + vim-runtime.preinst: Add diversion on major version upgrades. + + vim-runtime.postrm: Remove old diversion on major version upgrades. + + vim-runtime Breaks vim-tiny less than the current source version. + + -- James Vega <jamessan@debian.org> Sun, 13 Jun 2010 21:40:37 -0400 + +vim (2:7.2.438+hg~d44112feb815-4) unstable; urgency=low + + * vim-runtime.preinst: Use the right function name for removing diversions + when upgrading across major versions. + + -- James Vega <jamessan@debian.org> Sat, 12 Jun 2010 17:46:32 -0400 + +vim (2:7.2.438+hg~d44112feb815-3) unstable; urgency=low + + * vim-runtime.preinst: + + Remove code handling the Etch->Lenny diversion fixup. + + Add handling of diversions when upgrading across major versions. + * vim-runtime.postrm: Remove diversions on abort-install and disappear. + * Move gvimtutor to vim-gui-common from vim-runtime. (LP: #484851) + * debian/control: Remove versioned relationships which are satisified in + Lenny. + + -- James Vega <jamessan@debian.org> Sat, 12 Jun 2010 10:09:56 -0400 + +vim (2:7.2.438+hg~d44112feb815-2) unstable; urgency=low + + * Fix FTBFS with parallel builds and using the autoconf target to update the + configure script. + + -- James Vega <jamessan@debian.org> Sat, 29 May 2010 00:14:01 -0400 + +vim (2:7.2.438+hg~d44112feb815-1) unstable; urgency=low + + * Pull patches 437 - 438. + + 7.2.438: Fix crash when running “vim -r”. (Closes: #583122) + * Cherry-pick upstream/lang-breaks-floating-point.patch from upstream to + prevent floating point functionality from breaking when the :lang command + is issued. (Closes: #582421) + * Fix building against Debian's Python 2.6 package. (Closes: #566842) + + Cherry-pick upstream/python-modlibs.patch from upstream. + + debian/control: Add autoconf to Build-Depends. + + debian/rules: Re-generate configure at build time and remove on clean. + + -- James Vega <jamessan@debian.org> Wed, 26 May 2010 19:34:27 -0400 + +vim (2:7.2.436+hg~e12b9d992389-1) unstable; urgency=low + + * Pull patches 331 - 436. + + 7.2.367: Make xxd follow documented behavior when using “-r -p”. + (Closes: #567041) + + 7.2.405: Re-enable default value for IncSearch to allow highlighting of + matched text when using :substitute's c flag. (Closes: #572994) + + 7.2.413: Largefile support for all Vim packages. (LP: #128494) + + 7.2.426: Require literal commas be escaped in 'langmap'. (Fixes + #233008, obviating upstream/langmap-comma-parsing.patch) + + 7.2.429: Specifically check for ENOENT to decide a file doesn't exist. + Also fixes the check for EFBIG/EOVERFLOW. (Closes: #430205, #139510) + + Updated runtime files: + - Fix sqlcomplete's <Left>/<Right> maps so they don't interfere with + normal usage. (Closes: #560083) + - Recognize Perl 5.10's “state” keyword. (Closes: #499644) + - Handle a wider variety of quoting operators in Perl. (Closes: + #561080) + * debian/control: + + Update Vcs-* to point to the Mercurial repository. + + Bump Standards-Version to 3.8.4, no changes needed. + * vim-policy: Update links to package descriptions and repository. + * Reword presubj to provide a few methods for narrowing down the bug's + cause. + * debian/rules: + + Specify STRIP=: when running upstream's install targets to prevent + upstream's automatic stripping. + + Pass the --with-modified-by to the Debian Vim maintainers list. + + Remove git helper targets. + + Remove get-orig-source target and related variables, since we're just + using the upstream Mercurial repository. + * debian/source/format: Switch to “3.0 (quilt)”. + * debian/README.source: Update description according to the change to + Mercurial and use of “3.0 (quilt)” source format. + * runtime/ftplugin/debchangelog.vim: Update completion of Ubuntu bugs based + on a patch from Michael Bienia. (Closes: #566841) + * runtime/syntax/{debchangelog,debsources}.vim: Remove intrepid and add + maverick to the set of Ubuntu releases. + * Use case-insensitive matching for month and day of week names in crontab's + syntax file. Thanks to Chris Butler for the patch. (Closes: #568378) + + -- James Vega <jamessan@debian.org> Tue, 18 May 2010 18:40:17 -0400 + +vim (2:7.2.330-1) unstable; urgency=low + + * [34a85b6] Update README for patches 285 - 330 + - [1aee41b] [7.2.294] when using TEMPDIRS dir name could get too long + (Closes: #544682) + - [f3ea2c2] [7.2.300] file descriptors not closed when executing external + command (Closes: #290507) + - [f3ce928] [7.2.324] a negative column argument in setpos() may cause a + crash (Closes: #563071) + * [fd76420] Sync runtime files + - NetRW updated to handle 'equalalways' being set, but window sizes not + being equal. (Closes: #346089) + * debian/control: + - [49f131e] Add Depends: ${misc:Depends} to all binary stanzas. + - [8973628] Bump Standards-Version, no changes required + - [12ac9a3] Remove Pierre Habouzit from Uploaders. + + -- James Vega <jamessan@debian.org> Thu, 14 Jan 2010 00:21:04 -0500 + +vim (2:7.2.284-1) unstable; urgency=low + + * syntax/debcontrol.vim: + - [b997413] Add highlighting of Breaks field (Closes: #541989) + - [05a38bf] Recognize lpia and kopensolaris-i386. (Closes: #543207) + * [a85b832] Update README for patches 246 - 259 + - [669e098] [7.2.256] GTK font dialog doesn't have a default when + 'guifont' not set (Closes: #307158) + - [f4ed8fc] [7.2.257] GTK 2.17: lots of assertion error messages (Closes: + #545168) + * [83583c3] Add Ubuntu's next release, lucid, to the Debian-related runtime + files. + * [87f3b00] update-runtime: Use -A option for git-add so deleted files + are committed. + * [60cbb45] Sync runtime files + - Updated remind.vim syntax file. (Closes: #536770) + - Fix typos in Japanese vimtutor. (Closes: #539577) + * [96dca67] Move html docs from /u/s/d/vim-common/html to /u/s/d/vim- + doc/html. + * [9fec1cd] Use usr_toc.html for the usermanual Index page. + * [fbacb18] Update README for patches 268 - 284 + - [76d3dad] [7.2.283] GTK: changing font doesn't keep the window maximized + (Closes: #466088) + * [6e51684] debsources.vim: Recognize rc-buggy (alias for experimental). + (Closes: #553525) + + -- James Vega <jamessan@debian.org> Sun, 08 Nov 2009 16:51:59 -0500 + +vim (2:7.2.245-2) unstable; urgency=low + + * [5263ec7] Add Suggests: indent to vim-tiny since it will invoke indent + when the user tries to re-indent text without 'equalprg' set. (Closes: + #531647) + * [f24fadd] Restore previous behavior of Vim looking for its (g)vimrc in + $VIM for non vim-tiny packages. Only vim-tiny will look in /etc/vimrc. + + -- James Vega <jamessan@debian.org> Thu, 30 Jul 2009 16:14:44 +0200 + +vim (2:7.2.245-1) unstable; urgency=low + + [ James Vega ] + * debian/rules: + - [b131ea4] Remove SHELL=/bin/bash (again) along with the bashisms + - [ac8c907] Build Vim to look for its (g)vimrc at /etc/vim/(g)vimrc, not + in $VIM. This allows Vim to find the files even if /usr isn't mounted, + in preparation for moving vim-tiny to /bin. + - [24ab3e8] Remove calls to dh_desktop since desktop files are now handled + by triggers. + - [67f3b5b] Only install the UTF-8 versions of the man pages (Closes: + #527744) + * Debian-related runtime files: + - [3071077] Remove gutsy as a valid distribution -- EOLed. + - [be3e3b7] Add avr32 as a valid architecture. (Closes: #528438) + - [1e21fa5] Fix the upload target highlighting so experimental isn't + flagged as an error. (Closes: #532027) + - [9ed9ffd] Syntax highlight X[SB]-Python-Version and + XSBC-Original-Maintainer. (Closes: #536657) + - [ab86bac] Properly highlight comments in multi-line fields in + debian/control. + * [ea1da8a] Update README for patches 149 - 191 + * [f0b6a54] Update README for patches 192 - 196 + * [6c7d809] Update README for patches 197 - 209 + * [7489ef5] vim-variant.prerm: Cleanup of mis-handled alternatives is + no longer needed + * [7be3c83] vim-variant.postinst: Remove directory->symlink code from + Etch + * Lintian cleanups: + - [0be1067] debian/control: Remove Priority fields from binary package + stanzas if they're the same as the source package stanza. + - [bfba0d4] debian/control: Add version for debhelper Build-Depends + - [6fb245c] debian/control: Remove version for make Build-Depends + - [d62624b] debian/control: Drop make from Build-Depends since we the + version we were Build-Depending on is available in Lenny and it is a + build-essential package. + - [2fd98ed] Use “set -e” instead of passing -e on the shebang line for + maintainer scripts. + - [1759cb6] Fix hyphen-used-as-minus-sign in French man pages + - [a749e25] Fix hyphen-used-as-minus-sign/manpage-has-errors-from-man in + Russian man pages + - [b9533d9] Fix hyphen-used-as-minus-sign in English man pages + - [64aeabe] Fix manpage-has-errors-from-man in Polish man pages + - [7125002] Fix hyphen-used-as-minus-sign in Italian man page + - [4f9d282] Install upstream's README file which describes the patches + made since the last major upstream release as the upstream changelog. + * [fe81bdf] Restrict spell checking in matlab filetype to + strings/comments (Closes: #509123) + * [567c06a] Add debian/update-runtime script to automate syncing the latest + runtime files from upstream's ftp site. + * [6082754] Update README for patches 210 - 239 + - [ef67fb5] [7.2.221] X cut_buffer0 text may be used in the wrong encoding + (Closes: #531372) + * [f8033cf] Sync runtime files from upstream's ftp + - Support automatically reading/writing lzma files (Closes: #535665) + * [8132670] Make NRead's behavior for HTTP consistent across backends. They + will all download source by default but some can be configured to download + rendered text. (Closes: #525422) + * [cb968f3] Update README for patches 240 - 245 + * [e1e7abe] Sync runtime files from upstream's ftp + - Add LocalCommand keyword to sshconfig.vim (Closes: #536299) + + [ Stefano Zacchiroli ] + * [5f48b8d] Removing myself from Uploaders list. + + -- James Vega <jamessan@debian.org> Wed, 29 Jul 2009 20:18:17 +0200 + +vim (2:7.2.148-2) unstable; urgency=low + + * [0657c8d] debian/rules: SHELL really does need to be bash... + + -- James Vega <jamessan@debian.org> Sat, 18 Apr 2009 21:21:30 -0400 + +vim (2:7.2.148-1) unstable; urgency=low + + * [a97ec6d] Remove transitional vim-{full,perl,python,ruby,tcl} + packages as they were simply needed for Etch -> Lenny transitions. + * debian/control: + - [d92f9ec] Set vim-dbg to Section: debug to match the override. + - [5677315] Bump S-V to 3.8.1.0; no changes needed. + * syntax/debcontrol.vim: + - [8089fae] Update list of valid sections. (Closes: #520041) + - [2301bbd] Add kfreebsd-amd64 to architecture list. + * [5474b86] syntax/debsources.vim: Enable spell-checking only for + comments + * [33a8ff5] helpztags: Sanity check filenames being processed. + (Closes: #523963) + * [502102f] Update README for patches 131 - 148 + - [f4547c6] [7.2.147] cursor in wrong position after Tab for small version + (Closes: #506658) + * [ab97c3c] Sync runtime files from upstream. + - Correct checks which determine whether to use the c filetype for header + files. (Closes: #524338) + - Properly escape filenames when deleting a file from NetRW. + (CVE-2008-6235) + * [1baf458] Add karmic as a valid distribution for Debian-related + runtime files. + * debian/rules: + - [e8715d6] Remove stale comment and unnecessary use of bash as $SHELL + - [b11bf9f] Build vim.pot for translations. + - [665588f] update-orig will tag/archive either the upstream or + upstream-runtime branch as the upstream source based on whether there + are differences between the two. + * [fd87319] compiler/javac.vim: Remove automatic appending of filename + to compiler command as that removes flexibility from the user. Re-opens + #408338. + * [5ef47fb] README.source: Update text to match current practice regarding + generating the orig.tar.gz and branch merging. + + -- James Vega <jamessan@debian.org> Sat, 18 Apr 2009 15:40:09 -0400 + +vim (2:7.2.130-1) unstable; urgency=low + + * [3694d28] Update README for patches 80 - 093 + * [7a0baa7] update-patches: Redirect `which' output to /dev/null + * [6313a2e] Remove sarge and add squeeze to the Debian syntax files + * [5623ecb] Update README for patches 94 - 108 + * [a80edd8] syntax/fstab.vim: Recognize ext4 related options (Closes: + #512550) + * [813748e] Update README for patches 109 - 130 + - [9cff935] [7.2.130] Vim may haing until CTRL-C is typed when using + CTRL-Z (Closes: #516580) + + -- James Vega <jamessan@debian.org> Thu, 05 Mar 2009 08:58:23 -0500 + +vim (2:7.2.079-1) unstable; urgency=low + + * [4d191a4] Update README for patches 50 - 065 + * [37bd8e4] Update README for patches 66 - 079 + - [43035e4] [7.2.068] error when Emacs tags file line is too long (Closes: + #507116) + * debian/update-patches: + - [38e4f12] die if lftp isn't installed + - [fe1a8f1] Set GIT_AUTHOR_DATE when committing upstream patches + * [b5182c2] Fix a few typos in the French translation (Closes: + #511002) + * [75a19d8] vim-runtime: Remove old version diversions in postinst + (Closes: #503757) + * [b170d58] debian/rules: Call dh_desktop for vim-gui-common + + -- James Vega <jamessan@debian.org> Sun, 11 Jan 2009 13:25:53 -0500 + +vim (2:7.2.049-2) unstable; urgency=low + + * [444b68d] syntax/python.vim: Add missing contained keyword for + pythonDecoratorName (Closes: #504510) + + -- James Vega <jamessan@debian.org> Sun, 30 Nov 2008 12:42:01 -0500 + +vim (2:7.2.049-1) unstable; urgency=low + + [ James Vega ] + * [9525410] Remove EOLd feisty and add jaunty to + syntax/{debchangelog,debsources}.vim + * [c154fa3,606fc00] Update README for patches 026 - 049 + * [233b1c9] Add recognition of PRUNENAMES variable to syntax/updatedb.vim + (Closes: #504084) + * [f7bfa57] Don't install vim alternatives for vim-tiny. vim-tiny is built + to act like vi, so the vim alternative just causes more confusion than + it's worth (by default). + * [f0116b4] Make vim-runtime Conflict vim-tiny << ${source:Version} to + ensure diversions don't cause problems when upgrading to a new major + upstream version. (Closes: #503757) + * [401c913] Include rgb.txt in vim-runtime (Closes: #505069) + * [045810d] Fix a typo in ftplugin/gitcommit.vim's comments... (Closes: + #505165) + * [b4fe540,3454e66] Correctly highlight Python decorator names. (Closes: + #504510) + + [ Stefano Zacchiroli ] + * [64d3690] policy: bump version and copyright year + + -- James Vega <jamessan@debian.org> Tue, 25 Nov 2008 23:38:38 -0500 + +vim (2:7.2.025-2) unstable; urgency=low + + * Remove "deprecated" warnings about (g)vimrc.local from /etc/vim/(g)vimrc. + * src/if_python.c: Strip empty directories from Python's sys.path to prevent + Vim from using its current working directory as a module import path. + (Closes: #493937) + * debian/rules: Do not run tests in parallel as that may interfere with + their results. + + -- James Vega <jamessan@debian.org> Mon, 20 Oct 2008 12:13:42 -0400 + +vim (2:7.2.025-1) unstable; urgency=low + + [ James Vega ] + * New upstream patches (011 - 025), see README for details. + * debian/update-patches: + - Clear $snapshot since 7.2 was released + - Handle the -- arg that git-sh-setup adds. + - Adjust git-sh-setup usage for git 1.6. + * Add logcheck ftplugin/detection to set tw=0. (Closes: #382986) + * Fix a typo in the Spanish vimtutor. (Closes: #495298) + * Lintian fixes: + - Remove gvim.desktop's "Encoding" key. + - Add #DEBHELPER# to vim-common.preinst. + - Add "set -e" to the maintainer scripts which were lacking it. + * debian/rules: Remove the phony install-stamp target. Thanks to Bernhard + Link for pointing this out. + * debian/control: Remove unnecessary lynx Build-Depends. + * debian/policy/Makefile: Use $(INSTALL_STUFF) to refer to the generated + files in all targets. + * debian/runtime/vimrc.in: + - Use lastest last-position-jump snippet and keep it on one line + - Remove the "in terminals" qualification of the 'mouse' option + * debian/runtime/debian.vim: Set the papersize without using the shell. + Thanks to Matt Wozniski for the idea. + * debian/vim-runtime.preinst.in: Actually populate $inst and compare it + against a valid state. + * runtime/ftplugin/perl.vim: Remove Debian-specific keywordprg setting since + upstream added their own. + + -- James Vega <jamessan@debian.org> Sun, 12 Oct 2008 15:16:18 -0400 + +vim (2:7.2.010-2) unstable; urgency=low + + * src/normal.c: Only use the word under the cursor when constructing the + 'keywordprg' command. + * debian/control: Remove unnecessary lynx Build-Depends. + * Add missing "set -e" to vim-common and vim-runtime maintainer scripts. + + -- James Vega <jamessan@debian.org> Fri, 03 Oct 2008 12:03:03 -0400 + +vim (2:7.2.010-1) unstable; urgency=low + + * New upstream patches (1 - 10), see README.gz for details. + - 7.2.010 correctly escapes the visually selected text used by the K + command. (CVE-2008-4101, Closes: #500381) + * Add note to NEWS about how to re-enable filetype plugins. + + -- James Vega <jamessan@debian.org> Sat, 27 Sep 2008 14:56:03 -0400 + +vim (2:7.2.000-3) unstable; urgency=low + + * Add vim-runtime.preinst to handle removing /etc/vim/vimrc.tiny when + upgrading to 1:7.1.293-2 or later. The conffile was moved to vim-tiny and + therefore needs to be removed before the new vim-tiny is installed so dpkg + forgets about it. (Closes: #499451) + + -- James Vega <jamessan@debian.org> Mon, 22 Sep 2008 02:01:47 -0400 + +vim (2:7.2.000-2) unstable; urgency=low + + * src/main.c: After further discussion with upstream, revert behavior of + -N/-C causing (no)compatible to be set after all startup files/plugins are + sourced, c.f. #438560. + * debian/NEWS: Remove entry from a test build + * debian.vim: Remove commented out settings since this isn't meant to be + modified by users. + * /etc/vim/vimrc: Update filetype plugin comment to correctly state that + filetype plugins aren't enabled by default. + + -- James Vega <jamessan@debian.org> Wed, 13 Aug 2008 21:09:06 -0400 + +vim (2:7.2.000-1) unstable; urgency=low + + * New upstream release (7.2) + * debian/vim-runtime.preinst: Handle a couple of cases where files are + left-behind or diversions setup incorrectly if vim-tiny was currently + installed during the transition to vim-runtime Replacing vim-tiny. + (Closes: #492450) + + -- James Vega <jamessan@debian.org> Sun, 10 Aug 2008 20:22:02 -0400 + +vim (2:7.2c.000-1) experimental; urgency=low + + * New upstream release candidate. + - 7.2b.026 fixes continuous disk activity after using GTK2's "Recent + Files" selector. (Closes: #456897) + - runtime/syntax/zsh.vim: Fixed highlighting of "here-string" redirection. + (Closes: #482373) + * runtime/filetype.vim: Remove duplicate apache filetype detection. + * runtime/autoload/netrw.vim: Fix deletion of incorrect file in wide display + listing. Using Jan Minář's patch from the vim-dev list. (Closes: + #492519) + * debian.vim: Do not enable 'autoindent' and filetype plugins by default. + * vim-runtime.preinst: Use proper invocation of dpkg-divert when removing + diversions. + * README.Debian: Note that securemodelines is in vim-scripts. + * runtime/syntax/tex.vim: Revert diversions from upstream for packages + upstream author doesn't support. + * debian/rules: Instruct configure not to look at /usr/local for + includes/libs. + + -- James Vega <jamessan@debian.org> Thu, 07 Aug 2008 12:25:41 -0400 + +vim (2:7.2b.001-1) experimental; urgency=low + + [ James Vega ] + * New upstream release candidate and patch (001), see README.gz for details. + - 7.2a.004 use wget/curl/fetch if available for downloading spellfiles. + (Closes: #487221) + - runtime/autoload/netrw.vim: + + No longer creates an "undeletable" buffer when 'hidden' is set. + (Closes: #482776) + + Screen is redrawn after invoking external file handler. (Closes: + #487120) + + Hidden files are correctly opened when using NetRW's wide listing. + (Closes: #487385) + + Escaping of filenames cleaned-up which allows opening BTS attachments + again. (Closes: #488557) + - runtime/autoload/netrwsettings.vim: Remove use of non-existent + variables. (Closes: #488881) + - runtime/syntax/sh.vim + + Use stricter matches for shell loop control. (Closes: #486114) + * Bump epoch and use a saner format for the snapshot versioning. + * runtime/syntax/debcontrol.vim: Hilight DM-Upload-Allowed in control files + (Closes: #485119) + * runtime/filetype.vim: + - Udev filetype detection should match /etc/udev/*.rules not /etc/udev.d + - Remove duplicate debcontrol detection + - Detect .ptl files as python. Thanks to Santiago Ruano Rincón for the + patch. (Closes: #399784) + * debian/control: + - Add libxt-dev Build-Depends. + - vim-runtime Depends dpkg (>= 1.14.20) for sane dpkg-divert behavior. + * debian/rules: + - Update handling of DEB_BUILD_OPTIONS according to policy 3.8.0 + - Explicitly call upstream's installgtutorbin target + - Add a manpage for gvimtutor by symlinking to the vimtutor manpage. + - Remove needless branch checkouts from update-orig target. + * debian/update-patches: + - Update for 7.2b beta. Cleanup some code. + - Redirect git-show's stderr to /dev/null. + - Remove an erroneous comment. + - Include the patch number in the summary. + - Use git add debian/README instead of specifying the file to git-commit + - Fix syntax of an if block. + - Ignore leading 0's in patch numbers so they aren't treated as octal. + - Improve handling when fetching the first patch to a new release. + * debian/vim-runtime.links: Add gvimtutor.1 symlink. + * debian/vim-runtime.install: Use the upstream-installed gvimtutor instead + of the one from the src directory. + * debian/vim-common.install: Explicitly list which manpages are installed to + vim-common instead of installing all of /usr/share/man and sorting it out + in debian/rules. + * debian/vim-common.links: Remove listed symlinks which are generated by + debian/rules. + * runtime/syntax/debcontrol.vim: Accept http URIs as valid for Vcs-Git. + Thanks to martin krafft for the patch. (Closes: #489853) + * runtime/tools/vimm: Use printf instead of echo to avoid bashisms. + (Closes: 489667) + * src/ui.c: Remove "#if defined" checks around check_col/check_row + definitions to fix a compile error when building vim-tiny. + * debian/vim-runtime.preinst, debian/vim-runtime.postrm: + - Remove special handling of adding/removing diversions now that + dpkg-divert behavior is fixed (and migrated). + - Add vim72a to the list of previous diversions to remove on upgrade (if + only dpkg handled diversions internally...) + + [ Gerfried Fuchs ] + * runtime/syntax/debchangelog.vim: package names are allowed to start off + with alphanumeric, not only alpha. + + -- James Vega <jamessan@debian.org> Mon, 14 Jul 2008 10:38:52 -0400 + +vim (1:7.2.0~a-1) experimental; urgency=low + + * New upstream release candidate. + - Setting 'pastetoggle' to a multi-key string works again. (Closes: + #424033) + - Match offsets work correctly with multi-byte characters. (Closes: + #441785) + - GNU Screen is detected as supporting xterm mouse codes. + * Merged upstream: + - src/spell.c: Check for EOF while reading the spelllang file in case it + is a corrupt file. + * debian/README: + - Removed until upstream adds one for 7.2 + * debian/rules: + - Update upstream version to 7.2a snapshot + * debian/vim-runtime.preinst: + - The diversions we use are under a versioned directory based on the major + upstream version. Need to remove the diversions for the vim71 + directory. + * Change the shebang lines in all maintainer scripts back to #!/bin/sh since + we no longer use bashisms. + * debian/lintian/vim-runtime: + - Generate this file in debian/rules so the override always has the right + versioned directory. + + -- James Vega <jamessan@debian.org> Thu, 26 Jun 2008 12:49:16 -0400 + +vim (1:7.1.314-3) unstable; urgency=high + + * Update runtime files affected by the filename escape vulnerability. + (CVE 2008-2712, Closes: #486502) + * debian/vim-runtime.preinst: + - Only add the diversions if the preinst is called with the "install" or + "upgrade" (to handle the previous mishandling in postrm) arguments. + * debian/vim-runtime.postrm: + - Only remove the diversions if the postrm is called with the "remove" + argument. (Closes: #486446) + * runtime/menu.vim: + - Escape the buffer name when using the "Window -> Split File Explorer" + menu item. (Closes: #486417) + + -- James Vega <jamessan@debian.org> Tue, 17 Jun 2008 11:12:18 -0400 + +vim (1:7.1.314-2) unstable; urgency=low + + * debian/rules: + - Tell configure to only check the GUI toolkit specific to the variant + being built. (Closes: #486319, #486336) + * runtime/ftplugin/debchangelog.vim: + - Merge Launchpad bug completion from Ubuntu. + - Specify the full path when calling apt-listbugs instead of relying on + /usr/sbin being in the user's path. + - Improve error handling for Launchpad bug completion. + + -- James Vega <jamessan@debian.org> Sun, 15 Jun 2008 12:42:38 -0400 + +vim (1:7.1.314-1) unstable; urgency=low + + * New upstream patches (294 - 314), see README.gz for details. + - SELinux support merged upstream + * Update NetRW to version 125n (pre-release). + - Calculate length of multi-byte strings properly. (Closes: #474609) + - Display/navigate symlinks to directories properly. (Closes: #474980) + * Update vim-git runtime files. + * debian/update-patches: + - Fix determination of patch level from last commit. + - Use debian:debian/README to determine current patch level. + - Don't exit on error since that prevents correcting merges. + - Use a standard commit message for debian/README. + * runtime/ftplugin/debchangelog.vim: + - NewVersion() should only call foldopen if folding is enabled. + * runtime/macros/justify.vim: + - Calculate strlen for multi-byte strings properly. (Closes: #481115) + * debian/rules: + - Make use of upstream's "shadow" directories so the variants can be built + in parallel. + - Remove .NOTPARALLEL to allow parallel building. + - Remove useless dh_shlibdeps call in the binary-indep target. + - Remove autoconf-stamp target since we're no longer patching configure. + * debian/vim-runtime.install: + - Add new gvimtutor to vim-runtime package. + * Very carefully divert vim-tiny's help.txt and helptags so they will still + be in place if vim-runtime is removed. + * debian/control: + - Remove vim-runtime's Replaces of vim-tiny since the conflicting files + are now handled by diversions. + + -- James Vega <jamessan@debian.org> Tue, 10 Jun 2008 22:28:10 -0400 + +vim (1:7.1.293-3) unstable; urgency=low + + * runtime/syntax/debchangelog.vim,debsources.vim: + - Update the list of supported Ubuntu releases. + * debian/policy/vim-policy.xml: + - Remove svn keywords since it's not being stored in svn anymore. + * debian/vim-variant.postinst: + - Remove switching on $1 since it's safe to always add the alternatives. + * debian/vim-variants.prerm: + - Add removal of alternatives during deconfigure. (Closes: #411697) + * debian/README.Debian: + - Add information about mimicing Vim's default modeline behavior and the + securemodelines plugin. (Closes: #479060) + * debian/rules: + - Separate build-arch and build-indep targets so Vim's policy document + aren't built on the buildd's (thus avoiding the openjade segfault on + arm). + * debian/control: + - Move docbook-utils and docbook-xml to Build-Depends-Indep + * src/if_python.c: + - If building against Python 2.5, use ssize_t instead of int according to + PEP 353. + + -- James Vega <jamessan@debian.org> Sun, 04 May 2008 14:11:17 -0400 + +vim (1:7.1.293-2) unstable; urgency=low + + * debian/rules: + - Fix expansion of @VIMCUR@ in vimrc.tiny. Based off a patch by Daniel + Hahler. (Closes: #477379) + - Create a separate install-stamp-vim-tiny target. + - Add the proper lines for vimrc.tiny to vim-tiny.{install,links} in the + install-stamp-vim-tiny target. + * debian/control: + - Correct the vim-common and vim-runtime descriptions with regard to + vimtutor. + - Add Conflicts/Replaces to vim-tiny against vim-common since + /etc/vim/vimrc.tiny is moving to the vim-tiny package. + * runtime/syntax/messages.vim: + - Support highlighting of RFC3339 timestamps. (Closes: #475568) + * runtime/scripts.vim: + - Detect Mozilla Thunderbird's mbox file as mail filetype. Thanks to + Kevin B. McCarty for the patch. (Closes: #475300) + * runtime/filetype.vim: + - Add detection of more passwd/shadow related files. Based on a patch by + Jarek Kamiński. (Closes: #420304) + - Improve filetype detection of strace logs. Thanks to Philipp Marek for + the patch. (Closes: #473967) + - Add filetype detection of more Apache config files. Thanks to Josh + Triplett and Xavier Guimard for the patch. (Closes: #421312) + - Fix a missing comma in the cron filetype detection. + + -- James Vega <jamessan@debian.org> Wed, 23 Apr 2008 13:46:26 -0400 + +vim (1:7.1.293-1) unstable; urgency=low + + * debian/control: + - Add Provides for vim-{ruby,python,perl,tcl} to any variant that supports + those language bindings since some packages benefit from being able to + specify a Depends on a vim package with support for a specific language. + - Only Build-Depend on libselinux1-dev for linux systems. + - Remove Provides from the transition packages. + * runtime/filetype.vim: + - Use "setf" instead of "set ft" when setting the filetype to git so that + we don't override another filetype which may have been set during + filetype detection. + * runtime/syntax/debchangelog.vim: + - Cleanup the list of recognized releases and add + oldstable-proposed-updates/proposed-updates. + + -- James Vega <jamessan@debian.org> Tue, 15 Apr 2008 22:19:36 -0400 + +vim (1:7.1.291-1) unstable; urgency=low + + * Lintian cleanups + - Change doc-base section to Editors. + - Remove Encoding key from desktop entry. + * New upstream patches (286 - 291), see README.gz for details. + * Add SELinux support (Closes: #474102) + - Vim patch taken from Fedora's Vim packaging + - Thanks to Vaclav Ovsik for the patch to the Debian packaging. + * Fix indentation of Perl files when folding is enabled. Thanks to Gregory + Hainaut for the patch. (Closes: #473660) + * debian/control: + - Add libselinux1-dev and autoconf Build-Depends. + * debian/rules: + - Rule & dependency added for rebuilding src/auto/configure. + - Add update-orig target to prep a new upstream+patches orig.tar.gz for + release. + + -- James Vega <jamessan@debian.org> Tue, 08 Apr 2008 02:24:11 -0400 + +vim (1:7.1.285-1) unstable; urgency=low + + * Repack upstream tarball so we're no longer using tarball(s)-in-tarball. + * New upstream patches (267 - 285), see README.gz for details. + - 7.1.277 adds recognition of a few extra groff macros (TP, HP, Pp, Lp, + and It) in the default 'paragraphs' option. (Closes: #468924) + * Updated runtime files: + - syntax/sh.vim: + + No longer mishighlight parenthetical expressions inside arithmetic + expansions. (Closes: #468366) + - syntax/debcontrol.vim: + + Fix syntax highlighting for Vcs-Svn field to accept svn+ssh and remove + the leading "svn+" from http URLs. (Closes: #472201) + - syntax/debsource.vim: + + Add lenny as a recognized distribution. + + Add debtorrent, ssh, rsh, cdrom, and copy URIs. (Closes: #471556) + - filetype.vim + + Add .dpkg-{old,dist} to the list of extensions which are ignored + when determining filetype. (Closes: #421314) + + Recognize /etc/cron.d/* as crontab filetype. (Closes: #472375) + - Change the debchangelog and debcontrol ftplugins to require enabling of + folding instead of folding by default. + * Make debian/tiny/vimrc.tiny.diff a proper patch that is always applied and + update it to only be enabled when TINY_VIMRC is defined. + * debian/rules: + - Remove the special-case targets for vim-tiny and add -DTINY_VIMRC to the + CFLAGS used when building vim-tiny. + - Cleanup dead/useless code from the makefile. + - Restrict 'make test' from running unless build and host types are the + same. + - Allow vim-gnome to build on non-linux-gnu systems. + - Only enable gpm on linux-gnu systems. + - Automatically specify the Vim version when generating helpztags.1. + - Add .NOTPARALLEL target. + - Only run 'make distclean' if configure has already been run. + - Remove patch, unpatch, extract targets/prerequisites now that the + upstream source is directly unpacked in the tarball. + - Simplify get-orig-source so there's only one set of commands that + are run regardless of whether it's a normal or snapshot release. + * debian/control: + - Remove the [!hurd-i386] qualifier from libgnomeui-dev Build-Depend. + - Remove quilt from Build-Depends. + - Change Vcs-* fields to point at the git repo. + * Adjust 'modeline' help to indicate that Debian defaults it to off. + * Update README.Debian and FAQ to reflect the deviation from + upstream's 'modeline' default. (Closes: #472522) + * Remove NEWS entries relevant to stable or earlier releases. + + -- James Vega <jamessan@debian.org> Sun, 30 Mar 2008 12:39:51 -0400 + +vim (1:7.1-266+1) unstable; urgency=low + + [ James Vega ] + * New upstream patches (246 - 266), see README.gz for details. + - 7.1.265 fixes an infinite loop when <Space> is included in 'isfname' and + the user tries to complete a filename. (Closes: #465163) + - 7.1.266 fixes an issue where Vim would stop parsing a terminal response + early, causing the rest of the response to be interpreted as key presses + from the user. (Closes: #466789) + * debian/control: + - Build-Depend on tcl-dev instead of tcl8.4-dev per Tcl/Tk policy. + * Added patches: + - make.vim-syntax.diff: + + Add recognition of more function names. (Closes: #465912) + * Removed patches: + - configure-tcl_detection.diff: + + Accepted upstream and merged as 7.1.257 + * Add debian/watch file. + * debian/rules: + - Add a get-orig-source target. + + [ martin f. krafft ] + * add Tim Pope's vim-git integration (v1.1, commit a53cabb) to vim-runtime. + + [ James Vega ] + * Correct a typo in /etc/vim/vimrc's (Closes: #467057) and eval.txt's (via + new last-position-jump.diff patch) 'last-position-jump' code snippet which + would cause it to fail if the g key were remapped. + * runtime/syntax/debcontrol.vim: + - Ignore case for control file keys + - Match case for control file values + - Improve syntax matching for Vcs-Svn, Vcs-Git, and Vcs-Cvs field values. + - Match URLs for Vcs-Arch, Vcs-Bzr, Vcs-Darcs, Vcs-Hg. + - Recognize more fields as multi-line. + - Use the 'keepend' qualifier for the Vcs-* syntax regions to prevent + mishighlighting of debcontrolHTTPUrl matches. (Closes: #466338) + * debian/control: + - Add "Provides: vim" to all vim variant packages. (Closes: #447714) + + -- James Vega <jamessan@debian.org> Wed, 27 Feb 2008 12:12:26 -0500 + +vim (1:7.1-245+1) unstable; urgency=low + + * New upstream patches (242 - 245), see README.gz for details. + - 7.1.244 fixes an issue where a maximized gvim window would size itself + larger than the size of the workspace, cutting off part of the + command-line. (Closes: #378311) + * debian/control: + - Add libacl1-dev to Build-Depends so it actually builds with acl support. + Thanks to Lucas Nussbaum's dirty chroot builds for noticing this. + - Change TCL to Tcl in the package descriptions. + * New patches: + - option.c-langmap_comma.diff: + + Improves parsing of 'langmap' to follow the behavior specified in the + help. Commas need to be escaped if they're being used literally + instead of as a list separator. (Closes: #233008) + - commandline-compatible.diff: + + If either -N/-C options are given on the command line, set + 'nocompatible'/'compatible' after sourcing of the startup files + finishes. (Closes: #438560) + * Refreshed patches: + - vimrc.tiny.diff + * Register the justify and editexisting plugins for use with + vim-addons-manager. + - justify.vim right and left aligns text by inserting extra spaces into + the specified text. (Closes: #431945) + - editexisting.vim will attempt to bring a running gvim to the foreground + if 1) only one filename was given when invoking Vim and another Vim + instance is editing it or 2) a swapfile for a file exists. (Closes: + #316541) + * debian/rules: + - Add patch/unpatch targets. + - Fix how quilt is invoked so it doesn't use the local user's settings. + Thanks to Teemu Likonen for the patch. (Closes: #463775) + * debian/copyright: + - Adjust copyright string (capitalize the C) so it's recognized by + Lintian. + + -- James Vega <jamessan@debian.org> Mon, 11 Feb 2008 10:27:17 -0500 + +vim (1:7.1-241+1) unstable; urgency=low + + * New upstream patches (232 - 241), see README.gz for details. + * Remove vim-gui-common.menu and provide one menu file for each gvim + package. (Closes: #461805) + * debian/control: + - Re-add ruby1.8 Build-Depends since that's required for Vim to detect + that it can build with Ruby support. (Closes: #462284) + * Updated patches: + - netrwPlugin.vim-bwipe.diff: + + Do a full refresh of NetRW since the functionality is spread out among + multiple files. + - python.vim-ftplugin_include.diff: + + Fix an unescaped backslash so the option correctly matches whitespace + instead of the letter s. + * Removed patches: + - patches/ruby.vim-ftplugin_ri.diff: + + The ruby.vim in 7.1 already handles what the feature the patch was + adding. (Closes: #462418) + + -- James Vega <jamessan@debian.org> Thu, 24 Jan 2008 16:54:49 -0500 + +vim (1:7.1-231+1) unstable; urgency=low + + [ Debian Vim Maintainers ] + * New upstream patches (176 - 231), see README.gz for details. + - 7.1.227 fixes an issue where syntax highlighting could cause Vim to + hang. (Closes: #400771) + + [ James Vega ] + * debian/control: + - Bump policy version to 3.7.3.0 - no changes needed. + - Drop Build-Conflicts on old version of libperl-dev. + - Drop versioning from Build-Depends that are available in Sarge. + - Drop unnecessary ruby and perl Build-Depends. + - Suggest ttf-dejavu instead of ttf-bitstream-vera for the gvim packages. + (Closes: #461295) + - Remove dpkg Pre-Depends now that dak is accepting data.tar.bz2. + * runtime/syntax/debchangelog.vim: + - Adjust the "Closes" syntax highlighting to allow newlines as part of the + whitespace. (Closes: #460074) + - Recognize lenny-backports/lenny-volatile. (Closes: #461059) + * runtime/syntax/debcontrol.vim: Add s390x, sh3, sh3eb, sh4, sh4eb to the + list of recognized architectures. (Closes: #455993) + * Added patches: + - configure-tcl_detection.diff: + + Update Vim's configure script to detect Tcl again after the Tcl + maintainers' decision to move /usr/lib/tcl8.4/ to + /usr/share/tcltk/tcl8.4/. + - tex.vim-syntax_additions.diff: + + Disable spell checking for verbatim sections. (Closes: #445295) + - netrwPlugin.vim-bwipe.diff: + + Call bwipe when opening file:// URLs to remove the extra buffers that + get created. Their creation is inevitable but this will clean up the + buffer list. (Closes: #370082) + - filetype.vim-udev.d.diff: + + Detect /etc/udev.d/*.rules files as 'udevrules' instead of 'hog' + filetype. (Closes: #437434) + - vimspell.sh-typo.diff: + + Fix a missing end-quote in tools/vimspell.sh. + - mve.awk-interpreter.diff: + + Adjust the #! line to use awk instead of nawk. + * Updated patches: + - fstab.vim-syntax.diff: + + Added more sshfs support based on feedback from upstream. + * Removed patches: + - gui_gtk_x11.c_g_thread_init.diff: + + This patch was initially added to silence a GLib warning (#428854) + which isn't occurring anymore. + * Stop removing vimspell, vim132, and maze from the runtime tools/ + directory. The issues leading to their removal should be addressed + instead of removing them from the package. + - vimspell - The tempfile vulnerability (CAN-2005-0069) has been fixed + upstream for some time now. + - vim132 - Add lintian overrides for "csh is harmful" and not having a + Depends/Recommends/Suggests on tcsh | csh. This is the only file in the + package that would use the shell and its an example script. + - maze - maze.c doesn't work properly and its README suggests this may be + the case on newer compilers and to use mazeansi.c, which does work. + + -- James Vega <jamessan@debian.org> Thu, 17 Jan 2008 13:50:30 -0500 + +vim (1:7.1-175+2) unstable; urgency=low + + * runtime/syntax/debcontrol.vim: + - Reworked the URL regex so that it should properly match any non-local + domain name as specified in RFC 1738. + * debian/rules: + - Use bzip2 to compress the vim-runtime package. + * Add tex.vim-update.diff, which syncs from upstream to fix some folding + issues. (Closes: #456168) + * debian/control: + - Add Pre-Depends on dpkg (>= 1.10.24) for vim-runtime to please dak even + though Sarge has a newer dpkg. + + -- James Vega <jamessan@debian.org> Tue, 18 Dec 2007 09:13:59 -0500 + +vim (1:7.1-175+1) unstable; urgency=low + + [ James Vega ] + * debian/rules: + - Add LDFLAGS="-Wl,--as-needed" when calling configure. + * Fix a typo in debsources.vim-syntax.diff. (Closes: #454672) + + [ Debian Vim Maintainers ] + * New upstream patches (168 - 175), see README.gz for details. + + [ James Vega ] + * Add spellfile.vim-doc.diff, which explains that a writable spell directory + must exist for the plugin to download spell files. (Closes: #421045) + * Lintian cleanup: + - Remove /usr/share/vim/addons/plugins/ from vim-common.dirs. + - Remove /usr/share/vim/vim71/tools/vim132 to silence a warning and error + about csh. + - Remove /usr/share/consolefonts/ from vim-runtime.dirs. + - Remove /usr/share/doc/vim-common/html/policy/ from vim-doc.dirs. + - Override the "desktop-command-not-in-package" warning for + vim-gui-common. We make use of TryExec which should prevent the menu + entry from showing up if none of the gvim-providing packages are + installed. + * Move Vim's policy documentation to /usr/share/doc/vim-common/ instead of + being under a separate policy/ directory. + * runtime/ftplugin/debcontrol.vim: Correct a function definition to use !. + (Closes: #454933) + * runtime/syntax/debcontrol.vim: Don't require a three part domain for the + Homepage field. (Closes: #455341) + * Install the presubj file under /usr/share/bug/ for every vim variant, not + just vim. + * Add versioned Conflicts/Replaces on vim-common for the vim package since + it contains /usr/share/bug/vim/presubj now. + + -- James Vega <jamessan@debian.org> Sun, 09 Dec 2007 17:42:17 -0500 + +vim (1:7.1-167+1) unstable; urgency=low + + [ Debian Vim Maintainers ] + * New upstream patches (139 - 167), see README.gz for details. + - 7.1.147 fixes a crash when tab completing a user's home directory. + (Closes: #453049) + - 7.1.167 fixes a crash with large values for the -c option of xxd + (Closes: #452789) + + [ James Vega ] + * runtime/ftplugin/debchangelog.vim: + - Fix NewVersion() to use the distribution from the previous changelog + entry. (Closes: #446728) + - Fix NewVersion() to increment the version of the first changelog entry + regardless of how 'startofline' is set. + * runtime/syntax/debchangelog.vim: + - Recognize oldstable* upload targets. + * Refreshed patches: + - vimrc.tiny.diff + * Added patches: + - sh.vim_syntax.diff, which fixes the syntax highlighting of escaped + single-quotes and comments. (Closes: #425443, #425797) + - gnuada.diff, which updates the ada runtime files so they gracefully + handle the user not having certain variables defined. (Closes: #440221) + * syntax/debcontrol.vim: + - Add syntax highlighting for Vcs-* control fields. (Closes: #448543) + * Bump debhelper compat to 5. + * debian/vim-runtime.install: + - Remove usr/share/consolefonts/* since that's not shipped any more. + * debian/control: + - Add vim-dbg package to supply debugging symbols for the various vim + packages. + - Fix a typo in the long description for the vim package. + - Make use of multi-line (Build-)Depends support. + * debian/rules: + - Add binary-arch target for the vim-dbg package. + * debian/gvim.desktop: + - Add TryExec key so the menu entry is only shown if the gvim alternative + has been setup. + * Merges from Ubuntu: + - runtime/syntax/debcontrol.vim: + + Recognize restricted, universe, multiverse as part of the Section + field. + + Recognize XSBC-Original-Maintainer as a legal field. + - runtime/syntax/debchangelog.vim: + + Recognize Ubuntu releases as upload targets. + + Recognize syntax for closing Launchpad bugs. + - Add debsources.vim-syntax.diff: + + Recognize restricted, universe, multiverse Sections. + + Add more recent Ubuntu releases as recognized distributions. + + [ Stefano Zacchiroli ] + * debian/README.Debian + - fix typo in vim policy URL (Closes: #452555) + + [ James Vega ] + * Add lhaskell.vim-syntax.diff, which restricts the matching of % to the + beginning of the line when determining if the file is a TeX document. + Thanks to Chung-chieh Shan for the patch. (Closes: #451440) + * Add fstab.vim-syntax.diff, which adds support for sshfs syntax. + (Closes: #451754) + * Add filetype.vim-debfiles.diff, which improves detection of debcontrol and + debsources files. Thanks to Loïc Minier for the debsources part of the + patch. (Closes: #435552) + * debian/control: + - Remove Norbert Tretowski from Uploaders with his permission. Thanks for + all your work. + + -- James Vega <jamessan@debian.org> Mon, 03 Dec 2007 15:53:27 -0500 + +vim (1:7.1-138+1) unstable; urgency=medium + + [ Debian Vim Maintainers ] + * New upstream patches (136 - 138), see README.gz for details. + + [ James Vega ] + * Fix the lintian override files to match Lintian's output. + * debian/rules + - Remove a useless command from the variant clean target + - Clean vim-tiny's generated debhelper files + - Clean generated vim-policy files + * Brown-paper bag bug in vim-full.preinst. Need to grep for bin/vim.full + not vim/vim.full. (Closes: #446462) + + -- James Vega <jamessan@debian.org> Sat, 13 Oct 2007 12:45:04 -0400 + +vim (1:7.1-135+1) unstable; urgency=low + + [ Debian Vim Maintainers ] + * New upstream patches (057 - 135), see README.gz for details. + - Patch 125 corrects Vim's TermResponse autocmd behavior. + (Closes: #436452) + + [ Stefano Zacchiroli ] + * debian/control + - removing idle contributors from the Uploaders field + + [ James Vega ] + * Add a slave link for gnome-text-editor.1.gz when we add the + gnome-text-editor alternative. (Closes: #439549) + * Update debcontrol.vim.diff to recognize "Homepage:" (Closes: #443444) and + "XS-Vcs-*:" fields. + * Update patches/filetype.vim-better_tex_vs_plaintex.diff so it properly + escapes the pattern alternator (|) when determining whether the file is + latex. Thanks Martin Krafft. (Closes: #444346) + * Update patches/debchangelog-ftplugin.vim.diff to remove an extra + "foldopen" command. (Closes: #441315) + * Add de.po.diff to fix the translation of "Load File". Thanks Torsten + Werner. (Closes: #443529) + * Add samba.vim.diff which fixes the highlighting for "smb ports". Thanks + Alberto Reyes. (Closes: #386064) + * Add tex.vim-syntax_additions.diff, which adds syntax highlighting for + acronyms, URLs, and citetest. (Closes: #444411, #444408, #444301) + * Update menu file to use Applications instead of Apps and to require the + gvim package to be installed in order to display the entry. + * Update desktop file to remove legacy category. + * debian/rules: + - Remove vim-{python,perl,tcl,ruby,full} variants. + - Add vim-nox which has all language bindings but no X requirement. + - Include all language bindings when building vim-gtk. + * debian/control: + - Add Homepage field. + - Remove Build-Depends on dpkg and dpkg-dev since the specific versions we + need are older than what's in stable. + - Make vim-full a transition package Depending on vim-gnome. + - Make vim-{python,perl,tcl,ruby} transition packages Depending on + vim-gtk. + + -- James Vega <jamessan@debian.org> Sun, 07 Oct 2007 15:47:26 -0400 + +vim (1:7.1-056+2) unstable; urgency=low + + * Brown paper bag release -- vimrc.tiny should not be calling :let since + vim.tiny doesn't support that command. Copy the 'runtimepath' setting to + vimrc.tiny since that was the only reason we needed the :let and + "runtime! debian.vim" commands. (Closes: #436925) + + -- James Vega <jamessan@debian.org> Thu, 09 Aug 2007 10:57:51 -0400 + +vim (1:7.1-056+1) unstable; urgency=low + + [ Debian Vim Maintainers ] + * New upstream patches (023 - 056), see README.gz for details. + + [ Pierre Habouzit ] + * Make sure reportbug vim/presubj is named that way, without a `vim.` prefix + making reporbug skip it. + + [ Stefano Zacchiroli ] + * Add a entry to debian/NEWS describing why /usr/share/vim/addons/ is no + longer in the runtimepath and pointing to the appropriate documentation + + [ James Vega ] + * Add verilog.vim_ftplugin-cpoptions.diff, which locally enables line + continuations for the ftplugin in order to prevent an error when being run + in vi-compatible mode. (Closes: #430372) + * Build vim with the huge feature set to pull in +profile (the only + difference between the big and huge feature sets). + * Remove the !hurd-i386 restriction from the tcl8.4-dev Build-Depends now + that the package exists on hurd-i386. This allows building the vim-tcl + package for hurd-i386. (Closes: #434435) + * Remove the hacks we were doing to try and build vim-tiny with extra + features. Simply build vim-tiny using Vim's "small" feature set. This + removes a number of features but allows the package to build with the + current upstream patches. This also lessens the maintenance burden since + we no longer have to figure out which features to enable via trial and + error. + * debian/rules: + - Separate out {clean,configure,build}-stamp-vim-tiny targets + - Move the handling of the vimrc.tiny patch to the new *-vim-tiny targets. + - Remove configure-stamp* files in the clean target. + - Move the fake help files for vim-tiny from /usr/share/vim/doc to + /usr/share/vim/$VIMCUR so the user can actually see them when invoking + :help. + * Add ruby.vim_indent.diff, which fixes some improper indenting for Ruby + files. (Closes: #431212) + * Refresh vimrc.tiny.diff + * Add index.txt.diff, which adds some missing cross-references to the index + of Vim commands. (Closes: #434447) + * debian/control: + - Remove Conflicts/Replaces on packages that are older than Etch. + - Add a Replaces to vim-runtime since it ships files that overwrite files + in vim-tiny. + - Add a Conflicts to vim-tiny for earlier versions of vim-runtime to make + sure we don't attempt to overwrite files in versions of vim-runtime that + don't Replace vim-tiny. + + -- James Vega <jamessan@debian.org> Wed, 08 Aug 2007 00:18:16 -0400 + +vim (1:7.1-022+1) unstable; urgency=low + + [ Debian Vim Maintainers ] + * New upstream patches (001 - 022), see README.gz for details. + + Load all matching files in $VIMRUNTIME when using ":syn include" + (Closes: #395517) + + [ James Vega ] + * Add changelog.vim-date_end_entry.diff, which fixes a variable name which + is let in changelog.vim. (Closes: #424224) + * Remove 'viminfo' and 'textwidth' settings from $VIMRUNTIME/debian.vim. We + were uselessly setting 'textwidth' to the default value and 'viminfo' to + an almost-default but less useful value. + * Add Makefile_no-strip.diff, which removes the calls to strip in upstream's + makefile. We'll handle that in debian/rules. + * gvim.desktop should be using %F instead of %U to specify the filename. + (Closes: #406586) + * Remove debian/vim-{doc,variant,gui-common,common}.preinst, + debian/vim-common.postinst as they all handled special procedures for + upgrading from Sarge. + * debian/control + - Clarify the package description for the vim package to indicate it does + not provide a GUI version of Vim. + * debian/rules + - Update the extract and clean targets to not fail if quilt exits with + $? == 2. Also, remove the .pc directory in the clean target. + - Remove preinst from the list of per-variant files + * Add spell.c_getc-eof.diff, which causes Vim to stop reading a truncated + spellfile when it reaches EOF. + * debian/runtime/debian.vim.in + - set 'nomodeline' by default since modelines have historically been a + source of security/resource vulnerabilities. Users should have to + explicitly enable the option to assume the associated risks. + * Add gui_gtk_x11.c_g_thread_init.diff, which prevents a glib warning + related to glib 2.10's Memory Slices and threads. (Closes: #428854) + + [ Stefano Zacchiroli ] + * Add javac_cmdline-vim.diff, which fixes the invocation of the javac + compiler. (Closes: #408338) + * Add debchangelog-closes_omni.vim.diff, which add omni completion support + for "Closes: #..." retrieving data from the BTS via apt-listbugs + * Added the new Debian Vim Policy to the "vim-doc" package, overriding the + old unenforced one + * debian/runtime/debian.vim.in + - removing /usr/share/vim/addons/{,after/} from the vim runtimepath: + according to the VIM policy addons should not be enabled per default, + but manually using vim-addon-manager + * debian/control + - added build deps on docbook stuff to build the policy (note that this + includes lynx, due to #387035) + * Add map.vim-syntax.diff which ships syntax file for UMN map server + (Closes: #355900) + + -- James Vega <jamessan@debian.org> Sat, 07 Jul 2007 15:04:57 -0400 + +vim (1:7.1-000+1) unstable; urgency=low + + [ Debian Vim Maintainers ] + * New upstream release (7.1) + + [ James Vega ] + * debian/rules: + + Remove extraneous update-snapshot target since snapshots are being + handled similar to normal releases, but in a different directory on the + ftp server. + * upstream/patches: + + Remove all the 7.0 patches + * Removed patches: + + de.po.diff, applied upstream. + + zsh.vim-nested_quotes.diff, New upstream rewrite fixes the same problem + as our patch. + + mp.vim-cmd_check.diff, applied upstream. + + html.vim-syntax_spell.diff, applied upstream. + + changelog.vim-ftplugin_buffer-split.diff, applied upstream. + + netrw.vim-tmpfile_suffix_escape.diff, applied upstream. + * Refreshed patches: + + php.vim.diff, simple rediff against new upstream. + + dosini.vim-hash_comment.diff, simple rediff against new upstream. + * Updated patches: + + debchangelog-ftplugin.diff + - Call foldopen silently so Vim doesn't error if there are no folds. + (Closes: #416184) + - Allow users to "let g:debchangelog_fold_disabled" to disable automatic + folding of debchangelogs. 'foldexpr' and 'foldtext' will still be set + but 'foldmethod' will not be set to 'expr'. + + -- James Vega <jamessan@debian.org> Sat, 12 May 2007 13:24:27 -0400 + +vim (1:7.0-219+1) unstable; urgency=low + + [ Debian Vim Maintainers ] + * New upstream patches (165 - 219), see README.gz for details. + + [ Stefano Zacchiroli ] + * vim-addons support: + - converted to YAML the registry entry for matchit + * debian/control + - added XS-Vcs-Browser field + + [ James Vega ] + * Fix the file test for deciding whether we need to remove alternatives to + properly transition the Russian manpage alternatives. + * Fix the handling of the stale diversion when /usr/bin/vim.org is already + missing. + * Fix the handling of alternatives which pointed at the stale alternative so + the alternative isn't changed from auto to manual. + * Remove the 'iskeyword' setting in Ruby's ftplugin as suggested by Tim + Pope in #389332. + * Add patches/netrw.vim-tmpfile_suffix_escape.diff, which escapes the suffix + of the tmpfile filename. + + -- James Vega <jamessan@debian.org> Tue, 20 Mar 2007 18:27:27 -0400 + +vim (1:7.0-164+3) unstable; urgency=low + + [ James Vega ] + * Remove the patch notes for patches after 164 in debian/README. Forgot + about those when removing the patches from svn to prepare the last upload. + + -- James Vega <jamessan@debian.org> Sun, 14 Jan 2007 10:13:00 -0500 + +vim (1:7.0-164+2) unstable; urgency=medium + + [ James Vega ] + * debian/vim-variant.preinst: + + Move diversion removal here from vim-variant.postinst. Manually remove + /usr/bin/vim in order to be able to remove the diversion. Fixes + upgrades from Sarge leaving behind stale binaries. (closes: #401000) + + Remove the alternatives for ru.{UTF-8,KOI8-R} manpages so the + alternatives system doesn't attempt to keep the links around after the + upgrade. Fixes upgrades from Etch. (closes: #399024) + + -- James Vega <jamessan@debian.org> Thu, 4 Jan 2007 01:50:25 -0500 + +vim (1:7.0-164+1) unstable; urgency=low + + [ Debian Vim Maintainers ] + * New upstream patches (159 - 164), see README.gz for details. + + [ James Vega ] + * Shipped tags file was being regenerated (closes: #397837) + - Do not pre-generate tags file, vim-runtime's postinst is already + handling tag generation + - Remove tags file in vim-runtime's postrm + * Add Provides: editor to the gvim variants. (closes: #398572) + * Remove the empty vim-variant.postrm. + * Move the Russian KOI8-R man pages to /usr/share/man/ru/man1 and remove the + utf8 man pages. man will handle the conversion. (closes: #368754) + + -- James Vega <jamessan@debian.org> Wed, 15 Nov 2006 08:48:51 -0500 + +vim (1:7.0-158+1) unstable; urgency=medium + + [ Debian Vim Maintainers ] + * New upstream patches (153 - 158), see README.gz for details. + - Do not let the fold level become negative. (closes: #395413) + * Urgency medium since #396934 affects other packages. + + [ James Vega ] + * Add vim-runtime.postinst which runs helpztags so that we don't break the + help for other Vim addons everytime vim-runtime is upgraded. + (closes: #396934) + * Update the vim-basic install target in debian/rules to not rely on the + vimcurrent symlink before it has been setup. + + -- James Vega <jamessan@debian.org> Mon, 6 Nov 2006 22:41:59 -0500 + +vim (1:7.0-152+1) unstable; urgency=low + + [ Debian Vim Maintainers ] + * New upstream patches (123 - 152), see README.gz for details. + - Correct the button order in the GTK+ file chooser dialog so that it + matches the GNOME Human Interface Guidelines. (closes: #367639) + + [ James Vega ] + * Bump vim-common's priority to important to match the override. + * Remove patch gui_gtk.c-abs_path.diff, merged upstream. + * Remove patch gui_xmebw.c-lesstif_crash.diff, merged upstream. + * Add patch html.vim-syntax_spell.diff, which adds support for highlighting + of spelling mistakes. (closes: #393347) + * Add patch changelog.vim-ftplugin_split-buffer.diff, which corrects an + invalid command used for opening the changelog in a split window. + (closes: #392840) + + [ Stefano Zacchiroli ] + * Added patch dosini.vim-hash_comment.diff which adds support for # comments + in dosini syntax highlighting, thanks to Adeodato Simó. (closes: #378952) + * Added patch zh_TW.po-swap_recovery_typo.diff which fixes a typo in a + traditional Chinese message when editing a file for which a swap file + already exists. (closes: #347420) + * debian/control + - renamed svn info field to XS-Vcs-Svn, to match the forthcoming official + name + + -- Stefano Zacchiroli <zack@debian.org> Wed, 25 Oct 2006 17:07:37 +0200 + +vim (1:7.0-122+1) unstable; urgency=medium + + [ Debian Vim Maintainers ] + * New upstream patches (095 - 122), see README.gz for details. + * Urgency medium for RC bug fixes. + + [ James Vega ] + * Since vim-gui-common no longer depends on vim-common (to allow for + binNMUing), make /usr/share/doc/vim-gui-common a directory instead of a + symlink to /usr/share/doc/vim-common. (closes: #387794) + * Add versioned Conflicts/Replaces against vim-doc for vim to allow proper + upgrades from Sarge. (closes: #381526) + * Update debian/copyright with the license information for the user and + reference manuals. + * Add patch zsh.vim-nested_quotes.diff, which fixes handling of single + quotes nested inside double quotes. (closes: #390911) + * Add a gnome-icon-theme Suggests for the packages which use a GTK/Gnome + GUI. + * Build vim-tiny with multibyte support. (closes: #361378) + * Add patch gui_gtk.c-abs_path.diff, which ensures the GTK file selection + dialog remembers the previously used directory. (closes: #368668) + * Add mp.vim-cmd_check.diff, which fixes an incorrect boolean check. + (closes: #384154) + + [ Stefano Zacchiroli ] + * Added patches perl.vim-ftplugin_perldoc.diff, + perl.vim-ftplugin_pydoc.diff, and ruby.vim-ftplugin_ri.diff, which trigger + usage of perldoc/pydoc/ri for keyword lookup on perl/python/ruby files. + (closes: #389332) + + -- James Vega <jamessan@debian.org> Mon, 9 Oct 2006 19:37:58 -0400 + +vim (1:7.0-094+1) unstable; urgency=medium + + [ Debian Vim Maintainers ] + * New upstream patches (036 - 094), see README.gz for details. + * Urgency medium because of the fix to vim-lesstif's crash bug. + + [ James Vega ] + * Add patches/de.po.diff, which differentiates between "Delete" and + "Readonly" swap recovery messages for the German translation. + (closes: #379507) + * Update patches/scripts.vim.diff to add recognition of rst (including + rest2web) files as the filetype 'rst'. (closes: #382541) + * Update debian/rules to generate helptags for the plugins that are in + /usr/share/vim/addons. + * Add patches/gui_xmebw.c-lesstif_crash.diff, which fixes the crash bug when + invoking gvim from the vim-lesstif variant. Thanks Ben Hutchings! + (closes: #378721) + + [ Stefano Zacchiroli ] + * Modified patches/debchangelog.vim.diff so that when opening a changelog + the entry the cursor is on gets (recursively) unfolded. + * Added patches/filetype.vim-better_tex_vs_plaintex.diff, implementing + better recognition of tex vs plaintex filetype (namely it recognizes as + latex files containing sectioning commands). (closes: #384479) + * Added script upstream/patches/get_patches.py to automate downloading of + latest upstream patches. + * debian/control + - bumped Standards-Version to 3.7.2 (no changes needed) + - added X-Vcs-Svn field to source package + + -- Stefano Zacchiroli <zack@debian.org> Sun, 10 Sep 2006 11:59:14 +0200 + +vim (1:7.0-035+1) unstable; urgency=low + + [ Debian Vim Maintainers ] + * New upstream patches (018 - 035), see README.gz for details. + + [ James Vega ] + * debian/control: Make Vim binNMUable. + * Rename the augroup in $VIMRUNTIME/debian.vim so it doesn't conflict with + Vim's FileType autocmd event. + * Update patches/debcontrol.vim.diff to fix the package name regexp. + (closes: #375848) + * Update patches/debcontrol.vim.diff to include XS-Python-Version and + XB-Python-Version. (closes: #373661) + * Add patches/php.vim.diff, which removes the 'delete' keyword from PHP's + syntax highlighting. (closes: #368089) + + [ Stefano Zacchiroli ] + * Removed patch edit.c.diff, no longer needed after upstream patch 023 + + -- James Vega <jamessan@debian.org> Mon, 3 Jul 2006 01:43:11 -0400 + +vim (1:7.0-017+8) unstable; urgency=medium + + * Rebuild with fixed libruby1.8. Urgency medium since vim-full and vim-ruby + can now be properly configured. + (closes: #373696, #373762, #373890, #374060) + + -- James Vega <jamessan@debian.org> Sat, 17 Jun 2006 22:18:20 -0400 + +vim (1:7.0-017+7) unstable; urgency=low + + * Update $VIMRUNTIME/debian.vim and /etc/vim/vimrc.tiny to properly set + 'compatible' when vim-tiny is invoked as vi. (closes: #373680) + + -- James Vega <jamessan@debian.org> Wed, 14 Jun 2006 23:18:11 -0400 + +vim (1:7.0-017+6) unstable; urgency=low + + [ Pierre Habouzit ] + * Add a Replace: vim-runtime to vim-common because of the vimcurrent mess, + that may prevent vim upgrade. (closes: #370012, #373117). + + [ James Vega ] + * Add vim-variant.preinst to remove any cruft left behind in + /usr/share/doc/vim{,-$variant}, which is now a symlink to + /usr/share/vim/vim-common. (closes: #369740) + * Update the build process so only vim-tiny starts in 'compatible' mode when + invoked as vi. + + Move patches/virc.c.diff to debian/tiny/vimrc.tiny.diff and apply only + when building vim-tiny. + + Rename /etc/vim/virc to /etc/vim/vimrc.tiny and add + vim-common.{post,pre}inst code to handle the conffile renaming. + * Update README.Debian to specify which package contains the vim policy and + the correct directory that holds vim policy. + * Add debchangelog.vim.diff which fixes an inifinite loop bug in the + debchangelog filetype plugin. (closes: #367566) + * Add scripts.vim.diff which adds recognition of ltrace output and sets the + filetype to 'strace'. (closes: #372926) + + -- James Vega <jamessan@debian.org> Tue, 13 Jun 2006 11:06:59 -0400 + +vim (1:7.0-017+5) unstable; urgency=low + + [ James Vega ] + * Added po.vim.diff which locally enables line continuations while sourcing + the po.vim syntax file. (closes: #368589) + * Re-add /usr/share/vim/vimcurrent as a convenience symlink. + (closes: #369124) + * Add python.vim-ftplugin_include.diff which sets the 'include' option to a + stricter value to reduce the chance of mis-highlights. (closes: #367259) + * Add mysql.vim-syntax_comment.diff which corrects a syntax pattern for + MySQL comments. (closes: #367777) + + -- James Vega <jamessan@debian.org> Wed, 31 May 2006 12:39:44 -0400 + +vim (1:7.0-017+4) unstable; urgency=low + + [ James Vega ] + * Added edit.c.diff which fixes a crash when exiting insert mode spell + completion. + * Revert changes to alternative handling in vim-variant.prerm. They should + only be removed during a remove, not an upgrade. (closes: #368175) + * Move the removal of stale alternatives to vim-variant.prerm where it + should've been to begin with. Also, tighten the matching done when + deciding which alternatives are removed. Only alternatives pointing to + /usr/bin/vim should be removed since those are the known stale + alternatives. + * Remove support for building spellfiles as will be moved to another set of + packages. + + debian/control: Remove Build-Depends-Indep which was only used for + spellfile building. + + debian/rules: Remove build-spell* and build-locales* targets. + + Remove debian/locale-gen + + Remove bg_BG.diff.diff and spell-locales.diff. + + -- James Vega <jamessan@debian.org> Sat, 20 May 2006 21:57:31 -0400 + +vim (1:7.0-017+3) unstable; urgency=low + + [ James Vega ] + * Add support for building l10n spellfiles. + + Added unzip, aap, and locales to Build-Depends-Indep. + + Added debian/locale-gen to build the locale info. + + Update debian/rules to build spellfiles (temporarly disabled). + - Added a check for 'nospell' in DEB_BUILD_OPTIONS to prevent building + the spellfiles. + + Added spell-locales.diff patch which updates the aap recipes to set the + LC_ALL environment variable instead of LANG. + + Added bg_BG.diff.diff patch which fixes the line-endings in the + bg_BG.diff patch, allowing it to apply cleanly. + * Add /usr/share/vim/virc symlink, with this fix invoking vim as "vi" will + actually enable vim to behave differently than when invoked as "vim". + (closes: #367818) + + -- James Vega <jamessan@debian.org> Thu, 18 May 2006 08:11:15 -0400 + +vim (1:7.0-017+2) unstable; urgency=low + + [ Debian Vim Maintainers ] + * Upload to unstable + + [ James Vega ] + * Update debian/vim-variant.prerm to remove alternative also during + upgrades. + * Add debian/vim-variant.preinst to cleanup alternatives left behind from + previous vim-variant.prerm scripts. + + -- Stefano Zacchiroli <zack@debian.org> Tue, 16 May 2006 22:10:49 -0500 + +vim (1:7.0-017+1) experimental; urgency=low + + [ Debian Vim Maintainers ] + * New upstream patches (011 - 017), see README.gz for details. + + [ Stefano Zacchiroli ] + * Preliminary support for add-on infrastructure + + added symlinks from /usr/share/vim/addons/ to $VIMRUNTIME for the + matchit plugin, so that they are no longer version dependent + + added dir /var/lib/vim/addons/, now in the runtimepath + + added vim add-on registry entry for the matchit plugin + * Differentiated behaviour of Vim when invoked as "vi" + + added patch patches/virc.c.diff which source /etc/vim/virc when invoked + as such + + added debian/runtime/virc; it creates a vi-like environment setting + 'compatible' and nothing else + * Raised the alternative priority of vim.basic from 20 to 30. Rationale: the + relative order we want to achieve is vim.tiny < nvi < vim.basic + * vim-tiny is ready to enter the base system + + set vim-tiny priority to Important + + [ Norbert Tretkowski ] + * Removed outdated runtime files from package. + * Added s390x to debcontrolArchitecture in debcontrol.vim. (closes: #361281) + + -- Norbert Tretkowski <nobse@debian.org> Sat, 13 May 2006 13:23:35 -0500 + +vim (1:7.0-010+1) experimental; urgency=low + + [ Debian Vim Maintainers ] + * New upstream release (7.0) and patches (001 - 010), see README.gz for + details. (closes: #366396) + + CSS syntax highlighting properly handles non-UTF-8 aware environments. + (closes: #358734) + + crontab syntax highlighting recognizes % as starting stdin to the + cronjob. (closes: #363558) + + non-ASCII characters are properly handled when changing case in + :substitute commands. (closes: #266256) + + [ James Vega ] + * Massage the packaging back into "stable upstream releases" mode. + + Remove debian/watch since it isn't useful with Vim's method of releasing + stable updates. + + Swap out the unzip Build-Depends for bzip2. + + Update debian/rules to use the src/lang/extra tarballs instead of one + zip file. + + [ Stefano Zacchiroli ] + * handle debian/*.in files as autoconf files filling the @VIMCUR@ + placeholder with the appropriate vim<version> string + * got rid of the /usr/share/vim/vimcurrent symlink, no longer needed now we + source debian.vim (closes: #366504) + * source vimrc.local/gvimrc.local from system-wide vimrc/gvimrc since a lot + of users have it, added a comment about that file being deprecated + * added a comment to system-wide gvimrc about how to obtain a reversed video + vim gui + + -- James Vega <jamessan@debian.org> Thu, 11 May 2006 08:54:38 -0400 + +vim (1:6.4+7.0g01-1) experimental; urgency=low + + [ Debian Vim Maintainers ] + * New upstream snapshot (7.0g01). + + Remove 161_cmake-support.diff, merged upstream. + + Recognize zsh-beta as a shell that supports '2>&1| tee' for the + 'shellpipe' option. (closes: #362999) + + Assign filetype=php to any .php<digit> filename. (closes: #365055) + + Recognition in debcontrol's syntax file of all architectures listed at + http://www.debian.org/ports/ (closes: 364824) + + [ Stefano Zacchiroli ] + * Screening of patches no longer needed with vim7 & pushing upstream + of as many debian-specific patches as possible. Results: + + removed patches: 102_pythoncomplete.vim.diff, 104_debchangelog.vim.diff, + 106_fstab.vim.diff, 108_automake.vim.diff, 109_xdefaults.vim.diff, + 111_fstab.vim.diff, 119_php.vim.diff, 130_fstab.vim.diff, + 133_resolv.vim.diff, 136_muttrc.vim.diff, 140_muttrc.vim.diff, + 148_debchangelog.vim.diff, 157_slrnrc.vim.diff, 201_fr.po.diff, + 203_zh_TW.UTF8.po.diff + + The following runtime and translation files are now maintained upstream + in a best effort fashion (i.e. they are looking for a new maintainer) by + Debian VIM Maintainers: syntax/muttrc.vim, syntax/automake.vim, + syntax/php.vim, syntax/slrnrc.vim, lang/po/zh_TW.UTF-8.po. + + syntax/debchangelog.vim, syntax/debcontrol.vim, and syntax/tpp.vim are + now officially co-maintained upstream by Debian Vim Maintainers + * Improved comments and added more commented settings in /etc/vim/vimrc + + [ James Vega ] + * Add Replaces against manpages-it and manpages-pl since upstream now + provides i10n manpages. (closes: #364299) + * Moved Debian specific settings out from /etc/vim/{,g}vimrc, so that the + file can be (more) freely modified by sysadmins without risking merge + problems with maintainer updates. + + -- James Vega <jamessan@debian.org> Wed, 3 May 2006 12:34:14 -0400 + +vim (1:6.4+7.0d03-1) experimental; urgency=low + + [ Debian Vim Maintainers ] + * New upstream snapshot (7.0d03). + + A lot of new features have been added, most notably: spell checking, + omni completion, tabs, undo branches, internal grep, location lists, + list/dictionary/funcref types for scripting. + See ":help version7" for more information. + + bugfixes affecting Debian's BTS: + - new version of sh.vim syntax highlighting (closes: #355273, #361813) + - respect LC_MESSAGES in menus (closes: #147757, #217217) + - consistent behaviour of 'gq' when an external formatter is used + (closes: #177735) + - improved wildcard expansion of filename patterns + (closes: #262645, #258150) + - german tutorial now shows instruction on how to proceed in the first + page (closes: #289115) + - fixed encoding of slovak translation (closes: #257342) + - proper escaping of characters in URLs (closes: #353076, #361317) + - added g:is_posix flag to sh.vim to enable highlighting of POSIX shell + scripts (closes: #361177) + + [ Stefano Zacchiroli ] + * Screening of patches no longer needed with vim7 & pushing upstream + of as many debian-specific patches as possible. Results: + + removed patches: 101_make.vim.diff, 103_sh.vim.diff, + 117_fortram.vim.diff, 122_html_indent.vim.diff, 135_debsources.vim.diff, + 145_fortran.vim.diff, 155_rst.vim.diff + + removed updates: debian/updates/debsources.vim + + -- James Vega <jamessan@debian.org> Fri, 14 Apr 2006 13:29:49 -0400 + +vim (1:6.4+7.0c05-1) experimental; urgency=low + + [ Debian Vim Maintainers ] + * New upstream snapshot (7.0c05). + + Added support for bzr diffs in scripts.vim, thanks to Adeodato Simó. + (closes: #355922) + + Support python `as' keyword. (closes: #352885) + + [ James Vega ] + * Sync with the work that's been done on the 6.4 vim package. + * Add a missing quote in /etc/vim/vimrc's last-position-jump example. + (closes: #347597) + * Move vimtutor.1 to the same package (vim-runtime) as vimtutor. + Fixes a lintian warning. + * Add debian/watch. + * Cleanup handling of manpages and alternatives. (closes: 361845) + * debian/control: + + Remove references to obsolete packages. + + Move vim-doc to Section: doc. + + Update vim-common to Recommend all the vim variants. + + Add Build-Depends on libxpm-dev and unzip. + * debian/rules: + + Added support for running upstream's tests during the build process. + + Automatically generate the necessary .install/.links/.postinst settings + for installing the localized manpages. + + [ Pierre Habouzit ] + * Add support for cmake (from cmake.org). (closes: #357705) + * debcontrol.vim: add kfreebsd-amd64 to the ports list. + + [ Stefano Zacchiroli ] + * Screening of patches no longer needed with vim7 & pushing upstream + of as many debian-specific patches as possible. Results: + + removed patches: 102_filetype.vim.diff, 107_vim.1.diff, 107_xxd.1.diff, + 105_recognize-gnumakefile-am.diff, 123_accents.diff, + 133_filetype.vim.diff, 142_filetype.vim.diff, 153_filetype.vim.diff, + 154_svn.vim.diff, 156_scripts.vim.diff, 158_python.vim.diff, + 301_xxd.c.diff, 303_option.c.diff, 305_term.c.diff + * Added patch 102_pycomplete.vim: fixes a python omnicompletion bug when the + cursor is on an empty line + + [ Matthijs Mohlmann ] + * Updated debsources syntax file. + + Use debsources instead of sources. + + Make a regexpression of deb, deb-src, main, contrib and non-free. + + Remove setlocal iskeyword. + + Remove compatibility with vim 5.x. + + -- James Vega <jamessan@debian.org> Fri, 31 Mar 2006 17:50:11 -0500 + +vim (1:6.4-007+1) unstable; urgency=low + + [ Debian VIM Maintainers ] + * New upstream patch (007), see README.gz for details. + + [ Stefano Zacchiroli ] + * Handle /usr/bin/gvim with alternatives, so that it can be configured + to a vim executable with gui support when /usr/bin/vim is configured + to one with no such support. (closes: #345765) + + [ Pierre Habouzit ] + * vim's syntax coloring mode should consider .sce extension. + (Closes: #338771) + * subversion commit log syntax and l10n. (Closes: #341288) + * dh_install bug #349070 triggerd our svn.vim problem. + (rebuild Closes: #348955). + * enhances syntax/rst.vim. (Closes: #323044) + + [ James Vega ] + * Move alternatives handling out of vim-common so that we aren't modifying + alternatives when the targets don't yet exist. (closes: #348233) + * Add 'armeb' to debcontrol syntax file. (closes: #350513) + * debian/rules: Remove all binaries except xxd from vim-common. Handle the + rest with alternatives in the variant packages. + * debian/control: Changed vim-gui-common to Arch: all + * Added patch 156_scripts.vim.diff which adds detection of svk diffs as diff + filetype. (closes: #349764) + * Added patch 157_slrnrc.vim.diff which adds a few more functions to the + slrnrc syntax file. (closes: #347801) + * Added commented out example autocmd for last-position-jump to + /etc/vim/vimrc. (closes: #347597) + * Lintian cleanup: + + debian/control: Added a Depends line for vim-common. + + debian/rules: Use proper permissions when installing the console font in + vim-runtime + + debian/rules: Create a symlink to /usr/share/doc/vim-gui-common for each + GUI variant package. This fixes a usr-doc-symlink-without-dependency + warning. + + -- James Vega <jamessan@debian.org> Wed, 8 Feb 2006 15:11:37 -0500 + +vim (1:6.4-006+2) unstable; urgency=low + + [ Norbert Tretkowski ] + * debian/README.Debian: fixed typos (closes: #344608) + * patches/148_debchangelog.vim.diff: added sarge-{backports|volatile} to + debchangelog hilighting + * debian/control: removed build-dependencies added for woody backport + * debian/control: build-depend on make (>= 3.80+3.81.b4) + + [ Matthijs Mohlmann and Stefano Zacchiroli ] + * debian/rules: moved "export DH_OPTIONS" back to the beginning of the + file since old versions of make can't cope with it on + target-specific variables. Fixes FTBFS on some archs. + (closes: #344658) + + [ Stefano Zacchiroli ] + * debian/rules: added 'export' target to generate source package + * debian/rules: uses quilt to manage debian-specific patches, changed + build-deps accordingly + * Added patch 152_javascript.vim which fixes JavaScript syntax + highlighting (closes: #343402) + + [ Pierre Habouzit ] + * debian/control: fix vim-gui-common description. (closes: #347912) + * 304_memline.c.diff causes FTBFS on Hurd, fix it. (closes: #348170) + + -- Norbert Tretkowski <nobse@debian.org> Sun, 15 Jan 2006 19:41:58 +0100 + +vim (1:6.4-006+1) unstable; urgency=low + + [ Debian VIM Maintainers ] + * New upstream patches (005 and 006), see README.gz for details. + + [ Stefano Zacchiroli ] + * Epoched all 6.4 versioned relationships in debian/control, they were + erroneously non-epoched. (closes: #344368, #344414) + + -- Norbert Tretkowski <nobse@debian.org> Fri, 23 Dec 2005 00:30:20 +0100 + +vim (1:6.4-004+2) unstable; urgency=low + + [ Norbert Tretkowski ] + * Applied patch from Adeodato Simó to fix broken syntax hilighting + of urgency in debchangelog.vim. (closes: #338557, #343136, #344228) + * No longer lists a mailinglist as uploader in changelog, until a consensus + about policy items 4.4 and 5.6.4 is found. (closes: #343073) + + [ Stefano Zacchiroli ] + * Fixed typo in vim-gui-common description. (closes: #343152) + * Remove old /usr/share/doc/vim-common symlink during vim-doc and + vim-common preinst phase. (closes: #343289) + * debian/rules: finally found the karma of target-specific variables, + hopefully the file is clearer now ... Fixes FTBFS on hppa. + (closes: #344150) + * Fixed dangling manpage symlinks in vim-gui-common. + (closes: #344179, #343195, #343171) + * Moved vimtutor from vim-common to vim-runtime + * Added patch 151_sed.vim which improves sed's syntax highlighting. + (closes: #336125) + * Added patch 305_term.c which fixes 'pastetoggle' for working + properly with F1-F4 keys on Debian xterm's. (closes: #342220) + + -- Norbert Tretkowski <nobse@debian.org> Wed, 21 Dec 2005 10:09:37 +0100 + +vim (1:6.4-004+1) unstable; urgency=low + + [ Debian VIM Maintainers ] + * New upstream patches (002 to 004), see README.gz for details. + + [ Stefano Zacchiroli ] + * Added back vim-tiny package. (closes: #222138) + * Reshaped vim packaging as follows: + - vim-common -> arch-dependent common files (variants w/o GUI) + - vim-gui-common -> arch-dependent common files (variants w GUI) + (closes: #338027) + - vim-runtime -> vim runtime (arch-independent) + - vim -> default variant + - vim-* -> other variants + - vim-tiny -> tiny variant, no vim-runtime dependency + - the above changes additionally got rid of circular dependency + vim -> vim-common -> vim (closes: #340037) + * Added symlink /usr/share/vim/vimcurrent -> vim64, will be kept + proper in future releases. /etc/vim/vimrc no longer version-aware. + * Removed duplicate /usr/share/vim/vimfiles entry in vimrc. + (closes: #337825) + * (Re-)Fixed debian/runtime/vimrc, last version inhibit /usr/bin/ex. + * au commands in vimrc executed only if has("autocmd"). + * No longer try to move configuration files from /etc to /etc/vim + (ancient preinst, no longer needed to support upgrades from sarge). + * Updated Description-s in debian/control. + * Check for and removal of old vim.org diversion in postinst instead + of postrm (closes: #341081) + * Adds gvim, when compiled with gnome support, as an alternative for + gnome-text-editor, with priority lower than gedit (closes: #287202) + * Substituted @PKG@ in menu entry for package name (closes: #342074) + + [ James Vega ] + * Added patch 148_debchangelog, update syntax/debchangelog.vim to + recognize infrequently used but policy compliant syntax. + (closes: #338557) + * Fixed patch 304_memline.c.diff to avoid inifinte loops resolving + symlinks. (closes: #336560) + * Remove the 'p' vmap in /etc/vim/vimrc since it has various bad + side-effects such as not being able to paste from a register while + in visual mode. + + [ Matthijs Mohlmann ] + * Updated syntax for sshd_config and ssh_config. + * Updated syntax highlighting for asterisk.vim (Closes: #338256) + + -- Debian VIM Maintainers <pkg-vim-maintainers@lists.alioth.debian.org> Wed, 7 Dec 2005 22:02:34 +0100 + +vim (1:6.4-001+2) unstable; urgency=low + + [ Stefano Zacchiroli ] + * Fixed debian/runtime/vimrc, last version broke some plugins behaviour + (e.g. gzip, netrw) on files specified on cmdline. + + -- Debian VIM Maintainers <pkg-vim-maintainers@lists.alioth.debian.org> Sun, 23 Oct 2005 16:03:43 +0200 + +vim (1:6.4-001+1) unstable; urgency=low + + [ Debian VIM Maintainers ] + * New upstream patch (001), see README.gz for details. + + [ Stefano Zacchiroli ] + * Got rid of conflicts among vim-* packages (aka variants) using + alternatives for /usr/bin/vim. (closes: #67823, #123959, #280934) + * Got rid of removal of /usr/doc/* symlinks. + * Added "sources" debian/rules target which downloads upstream tarballs. + * Added patch 146_netrw.vim.diff, fixes some issues of netrw.vim with + file://* URLs. (closes: #334868) + * Added patch 303_option.c.diff, which fixes 'system()' behaviour when + $SHELL is empty. (closes: #219386) + * Added patch 304_memline.c.diff, which fixes swap file locking wrt + symlinks. (closes: #329826) + * Changed debian/runtime/vimrc so that /etc/papersize is read without using + system(), fixes issues with exotic shells. (closes: #271338) + + [ James Vega ] + * Added patch 147_perl.vim.diff, new upstream syntax file which supersedes + 120_perl.vim.diff. + + -- Debian VIM Maintainers <pkg-vim-maintainers@lists.alioth.debian.org> Sun, 23 Oct 2005 11:21:35 +0200 + +vim (1:6.4-000+1) unstable; urgency=low + + [ Debian VIM Maintainers ] + * New major upstream release (6.4). + + Fixed typo in /usr/share/vim/vim63/doc/usr_04.txt. (closes: #328664) + + [ Norbert Tretkowski ] + * Removed patches merged upstream: + + 118_ocaml.vim.diff + + -- Debian VIM Maintainers <pkg-vim-maintainers@lists.alioth.debian.org> Sat, 15 Oct 2005 18:40:22 +0200 + +vim (1:6.3+6.4b-003+1) experimental; urgency=low + + [ Debian VIM Maintainers ] + * New upstream patch (003), see README.gz for details. + + -- Debian VIM Maintainers <pkg-vim-maintainers@lists.alioth.debian.org> Fri, 14 Oct 2005 18:09:56 +0200 + +vim (1:6.3+6.4b-002+2) experimental; urgency=low + + [ Stefano Zacchiroli ] + * Updated patches for new release: + + 118_ocaml.vim.diff + + 124_errorformat.vim.diff + + 203_zh_TW.UTF8.po.diff + + -- Debian VIM Maintainers <pkg-vim-maintainers@lists.alioth.debian.org> Thu, 13 Oct 2005 13:09:25 +0200 + +vim (1:6.3+6.4b-002+1) experimental; urgency=low + + [ Debian VIM Maintainers ] + * New upstream patch (002), see README.gz for details. + + -- Debian VIM Maintainers <pkg-vim-maintainers@lists.alioth.debian.org> Wed, 12 Oct 2005 21:11:22 +0200 + +vim (1:6.3+6.4b-001+1) experimental; urgency=low + + [ Debian VIM Maintainers ] + * New major upstream beta release (6.4b). + * New upstream patch (001), see README.gz for details. + + [ Norbert Tretkowski ] + * Removed patches merged upstream: + + 110_php.vim.diff + + 112_prolog.vim.diff + + 113_xml.vim.diff + + 114_texinfo.vim.diff + + 116_sh.vim.diff + + 121_perl.vim.diff + + 126_filetype.vim.diff + + 128_vimdiff.1.diff + + 132_bib.vim.diff + + 139_perl.vim.diff + + 143_eruby.vim.diff + + 401_doc_exrc.diff + + 403_usr_04.txt.diff + + [ James Vega ] + * Updated patches for new release: + + 102_filetype.vim.diff + + 120_perl.vim.diff + + 142_filetype.vim.diff + + -- Debian VIM Maintainers <pkg-vim-maintainers@lists.alioth.debian.org> Wed, 12 Oct 2005 09:41:28 +0200 + +vim (1:6.3-090+2) unstable; urgency=low + + * Stefano Zacchiroli <zack@debian.org>: + + Fixed %ld typo in debian/patches/203_zh_TW.UTF8.po.diff + + Added patch debian/patches/403_usr_04.txt.diff, which fixes a + typo in usr_04.txt. (closes: #328664) + + -- Debian VIM Maintainers <pkg-vim-maintainers@lists.alioth.debian.org> Sat, 8 Oct 2005 16:09:41 +0200 + +vim (1:6.3-090+1) unstable; urgency=low + + * New upstream patches (087 to 090), see README.gz for details. + + * Norbert Tretkowski <nobse@debian.org>: + + Updated Standards-Version to 3.6.2 (no changes needed). + + Exec vim with -f parameter in .desktop file. (closes: #329292) + + * Stefano Zacchiroli <zack@debian.org>: + + Set SHELL=/bin/bash in debian/rules since we use bashisms. + (closes: #310974) + + Added patch 140_muttrc.vim.diff, which improves muttrc + highlighting. (closes: #327074) + + Added patch 141_asterisk.vim.diff, which adds support for Asterisk + configuration files sytnax highlighting. (closes: #322850) + + Added patch 142_filetype.vim.diff, which extends dch highlighting + to Debian NEWS files. (closes: #328081) + + Added patch 143_eruby.vim.diff, which adds support for eruby + highlighting. (closes: #315902) + + Added patch 144_scripts.vim.diff, which adds support for + highlighting tla diffs. (closes: #305677) + + Added patch 145_fortran.vim.diff, which fixes a matchit bug with + Fortran's "module procedure". (closes: #308865) + + Added patch 203_zh_TW.UTF8.po.diff, which fixes a translation + error in locale zh_TW.UTF-8. (closes: #319420) + + -- Debian VIM Maintainers <pkg-vim-maintainers@lists.alioth.debian.org> Fri, 30 Sep 2005 17:08:36 +0200 + +vim (1:6.3-086+1) unstable; urgency=low + + * New upstream patch (086), see README.gz for details. + + * Norbert Tretkowski <nobse@debian.org>: + + Corrected wrong capitalization of menu entry. (closes: #320602) + + * Stefano Zacchiroli <zack@debian.org>: + + Added patch 132_bib.vim.diff, which fixes highlighting of bibtex + comments. (closes: #316184) + + Added patch 133_filetype.vim.diff, which adds filetype recognition + for several Zope related file kinds. (closes: #311007) + + * Matthijs Mohlmann <matthijs@cacholong.nl>: + + Added patch 133_resolv.vim.diff, which fixes highlighting of resolv.conf + search entries. (closes: #321081) + + Added patch 134_sshconfig.vim.diff, added HashKnownHosts to syn keyword + sshconfigKeyword. (closes: #321119) + + Added debsources.vim to debian/updates to add syntax highlighting for + /etc/apt/sources.list and added this to filetype.vim. (closes: #308947) + + Added patch 136_muttrc.vim.diff, added crypt_autosign, crypt_autoencrypt + and xterm_set_titles to syn keyword. (closes: #323278) + + * Pierre Habouzit <madcoder@debian.org>: + + Fix patch 105_xmodmap.vim.diff: wrt XF86_ClearGrab. (closes: #322355) + + Fix typo in doc/editing.txt. (closes: #322254) + + * James Vega <jamessan@jamessan.com>: + + Added patch 137_filetype.vim.diff, recognize mutt-ng rc/temp files as + muttrc/mail filetypes. (closes: #307946) + + Added patch 138_filetype.txt.diff, fix a typo in the changelog-plugin + section of filetype.txt. (closes: #314595) + + Added patch 139_perl.vim.diff, fix recognition of regular expression + quantifiers. + + -- Debian VIM Maintainers <pkg-vim-maintainers@lists.alioth.debian.org> Thu, 1 Sep 2005 18:40:41 +0200 + +vim (1:6.3-085+1) unstable; urgency=high + + * New upstream patches (079 to 085), see README.gz for details. + + 6.3.081, 6.3.082: Fix arbitrary shell commands execution by wrapping + them in glob() or expand() function calls in modelines. (CAN-2005-2368) + (closes: #320017) + + * James Vega <jamessan@jamessan.com>: + + Added patch 129_filetype.vim.diff, which sets the filetype to perl for + *.plx files. (closes: #314309) + + * Matthijs Mohlmann <matthijs@cacholong.nl>: + + Added patch 130_fstab.vim.diff, added bind as option. (closes: #308890) + + Added patch 131_xxd.1.diff, fixes typo in xxd manpage. (closes: #311234) + + -- Debian VIM Maintainers <pkg-vim-maintainers@lists.alioth.debian.org> Thu, 28 Jul 2005 12:16:06 +0200 + +vim (1:6.3-078+1) unstable; urgency=low + + * New upstream patches (073 to 078), see README.gz for details. + + * James Vega <jamessan@jamessan.com>: + + Added patch 128_vimdiff.1.diff, which fixes a typo in the vimdiff + manpage. (closes: #310331) + + -- Debian VIM Maintainers <pkg-vim-maintainers@lists.alioth.debian.org> Tue, 14 Jun 2005 21:25:00 +0200 + +vim (1:6.3-072+1) unstable; urgency=high + + * New upstream patch (072), see README.gz for details. + + * James Vega <jamessan@jamessan.com>: + + Updated patch 125_gzip.vim.diff to match upstream's vim7 patch. + Removed compression detection for FileAppendPre since there's no good + way to retrieve the necessary information. + + Added patch 127_scripts.vim.diff, makes Vim automatically set the proper + filetype when editing lua scripts. The patch also enables recognition + of "#!/usr/bin/env xxx" hashbang lines. (closes: #309859) + + -- Debian VIM Maintainers <pkg-vim-maintainers@lists.alioth.debian.org> Fri, 20 May 2005 20:41:35 +0200 + +vim (1:6.3-071+2) unstable; urgency=low + + * Stefano Zacchiroli <zack@debian.org>: + + Modifications on debian/rules: + - Do not invoke dh_installdirs before creating .dirs file for current + variant (fixes non-installation of gvim.desktop in all variants). + - Optional cmdline parameter PATCH_NAME for make_patch target. + - Invoke dh_desktop to register gvim.desktop on postinst. + + Modifications on debian/vim-variant.desktop: + - Internationalized comment (inspired from gedit's one). + - Added MimeType entry. + - Uses svg icon. + + Added svg icon /usr/share/icons/vim.svg, thanks to + Paul Ortman <ortm8574@uidaho.edu>. (closes: #258669) + + Updated patch 118_ocaml.vim.diff (new upstream). + + Added patch 124_errorformat.vim.diff, makes vim follow error directories + on "make -C". (closes: #276005) + + Added patch 126_filetype.vim.diff, set tex filetype on .cls TeX classes, + distinguishing them from smalltalk sources. (closes: #169716) + + * Norbert Tretkowski <nobse@debian.org>: + + Build-Depend on debhelper (>= 4.2.21), required for dh_desktop call. + + Reverted value of backupcopy to default. + + * Matthijs Mohlmann <matthijs@cacholong.nl>: + + Added patch for german accents. (closes: #307807) + + * James Vega <jamessan@jamessan.com>: + + Added patch 125_gzip.vim.diff, maintain "max speed" and "max compression" + compression levels when editing gzip files. (closes: #280388) + + -- Debian VIM Maintainers <pkg-vim-maintainers@lists.alioth.debian.org> Sun, 15 May 2005 19:12:57 +0200 + +vim (1:6.3-071+1sarge1) stable; urgency=high + + * New upstream patches (081 and 082), see README.gz for details. + + 6.3.081, 6.3.082: Fix arbitrary shell commands execution by wrapping + them in glob() or expand() function calls in modelines. (CAN-2005-2368) + (closes: #320017) + + -- Norbert Tretkowski <nobse@debian.org> Sat, 30 Jul 2005 12:16:45 +0200 + +vim (1:6.3-071+1) unstable; urgency=medium + + * New upstream patches (069 to 071), see README.gz for details. + + * Norbert Tretkowski <nobse@debian.org>: + + Re-add dh_installdirs to vim-variant part in debian/rules, so copying + the desktop file no longer fails. (closes: #302830) + + Enabled backupcopy in global vimrc. (closes: #158657) + + * Stefano Zacchiroli <zack@debian.org>: + + Added vim-full variant with support for gnome and all interpreters. + (closes: #149077) + + Added /usr/share/common-licenses/ reference to debian/copyright. + + Remove debian/helpztags.1 on debian/rules clean (generated file). + + Updated patch 118_ocaml.vim.diff (new upstream). + + Added patch 122_html_indent.vim.diff, remove <bs> from indentkeys for + html. (closes: #280386) + + Added patch 401_doc_exrc.diff, fixes starting doc about "_exrc". + (closes: #279378) + + Suggests vim-scripts in debian/control. + + * Matthijs Mohlmann <matthijs@cacholong.nl>: + + Fixes menu entry with icon (wrong syntax used in menu file), thanks to + Alexis Sukrieh <sukria@sukria.net>. + + * James Vega <jamessan@jamessan.com>: + + Added patch 120_perl.vim.diff, update $VIMRUNTIME/syntax/perl.vim from + the author which fixes block indentation in packages. (closes: #220969) + + Added patch 121_perl.vim.diff, which adds syntax recognition for + CHECK/INIT blocks (similar to BEGIN/END). + + -- Norbert Tretkowski <nobse@debian.org> Sun, 24 Apr 2005 17:26:49 +0200 + +vim (1:6.3-068+4) unstable; urgency=medium + + * Norbert Tretkowski <nobse@debian.org>: + + Removed all kvim related packages, the code is no longer maintained. + Sorry. (closes: #234455, #237385, #283765, #293110, #194449, #205586, + #266431, #272621, #294848, #245006, #194964) + + Removed patch 401_gcc4.diff, it modified kvim code which is no longer + available. + + Added NEWS file, so people upgrading to this version getting informed + about the kvim removal. + + * Matthijs Mohlmann <matthijs@cacholong.nl>: + + Fixed up a patch for xml.vim. + + -- Norbert Tretkowski <nobse@debian.org> Sat, 2 Apr 2005 18:31:19 +0200 + +vim (1:6.3-068+3) unstable; urgency=medium + + * Norbert Tretkowski <nobse@debian.org>: + + Add a replaces: vim (<= 1:6.3-068+1) to every (k)vim-* package, required + for menu-icon-missing fix from 1:6.3-068+2. (closes: #301866) + + Urgency medium because above modification fixes regular upgrade with + apt-get. + + Fixed broken rgvim manpage. (closes: #301881) + + -- Norbert Tretkowski <nobse@debian.org> Tue, 29 Mar 2005 01:00:23 +0200 + +vim (1:6.3-068+2) unstable; urgency=low + + * Pierre Habouzit <pierre.habouzit@m4x.org>: + + Enhance the es.po. (closes: #206782) + + * Matthijs Mohlmann <matthijs@cacholong.nl>: + + Modified patch 113_xml.vim.diff that fixes #196001 has introduced + another syntax error. (closes: #301736) + + Fixed menu-icon-missing on vim-* packages. + + -- Norbert Tretkowski <nobse@debian.org> Mon, 28 Mar 2005 19:26:35 +0200 + +vim (1:6.3-068+1) unstable; urgency=low + + * New upstream patch (068), see README.gz for details. + + 6.3.068: When editing a compressed file xxx.gz which is a symbolic link + to the actual file a ":write" no longer renames the link (patch by James + Vega). (closes: #281630) + + * Norbert Tretkowski <nobse@debian.org>: + + Added James Vega <jamessan@jamessan.com> to uploaders. + + Fixed wrong executable registration in /usr/lib/mime/packages/kvim, + thanks to Robin Verduijn for the patch. (closes: #295471) + + Fixed synchronisation of syntax highlighting in fortran 90 programs. + (closes: #301452) + + Removed vim-doc's dependency on vim, so it's possible to install vim-doc + without also installing vim. + + * Pierre Habouzit <pierre.habouzit@m4x.org>: + + Fix php indent plugin, thanks to the ITLab at MUSC. (closes: #282135) + + Fix prolog syntax file. (closes: #269692) + + Fix xml syntax ('\' has no special meaning for xml). (closes: #196001) + + Fix texinfo syntax file warning. (closes: #286763) + + * Matthijs Mohlmann <matthijs@cacholong.nl>: + + Fix lintian warning packages-installs-file-to-usr-x11r6: + - Moving xpm files to /usr/share/pixmaps. + - Edited the menu files. + + Removed prerm-does-not-call-installdocs from lintian/vim. + + Added patch 111_fstab.vim.diff to fix highlighting in fstab. + (closes: #300108) + + Removed Suggests: vim from vim-doc in debian/control. + + Fixed binary-without-manpage for several packages. + + Fixed pkg-not-in-package-test in kvim-tcl, kvim-ruby, kvim-python and + kvim-perl. + + Fixed the errors postinst-does-not-call-updatemenus and + postrm-does-not-call-updatemenus. + + * James Vega <jamessan@jamessan.com>: + + Fixed wrong highlighting of comments in syntax/sh.vim when comments + occur between switches of case. (closes: #269325) + + * Stefano Zacchiroli <zack@debian.org>: + + Added patch 302_message.c.diff to fix CTRL-C quit loops in range commands. + (closes: #295639) + + Added patch 118_ocaml.vim.diff to ship latest version of ocaml runtime + support files: {syntax,ftplugin,ident}/ocaml.vim. + + Modifications on debian/rules: + - Uses debian/compat in place of debian/rules' DH_COMPAT. + - Ignores diff error in "make_patch" target since diff usually returns 1. + - Added support for command line VARIANT variable to override VARIANTS. + + * Pepijn de Langen <pepijn@ce.et.tudelft.nl>: + + Added patch 119_php.vim.diff to php syntax highlighting backticks. + (closes: #144754) + + -- Norbert Tretkowski <nobse@debian.org> Sat, 26 Mar 2005 16:32:25 +0100 + +vim (1:6.3-067+2) unstable; urgency=medium + + * Norbert Tretkowski <nobse@debian.org>: + + Disabled dh_installchangelogs and dh_installdocs for vim-doc. + + Raised urgency to medium because of upstream patch 6.3.066. + + -- Norbert Tretkowski <nobse@debian.org> Sun, 20 Mar 2005 22:05:36 +0100 + +vim (1:6.3-067+1) unstable; urgency=low + + * New upstream patches (065 to 067), see README.gz for details. + + 6.3.065: Entering Euro char via digraph doesn't always work. + (closes: #298162) + + * Norbert Tretkowski <nobse@debian.org>: + + Added Pierre Habouzit, Torsten Landschoff, Matthijs Mohlmann, Stefano + Zacchiroli, Alexis Sukrieh and Pepijn de Langen to uploaders. + (closes: #299446) + + Added a new patch from Christian Hammers which adds additional keywords + to /etc/fstab syntax hilighting. (closes: #299704) + + Modified --with-compiledby value to use $DEBFULLNAME and $DEBEMAIL. + + Updated tpp syntax file, thanks to Gerfried Fuchs. + + Changed priority of vim-common package from extra to optional. + + * Pierre Habouzit <pierre.habouzit@m4x.org>: + + Documented the /etc/vim/{g,}vimrc.local files in README.Debian. + + Fixed some debcontrol.vim issues: + - Don't search emails in fields that have not one. (closes: #114508) + - Fix debcontrolName according to Policy. (closes: #148144) + + Fixed tutor.vim to use usual locale envvars semantics. (closes: #289113) + + Added a 16px icon for menu entries too + (taken from http://www.vim.org/images/vim16x16.xpm). (closes: #39250) + + Fixed changelog.Debian.gz detection. (closes: #263740) + + Manpages various fixes: + - Escape some dashes in vim(1). (closes: #279606) + - Various fixes for xxd(1). (closes: #281124) + + Fixed french translation. (closes: #277502) + + * Matthijs Mohlmann <matthijs@cacholong.nl>: + + Add syntax highlighting for xmodmap. (closes: #296759) + + Fixed lintian warning unquoted-string-in-menu-item in kvim.menu. + + Fixed lintian warning spelling-error-in-readme-debian (adviced should + be advised). + + Changed current maintainer in copyright file. + + Fixed lintian warning package-relation-with-self in kvim. + + Fixed lintian warning binary-has-unneeded-section in vim (added + dh_strip). + + Added depends on vim in vim-doc. + + * Alexis Sukrieh <sukria@sukria.net>: + + Added a note about UTF-8 related issues in README.Debian. + + Added debian/patches/108_automake.vim.diff (thanks to Alexander Kogan) + which enables highlighting of _CPPFLAGS in automake files. + (closes: #196212) + + Added debian/patches/109_xdefaults.vim.diff (thanks to Peter De Wachter) + which fixes bad highlighting when putting a FONT directive in xdefaults. + (closes: #264284) + + * Stefano Zacchiroli <zack@debian.org>: + + Added #DEBHELPER# tag to debian/vim-{doc,common}.preinst. + + Minor cleanup of debian/rules so vim-{doc,common} uses dh_install + instead of dh_movefiles ("binary" target could now be invoked twice + after a single "install" invocation), let dh_compress compress README. + + -- Norbert Tretkowski <nobse@debian.org> Sun, 20 Mar 2005 10:56:11 +0100 + +vim (1:6.3-064+1) unstable; urgency=low + + * Norbert Tretkowski <nobse@debian.org>: + + New upstream patches (062 to 064), see README.gz for details. + + Set maintainer address to project mailinglist on alioth and added myself to + uploaders. + + Added a new patch which sets automake syntax recognition for files named + GNUmakefile.am. (closes: #277596) + + Added a new patch which adds testing-proposed-updates to debchangelog + syntax hilighting. + + -- Norbert Tretkowski <nobse@debian.org> Mon, 14 Mar 2005 14:58:49 +0100 + +vim (1:6.3-061+1) unstable; urgency=high + + * New upstream patches (059 to 061), see README.gz for details. + * Kudos to Javier Fernandez-Sanguino Pena, he discovered the usage of + insecure $$ constructs in vimspell.sh and tcltags.sh which have been + fixed with the last upload. + * Removed vimspell.sh and tcltags.sh, these scripts are no longer supported + upstream. + * Removed patch which was added in 1:6.3-058+1, it's no longer required. + + -- Norbert Tretkowski <nobse@debian.org> Tue, 01 Feb 2005 22:39:26 +0100 + +vim (1:6.3-058+1) unstable; urgency=high + + * New upstream patches (055 to 058), see README.gz for details. + * Added a new patch (stolen from Ubuntu) which modifies vimspell.sh and + tcltags.sh so they use mktemp instead of insecure $$ construction to + create temporary files. (CAN-2005-0069) (closes: #289560) + + -- Norbert Tretkowski <nobse@debian.org> Tue, 18 Jan 2005 20:12:25 +0100 + +vim (1:6.3-054+1) unstable; urgency=low + + * New upstream patches (047 to 054), see README.gz for details. + * Source /etc/vim/gvimrc.local if available. (closes: #272001) + * Added a new patch which fixes ftbfs on amd64 with gcc-4.0, thanks to + Andreas Jochens. (closes: #288731) + + -- Norbert Tretkowski <nobse@debian.org> Wed, 05 Jan 2005 20:51:36 +0100 + +vim (1:6.3-046+0sarge1) testing-proposed-updates; urgency=high + + * Built on testing for testing-proposed-updates because patch 045 fixes + several vulnerabilities found by Ciaran McCreesh related to the use of + options in modelines. (CAN-2004-1138) + + -- Norbert Tretkowski <nobse@debian.org> Sun, 19 Dec 2004 20:06:53 +0100 + +vim (1:6.3-046+1) unstable; urgency=low + + * New upstream patches (032 to 046), see README.gz for details. + * Added a desktop entry under /usr/share/applications/ for all variants. + (closes: #285065) + * Added farsi fonts to vim-common package. (closes: #258773) + + -- Norbert Tretkowski <nobse@debian.org> Sun, 12 Dec 2004 02:36:11 +0100 + +vim (1:6.3-031+3) unstable; urgency=low + + * Really add Brandens patch which adds XXX and FIXME comment hilighting + to sh.vim. (closes: #280471) + * Updated debcontrol.vim syntax file, which adds debcontrolArchitecture + for s390, thanks to Gerfried Fuchs. (closes: #281127) + + -- Norbert Tretkowski <nobse@debian.org> Sun, 14 Nov 2004 01:14:35 +0100 + +vim (1:6.3-031+2) unstable; urgency=low + + * Fixed broken vim-doc.preinst. (closes: #280824, #280825) + + -- Norbert Tretkowski <nobse@debian.org> Thu, 11 Nov 2004 23:56:12 +0100 + +vim (1:6.3-031+1) unstable; urgency=low + + * New upstream patches (026 to 031), see README.gz for details. + * Add symlink replacing from vim-common also to vim-doc. (closes: #279058) + * Added a new patch which adds XXX and FIXME comment hilighting to sh.vim, + thanks to Branden Robinson. (closes: #280471) + * Added a new patch which allows multiple spaces as arguments for xxd, + thanks to Glyn Kennington. (closes: #279709) + * Updated tpp and debcontrol syntax files, thanks to Gerfried Fuchs. + + -- Norbert Tretkowski <nobse@debian.org> Tue, 09 Nov 2004 18:56:42 +0100 + +vim (1:6.3-025+1) unstable; urgency=low + + * New upstream patches (020 to 025), see README.gz for details. + + -- Norbert Tretkowski <nobse@debian.org> Sun, 05 Sep 2004 21:13:04 +0200 + +vim (1:6.3-019+1) unstable; urgency=medium + + * New upstream patches (016 to 019), see README.gz for details. + * Added a new patch which adds some more sections to debcontrol.vim, + thanks to Branden Robinson. (closes: #258547) + * Removed setting the guifont in gvimrc. (closes: #267399, #268253) + * Compress README file. (closes: #267532) + + -- Norbert Tretkowski <nobse@debian.org> Mon, 30 Aug 2004 21:06:01 +0200 + +vim (1:6.3-015+1) unstable; urgency=medium + + * New upstream patches (014 and 015), see README.gz for details. + * Removed Luca from Uploaders, thanks for your work! (closes: #266476) + * Added a workaround for setting papersize when running vim in restricted + mode, thanks to Alexey Marinichev. (closes: #260452, #265227) + * Added a new patch which fixes broken else syntax hilighting in make.vim, + thanks to Steinar H. Gunderson. (closes: #260473, #259819) + * Fixed spelling error in vim-common description. (closes: #264279) + * Added a patch from 1:6.2-532+1 which got lost with the update to 6.3 + and fixes svn commit file highlighting. + * Added a new patch which adds s390 and amd64 to debcontrol.vim. + + -- Norbert Tretkowski <nobse@debian.org> Wed, 17 Aug 2004 19:34:13 +0200 + +vim (1:6.3-013+2) unstable; urgency=low + + * Empty vim-common directory before rmdir it. (closes: #258809) + * Add symlink replacing from vim-common also to vim-variant. + + -- Norbert Tretkowski <nobse@debian.org> Sun, 11 Jul 2004 18:11:45 +0200 + +vim (1:6.3-013+1) unstable; urgency=low + + * New upstream patches (012 and 013), see README.gz for details. + * More modifications on /usr/share/doc/vim-common symlink detection. + (closes: #257810) + * Source /etc/vim/vimrc.local if available. (closes: #257779) + * Added a virtual package gvim. + + -- Norbert Tretkowski <nobse@debian.org> Fri, 09 Jul 2004 22:56:33 +0200 + +vim (1:6.3-011+2) unstable; urgency=low + + * Modify detection of /usr/share/doc/vim-common symlink. (closes: #257623) + + -- Norbert Tretkowski <nobse@debian.org> Sun, 04 Jul 2004 19:35:16 +0200 + +vim (1:6.3-011+1) unstable; urgency=low + + * New upstream patch (011), see README.gz for details + * Disabled libgpm-dev build-dependency for kfreebsd-i386 (closes: #257230) + * Fixed vim-common's dependency on vim (closes: #257359, #257428, #257547) + * No longer compress version6.txt in documentation. (closes: #257338, #257445) + * Force replacing empty directories in /usr/share/doc with a symlink. + (closes: #257449) + + -- Norbert Tretkowski <nobse@debian.org> Sun, 04 Jul 2004 11:21:36 +0200 + +vim (1:6.3-010+1) unstable; urgency=low + + * Norbert Tretkowski <nobse@debian.org>: + + new upstream patches (005 to 010), see README.gz for details + + temporary disabled vim-tiny package, will be re-added with the next + upload + + * Mickael Marchand <marchand@kde.org>: + + updated kvim patch to apply without conflicts to new vim upstream + patches + + -- Norbert Tretkowski <nobse@debian.org> Thu, 30 Jun 2004 18:35:26 +0200 + +vim (1:6.3-004+1) unstable; urgency=low + + * Norbert Tretkowski <nobse@debian.org>: + + new major upstream release (6.3) + + new upstream patches (001 to 004), see README.gz for details + + merged changes from 1:6.2-532+6 + + fixed broken changelog symlink (closes: #253319) + + -- Norbert Tretkowski <nobse@debian.org> Fri, 11 Jun 2004 21:31:25 +0200 + +vim (1:6.2+6.3b-016+1) experimental; urgency=low + + * Norbert Tretkowski <nobse@debian.org>: + + new upstream patches (008 to 016), see README.gz for details + + made vim depend on vim-common in the same upstream version, so upgrading + to experimental vim will also install new vim-common (closes: #251736) + + merged changes from 1:6.2-532+5 + + -- Norbert Tretkowski <nobse@debian.org> Sun, 30 May 2004 16:45:02 -0300 + +vim (1:6.2+6.3b-007+1) experimental; urgency=low + + * Norbert Tretkowski <nobse@debian.org>: + + new upstream patches (002 to 007), see README.gz for details + + applied patch from Thomas de Grenier de Latour which fixes problems with + non-builtin icons and gtk+ 2.4 + + -- Norbert Tretkowski <nobse@debian.org> Wed, 26 May 2004 19:09:21 -0300 + +vim (1:6.2+6.3b-001+1) experimental; urgency=low + + * Norbert Tretkowski <nobse@debian.org>: + + new major upstream beta release (6.3b) + + new upstream patch (001), see README.gz for details + + modified runtime path in global vimrc + + merged changes from 1:6.2-532+3 and 1:6.2-532+4 + + -- Norbert Tretkowski <nobse@debian.org> Wed, 19 May 2004 19:19:26 +0200 + +vim (1:6.2+6.3a-018+1) experimental; urgency=low + + * Norbert Tretkowski <nobse@debian.org>: + + new upstream patches (007 to 018), see README.gz for details + + merged changes from 1:6.2-532+2 + + -- Norbert Tretkowski <nobse@debian.org> Wed, 12 May 2004 22:05:31 +0200 + +vim (1:6.2+6.3a-006+1) experimental; urgency=low + + * Norbert Tretkowski <nobse@debian.org>: + + new major upstream beta release (6.3a) + - removed second -X option from vim(1) (closes: #231504) + - added evim to executables in vim(1) (closes: #223866) + - fixed typo in man.vim plugin (closes: #256951) + + new upstream patches (001 to 006), see README.gz for details + + removed most debian specific patches, because they got merged upstream + now + + modified runtime path in global vimrc + + modified directories in vim.links and vim.install + + * Mickael Marchand <marchand@kde.org>: + + updated kvim patch to apply without conflicts to new vim upstream + beta release + + -- Norbert Tretkowski <nobse@debian.org> Sat, 08 May 2004 23:29:31 +0200 + +vim (1:6.2-532+6) unstable; urgency=low + + * Norbert Tretkowski <nobse@debian.org>: + + applied a patch from Eduard Bloch which makes gvim load the UTF-8 + version of fixed font when the $LANG or $LC_CTYPE environment variables + are set for the Unicode environment (closes: #177599) + + added a patch which enhances detection of html files (closes: #211263) + + removed c part from maze macro, looks like it doesn't work any longer + (closes: #121837) + + updated perl syntax file (closes: #232660) + + suggest 'ssh' instead of 'rsh' in tagsrch.txt (closes: #229634) + + capitalized 'unicode' string in description (closes: #172065) + + fixed broken removal of vim-gnome diversion (closes: #252248) + + fixed small typo in kvim mime files (closes: #250585) + + fixed small mistake in global vimrc (closes: #165964) + + added /usr/share/bug/vim/presubj file with some informations for + submitters of bugs + + -- Norbert Tretkowski <nobse@debian.org> Sat, 05 Jun 2004 16:42:42 +0200 + +vim (1:6.2-532+5) unstable; urgency=low + + * Norbert Tretkowski <nobse@debian.org>: + + re-added a vim-tiny package, looks like it got lost somewhere between + potato and woody (closes: #222138) + + added a patch which adds 'UsePAM' directive to sshdconfig.vim syntax file + (closes: #250064) + + added a patch from Doug Winter which add recognition of 'as' keyword in + python syntax file (closes: #247326) + + added a patch from Dirk Proesdorf which corrects new 'alternates' keyword + behaviour in mutt syntax file (closes: #247098) + + added a patch which adds syntax highlighting for whitespace files + (closes: #226352) + + added a patch from Brian M. Carlson which adds highlighting for 'lldiv_t' + in c syntax file (closes: #202316) + + added a patch which fixes a typo in map.txt (closes: #198667) + + modified gvim and kvim menu entry, so they are started with -f now + (closes: #153112) + + added -f to mailcap view rules (closes: #101377) + + -- Norbert Tretkowski <nobse@debian.org> Sat, 29 May 2004 22:43:11 -0300 + +vim (1:6.2-532+4) unstable; urgency=low + + * Norbert Tretkowski <nobse@debian.org>: + + used --with-features=big also for vim-basic variant (closes: #228485) + + binaries now including debugging information (closes: #249602) + + added support for "nostrip" in $DEB_BUILD_OPTIONS + + removed patch from Uli Martens introduced in 1:6.2-214+1 which modifies + runtime path in macros/less.sh, it's no longer needed since 1:6.2-532+3 + + modified link to upstream changelog, it's no longer gzipped since + 1:6.2-532+1 + + added version (>= 2.2) to libgtk2.0-dev build-dependency + + added priority to kvim package in control file + + -- Norbert Tretkowski <nobse@debian.org> Wed, 19 May 2004 16:30:25 +0200 + +vim (1:6.2-532+3) unstable; urgency=low + + * Norbert Tretkowski <nobse@debian.org>: + + added a patch from Peter Jay Salzman which fixes a typo in + hebrewp_utf-8.vim (closes: #197932) + + added a syntax file from Luca De Vitis which adds support for debconf + templates (closes: #168731) + + moved macros and tools back into runtime directory (closes: #190181) + + moved runtimepath above inclusion of filetype.vim in /etc/vim/vimrc + (closes: #248402) + + really added a patch from Jeff Layton with a syntax correction for + quoted here-documents (closes: #248562) + + less.sh is now executable (closes: #244599) + + modified new versioned dependencies from 1:6.2-532+2 so the dependency + is only on upstream release (closes: #248949) + + corrected version number in kvim conflicts/replaces, the epoche was + missing + + made /usr/share/doc/vim-common a symlink to /usr/share/doc/vim + + modified some overrides to shut up installer at ftp-master + + -- Norbert Tretkowski <nobse@debian.org> Sat, 15 May 2004 16:22:56 +0200 + +vim (1:6.2-532+2) unstable; urgency=low + + * Norbert Tretkowski <nobse@debian.org>: + + changes in debian/control from Michaels patch for hurd-i386 build got + lost (really closes: #244769) + + reenabled python package build for hurd-i386 build + + added versioned dependency on vim to vim-common and vice versa + (closes: #248423, #248563) + + build-conflict with libperl-dev (= 5.8.4-1) because it's broken + (see #247291 for details) + + added a patch from Jeff Layton with a syntax correction for quoted + here-documents (closes: #248562) + + updated netrw plugin (closes: #248623) + + updated squid syntax file (closes: #247810) + + added menu hints (closes: #82322) + + added background for syntax highlighting in vimrc (closes: #99762) + + disabled regenerating of tags file (closes: #244852) + + case-insensitive field names in debcontrol.vim (closes: #102232) + + added some notes about reporting bugs against this package to + README.Debian + + removed note about modelines from README.Debian + + -- Norbert Tretkowski <nobse@debian.org> Wed, 12 May 2004 20:42:56 +0200 + +vim (1:6.2-532+1) unstable; urgency=low + + * Norbert Tretkowski <nobse@debian.org>: + + new upstream patches (427 to 532), see README.gz for details + + no longer compress helpfiles, it breaks :helpg (closes: #244114) + + added a patch which fixes svn commit file highlighting + (closes: #239320, #242286) + + added a patch from Jan Minar which fixes a documentation error in + cmdline.txt (closes: #241907) + + added a patch from Roland Stigge which adds "Enhances" keyword to + debcontrol syntax highlighting (closes: #235524) + + added a patch from Domenico Andreoli which adds "reiserfs4" keyword to + fstab syntax highlighting (closes: #236571) + + applied a patch from Michael Bank which adds some exceptions for + hurd-i386 build (closes: #244769) + + added alternative for gnome-text-editor to vim-gnome (closes: #243443) + + added alternative for gvim.1.gz to vim.1.gz (closes: #231503, #238181) + + added vim-policy.txt to vim package (closes: #246174) + + cleaned up debian/rules file and files in debian/patches a bit + + * Mickael Marchand <marchand@kde.org>: + + updated kvim patch to apply without conflicts to new vim upstream + patches + + -- Norbert Tretkowski <nobse@debian.org> Sat, 08 May 2004 22:42:16 +0200 + +vim (1:6.2-426+1) unstable; urgency=low + + * Norbert Tretkowski <nobse@debian.org>: + + new upstream patches (365 to 426), see README.gz for details + + updated 01ruby_mkmf.diff to apply without conflicts to new vim upstream + patches + + * Mickael Marchand <marchand@kde.org>: + + updated kvim patch to apply without conflicts to new vim upstream + patches + + -- Norbert Tretkowski <nobse@debian.org> Thu, 01 Apr 2004 17:14:13 +0200 + +vim (1:6.2-364+1) unstable; urgency=low + + * Norbert Tretkowski <nobse@debian.org>: + + new upstream patches (354 to 364), see README.gz for details + + reenabled modelines in default vimrc (closes: #205501) + + -- Norbert Tretkowski <nobse@debian.org> Tue, 16 Mar 2004 19:09:35 +0100 + +vim (1:6.2-353+1) unstable; urgency=low + + * Norbert Tretkowski <nobse@debian.org>: + + new upstream patches (317 to 353), see README.gz for details + (closes: #188640) + + removed second /etc/vim from global runtime patch (closes: #237197) + + added vimrc_example.vim to $VIMRUNTIME (closes: #127141) + + -- Norbert Tretkowski <nobse@debian.org> Sat, 13 Mar 2004 16:25:06 +0100 + +vim (1:6.2-316+1) unstable; urgency=low + + * Norbert Tretkowski <nobse@debian.org>: + + new upstream patches (295 to 316), see README.gz for details + + -- Norbert Tretkowski <nobse@debian.org> Thu, 04 Mar 2004 22:27:35 +0100 + +vim (1:6.2-294+1) unstable; urgency=low + + * Norbert Tretkowski <nobse@debian.org>: + + new upstream patches (271 to 294), see README.gz for details + + moved arch independant data in a separate vim-common package + (closes: #233454) + + added a patch to recognize new keywords for java 1.5 in java syntax + file, thanks to Seneca Cunningham (closes: #231916) + + added a provides: kvim to kvim-packages (closes: #234690) + + * Mickael Marchand <marchand@kde.org>: + + updated kvim patch to apply without conflicts to new vim upstream + patches + + -- Norbert Tretkowski <nobse@debian.org> Sun, 29 Feb 2004 14:48:45 +0100 + +vim (1:6.2-270+1) unstable; urgency=low + + * Norbert Tretkowski <nobse@debian.org>: + + new upstream patches (215 to 270), see README.gz for details + + updated 01ruby_mkmf.diff and 11allow-threaded-perl.diff to apply without + conflicts to new vim upstream patches + + * Mickael Marchand <marchand@kde.org>: + + updated kvim patch to apply without conflicts to new vim upstream + patches + + -- Norbert Tretkowski <nobse@debian.org> Wed, 18 Feb 2004 00:22:01 +0100 + +vim (1:6.2-214+2) unstable; urgency=low + + * Mickael Marchand <marchand@kde.org>: + + add support for kvim-python, kvim-perl, kvim-tcl and kvim-ruby + (closes: #228865) + + add /etc/vim/gvimrc to kvim* packages + + -- Mickael Marchand <marchand@kde.org> Fri, 30 Jan 2004 00:52:11 +0100 + +vim (1:6.2-214+1) unstable; urgency=low + + * Norbert Tretkowski <nobse@debian.org>: + + new Co-Maintainer Mickael Marchand <marchand@kde.org> + + new upstream patches (182 to 214), see README.gz for details + + added a patch which adds sysfs to fstab keywords, thanks to Iain + Broadfoot (closes: #228475) + + added a patch which modifies runtime path in macros/less.sh, thanks + to Uli Martens (closes: #228779) + + * Mickael Marchand <marchand@kde.org>: + + updated kvim patch to apply without conflicts to new vim upstream + patches + + -- Norbert Tretkowski <nobse@debian.org> Wed, 28 Jan 2004 20:18:52 +0100 + +vim (1:6.2-181+1) unstable; urgency=low + + * new upstream patches (174 to 181), see README.gz for details + * added gvim to GNOME application menu, thanks to Lee Maguire + (closes: #226848) + + -- Norbert Tretkowski <nobse@debian.org> Fri, 16 Jan 2004 01:48:32 +0100 + +vim (1:6.2-173+1) unstable; urgency=low + + * new upstream patches (171 to 173), see README.gz for details + * added some more replaces to vim and kvim to avoid problems when upgrading + from older kvim (closes: #226735) + * added a patch which adds usbdevfs to fstab keywords, thanks to Ludovit + Hamaj (closes: #226714) + + -- Norbert Tretkowski <nobse@debian.org> Thu, 08 Jan 2004 19:19:01 +0100 + +vim (1:6.2-170+1) unstable; urgency=low + + * new upstream patches (155 to 170), see README.gz for details + * updated kvim patch to apply without conflicts to new vim upstream patches, + thanks to Mickael Marchand + * updated 01ruby_mkmf.diff and 11allow-threaded-perl.diff to apply without + conflicts to new vim upstream patches + * new Maintainer: Norbert Tretkowski <nobse@debian.org> + * new Co-Maintainer: Luca Filipozzi <lfilipoz@debian.org> + * added FAQ.gz to vim package (closes: #221909) + * added additional php keywords to syntax file, thanks to Tobias Olsson and + Jill Vogel (closes: #148757, #176448) + * added german umlauts to keymap file, thanks to Marco Herrn + (closes: #217633) + * added filetypes for php4 + + -- Norbert Tretkowski <nobse@debian.org> Tue, 30 Dec 2003 14:48:31 +0100 + +vim (1:6.2-154+1) unstable; urgency=low + + * new upstream patches (150 to 154), see README.gz for details + * added new variant for a lesstif package, thanks to Bernd Westphal + * added a patch to recognize reply-hook keyword in the muttrc syntax file, + thanks to Marco Herrn (closes: #221350) + + -- Norbert Tretkowski <nobse@debian.org> Wed, 10 Dec 2003 00:18:35 +0100 + +vim (1:6.2-149+1) unstable; urgency=low + + * new upstream patches (146 to 149), see README.gz for details + * added a patch to fix wrong highlighting in makefiles, thanks to Cyrille + Dunant (closes: #133323) + * added another patch to add '.' to debcontrolName highlighting, thanks to + David Weinehall (closes: #117038) + + -- Norbert Tretkowski <nobse@debian.org> Sun, 9 Nov 2003 21:21:39 +0100 + +vim (1:6.2-145+1) unstable; urgency=low + + * new upstream patches (140 to 145), see README.gz for details + * added arabic support, thanks to Mohammed Elzubeir and Anmar Oueja + (closes: #216012) + * updated kvim patch to apply without conflicts to new vim upstream patches, + thanks to Mickael Marchand + * updated 01ruby_mkmf.diff and 11allow-threaded-perl.diff to apply without + conflicts to new vim upstream patches + * renamed ruby1.8 build-dependency to ruby + + -- Norbert Tretkowski <nobse@debian.org> Wed, 5 Nov 2003 22:51:15 +0100 + +vim (1:6.2-139+1) unstable; urgency=low + + * new upstream patches (128 to 139), see README.gz for details + * merge with kvim source package, thanks to Mickael Marchand + (closes: #214076) + + -- Norbert Tretkowski <nobse@debian.org> Sun, 2 Nov 2003 19:51:14 +0100 + +vim (1:6.2-127+1) unstable; urgency=low + + * new upstream patches (107 to 127), see README.gz for details + * used suggests instead of depends on vim for vim-doc + + -- Norbert Tretkowski <nobse@debian.org> Fri, 17 Oct 2003 12:45:15 +0200 + +vim (1:6.2-106+4) unstable; urgency=low + + * vim-gnome now conflict with vim-gtk, and vice versa (closes: #214580) + * using pre-depends to fix #211710 and to handle overwriting of moved gvimrc + was a really bad idea, used replaces instead (closes: #214759) + * added a ttf-bitstream-vera suggests to gui packages because it seems to be + the only font which works fine with gtk2 gui + * added a note about gui support to perl, python, ruby and tcl package + description + * corrected short description in vim-gnome package + + -- Norbert Tretkowski <nobse@debian.org> Wed, 8 Oct 2003 23:52:27 +0200 + +vim (1:6.2-106+3) unstable; urgency=low + + * moved vim-usermanual and vim-referencemanual to vim-doc package + (closes: #214462, #214556) + * removed perl, python, ruby, tcl support from vim-gtk and vim-gnome + (closes: #214422) + * gzipped /usr/share/vim/vim62/doc/help.txt (closes: #214115) + + -- Norbert Tretkowski <nobse@debian.org> Tue, 7 Oct 2003 14:43:23 +0200 + +vim (1:6.2-106+2) unstable; urgency=low + + * really removed html documentation from vim package (closes: #211710) + + -- Norbert Tretkowski <nobse@debian.org> Mon, 29 Sep 2003 19:09:11 +0200 + +vim (1:6.2-106+1) unstable; urgency=low + + * new upstream patches (99 to 106), see README.gz for details + * added a note to README.Debian about new modeline behaviour + (closes: #212696) + * helpztags update, fixes production of tag files in improper format which + vim can't understand (closes: #213032) + * temporary disabled copying debian/vim-install into vim package, waiting + for an update (see #213034 for details) + + -- Norbert Tretkowski <nobse@debian.org> Sat, 27 Sep 2003 23:26:43 +0200 + +vim (1:6.2-098+5) unstable; urgency=low + + * added a several requested vim-gnome package (closes: #211820) + + -- Norbert Tretkowski <nobse@debian.org> Fri, 26 Sep 2003 20:19:51 +0200 + +vim (1:6.2-098+4) unstable; urgency=low + + * the "Happy Birthday Norbert" release + * corrected buggy Depends line in debian/control for packages depending on + vim, which should fix build problems (closes: #212686) + + -- Norbert Tretkowski <nobse@debian.org> Thu, 25 Sep 2003 12:36:47 +0200 + +vim (1:6.2-098+3) unstable; urgency=low + + * yet another helpztags update + + -- Norbert Tretkowski <nobse@debian.org> Wed, 24 Sep 2003 15:30:41 +0200 + +vim (1:6.2-098+2) unstable; urgency=low + + * added a pre-depends on vim to vim-doc (closes: #211710) + * updated helpztags and modified debian/rules to create a manpage, + thanks again to Artur R. Czechowski (closes: #211763) + * compiled in runtime path extension and removed entry from vimrc + * changed build-depends from tcl8.3 to tcl8.4 + + -- Norbert Tretkowski <nobse@debian.org> Wed, 24 Sep 2003 12:19:26 +0200 + +vim (1:6.2-098+1) unstable; urgency=low + + * new major upstream release (6.2) (closes: #196411, #205204) + * new upstream patches (1 to 98), see README.gz for details + * new Co-Maintainer: Norbert Tretkowski <nobse@debian.org> + * started putting upstream changes in a separate file + * added a patch that adds s390 support for control file syntax + highlighting (closes: #114750) + * moved to ruby1.8 (closes: #211539) + * enabled cscope functionality in vim package (closes: #159728) + * reenabled perl support in vim-perl package (closes: #200410) + * modified runtimepath in vimrc, added a README.Debian, helpztags and + vim-install to vim package, thanks Artur R. Czechowski + * added a Pre-Depends to packages depending on vim for a smooth upgrade + from older releases + * updated slrnrc syntax highlighting file, thanks to Sebastian Krause + * modified Build-Depends for an easier build on woody + * bumped up Standards-Version (no changes) + * moved config file and symlinks for gui version from vim package to each + of the additional packages (closes: #114944, #153068, #155711) + * fixed debchangelog syntax match, thanks to Gerfried Fuchs and Uli + Martens (closes: #153426) + * moved html documentation to new vim-doc package (closes: #121075) + + -- Norbert Tretkowski <nobse@debian.org> Sun, 14 Sep 2003 22:48:51 +0200 + +vim (1:6.1-474+2) unstable; urgency=low + + * debian/patches/07scripts.vim: fix typo that causes all files to be syntax + highlighed as though they were cvs diff files (closes: #194583) + + -- Luca Filipozzi <lfilipoz@debian.org> Mon, 26 May 2003 08:01:06 -0700 + +vim (1:6.1-474+1) unstable; urgency=low + + * debian/vim.postinst + debian/vim-variant.postinst: delete symlinks located + in /usr/doc (closes: #189858, #190022) + * debian/rules + debain/runtime/vimrc: applied a patch that causes build + system to not compress the top level vim documenation file, help.txt; this + is needed so that plugin documentation can be merged into the online help + (closes: #186673) [thanks to: Recai Oktas] + * debian/patches/02debcontrol.vim: applied a patch that prevents vim syntax + erroneous highlighting of email addresses in Debian control files + (closes: #186673) [thanks to: Dmitry Borodaenko] + * debian/patches/03debcontrol.vim: applied a patch that makes the syntax + highlighter recongize the new Debian sections: embedded, gnome, kde, + libdevel, perl, python + (closes: #193235) [thanks to: Branden Robinson] + * debian/patches/04vim.1: applied a patch that documents -X flag + (closes: #141804) [thanks to: Guido Guenther] + * debian/patches/05muttrc.vim: applied a patch that adds several keywords + starting with 'crypt-', reflecting recent changes in muttrc syntax + (closes: #190864) [thanks to: Marco Herrn] + * debian/patches/06tasm.vim: applied a patch that fixes minor typo + (closes: #165819) [thanks to: David Weinehall] + * debian/patches/07scripts.vim.diff: applied a patch that helps vim correctly + highlight cvs diff output + (closes: #152721) [thanks to: Guido Guenther] + * debian/patches/08sh.vim.diff: applied a patch that increases the strictness + of Bourne shell syntax highlighting with respect to "if [ ]" constructs + (closes: #140203) [thanks to: Malcolm Parsons] + * debian/patches/09c.vim.diff: applied a patch that adds additional signal + names to the list of recognized signals for syntax highlighting + (closes: #173797) [thanks to: Wolfram Quester] + * debian/patches/10apache.vim.diff: applied a patch that adds SSLEnable + to the list of recognized keyworkds (closes: #135243) + * debian/runtime/vimrc: applied a patch that makes vim set printoptions + paper to /etc/papersize as per Debian standards + (closes: #127830) [thanks to: Ken Shan] + * new upstream patches: + + 6.1.321: When 'mouse' includes 'n' but not 'v', don't allow starting + Visual mode with the mouse. + + 6.1.322: Win32: The host name is always "PC " plus the real host + name. + + 6.1.323: ":registers" doesn't stop listing for a "q" at the more + prompt. + + 6.1.324: Crash when dragging a vertical separator when <LeftMouse> + is remapped to jump to another window. + + 6.1.325: Shift-Tab is not automatically recognized in an xterm. + + 6.1.326: Using a search pattern may read from uninitialized data + (Yasuhiro Matsumoto) + + 6.1.327: When opening the "mbyte.txt" help file the utf-8 characters + are unreadable, because the fileencoding is forced to be latin1. + + 6.1.328: Prototype for enc_canon_search() is missing. + + 6.1.329: When editing a file "a b c" replacing "%" in ":Cmd %" or + ":next %" does not work properly. + + 6.1.330: GTK, Motif and Athena: Keypad keys produce the same code + as non-keypad keys, making it impossible to map them separately. + + 6.1.331: When translating the help files, "LOCAL ADDITIONS" no + longer marks the spot where help files from plugins are to be listed. + + 6.1.332: Win32: Loading Perl dynamically doesn't work with Perl + 5.8. Perl 5.8 also does not work with Cygwin and Ming. + + 6.1.333: Win32: Can't handle Unicode text on the clipboard. Can't + pass NUL byte, it becomes a line break. + + 6.1.334: Problem with drawing Hebrew characters. + + 6.1.335: Failure of obtaining the cursor position and window size + is ignored. + + 6.1.336: Warning for use of function prototypes of smsg(). + + 6.1.337: When using "finish" in debug mode in function B() for + ":call A(B())" does not stop after B() is finished. + + 6.1.338: When using a menu that checks out the current file from + Insert mode, there is no warning for the changed file until exiting + Insert mode. + + 6.1.339: Completion doesn't allow "g:" in ":let g:did_<Tab>". (Benji + Fisher) + + 6.1.340: Win32: Can't compile the Perl interface with nmake. + + 6.1.341: In Insert mode with 'rightleft' set the cursor is drawn + halfway a double-wide character. For CTRL-R and CTRL-K in Insert + mode the " or ? is not displayed. + + 6.1.342: With 'rightleft' set typing "c" on a double-wide character + causes the cursor to be displayed one cell to the left. + + 6.1.343: Cannot compile with the +multi_byte feature but without + +rightleft. Cannot compile without the GUI. + + 6.1.344: When using ":silent filetype" the output is still put in + the message history. + + 6.1.345: Win32: 'imdisable' doesn't work. + + 6.1.346: The scroll wheel can only scroll the current window. + + 6.1.347: When using cscope to list matching tags, the listed number + is sometimes not equal to what cscope uses. + + 6.1.348: Wildmode with wildmenu: ":set wildmode=list,full", + ":colorscheme <tab>" results in "zellner" instead of the first + entry. (Anand Hariharan) + + 6.1.349: "vim --serverlist" when no server was ever started gives + an error message without "\n". "vim --serverlist" doesn't exit when + the X server can't be contacted, it starts Vim unexpectedly. + + 6.1.350: When entering a buffer with ":bnext" for the first time, + using an autocommand to restore the last used cursor position + doesn't work. + + 6.1.351: Crash when starting Vim the first time in an X server. (John + McGowan) + + 6.1.352: Win32: Crash when setting "imdisable" in _vimrc. + + 6.1.353: Problem with drawing Arabic characters. + + 6.1.354: MS-Windows 98: Notepad can't paste text copied from Vim when + 'encoding' is "utf-8". + + 6.1.355: In a regexp '\n' will never match anything in a string. + + 6.1.356: Compiler warnings for using convert_setup() and a few + other things. + + 6.1.357: CR in the quickfix window jumps to the error under the + cursor, but this doesn't work in Insert mode. + + 6.1.358: The tutor doesn't select another locale version properly. + + 6.1.359: Mac Carbon: Vim doesn't get focus when started from the + command line. Crash when using horizontal scroll bar. + + 6.1.360: In Insert mode CTRL-K ESC messes up a multi-byte character. + + 6.1.361: Cannot jump to a file mark with ":'M". + + 6.1.362: tgetent() may return zero for success. tgetflag() may + return -1 for an error. + + 6.1.363: byte2line() can return one more than the number of lines. + + 6.1.364: That the FileChangedShell autocommand event never nests + makes it difficult to reload a file in a normal way. + + 6.1.365: Setting a breakpoint in a sourced file with a relative + path name doesn't work. + + 6.1.366: Can't use Vim with Netbeans. + + 6.1.367: Setting a breakpoint in a function doesn't work. For + a sourced file it doesn't work when symbolic links are + involved. (Servatius Brandt) + + 6.1.368: Completion for ":map" does not include <silent> and + <script>. ":mkexrc" do not save the <silent> attribute of mappings. + + 6.1.369: VMS: Vim hangs when attempting to edit a read-only file + in the terminal. Problem with VMS filenames for quickfix. + + 6.1.370: #ifdef nesting is unclear. + + 6.1.371: "%V" in 'statusline' doesn't show "0-1" in an empty line. + + 6.1.372: With 16 bit ints there are compiler warnings. + + 6.1.373: The default page header for printing is not translated. + + 6.1.374: MS-Windows: Cannot build GvimExt with MingW or Cygwin. + + 6.1.375: MS-Windows: ':!dir "%"' does not work for a file name + with spaces. + + 6.1.376: "vim --version" and "vim --help" have a non-zero exit + code. That is unusual. + + 6.1.377: Can't add words to 'lispwords' option. + + 6.1.378: When two buffer-local user commands are ambiguous, a full + match with a global user command isn't found. + + 6.1.379: Linux with kernel 2.2 can't use the alternate stack in + combination with threading, causes an infinite loop. + + 6.1.380: When 'winminheight' is zero and the quickfix window is + zero lines, entering the window doesn't make it highter. (Christian + J. Robinson) + + 6.1.381: When a BufWriteCmd is used and it leaves the buffer + modified, the window may still be closed. + + 6.1.382: Win32 GUI: When using two monitors, the code that + checks/fixes the window size and position (e.g. when a font changes) + doesn't work properly. + + 6.1.383: The filling of the status line doesn't work properly for + multi-byte characters. There is no check for going past the end of + the buffer. + + 6.1.384: It is not possible to find if a certain patch has been + included. + + 6.1.385: Can't compile without the multi-byte feature. + + 6.1.386: Get duplicate tags when running ":helptags". + + 6.1.387: Compiler warning for pointer cast. + + 6.1.388: Compiler warning for pointer cast. + + 6.1.389: Balloon evaluation doesn't work for GTK. has("balloon_eval") + doesn't work. + + 6.1.390: It's not possible to tell Vim to save and exit through the + Netbeans interface. Would still try to send balloon eval text after + the connection is closed. Can't use Unicode characters for sign text. + + 6.1.391: ml_get + + 6.1.392: Highlighting in the 'statusline' is in the wrong position + when an item is tructated. + + 6.1.393: When compiled with Python and threads, detaching the + terminal may cause Vim to loop forever. + + 6.1.394: The netbeans interface doesn't recognize multibyte glyph + names. + + 6.1.395: VMS: OLD_VMS is never defined. Missing function prototype. + + 6.1.396: Compiler warnings for using enum. + + 6.1.397: The install program may use a wrong path for the diff + command if there is a space in the install directory path. + + 6.1.398: Saving the typeahead for debug mode causes trouble for a + test script. + + 6.1.399: Warning for unused variable. + + 6.1.400: When a BufWriteCmd wipes out the buffer it may still + be accessed. + + 6.1.401: Building the Win16 version with Borland 5.01 doesn't + work. "make test" doesn't work with Make_dos.mak. + + 6.1.402: When evaluating a function name with curly braces, an + error is not handled consistently. + + 6.1.403: MS-Windows 16 bit: compiler warnings. + + 6.1.404: Various small problems. + + 6.1.405: A few files are missing from the toplevel Makefile. + + 6.1.406: When a statusline item doesn't fit arbitrary text appears. + + 6.1.407: ":set scrollbind | help" scrollbinds the help + window. (Andrew Pimlott) + + 6.1.408: When 'rightleft' is set unprintable character 0x0c is + displayed as ">c0<". + + 6.1.409: Generating tags for the help doesn't work for some locales. + + 6.1.410: Linking error when compiling with Netbeans but without + sign icons. + + 6.1.411: When 'virtualedit' is set, highlighting a Visual block + beyond the end of a line may be wrong. + + 6.1.412: When swapping terminal screens and using ":gui" to start + the GUI, the shell prompt may be after a hit-enter prompt. + + 6.1.413: When 'clipboard' contains "unnamed", "p" in Visual mode + doesn't work correctly. + + 6.1.414: VMS: Vim busy waits when waiting for input. + + 6.1.415: When there is a vertical split and a quickfix window, + reducing the size of the Vim window may result in a wrong window + layout and a crash. + + 6.1.416: When using the Netbeans interface, a line with a sign + cannot be changed. + + 6.1.417: Unprintable multi-byte characters are not handled + correctly. Multi-byte characters above 0xffff are displayed as + another character. + + 6.1.418: The result of strftime() is in the current locals. Need + to convert it to 'encoding'. + + 6.1.419: Vim doesn't compile on AIX 5.1. + + 6.1.420: convert_input() has an unnecessary STRLEN(). Conversion + from UCS-2 to a codepage uses word count instead of byte count. + + 6.1.421: MS-Windows 9x: When putting text on the clipboard it can + be in the wrong encoding. + + 6.1.422: Error in .vimrc doesn't cause hit-enter prompt when + swapping screens. + + 6.1.423: Can't find arbitrary text in help files. + + 6.1.424: Win32: Gvim compiled with VC++ 7.0 run on Windows 95 does + not show menu items. + + 6.1.425: ":helptags $VIMRUNTIME/doc" does not add the "help-tags" + tag. + + 6.1.426: "--remote-wait +cmd file" waits forever. + + 6.1.427: Several error messages for regexp patterns are not + translated. + + 6.1.428: FreeBSD: wait() may hang when compiled with Python support + and doing a system() call in a startup script. + + 6.1.429: Crash when using showmarks.vim plugin. + + 6.1.430: In Lisp code backslashed parens should be ignored for "%". + + 6.1.431: Debug commands end up in redirected text. + + 6.1.432: MS-Windows: ":make %:p" inserts extra backslashes. + + 6.1.433: ":popup" only works for Win32. + + 6.1.434: Win32: When there are more than 32767 lines, the scrollbar + has a roundoff error. + + 6.1.435: ":winsize x" resizes the Vim window to the minimal + size. (Andrew Pimlott) + + 6.1.436: When a long UTF-8 file contains an illegal byte it's hard + to find out where it is. + + 6.1.437: Using multi-byte functions when they are not available. + + 6.1.438: When Perl has thread support Vim cannot use the Perl + interface. + + 6.1.439: Netbeans: A "create" function doesn't actually create a + buffer, following functions may fail. + + 6.1.440: The "@*" command doesn't obtain the actual contents of + the clipboard. + + 6.1.441: "zj" and "zk" cannot be used as a motion command after + an operator. + + 6.1.442: Unicode 3.2 defines more space and punctuation characters. + + 6.1.443: Win32: The gvimext.dll build with Borland 5.5 requires + another DLL. + + 6.1.444: Win32: Enabling a build with gettext support is not + consistant. + + 6.1.445: DJGPP: get warning for argument of putenv() + + 6.1.446: Win32: The MingW makefile uses a different style of + arguments than other makefiles. Dynamic IME is not supported + for Cygwin. + + 6.1.447: "make install" uses "make" directly for generating help + tags. + + 6.1.448: 'titlestring' has a default maximum width of 50 chars + per item. + + 6.1.449: When "1" and "a" are in 'formatoptions', auto-formatting + always moves a newly added character to the next line. + + 6.1.450: Termcap entry "kB" for back-tab is not recognized. + + 6.1.451: GUI: When text in the find dialog contains a slash, + a backslash is inserted the next time it is opened. + + 6.1.452: Win32: IME support doesn't work for MSVC. + + 6.1.453: When compiled without sign icons but with sign support, + adding a sign may cause a crash. + + 6.1.454: Win32: pasting Russian text in Vim with 'enc' set to cp1251 + results in utf-8 bytes. Conversion from DBCS to UCS2 does not work + when 'encoding' is not the active codepage. + + 6.1.455: Some Unicode characters can be one or two character + cells wide. + + 6.1.456: Win32: IME doesn't work. + + 6.1.457: An empty register in viminfo causes conversion to fail. + + 6.1.458: Compiler warning for pointer. + + 6.1.459: Win32: libcall() may return an invalid pointer and cause + Vim to crash. + + 6.1.460: GTK: after scrolling the text one line with a key, clicking + the arrow of the scrollbar does not always work. + + 6.1.461: When a keymap is active, typing a character in Select mode + does not use it. + + 6.1.462: When autocommands wipe out a buffer, a crash may + happen. (Hari Krishna Dara) + + 6.1.463: When writing a compressed file, the file name that gzip + stores in the file is the weird temporary file name. + + 6.1.464: Crash when using C++ syntax highlighting. + + 6.1.465: Compile error when using cygwin. + + 6.1.466: The "-f" argument is a bit obscure. + + 6.1.467: Setting the window title doesn't work for Chinese. + + 6.1.468: ":mksession" also stores folds for buffers which will not + be restored. + + 6.1.469: 'listchars' cannot contain multi-byte characters. + + 6.1.470: Polish messages don't show up correctly on MS-Windows. + + 6.1.471: ":jumps" output continues after pressing "q" at the + more-prompt. + + 6.1.472: When there is an authentication error when connecting to + the X server Vim exits. + + 6.1.473: Referring to $curwin or $curbuf in Perl 5.6 causes a crash. + + 6.1.474: When opening the command-line window in Ex mode it's + impossible to go back. + + -- Luca Filipozzi <lfilipoz@debian.org> Sun, 6 Apr 2003 20:35:12 -0700 + +vim (1:6.1-320+1) unstable; urgency=low + + * new upstream patches: + + 6.1.291: Win32: CTRL-@ doesn't work. Don't even get a message for it. + + 6.1.292: Win32: Can't compile with new MingW compiler. Borland 5 + makefile doesn't generate pathdef.c. + + 6.1.293: byte2line() returns a wrong result for some values. + + 6.1.294: Can't include a multi-byte character in a string by its + hex value. + + 6.1.295: Processing the cs.po file generates an error. + + 6.1.296: Win32: When cancelling the font dialog 'guifont' remains + set to "*". + + 6.1.297: "make test" fails in test6 in an UTF-8 environment. + + 6.1.298: When using signs and the first line of a closed fold has + a sign it can be redrawn as if the fold was open. + + 6.1.299: ":edit +set\ ro file" doesn't work. + + 6.1.300: Handling of ETO_IGNORELANGUAGE is confusing. + + 6.1.301: French translation of file-save dialog doesn't show + file name. + + 6.1.302: Counting lines of the Visual area is incorrect for closed + folds. + + 6.1.303: The Top/Bottom/All text does not always fit in the ruler + when translated to Japanese. Problem with a character being wider + when in a bold font. + + 6.1.304: Win32: Postscript is always enabled in the + MingW Makefile. Pathdef.c isn't generated properly with + Make_bc5.mak. (Yasuhiro Matsumoto) + + 6.1.305: When 'verbose' is 14 or higher, a function call may cause + reading uninitialized data. + + 6.1.306: The AIX VisualAge cc compiler doesn't define __STDC__. + + 6.1.307: When a double-byte character has an illegal tail byte the + display is messed up. + + 6.1.308: Can't reset the Visual mode returned by visualmode(). + + 6.1.309: The tutor doesn't select German if the locale name is + "German_Germany.1252". + + 6.1.310: All double-byte characters are displayed as "XX". + + 6.1.311: VMS: path in window title doesn't include necessary + separator. file version doesn't always work properly with + Unix. Crashes because of memory overwrite in GUI. Didn't always + handle files with lowercase and correct path. + + 6.1.312: When using ":silent" debugging is also done silently. + + 6.1.313: When a ":drop fname" command is used and "fname" is open + in another window, it is also opened in the current window. + + 6.1.314: Missing backslash in "Generic Config file" syntax menu. + + 6.1.315: A very long hostname may lead to an unterminated + string. Failing to obtain a hostname may result in garbage. + + 6.1.316: When exiting with "wq" and there is a hidden buffer, after + the "file changed" dialog there is a warning for a changed buffer. + + 6.1.317: Closing a window may cause some of the remaining windows + to be positioned wrong if there is a mix of horizontal and vertial + splits. + + 6.1.318: auto/pathdef.c can include wrong quotes when a compiler + flag includes quotes. + + 6.1.319: Using "--remote +cmd file" does not execute "cmd". + + 6.1.320: When a ":drop one\ file" command is used the file "one\ + file" is opened, the backslash is not removed. + * debian/patches/01ruby_mkmf: fixes an FTBFS that impacts ia64 but should + probably have affected all archs (closes: Bug#174375) + + -- Luca Filipozzi <lfilipoz@debian.org> Sat, 8 Feb 2003 12:28:24 -0800 + +vim (1:6.1-290+1) unstable; urgency=low + + * new upstream patches: + + 6.1.267: Using "p" to paste into a Visual selected area may cause + a crash. + + 6.1.268: When triggering an abbreviation with a multi-byte character, + this character is not correctly inserted after expanding the + abbreviation. + + 6.1.269: After using input() text written with ":redir" gets + extra indent. + + 6.1.270: GCC 3.2.1 still seems to have an optimizer problem. + + 6.1.271: When compiling without the +syntax feature there are errors. + + 6.1.272: After using ":set define<" a crash may happen. + + 6.1.273: When the cursor doesn't blink, redrawing an exposed area + may hide the cursor. + + 6.1.274: Resetting the iconv() state after each error is wrong for + an incomplete sequence. + + 6.1.275: When using "v" in a startup script, get warning message + that terminal cannot highlight. + + 6.1.276: "gvim --remote file" doesn't prompt for an encryption key. + + 6.1.277: Compilation error when building without GUI. + + 6.1.278: When using signs the line number of a closed fold doesn't + line up with the other line numbers. + + 6.1.279: The prototype for smsg() and smsg_attr() do not match the + function definition. This may cause trouble for some compilers. + + 6.1.280: It's possible to use an argument "firstline" or "lastline" + for a function but using "a:firstline" or "a:lastline" in the + function won't work. + + 6.1.281: In Insert mode CTRL-X CTRL-G leaves the cursor after + the ruler. + + 6.1.282: Elvis uses "se" in a modeline, Vim doesn't recognize this. + + 6.1.283: For ":sign" the icon file name cannot contain a space. + + 6.1.284: On Solaris there is a warning for "struct utimbuf". + + 6.1.285: Can't wipe out a buffer with 'bufhidden' option. + + 6.1.286: 'showbreak' cannot contain multi-byte characters. + + 6.1.287: Effect of "delete" and "wipe" in 'bufhide' were mixed up. + + 6.1.288: ":silent function F" hangs. + + 6.1.289: Compiler warning for pointer. + + 6.1.290: Truncating long text for message box may break multi-byte + character. + + -- Luca Filipozzi <lfilipoz@debian.org> Thu, 16 Jan 2003 21:37:13 -0800 + +vim (1:6.1-266+1) unstable; urgency=low + + * new epoch: change package version numbering so that new upstream patches + don't generate new source packages + * new upstream patches: + + 6.1.264: exists() does not work for built-in functions + + 6.1.265: libcall() can be used in 'foldexpr' to call any system + function. rename(), delete() and remote_send() can also be used in + 'foldexpr'. These are security problems. + + 6.1.266: Win32: compile error in eval.c. + + -- Luca Filipozzi <lfilipoz@debian.org> Tue, 24 Dec 2002 14:06:30 -0800 + +vim (6.1.263-2) unstable; urgency=low + + * debian/control: fix Build-Depends to include bzip2 (closes: Bug#171078) + * debian/patches: 00os_unix.h - set default runtime path to include /etc/vim + + -- Luca Filipozzi <lfilipoz@debian.org> Thu, 28 Nov 2002 09:15:32 -0800 + +vim (6.1.263-1) unstable; urgency=low + + * New maintainer + * New debian build scripts + * debian/runtime/vimrc: added 'set nomodeline' to address potential + security issue wherein malicious persons author files with hazardous + modelines, users unwittingly open said files and vim evaluates the + dangerous modelines + * Apply upstream patches: + + 6.1.207: Indenting a Java file hangs below a line with a comment + after a command. + + 6.1.208: Can't use the buffer number from the Python interface. + + 6.1.209: Printing doesn't work on Mac OS classic. + + 6.1.210: When there is an iconv() conversion error when reading a + file there can be an error the next time iconv() is used. + + 6.1.211: The message "use ! to override" is confusing. + + 6.1.212: When Vim was started with "-R" ":new" creates a buffer + 'noreadonly' while ":enew" has 'readonly' set. + + 6.1.213: Using CTRL-W H may cause a big gap to appear below the + last window. + + 6.1.214: When installing Vim and the runtime files were checked + out from CVS the CVS directories will also be installed. + + 6.1.215: Win32: ":pwd" uses backslashes even when 'shellslash' + is set. + + 6.1.216: When dynamically loading the iconv library, the error + codes may be confused. + + 6.1.217: When sourcing the same Vim script using a different name + (symbolic link or MS-Windows 8.3 name) it is listed twice with + ":scriptnames". (Tony Mechelynck) + + 6.1.218: No error message for using the function argument + "5+". (Servatius Brandt) + + 6.1.219: When using ":amenu :b 1<CR>" with a Visual selection and + 'insertmode' is set, Vim does not return to Insert mode. (Mickael + Marchand) + + 6.1.220: When using a BufReadPost autocommand that changes the line + count, e.g., "$-1join", reloading a file that was changed outside + Vim does not work properly. + + 6.1.221: Changing case may not work properly, depending on the + current locale. + + 6.1.222: Patch 6.1.219 was incomplete. + + 6.1.223: Win32: When IME is activated 'iminsert' is set, but it + might never be reset when IME is disabled. All systems: 'iminsert' is + set to 2 when leaving Insert mode, even when langmap is being used. + + 6.1.224: "expand('$VAR')" returns an empty string when the expanded + $VAR is not an existing file. + + 6.1.225: Using <C-O><C-^> in Insert mode has a delay when starting + "vim -u NONE" and ":set nocp hidden". (Emmanuel) do_ecmd() uses + fileinfo(), the redraw is done after a delay to give the user time + to read the message. + + 6.1.226: Using ":debug" with a ":normal" command may cause a + hang. (Colin Keith) + + 6.1.227: It is possible to use a variable name "asdf:asdf" and + ":let j:asdf = 5" does not give an error message. + + 6.1.228: Win32: The special output function for Hangul is used + too often, causing special handling for other situations + to be skipped. bInComposition is always FALSE, causing + ImeGetTempComposition() always to return NULL. + + 6.1.229: Win32: Conversion to/from often used codepages requires + the iconv library, which is not always available. + + 6.1.230: Win16: building doesn't work. + + 6.1.231: Double clicking with the mouse to select a word does not + work for multi-byte characters. + + 6.1.232: Using ex_normal_busy while it might not be available. (Axel + Kielhorn) + + 6.1.233: ":help expr-||" does not work. + + 6.1.234: Get a warning for using a negative value for st_dev. + + 6.1.235: 'iminsert' is changed from 1 to 2 when leaving Insert + mode. (Peter Valach) + + 6.1.236: Memory leaks when appending lines for ":diffget" or + ":diffput" and when reloading a changec buffer. + + 6.1.237: Putting in Visual block mode does not work correctly when + "$" was used or when the first line is short. + + 6.1.238: Win32: The "icon=" argument for the ":menu" command does + not search for the bitmap file. + + 6.1.239: Giving an error for missing :endif or :endwhile when + being interrupted. + + 6.1.240: Win32 with BCC 5: CPU may be defined in the environment, + which causes a wrong argument for the compiler. + + 6.1.241: Something goes wrong when drawing or undrawing the cursor. + + 6.1.242: When pasting a large number of lines on the command line + it is not possible to interrupt. + + 6.1.243: Win32: When the OLE version is started and wasn't + registered, a message pops up to suggest registering, even when + this isn't possible (when the registry is not writable). + + 6.1.244: Patch 6.1.237 was missing the diff for vim.h. + + 6.1.245: Comparing with ignored case does not work properly for + Unicode with a locale where case folding an ASCII character results + in a multi-byte character. + + 6.1.246: ":blast" goes to the first buffer if the last one is + unlisted. + + 6.1.247: ACL support doesn't always work properly. + + 6.1.248: Typing 'q' at the more-prompt for ":let" does not quit + the listing. + + 6.1.249: Can't expand a path on the command line if it includes a + "|" as a trail byte of a multi-byte character. + + 6.1.250: When changing the value of 'lines' inside the expression + set with 'diffexpr' Vim might crash. + + 6.1.251: Can't use completion for ":lcd" and ":lchdir" like ":cd". + + 6.1.252: "vi}" does not include a line break when the "}" is at + the start of a following line. + + 6.1.253: Win32 with Cygwin: Changes the path of arguments in a + wrong way. + + 6.1.254: exists("foo{bar}") does not work. ':unlet v{"a"}r' does + not work. ":let v{a}r1 v{a}r2" does not work. ":func F{(1)}" does + not work. ":delfunc F{" does not give an error message. ':delfunc + F{"F"}' does not work. + + 6.1.255: Crash when loading menu.vim a second time. ":unlet garbage + foo" tries unletting "foo" after an error message. Very long function + arguments cause very long messages when 'verbose' is 14 or higher. + + 6.1.256: Defining a function after ":if 0" could still cause an + error message for an existing function. Leaking memory when there + are trailing characters for ":delfunc". + + 6.1.257: ":cwindow" always sets the previous window to the last + but one window. + + 6.1.258: Buffers menu doesn't work properly for multibyte buffer + names. + + 6.1.259: Mac: with 'patchmode' is used filenames are truncated. + + 6.1.260: GCC 3.2 still seems to have an optimizer problem. + + 6.1.261: When deleting a line in a buffer which is not the current + buffer, using the Perl interface Delete(), the cursor in the current + window may move. + + 6.1.262: When jumping over folds with "z[", "zj" and "zk" the + previous position is not remembered. + + 6.1.263: When typing a multi-byte character that triggers an + abbreviation it is not inserted properly. + + -- Luca Filipozzi <lfilipoz@debian.org> Tue, 26 Nov 2002 09:46:26 -0800 + +vim (6.1.206-1) unstable; urgency=low + + * Change priority of vim package back to optional + * Switch to tcl8.4-dev + * Apply upstream patches: + + 6.1.166: When 'autoindent' is set and mswin.vim has been sourced, + pasting with CTRL-V just after auto-indenting removes the + indent. + + 6.1.167: When giving a negative argument to ":retab" strange things + start happening. + + 6.1.168: Pressing CTRL-C at the hit-enter prompt doesn't end + the prompt. + + 6.1.169: bufexists() finds a buffer by using the name of a symbolic + link to it, but bufnr + + 6.1.170: Using ":mksession" uses the default session file name, + but "vim -S" doesn't. + + 6.1.171: When opening a line just above a closed fold with "O" + and the comment leader is automatically inserted, the cursor is + displayed in the first column. + + 6.1.172: Command line completion of ":tag /pat" does not show the + same results as the tags the command actually finds. + + 6.1.173: When using remote control to edit a position in a file + and this file is the current buffer and it's modified, the window + is split and the ":drop" command fails. + + 6.1.174: It is difficult to know in a script whether an option not + only exists but really works. + + 6.1.175: When reading commands from a pipe and a CTRL-C is pressed, + Vim will hang. + + 6.1.176: When the stack limit is very big a false out-of-stack + error may be detected. + + 6.1.177: ":wincmd" does not allow a following command. + + 6.1.178: When 'expandtab' is set "r<C-V><Tab>" still expands the Tab. + + 6.1.179: When using X11R5 XIMPreserveState is undefined. + + 6.1.180: Use of the GUI code for forking is inconsistent. + + 6.1.181: If the terminal doesn't wrap from the last char in a line + to the next line, the last column is blanked out. + + 6.1.182: It is not possible to auto-format comments only. + + 6.1.183: When 'fencs' is empty and 'enc' is utf-8, reading a file + with illegal bytes gives "CONVERSION ERROR" even though no conversion + is done. 'readonly' is set, even though writing the file results + in an unmodified file. + + 6.1.184: The extra mouse buttons found on some mice don't work. + + 6.1.185: Can't compile without +comments feature. + + 6.1.186: ":wincmd" does not allow a following comment. + + 6.1.187: Using ":doarg" with 'hidden' set and the current file is + the only argument and was modified gives an error message. + + 6.1.188: Unused variable in the small version. + + 6.1.189: inputdialog() doesn't work when 'c' is in 'guioptions'. + + 6.1.190: VMS: doesn't build with GTK GUI. Various other problems. + + 6.1.191: When using "vim -s script" and redirecting the output, + the delay for the "Output is not to a terminal" warning slows Vim + down too much. + + 6.1.192: ":diffsplit" doesn't add "hor" to 'scrollopt'. + + 6.1.193: Crash in in_id_list() for an item with a "containedin" list. + + 6.1.194: When "t_ti" is set but it doesn't cause swapping terminal + pages, "ZZ" may cause the shell prompt to appear on top of the + file-write message. + + 6.1.195: The quickfix and preview windows always keep their height, + while other windows can't fix their height. + + 6.1.196: On Mac OS X 10.2 generating osdef.h fails. + + 6.1.197: ":help <C-V><C-\><C-V><C-N>" (resulting in <1c><0e>) + gives an error message. + + 6.1.198: Mac OS X: Dialogues don't work. + + 6.1.199: 'guifontwide' doesn't work on Win32. + + 6.1.200: ":syn sync fromstart" is not skipped after ":if 0". This + can make syntax highlighting very slow. + + 6.1.201: Warning for illegal pointer combination. + + 6.1.202: Win32: filewritable() doesn't work properly on directories. + + 6.1.203: ":%s/~//" causes a crash after ":%s/x//". + + 6.1.204: Warning for an illegal pointer on Solaris. + + 6.1.205: The gzip plugin changes the alternate file when editing + a compressed file. + + 6.1.206: The script generated with ":mksession" doesn't work properly + when some commands are mapped. + + -- Wichert Akkerman <wakkerma@debian.org> Tue, 1 Oct 2002 23:20:57 +0200 + +vim (6.1.165-1) unstable; urgency=low + + * Change priority to extra + * Build-Depend on libperl-dev >= 5.8.0-7 in order to force perl transition + * Apply upstream patches: + + 6.1.152: When $LANG is iso8859-1 translated menus are not used. + + 6.1.153: Searching in included files may search recursively when + the path starts with "../". + + 6.1.154: DJGPP: "vim -h" leaves the cursor in a wrong position. + + 6.1.155: Win32: Cursor may sometimes disappear in Insert mode. + + 6.1.156: Conversion between DBCS and UCS-2 isn't implemented cleanly. + + 6.1.157: 'hlsearch' highlights only the second comma in ",,,,," + with "/,\@<=[^,]*". + + 6.1.158: "zs" and "ze" don't work correctly with ":set nowrap + siso=1". + + 6.1.159: When expanding an abbreviation that includes a multi-byte + character too many characters are deleted. + + 6.1.160: ":$read file.gz" doesn't work. + + 6.1.161: Warning for signed/unsigned compare. Can set 'siso' to a + negative value. + + 6.1.162: Python interface: Didn't initialize threads properly. + + 6.1.163: Win32: Can't compile with Python after 6.1.162. + + 6.1.164: If 'modifiable' is off, converting to xxd fails and + 'filetype' is changed to "xxd" anyway. + + 6.1.165: Making changes in several lines and then a change in one + of these lines that splits it in two or more lines, undo information + was corrupted. May cause a crash. + + -- Wichert Akkerman <wakkerma@debian.org> Tue, 27 Aug 2002 17:10:44 +0000 + +vim (6.1.152-1) unstable; urgency=low + + * Apply upstream patches: + + 6.1.049: On a 32 bit display a valid color may cause an error + message, because its pixel value is negative. + + 6.1.050: After patch 6.1.049 the non-GUI version doesn't compile. + + 6.1.051: Doesn't compile with GUI and small features. + + 6.1.052: Unix: The executable() function doesn't work when the + "which" command isn't available. + + 6.1.053: When 'sessionoptions' contains "globals", or "localoptions" + and an option value contains a line break, the resulting script + is wrong. + + 6.1.054: GUI: A mouse click is not recognized at the more prompt, + even when 'mouse' includes 'r'. + + 6.1.055: When editing a compressed file, Vim will inspect the + contents to guess the filetype. + + 6.1.056: Loading the Syntax menu can take quite a bit of time. + + 6.1.057: An ESC inside a mapping doesn't work as documented when + 'insertmode' is set, it does go from Visual or Normal mode to + Insert mode. + + 6.1.058: When there is a closed fold just above the first line in + the window, using CTRL-X CTRL-Y in Insert mode will show only one + line of the fold. + + 6.1.059: ":redir > ~/file" doesn't work. + + 6.1.060: When 'virtualedit' is set and 'selection' is "exclusive", + deleting a character just before a tab changes the tab into + spaces. Undo doesn't restore the tab. + + 6.1.061: When 'virtualedit' is set and 'selection' is "exclusive", + a Visual selection that ends just after a tab doesn't include that + tab in the highlighting. + + 6.1.062: The "man" filetype plugin doesn't work properly on + Solaris 5. + + 6.1.063: Java indenting doesn't work properly. + + 6.1.064: The URLs that the netrw plugin recognized for ftp and rcp + did not conform to the standard method://[user@]host[:port]/path. + + 6.1.065: VMS: The colorscheme, keymap and compiler menus are not + filled in. + + 6.1.066: When calling system() in a plugin reading stdin hangs. + + 6.1.067: ":set viminfo+=f0" is not working. + + 6.1.068: When a file is reloaded after it was changed outside of Vim, + diff mode isn't updated. + + 6.1.069: When 'showmatch' is set and "$" is in 'cpoptions', using + "C}<Esc>" may forget to remove the "$". + + 6.1.070: Compiler warning for signed/unsigned mismatch. + + 6.1.071: When 'selection' is exclusive, g CTRL-G in Visual mode + counts one character too much. + + 6.1.072: When a file name in a tags file starts with http:// + or something else for which there is a BufReadCmd autocommand, + the file isn't opened anyway. + + 6.1.073: BC5: Can't easily specify a tiny, small, normal, big or + huge version. + + 6.1.074: When 'cdpath' includes "../..", changing to a directory + in which we currently already are doesn't work. ff_check_visited() + adds the directory both when using it as the root for searching + and for the actual matches. + + 6.1.075: Can't compile fileio.c on MS-Windows. + + 6.1.076: Macintosh: explorer plugin doesn't work on Mac Classic. IME + doesn't work. Dialog boxes don't work on Mac OS X + + 6.1.077: On a Debian system wht ACL linking fails. + + 6.1.078: When using 'foldmethod' "marker" and the end marker appears + before the start marker in the file, no fold is found. + + 6.1.079: When using "s" in Visual block mode with 'virtualedit' + set, when the selected block is after the end of some lines the + wrong text is inserted and some lines are skipped. + + 6.1.080: When using gcc with /usr/local already in the search path, + adding it again causes problems. + + 6.1.081: ":help CTRL-\_CTRL-N" doesn't work. + + 6.1.082: On MS-Windows the vimrc_example.vim script is sourced + and then mswin.vim. This enables using select mode, but since "p" + is mapped it doesn't replace the selection. + + 6.1.083: When $LANG is "sk" or "sk_sk", the Slovak menu file + isn't found. + + 6.1.084: "include" and "lib" are mixed up when checking the + directories gcc already searches. + + 6.1.085: When using CTRL-O CTRL-\ CTRL-N from Insert mode, the + displayed mode " + + 6.1.086: The guifg color for CursorIM doesn't take effect. + + 6.1.087: A thesaurus with Japanese characters has problems with + characters in different word classes. + + 6.1.088: Win32: no debugging info is generated. Tags file excludes + .cpp files. + + 6.1.089: On BSDI systems there is no ss_sp field in stack_t. + + 6.1.090: CTRL-F gets stuck when 'scrolloff' is non-zero and there + is a mix of long wrapping lines and a non-wrapping line. + + 6.1.091: GTK: Can't change preeditstate without setting + 'imactivatekey'. + + 6.1.092: ":mapclear <buffer>" doesn't work. + + 6.1.093: Mac and MS-Windows GUI: when scrolling while ":s" is + working the results can be messed up, because the cursor is moved. + + 6.1.094: Cygwin: Passing a file name that has backslashes isn't + handled very well. + + 6.1.095: When using signs can free an item on the stack. Overruling + sign colors doesn't work. + + 6.1.096: When erasing the right halve of a double-byte character, + it may cause further characters to be erased. + + 6.1.097: When 'scrolloff' is set to a huge value, CTRL-F at the + end of the file scrolls one line. + + 6.1.098: MS-Windows: When the xxd program is under "c:\program files" + the "Convert to Hex" menu doesn't work. + + 6.1.099: Memory corrupted when closing a fold with more than + 99999 lines. + + 6.1.100: Win32: VC5 and earlier don't support the /mapinfo option. + + 6.1.101: After using ":options" the tabstop of a new window is + 15. Entry in ":options" window for 'autowriteall' is wrong. (Antoine + J Mechelynck) Can't insert a space in an option value. + + 6.1.102: Unprintable and multi-byte characters in a statusline item + are not truncated correctly. + + 6.1.103: A function returning from a while loop, with 'verbose' + set to 12 or higher, doesn't mention the return value. A function + with the 'abort' attribute may return -1 while the verbose message + says something else. + + 6.1.104: GCC 3.1 appears to have an optimizer problem that makes + test 3 crash. + + 6.1.105: Win32: The default for 'shellpipe' doesn't redirect + stderr. (Dion Nicolaas) + + 6.1.106: The maze program crashes. + + 6.1.107: When 'list' is set the current line in the error window + may be displayed wrong. + + 6.1.108: When interrupting a filter command such as "!!sleep 20" + the file becomes read-only. + + 6.1.109: When 'eadirection' is "hor", using CTRL-W = doesn't equalize + the window heights. + + 6.1.110: When using ":badd file" when "file" is already present + but not listed, it stays unlisted. + + 6.1.111: It's not possible to detect using the Unix sources on + Win32 or Mac. + + 6.1.112: When using ":argdo", ":bufdo" or ":windo", CTRL-O doesn't + go to the cursor position from before this command but every position + where the argument was executed. + + 6.1.113: ":bufdo bwipe" only wipes out half the buffers. + + 6.1.114: ":python import vim", ":python vim.current.buffer[0:0] = + []" gives a lalloc + + 6.1.115: "das" on the white space at the end of a paragraph does + not delete the "." the sentence ends with. + + 6.1.116: When 'endofline' is changed while 'binary' is set a file + should be considered modified. + + 6.1.117: Small problem with editing a file over ftp: and with Cygwin. + + 6.1.118: When a file in diff mode is reloaded because it changed + outside of Vim, other windows in diff mode are not always updated. + + 6.1.119: With the Sniff interface, using Sniff 4.0.X on HP-UX, + there may be a crash when connecting to Sniff. + + 6.1.120: When 'scrolloff' is non-zero and there are folds, CTRL-F + at the end of the file scrolls part of a closed fold. + + 6.1.121: When starting Select mode from Insert mode, then using + the Paste menu entry, the cursor is left before the laste pasted + character. + + 6.1.122: ":file name" creates a new buffer to hold the old buffer + name, which becomes the alternate file. This buffer is unexpectedly + listed. + + 6.1.123: A ":match" command with more than one argument doesn't + report an error. + + 6.1.124: When trying to exit and there is a hidden buffer that had + 'eol' off and 'bin' set exiting isn't possible. + + 6.1.125: Explorer plugin asks for saving a modified buffer even + when it's open in another window as well. + + 6.1.126: Adding the choices in the syntax menu is consuming much + of the startup time of the GUI while it's not often used. + + 6.1.127: When using "--remote file" and the server has 'insertmode' + set, commands are inserted instead of being executed. + + 6.1.128: The expression "input('very long prompt')" puts the cursor + in the wrong line (column is OK). + + 6.1.129: On Solaris editing "file/" and then "file" results in + using the same buffer. + + 6.1.130: The documentation for some of the 'errorformat' items + is unclear. + + 6.1.131: X11 GUI: when expanding a CSI byte in the input stream to + K_CSI, the CSI byte itself isn't copied. + + 6.1.132: Executing a register in Ex mode may cause commands to + be skipped. + + 6.1.133: When drawing double-wide characters in the statusline, + may clear half of a character. + + 6.1.134: An error for a trailing argument of ":match" should not + be given after ":if 0". + + 6.1.135: Passing a command to the shell that includes a newline + always has a backslash before the newline. + + 6.1.136: When $TERM is "linux" the default for 'background' is + "dark", even though the GUI uses a light background. + + 6.1.137: Converting to HTML has a clumsy way of dealing with tabs + which may change the highlighting. + + 6.1.138: Adding extra items to the Syntax menu can't be done when + the "Show individual choices" menu is used. + + 6.1.139: Cygwin: PATH_MAX is not defined. + + 6.1.140: Cygwin: ":args `ls *.c`" does not work if the shell command + produces CR NL line separators. + + 6.1.141: ":wincmd gx" may cause problems when mixed with other + commands. ":wincmd c" doesn't close the window immediately. + + 6.1.142: Defining paragraphs without a separating blank line isn't + possible. Paragraphs can't be formatted automatically. + + 6.1.143: Auto formatting near the end of the file moves the cursor + to a wrong position. In Insert mode some lines are made one char + too narrow. When deleting a line undo might not always work properly. + + 6.1.144: Obtaining the size of a line in screen characters can be + wrong. A pointer may wrap around zero. + + 6.1.145: GTK: Drag&drop with more than 3 files may cause a + crash. (Mickael Marchand) + + 6.1.146: MS-Windows: When $HOME is constructed from $HOMEDRIVE and + $HOMEPATH, it is not used for storing the _viminfo file. (Normal + Diamond) + + 6.1.147: MS-Windows: When a dialog has no default button, pressing + Enter ends it anyway and all buttons are selected. + + 6.1.148: MS-Windows: ACL is not properly supported. + + 6.1.149: MS-Windows: Can't use diff mode from the file explorer. + + 6.1.150: OS/2, MS-Windows and MS-DOS: When 'shellslash' is set + getcwd() still uses backslash. + + 6.1.151: Win32: The NTFS substream isn't copied. + + 6.1.152: When $LANG is iso8859-1 translated menus are not used. + + -- Wichert Akkerman <wakkerma@debian.org> Tue, 13 Aug 2002 10:54:13 +0200 + +vim (6.1.048-1) unstable; urgency=low + + * Bump Standards-Version. Closes: Bug#145062 + * Sync cscope support and dependencies. Closes: Bug#143205 + * Apply upstream patches: + + 6.1.019: Win32: File name is messed up when editing just a drive + name. + + 6.1.020: col("'>") returns a huge number after using Visual line + mode. + + 6.1.021: Vim crashes when using a huge number for the minwid value + in a statusline. + + 6.1.022: Grabbing the status line above the command-line window + works like the bottom status line was grabbed. + + 6.1.023: VMS: running tests doesn't work properly. + + 6.1.024: When header files use a new syntax for declaring functions, + Vim can't figure out missing prototypes properly. + + 6.1.025: Five messages for "vim --help" don't start with a + capital. + + 6.1.026: *.patch files are not recognized as diff files. In a script + a "VAR=val" argument after "env" isn't ignored. PHP scripts are + not recognized. + + 6.1.027: When 'foldcolumn' is non-zero, a special character + that wraps to the next line disturbs the foldcolumn + highlighting. + + 6.1.028: Client-server: When a --remote-expr fails, Vim still exits + with status zero. + + 6.1.029: When 'encoding' is an 8-bit encoding other than "latin1", + editing a utf-8 or other Unicode file uses the wrong conversion. (Jan + Fedak) + + 6.1.030: When CTRL-N is mapped in Insert mode, it is also mapped + after CTRL-X CTRL-N, while it is not mapped after CTRL-X CTRL-F. + + 6.1.031: Cygwin: Xxd could read a file in text mode intead of + binary mode. + + 6.1.032: Can't specify a quickfix file without jumping to the + first error. + + 6.1.033: GUI: When the selection is lost and the Visual highlighting + is changed to underlining, the cursor is left in a different + position. + + 6.1.034: A CVS diff file isn't recognized as diff filetype. + + 6.1.035: Win32: Outputting Hebrew or Arabic text might have a + problem with reversing on MS-Windows 95/98/ME. + + 6.1.036: This command may cause a crash: ":v/./,//-j". + + 6.1.037: When 'lazyredraw' is set, pressing "q" at the hit-enter + prompt causes an incomplete redraw and the cursor isn't positioned. + + 6.1.038: Multi-byte: When a ":s" command contains a multi-byte + character where the trail byte is '~' the text is messed up. + + 6.1.039: When folds are defined and the file is changed outside + of Vim, reloading the file doesn't update the folds. (Anders + Schack-Nielsen) + + 6.1.040: When changing directory for expanding a file name fails + there is no error message. + + 6.1.041: ":mkvimrc" doesn't handle a mapping that has a leading + space in the rhs. + + 6.1.042: "vim -r" doesn't show all matches when 'wildignore' + removes swap files. + + 6.1.043: After patch 6.1.040 a few warnings are produced. + + 6.1.044: GUI: When using the find/replace dialog with text that + contains a slash, an invalid substitute command is generated. On + Win32 a find doesn't work when 'insertmode' is set. + + 6.1.045: In Visual mode, with lots of folds and 'scrolloff' set + to 999, moving the cursor down near the end of the file causes the + text to jump up and down. + + 6.1.046: X11 GUI: ":set lsp=2 gcr=n-v-i:hor1-blinkon0" draws a + black rectangle. ":set lsp=2 gcr=n-v-i:hor10-blinkon0" makes the + cursor disappear. + + 6.1.047: When skipping commands after an error was encountered, + expressions for ":if", ";elseif" and ":while" are still evaluated. + + 6.1.048: Unicode 3.2 changes were missing a few Hangul Jamo + characters. + + -- Wichert Akkerman <wakkerma@debian.org> Sat, 4 May 2002 17:57:01 +0200 + +vim (6.1.018-1) unstable; urgency=low + + * Apply upstream patches: + + 6.1.012: A system() call might fail if fread() does CR-LF to LF + translation. + + 6.1.013: Win32: The default for 'printexpr' doesn't work when there + are special characters in 'printdevice'. + + 6.1.014: An operator like "r" used in Visual block mode doesn't use + 'virtualedit' when it's set to "block". + + 6.1.015: After patch 6.1.014 can't compile with tiny + features. + + 6.1.016: Win32: Outputting Hebrew or Arabic text might have a + problem with reversing. + + 6.1.017: Cygwin: After patch 6.1.012 Still doesn't do binary + file I/O. + + 6.1.018: Error message when using cterm highlighting. Closes: Bug#142663 + + -- Wichert Akkerman <wakkerma@debian.org> Sun, 14 Apr 2002 20:38:53 +0200 + +vim (6.1.011-1) unstable; urgency=low + + * Enable langmap and keymap in all builds. Closes: Bug#141127 + * Apply upstream patches: + + 6.1.001: When formatting UTF-8 text it might be wrapped at a space + that is followed by a composing character. Also correct a display + error for removing a composing char on top of a space. + + 6.1.002: Win32: after a ":popup" command the mouse pointer stays + hidden. + + 6.1.003: When 'laststatus' is zero and there is a vertical split, the + vertical separator is drawn in the command line. + + 6.1.004: Unicode 3.2 changes width and composing of a few characters. + + 6.1.005: When using more than 50 items in 'statusline' Vim might + crash. + + 6.1.006: When using "P" in Visual mode to put linewise selected text, + the wrong text is deleted. + + 6.1.007: Using ":filetype plugin off" when filetype plugins were + never enabled causes an error message. + + 6.1.008: The "%" command doesn't ignore \" inside a string, it's + seen as the end of the string. + + 6.1.009: Vim crashes when using a huge number for the maxwid value + in a statusline. + + 6.1.010: Searching backwards for a question mark with "?\?" doesn't + work. Same problem in ":s?\??" and ":g?\??". + + 6.1.011: XIM: doesn't work correctly when 'number' is set. Also, + a focus problem when selecting candidates. + + -- Wichert Akkerman <wakkerma@debian.org> Thu, 4 Apr 2002 14:49:27 +0200 + +vim (6.1.000-2) unstable; urgency=low + + * Fix version number + * Update copyright the uganda.txt version. Closes: Bug#139780 + + -- Wichert Akkerman <wakkerma@debian.org> Mon, 25 Mar 2002 13:42:03 +0100 + +vim (6.1.-1) unstable; urgency=low + + * Small fixes to default vimrc + * New upstream version. + + includes 6.1b.033: When using a count after a ":s" command may get + ml_get errors. Closes: Bug#139403 + + -- Wichert Akkerman <wakkerma@debian.org> Sun, 24 Mar 2002 18:24:35 +0100 + +vim (6.0.270-1) unstable; urgency=low + + * Switch to copyright from vim 6.1BETA which is fully GPL compatible + * More upstream patches: + + 6.0.227: The RISC OS port has several problems. + + 6.0.228: After putting text in Visual mode the '] mark is not at + the end of the put text. Undo doesn't work properly when putting + a word into a Visual selection that spans more than one line. + + 6.0.229: Multi-byte: With 'm' in 'formatoptions', formatting + doesn't break at a multi-byte char followed by an ASCII char, + and the other way around. When joining lines a space is inserted + between multi-byte characters, which is not always wanted. + + 6.0.230: The ":" used as a motion after an operator is exclusive, + but sometimes it should be inclusive. + + 6.0.231: "gd" and "gD" don't work when the variable matches in a + comment just above the match to be found. + + 6.0.232: "vim --version" prints on stderr while "vim --help" prints + on stdout. + + 6.0.233: "\1\{,8}" in a regexp is not allowed, but it should work, + because there is an upper limit. + + 6.0.234: It's not easy to set the cursor position without modifying + marks. + + 6.0.235: When writing a file and renaming the original file to make + the backup, permissions could change when setting the owner. + + 6.0.236: ":edit" without argument should move cursor to line 1 in + Vi compatible mode. + + 6.0.237: In a C file, using the filetype plugin, re-indenting a + comment with two spaces after the middle "*" doesn't align properly. + + 6.0.238: Using a ":subsitute" command with a substitute() call in + the substitution expression causes errors. + + 6.0.239: Using "A" to append after a Visually selected block which + is after the end of the line, spaces are inserted in the wrong line + and other unexpected effects. + + 6.0.240: Win32: building with Python 2.2 doesn't work. + + 6.0.241: Win32: Expanding the old value of an option that is a path + that starts with a backslash, an extra backslash is inserted. + + 6.0.242: GUI: On a system with an Exceed X server sometimes get a + "Bad Window" error. + + 6.0.243: Unix: "vim --version" outputs a NL before the last line + instead of after it. + + 6.0.244: Multi-byte: Problems with (illegal) UTF-8 characters in + menu and file name (e.g., icon text, status line). + + 6.0.245: After using a color scheme, setting the 'background' + option might not work. + + 6.0.246: ":echomsg" didn't use the highlighting set by + ":echohl". (Gary Holloway) + + 6.0.247: GTK GUI: Can't use gvim in a kpart widget. + + 6.0.248: When using compressed help files and 'encoding' isn't + "latin1", Vim converts the help file before decompressing. + + 6.0.249: "vim -t edit -c 'sta ex_help'" doesn't move cursor to + edit(). + + 6.0.250: Macintosh: Various problems when compiling. + + 6.0.251: Macintosh: menu shortcuts are not very clear. + + 6.0.252: When a user function was defined with "abort", an error that + is not inside if/endif or while/endwhile doesn't abort the function. + + 6.0.253: When 'insertmode' is set, after "<C-O>:edit file" the next + <C-O> doesn't work. (Benji Fisher) <C-L> has the same problem. + + 6.0.254: Borland C++ 5.5: Checking for stack overflow doesn't work + correctly. Matters when using a complicated regexp. + + 6.0.255: Win32: ACL support doesn't work well on Samba drives. + + 6.0.256: Win32: ":highlight Comment guifg=asdf" does not give an + error message. (Randall W. Morris) Also for other systems. + + 6.0.257: Win32: When 'mousefocus' is set and there is a BufRead + autocommand, after the dialog for permissions changed outside of Vim: + 'mousefocus' stops working. + + 6.0.258: When 'scrolloff' is 999 and there are folds, the text + can jump up and down when moving the cursor down near the end of + the file. + + 6.0.259: MS-DOS: after editing the command line the cursor shape + may remain like in Insert mode. + + 6.0.260: GUI: May crash while starting up when giving an error + message for missing color. + + 6.0.261: nr2char() and char2nr() don't work with multi-byte + characters. + + 6.0.262: Win32: IME doesn't work properly. OnImeComposition() + isn't used at all. + + 6.0.263: GTK: When a dialog is closed by the window manager, + Vim hangs. + + 6.0.264: The amount of virtual memory is used to initialize + 'maxmemtot', which may be much more than the amount of physical + memory, resulting in a lot of swapping. + + 6.0.265: Win32: Using backspace while 'fkmap' is set causes a crash. + + 6.0.266: The rename() function deletes the file if the old and the + new name are the same. + + 6.0.267: UTF-8: Although 'isprint' says a character is printable, + utf_char2cells() still considers it unprintable. + + 6.0.268: Win32: ACL check crashes when using forward slash in + file name. + + 6.0.269: Unprintable characters in a file name may cause problems + when using the 'statusline' option or when 'buftype' is "nofile". + + 6.0.270: A tab causes UTF-8 text to be displayed in the wrong + position. + + -- Wichert Akkerman <wakkerma@debian.org> Sun, 24 Feb 2002 23:16:17 +0100 + +vim (6.0.226-1) unstable; urgency=medium + + * Don't abort if update-alternatives reports an error + * More upstream patches: + + 6.0.223: When splitting a window that contains the explorer, hitting CR + on a file name gives error messages. + + 6.0.224: When 'sidescroll' and 'sidescrolloff' are set in a narrow + window the text may jump left-right and the cursor is displayed in the + wrong position. + + 6.0.225: In Visual mode "gk" gets stuck in a closed fold. / + + 6.0.226: When doing ":recover file" get the ATTENTION prompt. After + recovering the same file five times get a read error or a crash. + + -- Wichert Akkerman <wakkerma@debian.org> Sun, 17 Feb 2002 15:08:03 +0100 + +vim (6.0.222-1) unstable; urgency=low + + * Do not Build-Depend on libgpmg1-dev for hurd-i386. Closes: Bug#117313 + * chown a file before we chmod it so we don't lose s[ug]id bits + * Set compiled-by flag in configure + * More upstream patches: + + 6.0.202: The "icon=" argument for the menu command to define a toolbar + icon with a file didn't work for GTK. For Motif and Athena a full path + was required. + + 6.0.203: Can change 'fileformat' even though 'modifiable is off. + + 6.0.204: ":unlet" doesn't work for variables with curly braces. + + 6.0.205: "gvim -f" still forks when using the batch script to start Vim. + + 6.0.206: Unix: if expanding a wildcard in a file name results in a + wildcard character and there are more parts in the path with a wildcard, + it is expanded again. Windows: ":edit \[abc]" could never edit the file + "[abc]". + + 6.0.207: Win32: The shortcuts and start menu entries let Vim startup in + the desktop directory, which is not very useful. + + 6.0.208: GUI: When using a keymap and the cursor is not blinking, CTRL-^ + in Insert mode doesn't directly change the cursor color. + + 6.0.209: GUI GTK: After selecting a 'guifont' with the font dialog there + are redraw problems for multi-byte characters. + + 6.0.210: After patch 6.0.167 it's no longer possible to edit a help file + in another encoding than latin1. + + 6.0.211: When reading a file fails, the buffer is empty, but it might + still be possible to write it with ":w" later. The original file is lost + then. + + 6.0.212: GUI GTK: confirm("foo", "") causes a crash. + + 6.0.213: When a file name contains unprintable characters, CTRL-G and + other commands don't work well. + + 6.0.214: When there is a buffer without a name, empty entries appear in + the jumplist saved in the viminfo file. + + 6.0.215: After using "/" from Visual mode the Paste menu and Toolbar + entries don't work. Pasting with the middle mouse doesn't work and + modeless selection doesn't work. + + 6.0.216: After reloading a file, displayed in another window than the + current one, which was changed outside of Vim the part of the file around + the cursor set by autocommands may be displayed, but jumping back to the + original cursor position when entering the window again. + + 6.0.217: When getting help from a help file that was used before, an + empty unlisted buffer remains in the buffer list. + + 6.0.218: With explorer plugin: "vim -o filename dirname" doesn't load the + explorer window until entering the window. + + 6.0.219: ":setlocal" and ":setglobal", without arguments, display + terminal options. + + 6.0.220: After patch 6.0.218 get a beep on startup. + + 6.0.221: When using ":bdel" and all other buffers are unloaded the lowest + numbered buffer is jumped to instead of the most recent one. + + 6.0.222: When 'virtualedit' is set and using autoindent, pressing Esc + after starting a new line leaves behind part of the autoindent. + + -- Wichert Akkerman <wakkerma@debian.org> Sat, 16 Feb 2002 00:15:24 +0100 + +vim (6.0.201-1) unstable; urgency=low + + * More upstream patches: + + 6.0.157: When defining a user command with "-complete=dir" files will + also be expanded. Also, "-complete=mapping" doesn't appear to work. + + 6.0.158: When getting the warning for a file being changed outside of Vim + and reloading the file, the 'readonly' option is reset, even when the + permissions didn't change. + + 6.0.159: Wildcard expansion for ":emenu" also shows separators. + + 6.0.160: When compiling with GCC 3.0.2 and using the "-O2" argument, the + optimizer causes a problem that makes Vim crash. + + 6.0.161: Win32: Bitmaps don't work with signs. + + 6.0.162: Client-server: An error message for a wrong expression appears + in the server instead of the cient. + + 6.0.163: When using a GUI dialog, a file name is sometimes used like it + was a directory. + + 6.0.164: After patch 6.0.135 the menu entries for pasting don't work in + Insert and Visual mode. + + 6.0.165: Using --remote and executing locally gives unavoidable error + messages. + + 6.0.166: GUI: There is no way to avoid dialogs to pop up. + + 6.0.167: When 'fileencodings' is "latin2" some characters in the help + files are displayed wrong. + + 6.0.168: ":%s/\n/#/" doesn't replace at an empty line. + + 6.0.169: When run as evim and the GUI can't be started we get stuck in a + terminal without menus in Insert mode. + + 6.0.170: When printing double-width characters the size of tabs after + them is wrong. + + 6.0.171: With 'keymodel' including "startsel", in Insert mode after the + end of a line, shift-Left does not move the cursor. + + 6.0.172: CTRL-Q doesn't replace CTRL-V after CTRL-X in Insert mode while + it does in most other situations. + + 6.0.173: When using "P" to insert a line break the cursor remains past + the end of the line. + + 6.0.174: After using "gd" or "gD" the search direction for "n" may still + be backwards. + + 6.0.175: ":help /\z(\)" doesn't work + + 6.0.176: When killed by a signal autocommands are still triggered as if + nothing happened. + + 6.0.177: When 'commentstring' is empty and 'foldmethod' is "marker", "zf" + doesn't work. + + 6.0.178: Uninitialized memory read from xp_backslash field. + + 6.0.179: Win32: When displaying UTF-8 characters may read uninitialized + memory. + + 6.0.180: Expanding environment variables in a string that ends in a + backslash could go past the end of the string. + + 6.0.181: When using ":cd dir" memory was leaked. + + 6.0.182: When using a regexp on multi-byte characters, could try to read + a character before the start of the line. + + 6.0.183: Leaking memory when ":func!" redefines a function. + + 6.0.184: Leaking memory when expanding option values. + + 6.0.185: Crash in Vim when pasting a selection in another application, on + a 64 bit machine. + + 6.0.186: X11: Three warnings when compiling the client-server code. + + 6.0.187: "I" in Visual mode and then "u" reports too many changes. "I" in + Visual linewise mode adjusts the indent for no apparent reason. + + 6.0.188: After patch 6.0.161 signs defined in the vimrc file don't work. + + 6.0.189: The size of the Visual area isn't always displayed when + scrolling ('ruler' off, 'showcmd' on). Also not when using a search + command. + + 6.0.190: GUI: when 'mouse' is empty a click with the middle button still + moves the cursor. + + 6.0.191: When no servers are available serverlist() gives an error + instead of returning an empty string. + + 6.0.192: When 'virtualedit' is set, "ylj" goes to the wrong column. + + 6.0.193: When 'virtualedit' is set, col(".") after the end of the line + should return one extra. + + 6.0.194: "--remote-silent" tries to send a reply to the client, like it + was "--remote-wait". + + 6.0.195: When 'virtualedit' is set and a search starts in virtual space + ":call search + + 6.0.196: When 'virtualedit' is set, 'selection' is "exclusive" and + visually selecting part of a tab at the start of a line, "x" joins it + with the previous line. Also, when the selection spans more than one line + the whole tab is deleted. + + 6.0.197: When 'virtualedit' is set and 'selection' is "exclusive", "v$x" + doesn't delete the last character in the line. + + 6.0.198: When 'virtualedit' is set and 'showbreak' is not empty, moving + the cursor over the line break doesn't work properly. + + 6.0.199: Multi-byte: could use iconv() after calling iconv_end(). + + 6.0.200: A script that starts with "#!perl" isn't recognized as a Perl + filetype. + + 6.0.201: When scrollbinding and doing a long jump, switching windows + jumps to another position in the file. Scrolling a few lines at a time + is OK. + + -- Wichert Akkerman <wakkerma@debian.org> Thu, 7 Feb 2002 22:14:09 +0100 + +vim (6.0.156-1) unstable; urgency=low + + * Fix typo in comment in vimrc. Closes: Bug#129815 + * More upstream patches: + + 6.0.119: VMS: filewritable() doesn't work properly. + + 6.0.120: The conversion to html isn't compatible with XHTML. + + 6.0.121: Win32: After patch 6.0.116 Vim doesn't compile with mingw32. + + 6.0.122: Win16: Same resize problems as patch 6.0.117 fixed for + Win32. And dialog textfield problem from patch 6.0.115. + + 6.0.123: Win16: Compilation problems. + + 6.0.124: When using a ":substitute" command that starts with "\=" + (evaluated as an expression), "~" was still replaced with the + previous substitute string. + + 6.0.125: Win32: When using the multi_byte_ime feature pressing the + shift key would be handled as if a character was entered, thus + mappings with a shifted key didn't work. + + 6.0.126: The python library was always statically linked. + + 6.0.127: When using a terminal that swaps screens and the Normal + background color has a different background, using an external + command may cause the color of the wrong screen to be changed. + + 6.0.128: When moving a vertically split window to the far left or + right, the scrollbars are not adjusted. (Scott E Lee) When + 'mousefocus' is set the mouse pointer wasn't adjusted. + + 6.0.129: When using a very long file name, ":ls" (repeated a few + times) causes a crash. Test with "vim `perl -e 'print "A"x1000'`". + + 6.0.130: When using ":cprev" while the error window is open, and the + new line at the top wraps, the window isn't correctly drawn. + + 6.0.131: When using bufname() and there are two matches for listed + buffers and one match for an unlisted buffer, the unlisted buffer is + used. + + 6.0.132: When setting 'iminsert' in the vimrc and using an xterm with + two screens the ruler is drawn in the wrong screen. + + 6.0.133: When opening another buffer while 'keymap' is set and + 'iminsert' is zero, 'iminsert' is set to one unexpectedly. + + 6.0.134: When completing ":set tags=" a path with an embedded space + causes the completion to stop. + + 6.0.135: Menus that are not supposed to do anything used "<Nul>", + which still produced an error beep. When CTRL-O is mapped for Insert + mode, ":amenu" commands didn't work in Insert mode. Menu language + falls back to English when $LANG ends in "@euro". + + 6.0.136: When completing in Insert mode, a mapping could be + unexpectedly applied. + + 6.0.137: GUI: When using the find or find/replace dialog from Insert + mode, the input mode is stopped. + + 6.0.138: GUI: When using the find or find/replace dialog from Insert + mode, the text is inserted when CTRL-O is mapped. When opening the + dialog again, a whole word search isn't recognized. When doing + "replace all" a whole word search was never done. + + 6.0.139: When stopping 'wildmenu' completion, the statusline of the + bottom-left vertically split window isn't redrawn. + + 6.0.140: Memory allocated for local mappings and abbreviations is + leaked when the buffer is wiped out. + + 6.0.141: When using ":enew" in an empty buffer, some buffer-local + things are not cleared. b:keymap_name is not set. + + 6.0.142: When Python is linked statically, loading dynamic extensions + might fail. + + 6.0.143: When a syntax item includes a line break in a pattern, the + syntax may not be updated properly when making a change. + + 6.0.144: After patch 6.0.088 redoing "veU" doesn't work. + + 6.0.145: When Vim can't read any input it might get stuck. When + redirecting stdin and stderr Vim would not read commands from a file. + + 6.0.146: When 'statusline' contains "%{'-'}" this results in a zero. + + 6.0.147: It's not easy to mark a Vim version as being modified. The + new license requires this. + + 6.0.148: After "p" in an empty line, `[ goes to the second character. + + 6.0.149: The pattern "\(.\{-}\)*" causes a hang. When using a search + pattern that causes a stack overflow to be detected Vim could still + hang. + + 6.0.150: When using a multi-byte encoding, patch 6.0.148 causes "p" + to work like "P". + + 6.0.151: Redrawing the status line and ruler can be wrong when it + contains multi-byte characters. + + 6.0.152: strtrans() could hang on an illegal UTF-8 byte sequence. + + 6.0.153: When using (illegal) double-byte characters and Vim syntax + highlighting Vim can crash. + + 6.0.154: MS-DOS and MS-Windows: The menu entries for xxd don't work + when there is no xxd in the path. When converting back from Hex the + filetype may remain "xxd" if it is not detected. + + 6.0.155: Mac: compilation problems in ui.c after patch 6.0.145. + + 6.0.156: Starting Vim with the -b argument and two files, ":next" + doesn't set 'binary' in the second file, like Vim 5.7. + + -- Wichert Akkerman <wakkerma@debian.org> Wed, 30 Jan 2002 15:26:04 +0100 + +vim (6.0.118-1) unstable; urgency=low + + * Re-bump alternative priority, change got lost in the move to vim6 + * Update comment in vimrc about filetype indents + * Update autocommand for reportbug. Closes: Bug#127838 + * More upstream patches: + + 6.0.094: Athena: When clicking in the horizontal scrollbar Vim crashes. + + 6.0.095: Perl: Deleting lines may leave the cursor beyond the + end of the file. + + 6.0.096: When ":saveas fname" fails because the file already + exists, the file name is changed anyway and a following ":w" + will overwrite the file. + + 6.0.097: Re-indenting in Insert mode with CTRL-F may cause a + crash with a multi-byte encoding. + + 6.0.098: GTK: When using Gnome the "Search" and "Search and + Replace" dialog boxes are not translated. + + 6.0.099: Cygwin: When running Vi compatible MS-DOS line endings + cause trouble. + + 6.0.100: ":badd +0 test%file" causes a crash. + + 6.0.101: ":mksession" doesn't restore editing a file that has a + '#' or '%' in its name. + + 6.0.102: When changing folds the cursor may appear halfway a + closed fold. + + 6.0.103: When using 'scrollbind' a large value of 'scrolloff' + will make the scroll binding stop near the end of the file. + + 6.0.104: Multi-byte: When '$' is in 'cpoptions', typing a + double-wide character that overwrites the left halve of an old + double-wide character causes a redraw problem and the cursor stops + blinking. + + 6.0.105: Multi-byte: In a window of one column wide, with syntax + highlighting enabled a crash might happen. + + 6.0.106: Win32: When the printer font is wrong, there is no + error message. + + 6.0.107: VisVim: When editing another file, a modified file may + be written unexpectedly and without warning. + + 6.0.108: When using folding could try displaying line zero, + resulting in an error for a NULL pointer. + + 6.0.109: XIM: When the input method is enabled, repeating an + insertion with "." disables it. + + 6.0.110: Using undo after executing "OxjAxkdd" from a + register in an empty buffer gives an error message. + + 6.0.111: The virtcol() function doesn't take care of 'virtualedit'. + + 6.0.112: The explorer plugin doesn't sort directories with a + space or special character after a directory with a shorter name. + + 6.0.113: ":edit ~/fname" doesn't work if $HOME includes a space. + Also, expanding wildcards with the shell may fail. + + 6.0.114: Using ":p" with fnamemodify() didn't expand "~/" or + "~user/" to a full path. For Win32 the current directory was + prepended. + + 6.0.115: Win32: When using a dialog with a textfield it cannot + scroll the text. + + 6.0.116: MS-Windows NT/2000/XP: filewritable() doesn't work + correctly for filesystems that use ACLs. + + 6.0.117: Win32: when disabling the menu, "set lines=999" doesn't + use all the available screen space. + + 6.0.118: When $TMPDIR is a relative path, the temp directory is + missing a trailing slash and isn't deleted when Vim exits. + + -- Wichert Akkerman <wakkerma@debian.org> Mon, 7 Jan 2002 00:03:23 +0100 + +vim (6.0.093-2) unstable; urgency=low + + * Remove stray comments from default vimrc + * No longer enable filetype indenting by default on popular request + + -- Wichert Akkerman <wakkerma@debian.org> Thu, 6 Dec 2001 14:28:24 +0100 + +vim (6.0.093-1) unstable; urgency=low + + * More upstream patches: + + 6.0.062: Crash when 'verbose' is > 3 and using ":shell". + + 6.0.063: When 'cpoptions' includes "$", using "cw" to type a ')' + on top of the + "$" doesn't update syntax highlighting after it. + + 6.0.064: The NSIS install script doesn't work with newer + versions of NSIS. The diff feature doesn't work when there isn't + a good diff.exe on the system. + + 6.0.065: When using ":normal" in 'indentexpr' it may use redo + characters before its argument. + + 6.0.066: Sometimes undo for one command is split into two undo actions. + + 6.0.067: if_xcmdsrv.c doesn't compile on systems where fd_set + isn't defined in the usual header file + + 6.0.068: When formatting a Visually selected area with "gq" and + the number of lines increases the last line may not be redrawn + correctly. + + 6.0.069: Using "K" on a word that includes a "!" causes a + "No previous command" error, because the "!" is expanded. + + 6.0.070: Win32: The error message for a failed dynamic + linking of a Perl, Ruby, Tcl and Python library is unclear + about what went wrong. + + 6.0.071: The "iris-ansi" builtin termcap isn't very good. + + 6.0.072: When 'lazyredraw' is set, a mapping that stops + Visual mode, moves the cursor and starts Visual mode again + causes a redraw problem. + + 6.0.073: DJGPP: When using CTRL-Z to start a shell, the + prompt is halfway the text. + + 6.0.074: When using "&" in a substitute string a multi-byte + character with a trailbyte 0x5c is not handled correctly. + + 6.0.075: When closing a horizontally split window while + 'eadirection' is "hor" another horizontally split window is + still resized. + + 6.0.076: Warning for wrong pointer type when compiling. + + 6.0.077: Patch 6.0.075 was incomplete. + + 6.0.078: Using "daw" at the end of a line on a single-character + word didn't include the white space before it. At the end of the + file it didn't work at all. + + 6.0.079: When "W" is in 'cpoptions' and 'backupcopy' is "no" or + "auto", can still overwrite a read-only file, because it's + renamed. + + 6.0.080: When using a session file that has the same file in two + windows, the fileinfo() call in do_ecmd() causes a scroll and a + hit-enter prompt. + + 6.0.081: After using ":saveas" the new buffer name is added to + the Buffers menu with a wrong number. + + 6.0.082: When swapping screens in an xterm and there is an + (error) message from the vimrc script, the shell prompt is after + the message. + + 6.0.083: GTK: When compiled without menu support the buttons in + a dialog don't have any text. + + 6.0.084: UTF-8: a "r" command with an argument that is a keymap + for a character with a composing character can't be repeated + with ".". + + 6.0.085: When 'mousefocus' is set, using "s" to go to Insert + mode and then moving the mouse pointer to another window stops + Insert mode, while this doesn't happen with "a" or "i". + + 6.0.086: When using "gu" the message says "~ed". + + 6.0.087: Message translations are incorrect, which may cause a + crash. The Turkish translations needed more work and the + maintainer didn't have time. + + 6.0.088: "." doesn't work after using "rx" in Visual mode. + + 6.0.089: In a C file, using "==" to align a line starting with + "* " after a line with "* -" indents one space too few. + + 6.0.090: When a wrapping line does not fit in a window and + 'scrolloff' is bigger than half the window height, moving the + cursor left or right causes the screen to flash badly. + + 6.0.091: Using CTRL-O in Insert mode, while 'virtualedit' is + "all" and the cursor is after the end-of-line, moves the cursor + left. + + 6.0.092: The explorer plugin doesn't ignore case of 'suffixes' + on MS-Windows. + + 6.0.093: When the Tcl library couldn't be loaded dynamically, + get an error message when closing a buffer or window. + + -- Wichert Akkerman <wakkerma@debian.org> Mon, 12 Nov 2001 14:35:08 +0100 + +vim (6.0.061-1) unstable; urgency=low + + * Add build to binary-arch dependencies. Closes: Bug#117619 + * More upstream patches: + + 6.0.037: When the user has set "did_install_syntax_menu" to avoid + the default Syntax menu it still appears. + + 6.0.038: When 'selection' is "exclusive", deleting a block of text + at the end of a line can leave the cursor beyond the end of the line. + + 6.0.039: "gP" leaves the cursor in the wrong position when + 'virtualedit' is used. Using "c" in blockwise Visual mode leaves the + cursor in a strange position. + + 6.0.040: When 'fileencoding' is invalid and writing fails because of + this, the original file is gone. + + 6.0.041: Using ":language messages en" when LC_MESSAGES is undefined + results in setting LC_CTYPE. + + 6.0.042: ":mksession" can't handle file names with a space. + + 6.0.043: Patch 6.0.041 was wrong. + + 6.0.044: Using a "containedin" list for a syntax item doesn't work + for an item that doesn't have a "contains" argument. Also, + "containedin" doesn't ignore a transparent item. + + 6.0.045: After creating a fold with a Visual selection, another + window with the same buffer still has inverted text. + + 6.0.046: When getrlimit() returns an 8 byte number the check for + running out of stack may fail. + + 6.0.047: Using a regexp with "\(\)" inside a "\%[]" item causes a + crash. + + 6.0.048: Win32: In the console the mouse doesn't always work + correctly. Sometimes after getting focus a mouse movement is + interpreted like a button click. + + 6.0.049: When using evim the intro screen is misleading. + + 6.0.050: UTF-8: "viw" doesn't include non-ASCII characters before + the cursor. + + 6.0.051: UTF-8: Using CTRL-R on the command line doesn't insert + composing characters. + + 6.0.052: The check for rlim_t in patch 6.0.046 does not work on some + systems. + + 6.0.053: Various problems with QNX. + + 6.0.054: When using mswin.vim, CTRL-V pastes a block of text like it + is normal text. Using CTRL-V in blockwise Visual mode leaves "x" + characters behind. + + 6.0.055: GTK: The selection isn't copied the first time. + + 6.0.056: Using "CTRL-O cw" in Insert mode results in a nested Insert + mode. <Esc> doesn't leave Insert mode then. + + 6.0.057: Using ":wincmd g}" in a function doesn't work. + + 6.0.058: When a Cursorhold autocommand moved the cursor, the ruler + wasn't updated. + + 6.0.059: Highlighting for 'hlsearch' isn't visible in lines that are + highlighted for diff highlighting. + + 6.0.060: Motif: When the tooltip is to be popped up, Vim crashes. + + 6.0.061: The toolbar buttons to load and save a session do not + correctly use v:this_session. + + -- Wichert Akkerman <wakkerma@debian.org> Thu, 1 Nov 2001 17:16:37 +0100 + +vim (6.0.036-1) unstable; urgency=low + + * More upstream patches: + + 6.0.028: Can't compile without +virtualedit and with +visualextra. + + 6.0.029: When making a change in line 1, then in line 2 and then + deleting line 1, undo info could be wrong. Only when the + changes are undone at once. + + 6.0.030: Using ":source! file" doesn't work inside a loop or after + ":argdo". + + 6.0.031: Nextstep doesn't have setenv() or putenv(). + + 6.0.032: When changing a setting that affects all folds, they are not + displayed immediately. + + 6.0.033: Using 'wildmenu' on MS-Windows, file names that include a + space are only displayed starting with that space. + + 6.0.034: Calling searchpair() with three arguments could result in a + crash or strange error message. + + 6.0.035: The menu item Edit/Global_Settings/Toggle_Toolbar doesn't + work when 'ignorecase' is set. + + 6.0.036: OS/2, MS-DOS and MS-Windows: Using a path that starts with a + slash in 'tags' doesn't work as expected. + + -- Wichert Akkerman <wakkerma@debian.org> Mon, 29 Oct 2001 20:09:06 +0100 + +vim (6.0.027-1) unstable; urgency=low + + * More upstream patches: + + 6.0.012: Polish translations contains printf format errors, this can + result in a crash when using one of them. + + 6.0.013: Using ":silent! cmd" still gives some error messages, like + for an invalid range. + + 6.0.014: When 'modifiable' is off and 'virtualedit' is "all", "rx" + on a TAB still changes the buffer. + + 6.0.015: When 'cpoptions' includes "S" and "filetype plugin on" has + been used, can get an error for deleting the b:did_ftplugin + variable. + + 6.0.016: bufnr(), bufname() and bufwinnr() don't find unlisted + buffers when the argument is a string. Also for + setbufvar() and getbufvar(). + + 6.0.017: When 'ttybuiltin' is set and a builtin termcap entry defines + t_Co and the external one doesn't, it gets reset to empty. + + 6.0.018: Initializing 'encoding' may cause a crash when setlocale() + is not used. + + 6.0.019: Converting a string with multi-byte characters to a + printable string, e.g., with strtrans(), may cause a crash. + + 6.0.020: When obtaining the value of a global variable internally, + could get the function-local value instead. Applies to + using <Leader> and <LocalLeader> and resetting highlighting + in a function. + + 6.0.021: The 'cscopepathcomp' option didn't work. + + 6.0.022: When using the 'langmap' option, the second character of a + command starting with "g" isn't adjusted. + + 6.0.023: Loading the lhaskell syntax doesn't work. + + 6.0.024: Using "CTRL-V u 9900" in Insert mode may cause a crash. + + 6.0.025: The pattern "\vx(.|$)" doesn't match "x" at the end of a + line. + + 6.0.026: GTK: When using arrow keys to navigate through the menus, + the separators are selected. + + 6.0.027: VMS: Printing doesn't work, the file is deleted too + quickly. No longer need the VMS specific printing menu. + gethostname() is not available with VAXC. The makefile was + lacking selection of the tiny-huge feature set. + * Add a new icon based on vim32x32.xpm with colours remapped to the + menu packages' cmap.xpm. + * Move gvim MIME entries to vim-variant packages only + * Fix packagename in vim menu entry (vim-rt no longer exists) + * Move gvim menu entry to vim-variant packages only + * Properly install menu and mime entries for all packages and make sure + failure cases are handled correctly. + * Add lintian overrides to make it stop complaining about perfectly + correct things. + * Fix debcontrol.vim: allow variable substitution in multiline fields + as well. Closes: Bug#116741 + * Fix inconsistent printf format strings in translations + + -- Wichert Akkerman <wakkerma@debian.org> Sun, 28 Oct 2001 13:44:50 +0900 + +vim (6.0.011-3) unstable; urgency=low + + * Always enable multibyte support + + -- Wichert Akkerman <wakkerma@debian.org> Wed, 3 Oct 2001 17:01:46 +0200 + +vim (6.0.011-2) unstable; urgency=low + + * Create a new vim-ruby package. Closes: Bug#114053 + + -- Wichert Akkerman <wakkerma@debian.org> Mon, 1 Oct 2001 17:25:06 +0200 + +vim (6.0.011-1) unstable; urgency=low + + * Add Build-Depends for libperl-dev. Closes: Bug#114011 + * More upstream patches: + + 6.0.009: Nextstep doesn't have S_ISBLK. + + 6.0.010: Using "gf" on a file name starting with "./" or "../" in + a buffer without a name causes a crash. + + 6.0.011: Python: After replacing or deleting lines get an ml_get error. + + -- Wichert Akkerman <wakkerma@debian.org> Mon, 1 Oct 2001 00:35:55 +0200 + +vim (6.0.008-1) unstable; urgency=low + + * More upstream patches: + + 6.004: The find/replace dialog doesn't reuse a previous argument properly. + + 6.005: Insert mode, "CTRL-O :ls" has a delay before redrawing. + + 6.006: With a vertical split, 'number' set and 'scrolloff' non-zero, + making the window width very small causes a crash. + + 6.007: When setting 'filetype' while there is no FileType autocommand, a + following ":setfiletype" would set 'filetype' again. + + 6.008: 'imdisable' is missing from the options window. + * Fix typo in debian/rules which accidentily disabled perl interpreter + support in vim-perl + + -- Wichert Akkerman <wakkerma@debian.org> Sat, 29 Sep 2001 17:03:42 +0200 + +vim (6.0.003-1) unstable; urgency=low + + * Merge three upstream patches: + + 6.001: Loading the sh.vim syntax file causes error messages + + 6.002: The configure check for ACLs on AIX doesn't work + + 6.003: Using a '@' item in 'viminfo' doesn't work + + -- Wichert Akkerman <wakkerma@debian.org> Thu, 27 Sep 2001 22:37:45 +0200 + +vim (6.0-1) unstable; urgency=low + + * Merge changelog entries from 5.* packages + * Rework debian/rules further + * Add Build-Depends on dpkg >> 1.7.0 since we use dpkg:Version in + debian/control + + -- Wichert Akkerman <wakkerma@debian.org> Wed, 26 Sep 2001 20:40:15 +0200 + +vim (6.0-0.99-1) unstable; urgency=low + + * New upstream version + * Restore vim-{gtk,perl,python,tcl} packages + + -- Wichert Akkerman <wakkerma@debian.org> Wed, 26 Sep 2001 20:40:15 +0200 + +vim (6.0-0.60aw.006-1) unstable; urgency=low + + * Add 6 upstream bugfixes + * Add doc symlinks + + -- Wichert Akkerman <wakkerma@debian.org> Sun, 16 Sep 2001 23:14:43 +0200 + +vim (6.0-0.60aw-1) unstable; urgency=low + + * Seventh and hopefully last beta release + * Enable signs feature + + -- Wichert Akkerman <wakkerma@debian.org> Sun, 16 Sep 2001 23:14:43 +0200 + +vim (6.0-0.60av-1) unstable; urgency=low + + * Sixth beta release + + -- Wichert Akkerman <wakkerma@debian.org> Mon, 10 Sep 2001 03:19:54 +0200 + +vim (6.0-0.60au-1) unstable; urgency=low + + * Fifth `golden' beta release + + -- Wichert Akkerman <wakkerma@debian.org> Tue, 4 Sep 2001 11:32:35 +0200 + +vim (6.0-0.60at-1) unstable; urgency=low + + * Fourth beta release + + -- Wichert Akkerman <wakkerma@debian.org> Mon, 27 Aug 2001 15:43:24 -0700 + +vim (6.0-0.60ar-1) unstable; urgency=low + + * Third beta release + + -- Wichert Akkerman <wakkerma@debian.org> Mon, 13 Aug 2001 14:05:23 +0200 + +vim (6.0-0.60aq-1) unstable; urgency=low + + * Second beta release + + -- Wichert Akkerman <wakkerma@debian.org> Sun, 5 Aug 2001 23:25:28 +0200 + +vim (6.0-0.60ap-2) unstable; urgency=low + + * Oops, vimrc and gvimrc are not normal runtime files, so do symlink + them. + + -- Wichert Akkerman <wakkerma@debian.org> Mon, 30 Jul 2001 10:16:15 +0200 + +vim (6.0-0.60ap-1) unstable; urgency=low + + * First beta release + + -- Wichert Akkerman <wakkerma@debian.org> Sun, 29 Jul 2001 18:03:48 +0200 + +vim (6.0-0.60ao-1) unstable; urgency=low + + * Another new alpha release. + * Symlink /usr/share/vim/vimfiles to /etc/vim and drop vim and gvimrc + symlinks. This means we no longer need any patches to the upstream + source now. + + -- Wichert Akkerman <wakkerma@debian.org> Mon, 23 Jul 2001 16:17:03 +0200 + +vim (6.0-0.60an-1) unstable; urgency=low + + * Another new alpha release. + + -- Wichert Akkerman <wakkerma@debian.org> Thu, 12 Jul 2001 13:12:17 -0700 + +vim (6.0-0.60am-1) unstable; urgency=low + + * Another new alpha release. + + -- Wichert Akkerman <wakkerma@debian.org> Sun, 1 Jul 2001 21:42:56 +0200 + +vim (6.0-0.60al-1) unstable; urgency=low + + * Another new alpha release. + + -- Wichert Akkerman <wakkerma@debian.org> Mon, 25 Jun 2001 00:05:28 +0200 + +vim (6.0-0.60ak-1) unstable; urgency=low + + * Another new alpha release. + + -- Wichert Akkerman <wakkerma@debian.org> Sun, 17 Jun 2001 23:09:43 +0200 + +vim (6.0-0.60aj-1) unstable; urgency=low + + * Another new alpha release. + + -- Wichert Akkerman <wakkerma@debian.org> Sun, 10 Jun 2001 23:35:47 +0200 + +vim (6.0-0.60ai-1) unstable; urgency=low + + * Another new alpha release. + + -- Wichert Akkerman <wakkerma@debian.org> Sun, 3 Jun 2001 22:02:40 +0200 + +vim (6.0-0.60ag-1) unstable; urgency=low + + * Another new alpha release. + * Use DESTDIR to install. + + -- Wichert Akkerman <wakkerma@debian.org> Sun, 20 May 2001 23:55:36 +0200 + +vim (6.0-0.60af-1) unstable; urgency=low + + * Another new alpha release. + + -- Wichert Akkerman <wakkerma@debian.org> Mon, 14 May 2001 19:42:22 +0200 + +vim (6.0-0.60ae-1) unstable; urgency=low + + * Another new alpha release. + + -- Wichert Akkerman <wakkerma@debian.org> Sun, 6 May 2001 22:14:25 +0200 + +vim (6.0-0.60ad-1) unstable; urgency=low + + * Another new alpha release. + + -- Wichert Akkerman <wakkerma@debian.org> Mon, 30 Apr 2001 22:36:49 +0200 + +vim (6.0-0.60ac-1) unstable; urgency=low + + * Another new alpha release. + * Update Debian syntax files with copy from Michael Pfiefel + + -- Wichert Akkerman <wakkerma@debian.org> Sun, 22 Apr 2001 22:09:00 +0200 + +vim (6.0-0.60ab-1) unstable; urgency=low + + * Another new alpha release. + + -- Wichert Akkerman <wakkerma@debian.org> Mon, 16 Apr 2001 22:30:12 +0200 + +vim (6.0-0.60aa-1) unstable; urgency=low + + * Another new alpha release. + + -- Wichert Akkerman <wakkerma@debian.org> Sun, 8 Apr 2001 16:54:34 +0200 + +vim (6.0-0.60z-1) unstable; urgency=low + + * Another new alpha release. + + -- Wichert Akkerman <wakkerma@debian.org> Mon, 26 Mar 2001 17:45:23 +0200 + +vim (6.0-0.60x-1) unstable; urgency=low + + * Another new alpha release. + + -- Wichert Akkerman <wakkerma@debian.org> Wed, 14 Mar 2001 16:25:04 +0100 + +vim (6.0-0.60w-1) unstable; urgency=low + + * Another new alpha release. Closes: Bug#86574 + + -- Wichert Akkerman <wakkerma@debian.org> Tue, 27 Feb 2001 17:59:34 +0100 + +vim (6.0-0.60v-1) unstable; urgency=low + + * Another new alpha release. + + -- Wichert Akkerman <wakkerma@debian.org> Fri, 16 Feb 2001 23:04:32 +0100 + +vim (6.0-0.60u-2) unstable; urgency=low + + * Add patch to memline.c to fix redraw on double-editing error message + + -- Wichert Akkerman <wakkerma@debian.org> Fri, 9 Feb 2001 23:48:09 +0100 + +vim (6.0-0.60u-1) unstable; urgency=low + + * Another new alpha release. + + -- Wichert Akkerman <wakkerma@debian.org> Mon, 5 Feb 2001 23:17:38 +0100 + +vim (6.0-0.60t-1) unstable; urgency=low + + * Another new alpha release. + + -- Wichert Akkerman <wakkerma@debian.org> Sat, 3 Feb 2001 17:11:23 +0100 + +vim (6.0-0.60s-1) unstable; urgency=low + + * Another new alpha release. + + -- Wichert Akkerman <wakkerma@debian.org> Fri, 19 Jan 2001 15:53:05 +1100 + +vim (6.0-0.60r-1) unstable; urgency=low + + * Another new alpha release. + + -- Wichert Akkerman <wakkerma@debian.org> Mon, 8 Jan 2001 05:44:55 +0100 + +vim (6.0-0.60q-1) unstable; urgency=low + + * Another new alpha release. + * Print newline after moving a {g,}vimrc + + -- Wichert Akkerman <wakkerma@debian.org> Wed, 20 Dec 2000 01:45:23 +0100 + +vim (6.0-0.60p-1) unstable; urgency=low + + * Another new alpha release. We're slowly starting to run out of letters! + + -- Wichert Akkerman <wakkerma@debian.org> Fri, 15 Dec 2000 01:05:58 +0100 + +vim (6.0-0.60o-1) unstable; urgency=low + + * You guessed it, another new upstream alpha release for vim6 + + -- Wichert Akkerman <wakkerma@debian.org> Mon, 4 Dec 2000 00:25:33 +0100 + +vim (6.0-0.60m-2) unstable; urgency=low + + * Update Ray's email address in vimrc + * Remove handling of compressed files in vimrc since that is now + done by the gzip plugin + + -- Wichert Akkerman <wakkerma@debian.org> Sun, 3 Dec 2000 02:42:13 +0100 + +vim (6.0-0.60m-1) unstable; urgency=low + + * Another new upstream alpha release for vim6 + * Fix fixup of tags-file: we don't compress the tags file itself + + -- Wichert Akkerman <wakkerma@debian.org> Sun, 26 Nov 2000 16:29:30 +0100 + +vim (6.0-0.60k-2) unstable; urgency=low + + * Add patch to fix partial renaming of rpchf to rcphf in netrw.vim + * Add patch to handle double-byte charactres properly + + -- Wichert Akkerman <wakkerma@debian.org> Mon, 30 Oct 2000 17:33:24 +0100 + +vim (6.0-0.60k-1) unstable; urgency=low + + * Another new upstream alpha release for vim6 + * Use libgtk1.2-dev instead of libgtk-dev for Build-Depends + * Update default vimrc to use new plugins + + -- Wichert Akkerman <wakkerma@debian.org> Sun, 29 Oct 2000 23:57:24 +0100 + +vim (6.0-0.60j-1) unstable; urgency=low + + * Another new upstream alpha release for vim6 + + -- Wichert Akkerman <wakkerma@debian.org> Sun, 22 Oct 2000 22:40:21 +0200 + +vim (6.0-0.60h-1) unstable; urgency=low + + * New upstream release, eighth alpha for vim6 + + -- Wichert Akkerman <wakkerma@debian.org> Fri, 1 Sep 2000 17:24:45 +0200 + +vim (6.0-0.60g-1) unstable; urgency=low + + * New upstream release, seventh alpha for vim6 + + -- Wichert Akkerman <wakkerma@debian.org> Sat, 26 Aug 2000 22:59:48 +0200 + +vim (6.0-0.60f-1) unstable; urgency=low + + * New upstream release, sixth alpha for vim6 + * Add /etc/vim to DFLT_RUNTIMEPATH so sysadmins can customize stuff + in there + + -- Wichert Akkerman <wakkerma@debian.org> Sat, 19 Aug 2000 17:25:33 -0700 + +vim (6.0-0.60e-1) unstable; urgency=low + + * New upstream release, fifth alpha for vim6 + + -- Wichert Akkerman <wakkerma@debian.org> Sun, 6 Aug 2000 18:38:56 -0700 + +vim (6.0-0.60d-2) unstable; urgency=low + + * Small fix for xim_reset to fix segfaults on mouseclick in gvim + + -- Wichert Akkerman <wakkerma@debian.org> Fri, 4 Aug 2000 22:28:20 +0200 + +vim (6.0-0.60d-1) unstable; urgency=low + + * New upstream release, fourth alpha for vim6 + + -- Wichert Akkerman <wakkerma@debian.org> Fri, 4 Aug 2000 00:20:40 +0200 + +vim (6.0-0.60b-1) unstable; urgency=low + + * New upstream release, second alpha for vim6 + * Include lang sources as well now + * Repackaged from scratch: + + vim-rt merged back into vim package + + seperate versions now only include the {g,}vim binary. + * Create html-version of documentation as well + * Move configuration files to /etc/vim/. Closes: Bug#61574 + * Closes: Bug#68502 + + -- Wichert Akkerman <wakkerma@debian.org> Sat, 22 Jul 2000 22:53:40 +0200 + +vim (5.8.007-4) unstable; urgency=low + + * Stupid, I moved a file over but forgot to add a Replaces + to vim-rt. Fixed now. + + -- Wichert Akkerman <wakkerma@debian.org> Thu, 16 Aug 2001 20:33:39 +0200 + +vim (5.8.007-3) unstable; urgency=low + + * Don't Build-Depend on libgmpg1-dev on hurd. Closes: Bug#108239 + * Enable filename modifiers in vim-tiny since we use them in the + default vimrc to read compressed files (such as the documentation). + Closes: Bug#108737 + * We handle spaces in architecture fields now. Closes: Bug#103257 + * Force vimtutor to use /etc/vimrc so it can load compressed files + Closes: Bug#83915 + * Move vimtutor to vim-rt package. Closes: Bug#78783 + + -- Wichert Akkerman <wakkerma@debian.org> Wed, 15 Aug 2001 13:18:09 +0200 + +vim (5.8.007-2) unstable; urgency=low + + * Fix typo in debcontrol.vim + + -- Wichert Akkerman <wakkerma@debian.org> Sun, 15 Jul 2001 21:38:02 +0200 + +vim (5.8.007-1) unstable; urgency=low + + * Merge upstream bugfixes: + + When including a syntax cluster in itself, Vim crashes. + + With the GTK GUI, when 'shell' is not a valid program, ":make" + causes Vim to exit. + + ":hi def link" adds a link to a highlight group while it already + has attributes for the GUI. + + With syntax highlighting, synchronizing on a C-comment failed + after "//*/". + * Update debcontrol.vim. Closes: Bug#105306 + + -- Wichert Akkerman <wakkerma@debian.org> Sun, 15 Jul 2001 15:32:40 +0200 + +vim (5.8.003-1) unstable; urgency=low + + * Use the debchangelog filetype for changelog.dch + * Use a versioned Recommends for vim-rt. Note that this will not help + if you use apt-get. Use a proper frontend instead. + Closes: Bug#100105,#55812,#100021 + * Add Build-Depends on dpkg >= 1.7.0 since we use ${dpkg:Version} now. + * Update debcontrol.vim: + + the section is `doc', not `docs' + + Add non-US/{main,contrib,non-free} + + Accept both `tex' and `text' as sections (ordering problem in regexp) + Closes: Bug#99995 + * Merge upstream bugfixes: + + When exiting and 'cmdheight' is 2 or bigger and 'showcmd' is set, + the cursor is left in the wrong place. (Sascha Blank) + + The dtd.vim syntax file contained a few items that require Vim 6.0. + Closes: Bug#100338,#100348 + + -- Wichert Akkerman <wakkerma@debian.org> Sun, 10 Jun 2001 14:42:30 +0200 + +vim (5.8-1) unstable; urgency=low + + * New upstream bugfix version. Closes: Bug#98731,#74105,#67438,#66882,#65244 + * Use libgtk1.2-dev in the Build-Depends. + Closes: Bug#98101,#67737,#83825,#87291,#93882,#95227,#92065 + * doc symlinks were fixed earlier already. Closes: Bug#48587 + * exuberant-tags is no longer part of the vim source, update debian/rules + accordingly + + -- Wichert Akkerman <wakkerma@debian.org> Sun, 3 Jun 2001 23:28:21 +0200 + +vim (5.7.028-1) unstable; urgency=low + + * Apply more upstream bugfixes + * Use libperl-dev instead of perl5 as Build-Depends. Closes: Bug#92367 + * Add #DEBHELPER# to vim postinst + + -- Wichert Akkerman <wakkerma@debian.org> Sat, 14 Apr 2001 16:47:39 +0200 + +vim (5.7.019-3) unstable; urgency=high + + * Change spaces to tabs in tags file for documentation. Gotta love + cut & paste. Closes: Bug#80802 + * Teach debhelper to handle the doc-symlink. Closes: Bug#80834 + + -- Wichert Akkerman <wakkerma@debian.org> Fri, 29 Dec 2000 17:20:11 +0100 + +vim (5.7.019-2) unstable; urgency=high + + * Fix postinst.. silly cut&paste error. Closes: Bug#80610 + + -- Wichert Akkerman <wakkerma@debian.org> Thu, 28 Dec 2000 00:45:58 +0100 + +vim (5.7.019-1) unstable; urgency=low + + * More upstream bugfixes merged. Closes: Bug#74664 + * Add syntax styles for debian control and changelog files + * Fix alternatives in postinst. Closes: Bug#65066,#74347,#79424,#65843 + * Bump Standards-Version to 3.2.1. Closes: Bug#79982 + * Remove mention of Linux in copyright, this works on other OSes just as + well. + * Update location of upstream sources, they are at ftp.vim.org now + * Teach src/Makefile to quote quotes in pathdef.c so things compile with + the current perl as well. + * Fix handling of xterm clipboard, this should fix the X BadAccess errors + when running gvim remotely with ssh X11 forwarding + * Fix menu icon. Closes: Bug#63622,#69364,#61838,#34404,#79838 + * Actually move manpages to /usr/share + * Bump alternative priority to be the same as elvis + * Fix fixup of tags-file: we don't compress the tags file itself. + * Install tags with mode 644. Closes: Bug#63742 + Closes: Bug#77506 + * Use mail highlightning for SLRN files. Closes: Bug#50206 + * Fix typo in extended descriptions. Closes: Bug#66332 + + -- Wichert Akkerman <wakkerma@debian.org> Tue, 26 Dec 2000 18:14:21 +0100 + +vim (5.7.002-1) unstable; urgency=low + + * Upstream bugfix merged + * Fix typo in build-depends + + -- Wichert Akkerman <wakkerma@debian.org> Thu, 29 Jun 2000 16:10:43 +0200 + +vim (5.7.001-1) unstable; urgency=low + + * Upstream bugfix merged + + -- Wichert Akkerman <wakkerma@debian.org> Tue, 27 Jun 2000 11:29:20 +0200 + +vim (5.7-1) unstable; urgency=low + + * New upstream version + * Suggest cscope + * Update Build Dependencies + * Fix alternatives + + -- Wichert Akkerman <wakkerma@debian.org> Sat, 24 Jun 2000 23:47:45 +0200 + +vim (5.6.090-1) unstable; urgency=low + + * Another upstream bugfix merged, Closes:Bug#65236 + * Compiled with the Debian libgtk, not the helixcode version + + -- Wichert Akkerman <wakkerma@debian.org> Tue, 6 Jun 2000 10:58:54 +0200 + +vim (5.6.089-1) unstable; urgency=low + + * More upstream bugfixes merged + + -- Wichert Akkerman <wakkerma@debian.org> Mon, 5 Jun 2000 20:40:47 +0200 + +vim (5.6.080-1) unstable; urgency=low + + * Enable cscope support + * More upstream bugfixes merged + * Add some build-depends. The list is probably not complete though. + + -- Wichert Akkerman <wakkerma@debian.org> Mon, 5 Jun 2000 18:13:25 +0200 + +vim (5.6.072-1) unstable; urgency=low + + * More upstream bugfixes merged + + -- Wichert Akkerman <wakkerma@debian.org> Tue, 16 May 2000 18:34:10 +0200 + +vim (5.6.070-1) frozen unstable; urgency=low + + * More upstream bugfixes merged + * Use vim-rt package in menu entries. Without this change vim would + never show up in menus. Closes: Bug#63100 + * Change update-alternatives call to reflect that manpages are now in + /usr/share/man. Closes: Bug#63320 + * Add Pre-Depends and check in a new preinst to make sure the running dpkg + supports multiple conflicts & replaces + + -- Wichert Akkerman <wakkerma@debian.org> Mon, 1 May 2000 13:51:11 +0200 + +vim (5.6.052-1) frozen unstable; urgency=low + + * Another 21 new upstream bugfixes merged + + -- Wichert Akkerman <wakkerma@debian.org> Mon, 3 Apr 2000 17:16:59 +0200 + +vim (5.6.031-1) frozen unstable; urgency=low + + * Figures that in the 24 hours after I release an update 16 upstream + patches are released.. + * Enable gpm support (except in vim-tiny of course) on popular request. + * Enable rightleft support in packages with gvim + + -- Wichert Akkerman <wakkerma@debian.org> Sun, 26 Mar 2000 17:18:54 +0200 + +vim (5.6.015-1) frozen unstable; urgency=low + + * 3 more upstream bugfixes applied + * Fix menu entries so we don't mention gvim for vim and vim-tiny + * Link dynamically to libpython + + -- Wichert Akkerman <wakkerma@debian.org> Fri, 24 Mar 2000 15:13:33 +0100 + +vim (5.6.012-1) frozen unstable; urgency=low + + * Another bugfix patch applied (hang with zsh) + * Fooled by debhelper again.. restore maintainer scripts + which were suddenly gone missing, Closes: Bug# 57491, #57500 + + -- Wichert Akkerman <wakkerma@debian.org> Thu, 10 Feb 2000 17:22:37 +0100 + +vim (5.6.011-1) frozen unstable; urgency=low + + * Seven more bugfix patches applied + * Don't include all the gvim stuff in the standard vim package + + -- Wichert Akkerman <wakkerma@debian.org> Thu, 27 Jan 2000 03:05:23 +0100 + +vim (5.6.000-1) frozen unstable; urgency=low + + * No longer beta. There are no changes from the previous package except + that this version is no longer marked as a beta version. + + -- Wichert Akkerman <wakkerma@debian.org> Mon, 17 Jan 2000 00:28:15 +0100 + +vim (5.6-0.5.6a.028-1) frozen unstable; urgency=low + + * Include more upstream bugfixes + * Add Debian-specific filetypes to default vimrc, Closes: Bug#54339 + * Make vim-rt only recommend vim + + -- Wichert Akkerman <wakkerma@debian.org> Sat, 15 Jan 2000 16:38:17 +0100 + +vim (5.6-0.5.6a.019-1) unstable; urgency=low + + * Include patches up to 5.6a.019 + * Rebuild to get VIMRUNTIME correct + * Fix description for vim-gtk, Closes: Bug#54748 + + -- Wichert Akkerman <Wakkerma@debian.org> Tue, 11 Jan 2000 10:14:10 +0100 + +vim (5.6-0.5.6a.018-1) unstable; urgency=low + + * New upstream version, pre-release for 5.6, patchlevel 018 + * Provide editor + * vim no longer has any X support + * Add vim-gtk with the GTK frontend + + -- Wichert Akkerman <Wakkerma@debian.org> Mon, 10 Jan 2000 03:00:44 +0100 + +vim (5.5.033-1) unstable; urgency=low + + * Include patches up to 5.5.033 + + -- Wichert Akkerman <wakkerma@debian.org> Mon, 18 Oct 1999 16:14:21 +0200 + +vim (5.5.009-1) unstable; urgency=low + + * Include patches up to 5.5.009 + * Fix paths in manpages + + -- Wichert Akkerman <wakkerma@debian.org> Tue, 28 Sep 1999 02:08:28 +0200 + +vim (5.5-1) unstable; urgency=low + + * New upstream version + + -- Wichert Akkerman <wakkerma@debian.org> Tue, 21 Sep 1999 04:07:57 +0200 + +vim (5.4.49-1) unstable; urgency=low + + * Include patches up to 5.4.49 + * Build with multibyte and xim support, Closes:Bug#43245 + + -- Wichert Akkerman <wakkerma@debian.org> Thu, 2 Sep 1999 15:50:12 +0200 + + +vim (5.4.21-1) unstable; urgency=low + + * Include patches up to 5.4.21 + * Fix asnother concatenated line in vimrc + * Don't register gvim for vim-tty + + -- Wichert Akkerman <wakkerma@debian.org> Wed, 11 Aug 1999 01:18:01 +0200 + +vim (5.4.17-1) unstable; urgency=low + + * Include patches up to 5.4.17 + * Make vim-tty provide vim, Closes:Bug#42659 + * Fix accidentily joined lines in vimrc, Closes:Bug#42663 + + -- Wichert Akkerman <wakkerma@debian.org> Mon, 9 Aug 1999 04:30:37 +0200 + +vim (5.4.12-1) unstable; urgency=low + + * Include patches up to 5.4.12 + * Add a new package: vim-tty. This is a build with all the normal + features, but without any X support. + + -- Wichert Akkerman <wakkerma@debian.org> Thu, 5 Aug 1999 21:31:13 +0200 + +vim (5.4.11-1) unstable; urgency=low + + * Include patches up to 5.4.11 + + -- Wichert Akkerman <wakkerma@debian.org> Mon, 2 Aug 1999 03:03:02 +0200 + +vim (5.4.7-1) unstable; urgency=low + + * Include patches up to 5.4.7 + * Fix replaces, dpkg can't handle multiple replaces-lines in control + * Fix typo in debian/rules causing vim-tiny to get X11 support + * Only change extension in second column of documentation tags-file + * Remove [ce]tags, they are packaged seperately + + -- Wichert Akkerman <wakkerma@debian.org> Thu, 29 Jul 1999 17:17:05 +0200 + +vim (5.4-1) unstable; urgency=low + + * Finally, vim 5.4 has arrived! + * Lets build vim-rt only in binary-indep now + + -- Wichert Akkerman <wakkerma@debian.org> Sun, 25 Jul 1999 23:19:03 +0200 + +vim (5.4-0.5.4p-1) unstable; urgency=low + + * Yet-another-last-beta for vim 5.4 + * Make vim-* replace vim-rt since we moved some stuff around + + -- Wichert Akkerman <wakkerma@debian.org> Mon, 19 Jul 1999 17:29:49 +0200 + +vim (5.4-0.5.4o.6) unstable; urgency=low + + * Patched up to version 5.4o.6 beta + * Default vimrc clean on request of the Cistron crew: :) + + Change default vimrc to be more compatible with upstream defaults + + Turn backup off by default + + Don't map Q to gq anymore + + -- Wichert Akkerman <wakkerma@debian.org> Thu, 15 Jul 1999 23:18:28 +0200 + +vim (5.4-0.5.4o.1) unstable; urgency=low + + * Third upstream beta-version + * Patched up to version 5.4o.1 beta + + -- Wichert Akkerman <wakkerma@debian.org> Mon, 12 Jul 1999 17:26:01 +0200 + +vim (5.4-0.5.4n.18) unstable; urgency=low + + * Second upstream beta-version + * Patched up to version 5.4n.18 beta + * Fix vimrc: we should explicitly use expand now + + -- Wichert Akkerman <wakkerma@debian.org> Thu, 8 Jul 1999 01:56:55 +0200 + +vim (5.4-0.5.4m.17) unstable; urgency=low + + * Lets upload this somewhere as well + * Patched up to version 5.4m.17 beta + + -- Wichert Akkerman <wakkerma@debian.org> Tue, 29 Jun 1999 00:21:52 +0200 + +vim (5.4m-1) unstable; urgency=low + + * Experimental package to test vim 5.4 packaging + * Patched up to version 5.4m.5 + * Use GTK 1.2 frontend by default now + * Merge src and runtime tarballs from upstream, since they need eachother + in order to compile. + * Rewritten debian/rules to make it more manageable + * Take advantage of new location for runtime-support so we no longer need + a patch to relocate the system-wide configfiles + * Don't make vim-rt depend on a versioned vim + * Bumb standards-version to 2.5.1 + + -- Wichert Akkerman <wakkerma@debian.org> Tue, 22 Jun 1999 01:17:16 +0200 + +vim (5.3-13) frozen unstable; urgency=low + + * Compile vim-python with python-dev installed so it actually works + * Note to release-manager: no new code since previous version in slink, + only simple bugfixes + + -- Wichert Akkerman <wakkerma@debian.org> Sun, 14 Feb 1999 21:06:16 +0100 + +vim (5.3-12) unstable; urgency=low + + * New license: vim is now fully DFSG-free! + * Run gvim with -f from mailcap so it doesn't background and confuse + the hell out of metamail (Bug# 32141) + * Remove */* entry that was accidently left in the mailcap for vim-tiny + + -- Wichert Akkerman <wakkerma@debian.org> Tue, 26 Jan 1999 23:58:50 +0100 + +vim (5.3-11) unstable; urgency=low + + * Added langmap support for all packages, except vim-tiny (Bug# 28118). + + -- Wichert Akkerman <wakkerma@debian.org> Thu, 26 Nov 1998 20:55:47 +0100 + +vim (5.3-10) frozen unstable; urgency=low + + * Add autocmd support to vim-tiny so it can read the online help again. + (this adds 12Kb to the memory usage). + * Rebuild with ncurses4 + + -- Wichert Akkerman <wakkerma@debian.org> Mon, 2 Nov 1998 16:34:56 +0100 + +vim (5.3-9) unstable; urgency=low + + * Downgraded vim-rt Recommend to Suggest for vim-tiny (Bug# 27436) + + -- Wichert Akkerman <wakkerma@debian.org> Tue, 13 Oct 1998 15:53:33 +0200 + +vim (5.3-8) unstable; urgency=low + + * Update mime-support + + -- Wichert Akkerman <wakkerma@debian.org> Tue, 29 Sep 1998 01:56:06 +0200 + +vim (5.3-7) unstable; urgency=low + + * Recompiled with python-dev installed + + -- Wichert Akkerman <wakkerma@debian.org> Fri, 18 Sep 1998 13:57:52 +0200 + +vim (5.3-6) unstable; urgency=low + + * Fix mime-support somewhat: + + change test for $DISPLAY + + use (g)view when only viewing files + * Create multiple vim-packages (vim, vim-tiny, vim-perl, vim-python and + vim-tcl) + * Removed empty /usr/share/vim directory, it's now completely in the vim-rt + package anyway. + + -- Wichert Akkerman <wakkerma@debian.org> Mon, 14 Sep 1998 01:13:31 +0200 + +vim (5.3-5) unstable; urgency=low + + * Added support for update-mime, based on sample from + Brian White <bcwhite@verisim.com> (Bug# 26550) + + -- Wichert Akkerman <wakkerma@debian.org> Thu, 10 Sep 1998 20:56:04 +0200 + +vim (5.3-4) unstable; urgency=low + + * Revamped postinst not to override alternatives (Bug# 26186) + * Be lazy and let debhelper add the update-menus call + + -- Wichert Akkerman <wakkerma@debian.org> Wed, 9 Sep 1998 12:02:14 +0200 + +vim (5.3-3) unstable; urgency=low + + * Fix typo on control-file (found by Matt McLean <keys@yikes.com>) + + -- Wichert Akkerman <wakkerma@debian.org> Tue, 1 Sep 1998 19:04:45 +0200 + +vim (5.3-2) unstable; urgency=low + + * Fix typo in changelog (noted by Ruud de Rooij) + + -- Wichert Akkerman <wakkerma@debian.org> Mon, 31 Aug 1998 13:11:13 +0200 + + +vim (5.3-1) unstable; urgency=low + + * New upstream version (bugfix release) + * Recommend vim-rt instead of only suggesting it + * Put menu-file back in this package + + -- Wichert Akkerman <wakkerma@debian.org> Mon, 31 Aug 1998 11:41:37 +0200 + +vim (5.2-2) unstable; urgency=low + + * Add email-address to maintainer-field in debian/control + * Added patch to fix some small errors for certain commands + + -- Wichert Akkerman <wakkerma@debian.org> Wed, 26 Aug 1998 01:09:09 +0200 + +vim (5.2-1) unstable; urgency=low + + * New upstream version + + package split in 2: vim and vim-rt + + UNICODE support + * Make vim honour TMPDIR on all systems except OS/2 and win32 + * Update debian/control to reflect new maintainer :) + + -- Wichert Akkerman <wakkerma@debian.org> Tue, 25 Aug 1998 13:33:26 +0200 + +vim (5.1-1) unstable; urgency=low + + * New maintainer + * Fix ex alternative (Bug# 23675) + * Fix copyright (Bug# 24984) + * Don't install sample macros twice + * Clean debian/rules some more + * Move tools to the examples-subdirectory + * Fix location of perl in examples + * Fix some filemodes of examples + + -- Wichert Akkerman <wakkerma@debian.org> Mon, 17 Aug 1998 02:34:01 +0200 + +vim (5.1-0.4) unstable; urgency=low + + * Yet another non-maintainer upload + * Fixed alignment trap on alpha's (Bug# 23590) + * Added some example-vimrc code + * Also provide alternatives for ex and /usr/bin/editor (Bug# 22310) + + -- Wichert Akkerman <wakkerma@debian.org> Tue, 16 Jun 1998 15:58:07 +0200 + +vim (5.1-0.3) unstable; urgency=low + + * Yet another non-maintainer upload + * Added support for editing bzip2'ed files (from Vaclav Hula) + * Added octave to the syntax-menu + + -- Wichert Akkerman <wakkerma@debian.org> Fri, 24 Apr 1998 16:28:42 +0200 + +vim (5.1-0.2) unstable; urgency=low + + * Previous upload didn't include .orig.tar.gz . + * Modified /etc/vimrc: included some recommendations for more + user-friendly behaviour (commented out as they deviate from standard vi + behaviour) + + -- J.H.M. Dassen (Ray) <jdassen@wi.LeidenUniv.nl> Fri, 24 Apr 1998 14:33:34 +0200 + +vim (5.1-0.1) unstable; urgency=low + + * Non-maintainer upload + * New upstream release. + * Bumped Standards-Version. + * Re-enabled athena GUI (fixes #21194). + * Made /etc/gvimrc a conffile. + * Added syntax highlighting for Octave (fixes #18817). + * Disable syntax hightlighting for vim & enable it for gvim + * Revamped building process (debhelper) + * Modified & commented vimrc + * Enhanced menu-support (include gvim & icons) + + -- Wichert Akkerman <wakkerma@debian.org> Tue, 21 Apr 1998 16:18:02 +0200 + +vim (5.0-0.2) frozen unstable; urgency=low + + * Switched to the .gz autocommands from vimrc_example, so that :help works + again (fixes #20897). + + -- J.H.M. Dassen (Ray) <jdassen@wi.LeidenUniv.nl> Mon, 13 Apr 1998 15:50:46 +0200 + +vim (5.0-0.1) unstable; urgency=low + + * Merged in the patches from the mailing list + * Non-maintainer release + * New upstream version + + -- Alexey Marinichev <lyosha@math.uu.se> Sun, 15 Mar 1998 02:41:37 +0100 + +vim (4.6-2) unstable; urgency=low + + * Built with libc6, ncurses3.4, and xlib6g + * Updated menu entry + + -- Galen Hazelwood <galenh@micron.net> Thu, 9 Sep 1997 12:44:30 -0600 + +vim (4.6-1) frozen unstable; urgency=low + + * New upstream version (fixes #8674) + * Enabled right-to-left support + + -- Galen Hazelwood <galenh@micron.net> Sat, 12 Apr 1997 11:11:00 -0600 + +vim (4.5-5) unstable; urgency=low + + * New maintainer + * Menu entry /usr/lib/menu/vim included + * No longer Provides: editor (fixes bug #5602) + + -- Galen Hazelwood <galenh@micron.net> Thu, 20 Feb 1997 13:44:36 -0700 + +vim (4.5-4) unstable; urgency=low + + * GUI support is back in now. + * modified postinst to put gvim into fvwm's menus, not normal vim. + + -- Stuart Lamble <lamble@yoyo.cc.monash.edu.au> Tue, 19 Nov 1996 21:51:28 +1100 + +vim (4.5-3) unstable frozen; urgency=low + + * Last release without GUI support - I've finally downloaded the 3.2 .deb + files. + * added view and view.1.gz to /etc/alternatives. + * changed CFLAGS to compile with -g -O2 (instead of -g -O) + * modified the default vimrc to allow full read/writing of text files + compressed with gzip. + * added "version 4.0" to the default vimrc (so much for getting people + to RTFM :-) + * Ray Dassen sent me some email about not capturing stderr by default; + after thinking about it, I decided against this. It's useful for + programmers when compiling from within vim, and besides, it's easy to + configure (look at the shellredir setting :) + + -- Stuart Lamble <lamble@yoyo.cc.monash.edu.au> Tue, 19 Nov 1996 19:43:56 +1100 + +vim (4.5-2) unstable; urgency=low + + * merged in patches from Bram into both source trees (the new version is + also called 4.5 ... go figure. :-) + * removed ctags from the distribution, pending further discussion on it: + it's the same as the ctags found elsewhere in the distribution. + * fixed a small typo in the copyright: referred to 4.4 instead of 4.5. + Oops. :) + + -- Stuart Lamble <lamble@yoyo.cc.monash.edu.au> Sun, 20 Oct 1996 19:20:36 +1000 + +vim (4.5-1) unstable; urgency=low + + * new upstream version + * merged in the patches from 4.4-2 into the new source tree + + -- Stuart Lamble <lamble@yoyo.cc.monash.edu.au> Fri, 11 Oct 1996 19:10:13 +1000 + +vim (4.4-2) unstable; urgency=low + + * uncompressed doc/vim_tags to allow vim to handle gzipped docs, and + modified the installed version to direct help to those gzipped docs. + * added an empty gvimrc to /etc + * added a vimrc capable of reading the gzipped docs + * merged in Lars' patches for install-fvwm2menu + + -- Stuart Lamble <lamble@yoyo.cc.monash.edu.au> Thu, 26 Sep 1996 19:46:11 +1000 + +vim (4.4-1.1) unstable; urgency=low + + * added calls to install-fvwm2menu to postinst and prerm + + -- Lars Wirzenius <liw@iki.fi> Thu, 3 Oct 1996 21:28:42 +0300 + +vim (4.4-1) unstable; urgency=low + + * new upstream version (considered beta, but seems pretty stable to + me.) + * modified Makefile to allow for installation to .../debian/tmp rather + than /usr/ (otherwise, man pages would have been sorta fubar..) + * redirected global vimrc/gvimrc to /etc + * modified configure to look for termcap _last_, ncurses first + (upstream version: termcap, then ncurses.) + * added a "Provides: editor" (don't know if this is still current, but + it won't hurt if it isn't.) + + -- Stuart Lamble <lamble@yoyo.cc.monash.edu.au> Sun, 22 Sep 1996 17:38:15 +1000 diff --git a/debian/changelog.upstream b/debian/changelog.upstream new file mode 100644 index 0000000..cdc4bbf --- /dev/null +++ b/debian/changelog.upstream @@ -0,0 +1,1365 @@ +Patches for Vim - Vi IMproved 9.0 + +The files in this directory contain source code changes to fix problems +in a released version of Vim. Each file also contains an explanation of +the problem that is fixed, like the message that was sent to the vim-dev +maillist. + +The best is to apply the patches in sequence. This avoids problems when +a patch depends on a previous patch. + +Before patching, change to the top Vim directory, where the "src" and +"runtime" directories are located. +Depending on the version of "patch" that you use, you may have add an +argument to make it patch the right file: + patch -p < 9.0.0001 + patch -p0 < 9.0.0001 + +After applying a patch, you need to compile Vim. There are no patches +for binaries. + +Checksums for the patch files can be found in the file MD5SUMS. + + +Individual patches for Vim 9.0: + + SIZE NAME FIXES + 10943 9.0.0001 Travis CI is no longer used + 7187 9.0.0002 map functionality outside of map.c + 13500 9.0.0003 functions are global while they could be local + 3161 9.0.0004 plural messages not translated properly + 1987 9.0.0005 hare files are not recognized + 7042 9.0.0006 not all Visual Basic files are recognized + 23035 9.0.0007 no support for double, dotted and dashed underlines + 6874 9.0.0008 cannot specify the variable name for "xxd -i" + 2278 9.0.0009 going past the end of a menu item with only modifier + 3026 9.0.0010 returning 0 for has('patch-9.0.0') is inconsistent + 1982 9.0.0011 reading beyond the end of the line with put command + 5607 9.0.0012 signature files not detected properly + 22831 9.0.0013 reproducing memory access errors can be difficult + 2178 9.0.0014 missing part of the test override change + 2455 9.0.0015 with EXITFREE defined terminal menus are not cleared + 6026 9.0.0016 comparing line pointer for 'breakindent' is not reliable + 1968 9.0.0017 accessing memory beyond the end of the line + 2237 9.0.0018 going over the end of the typahead + 2038 9.0.0019 timers test not run where possible + 2512 9.0.0020 with some completion reading past end of string + 3392 9.0.0021 invalid memory access when adding word to spell word list + 1537 9.0.0022 spell test fails + 7528 9.0.0023 on Solaris timer_create() exists but does not work + 1807 9.0.0024 may access part of typeahead buf that isn't filled + 2411 9.0.0025 accessing beyond allocated memory with the cmdline window + 2597 9.0.0026 accessing freed memory with diff put + 28245 9.0.0027 the command line test is getting quite big + 3048 9.0.0028 MS-Windows: tests fail if there is a "runtime" directory + 4014 9.0.0029 the bitmaps/vim.ico file is not in the distribution + 1834 9.0.0030 matchfuzzy test depends on path of current directory + 6659 9.0.0031 <cmod> of user command does not have correct verbose value + 3962 9.0.0032 in the quickfix window 'cursorline' overrules QuickFixLine + 2617 9.0.0033 on a Belgian keyboard CTRL-[ does not work + 3121 9.0.0034 spell tests do not always clear the word list + 2749 9.0.0035 spell dump may go beyond end of an array + 43198 9.0.0036 'fillchars' cannot have window-local values + 1806 9.0.0037 build error + 3496 9.0.0038 'listchars' test fails + 1584 9.0.0039 not all systems have GDK_KEY_dead_circumflex + 15109 9.0.0040 use of set_chars_option() is confusing + 5565 9.0.0041 a couple of filetype patterns do not have "*" before "/etc" + 1498 9.0.0042 missing change for filetype detection + 3054 9.0.0043 insufficient testing for bracket commands + 4013 9.0.0044 typos in comments, wrapping lines + 8646 9.0.0045 reading past end of completion with a long line + 2228 9.0.0046 reading past end of completion with duplicate match + 2821 9.0.0047 using freed memory with recursive substitute + 21444 9.0.0048 cursor in wrong column with mouse click after concealed text + 2452 9.0.0049 csv and tsv files are not recognized + 1553 9.0.0050 split else-if is confusing + 2767 9.0.0051 using CTRL-C wih :append may hang Vim + 3201 9.0.0052 "zG" may throw an error if invalid character follows + 2194 9.0.0053 E1281 not tested with the old regexp engine + 1608 9.0.0054 compiler warning for size_t to int conversion + 4433 9.0.0055 bitbake files are not detected + 2158 9.0.0056 wrong line number reported when :cexpr fails in :def function + 2009 9.0.0057 has('patch-xxx') returns true + 8298 9.0.0058 Win32: cannot test low level events + 11801 9.0.0059 test file has wrong name + 2022 9.0.0060 accessing uninitialized memory when completing long line + 5900 9.0.0061 ml_get error with nested autocommand + 1889 9.0.0062 compiler warnings for signed/unsigned char + 57792 9.0.0063 too many type casts for dict_get functions + 2537 9.0.0064 confusing error when using "q:" in command line window + 6470 9.0.0065 cross-compiling doesn't work because of timer_create check + 2828 9.0.0066 switching window uneccarily when getting buffer options + 76728 9.0.0067 cannot show virtual text + 1896 9.0.0068 build fails with tiny features + 1595 9.0.0069 leaking memory when using text prop with inserted text + 2892 9.0.0070 using utfc_ptr2char_len() when length is negative + 2635 9.0.0071 command overlaps with printed text in scrollback + 1617 9.0.0072 compiler warning for uninitialized variable + 3866 9.0.0073 too many files recognized as bsdl + 2538 9.0.0074 Coverity warns for double free + 2021 9.0.0075 some compilers warn for using an uninitialized variable + 2302 9.0.0076 no test for what patch 8.1.1424 fixes + 4067 9.0.0077 wrong restored cursor position if switching window in autocmd + 4153 9.0.0078 star register is unexpectedly changed when deleting + 3168 9.0.0079 error in autoload script not reported for 'foldexpr' + 2242 9.0.0080 compiler warning for size_t to int conversion + 2614 9.0.0081 command line completion of user command may have duplicates + 3965 9.0.0082 cannot interrupt global command from command line + 8265 9.0.0083 ModeChanged event not triggered when leaving cmdline window + 2596 9.0.0084 using "terraform" filetype for .tfvars file is bad + 2232 9.0.0085 ":write" fails after ":file name" and then ":edit" + 2801 9.0.0086 tabline is not redrawn when entering command line + 9266 9.0.0087 MS-Windows: CTRL-[ on Belgian keyboard does not work like Esc + 2810 9.0.0088 pattern for detecting bitbake files is not sufficient + 2771 9.0.0089 fuzzy argument completion doesn't work for shell commands + 3448 9.0.0090 no error when assigning bool to a string option + 1571 9.0.0091 duplicate error number + 3344 9.0.0092 plugins cannot change v:completed_item + 2610 9.0.0093 sway config files are recognized as i3config + 3305 9.0.0094 cursor restored unexpected with nested autocommand + 3211 9.0.0095 conditions are always true + 9909 9.0.0096 flag "new_value_alloced" is always true + 3080 9.0.0097 long quickfix line is truncated for :clist + 4463 9.0.0098 missing include file in timer_create configure check + 6440 9.0.0099 scrollback can be wrong after redrawing the command line + 1791 9.0.0100 get hit-enter prompt for system() when '!' is in 'guioptions' + 2794 9.0.0101 invalid memory access in diff mode with "dp" and undo + 1977 9.0.0102 reading past end of line with insert mode completion + 10290 9.0.0103 if running configure with cached results -lrt may be missing + 2192 9.0.0104 going beyond allocated memory when evaluating string constant + 4082 9.0.0105 illegal memory access when pattern starts with illegal byte + 1965 9.0.0106 illegal byte regexp test doesn't fail when fix is reversed + 1679 9.0.0107 condition always has the same value + 3603 9.0.0108 configure check for timer_create may give wrong error + 3041 9.0.0109 writing over the end of a buffer on stack + 6200 9.0.0110 help tag generation picks up words in code examples + 3507 9.0.0111 "nocombine" is missing from synIDattr() + 2215 9.0.0112 MS-Windows: test fails because file already exists + 3585 9.0.0113 has() is not strict about parsing the patch version + 20547 9.0.0114 the command line takes up space even when not used + 3596 9.0.0115 when 'cmdheight' is zero pressing ':' may scroll a window + 4387 9.0.0116 virtual text not displayed if 'signcolumn' is "yes" + 4359 9.0.0117 text of removed textprop with text is not freed + 5408 9.0.0118 no test for what patch 9.0.0115 fixes + 2331 9.0.0119 tiny chance that creating a backup file fails + 2374 9.0.0120 MS-Windows GUI: cannot use AltGr + Space + 25626 9.0.0121 cannot put virtual text after or below a line + 2021 9.0.0122 breakindent test fails + 1599 9.0.0123 cannot build with small features + 20585 9.0.0124 code has more indent than needed + 3234 9.0.0125 cursor positioned wrong with virtual text after the line + 3110 9.0.0126 expanding file names fails in dir with more than 255 entries + 1607 9.0.0127 unused variable + 2669 9.0.0128 Coverity complains about possible double free + 1558 9.0.0129 compiler warning for int/size_t usage + 5275 9.0.0130 cursor position wrong when inserting around virtual text + 4402 9.0.0131 virtual text with Tab is not displayed correctly + 9119 9.0.0132 multi-byte characters in virtual text not handled correctly + 8894 9.0.0133 virtual text after line moves to joined line + 2416 9.0.0134 no test for text property with column zero + 2321 9.0.0135 comment about tabpage line above the wrong code + 2556 9.0.0136 after CTRL-Left-mouse click a mouse scroll also has CTRL + 1489 9.0.0137 debugger test may fail when $CWD is very long + 4083 9.0.0138 not enough characters accepted for 'spellfile' + 19135 9.0.0139 truncating virtual text after a line not implemented + 3634 9.0.0140 execute() does not use the "legacy" command modifier + 3107 9.0.0141 "delmenu" does not remove autocmmands + 4144 9.0.0142 crash when adding and removing virtual text + 7209 9.0.0143 cursor positioned after virtual text in empty line + 6648 9.0.0144 text property cannot override 'cursorline' highlight + 9354 9.0.0145 substitute that joins lines drops text properties + 4116 9.0.0146 missing part of change for "override" flag + 3791 9.0.0147 cursor positioned wrong after two "below" text properties + 3348 9.0.0148 a "below" aligned text property gets 'showbreak' displayed + 2744 9.0.0149 test for fuzzy completion fails sometimes + 4119 9.0.0150 error for using #{ in an expression is a bit confusing + 73530 9.0.0151 a "below" aligned text property does not work with 'nowrap' + 1616 9.0.0152 warning for unused argument in small build + 85848 9.0.0153 no fold and sign column for virtual text with "below" align + 10213 9.0.0154 text properties wrong after splitting a line + 7252 9.0.0155 text properties "right" and "after" wrong with 'nowrap' + 5883 9.0.0156 giving E1170 only in an expression is confusing + 5456 9.0.0157 'showbreak' displayed below truncated "after" text prop + 6984 9.0.0158 with 'nowrap' "below" property not displayed correctly + 1981 9.0.0159 cannot build with small features + 1612 9.0.0160 some diff mode tests fail + 1692 9.0.0161 warning for uninitialized variable + 3263 9.0.0162 text property "below" gets indent if 'breakindent' is set + 2771 9.0.0163 text property not adjusted for text inserted with "p" + 2051 9.0.0164 using freed memory with put command + 10170 9.0.0165 looking up a text property type by ID is slow + 2762 9.0.0166 when using text properties line text length computed twice + 2445 9.0.0167 checking for text properties could be a bit more efficient + 12352 9.0.0168 cursor positioned wrong with two virtual text properties + 2982 9.0.0169 insufficient testing for line2byte() with text properties + 4918 9.0.0170 various minor code formatting issues + 1929 9.0.0171 quickfix line highlight is overruled by 'cursorline' + 2292 9.0.0172 trying to allocate zero bytes + 1718 9.0.0173 assert fails only on MS-Windows + 2230 9.0.0174 no error for using "#{ comment" in a compiled function + 3698 9.0.0175 spell checking for capital not working with trailing space + 5960 9.0.0176 checking character options is duplicated and incomplete + 3553 9.0.0177 cursor position wrong with 'virtualedit' and mouse click + 12603 9.0.0178 cursor position wrong with virtual text before Tab + 10693 9.0.0179 cursor pos wrong with wrapping virtual text in empty line + 1599 9.0.0180 stray logfile appears when running tests + 8334 9.0.0181 textprop test with line2byte() fails on MS-Windows + 2585 9.0.0182 quarto files are not recognized + 4622 9.0.0183 extra space after virtual text when 'linebreak' is set + 2851 9.0.0184 virtual text prop highlight continues after truncation + 5393 9.0.0185 virtual text does not show if text prop at same position + 10322 9.0.0186 virtual text without highlighting does not show + 2194 9.0.0187 command line height changes when maximizing window height + 2491 9.0.0188 strange effects when using "text_align" with non-zero column + 2050 9.0.0189 invalid memory access for text prop without highlight + 6751 9.0.0190 the way 'cmdheight' can be made zero is inconsistent + 3834 9.0.0191 messages test fails; window size incorrect + 2600 9.0.0192 possible invalid memory access when 'cmdheight' is zero + 11352 9.0.0193 search and match highlight interfere with virtual text + 5895 9.0.0194 cursor displayed in wrong position after removing text prop + 2540 9.0.0195 metafun files are not recogized + 17289 9.0.0196 finding value in list may require a for loop + 2045 9.0.0197 astro files are not detected + 2284 9.0.0198 ml_get error when switching buffer in Visual mode + 5503 9.0.0199 cursor position wrong with two right-aligned virtual texts + 8402 9.0.0200 cursor wrong if 'nowrap' and two right aligned text props + 6257 9.0.0201 CursorLine highlight overrules virtual text highlight + 10832 9.0.0202 code and help for indexof() is not ideal + 7107 9.0.0203 confusing variable name + 5210 9.0.0204 indexof() may leak memory + 8258 9.0.0205 cursor in wrong position when inserting after virtual text +175700 9.0.0206 redraw flags are not named specifically + 2859 9.0.0207 stacktrace not shown when debugging + 5593 9.0.0208 the override flag has no effect for virtual text + 2383 9.0.0209 build error with small features + 7914 9.0.0210 'list' mode does not work properly with virtual text + 2315 9.0.0211 invalid memory access when compiling :lockvar + 2221 9.0.0212 invalid memory access when compiling :unlet + 3090 9.0.0213 using freed memory with error in assert argument + 11813 9.0.0214 splitting a line may duplicate virtual text + 1732 9.0.0215 not passing APC_INDENT flag + 2211 9.0.0216 undo earlier test sometimes fails on MS-Windows + 4327 9.0.0217 'shellslash' works differently when sourcing a script again + 2922 9.0.0218 reading before the start of the line + 4005 9.0.0219 cannot make a funcref with "s:func" in a def function + 3758 9.0.0220 invalid memory access with for loop over NULL string + 3307 9.0.0221 accessing freed memory if compiling nested function fails + 14260 9.0.0222 no good reason why text objects are only in larger builds + 1750 9.0.0223 typo in diffmode test + 2841 9.0.0224 Using NULL pointer when skipping compiled code + 8498 9.0.0225 using freed memory with multiple line breaks in expression + 1744 9.0.0226 job_start() test may fail under valgrind + 1826 9.0.0227 cannot read error message when abort() is called + 3601 9.0.0228 crash when pattern looks below the last line + 7271 9.0.0229 Vim9: error message for missing type is not clear + 8754 9.0.0230 no error for comma missing in list in :def function + 3663 9.0.0231 expanding "**" may loop forever with directory links + 2439 9.0.0232 test with BufNewFile autocmd is flaky + 16452 9.0.0233 removing multiple text properties takes many calls + 3115 9.0.0234 cannot make difference between :normal end and argument char + 3539 9.0.0235 'autoshelldir' does not work with chunked respose + 2162 9.0.0236 popup menu not removed when 'wildmenu' reset while visible + 1521 9.0.0237 Mac: cannot build if dispatch.h is not available + 2690 9.0.0238 Shift-Tab shows matches on cmdline when 'wildmenu' is off + 1646 9.0.0239 build failure without the +wildmenu feature + 2485 9.0.0240 crash when using ":mkspell" with an empty .dic file + 3716 9.0.0241 "make install" does not install shared syntax file + 2533 9.0.0242 "make install" still fails + 2016 9.0.0243 text properties "below" sort differently on MS-Windows + 8292 9.0.0244 cannot easily get the list of sourced scripts + 15012 9.0.0245 mechanism to prevent recursive screen updating is incomplete + 2774 9.0.0246 using freed memory when 'tagfunc' deletes the buffer + 36292 9.0.0247 cannot add padding to virtual text without highlight + 2721 9.0.0248 duplicate code in finding a script in the execution stack + 2079 9.0.0249 no test for what 9.0.0234 fixes + 2009 9.0.0250 slightly inconsistent error messages + 1562 9.0.0251 test output shows up in git + 4311 9.0.0252 cursor in wrong place after virtual text + 16714 9.0.0253 a symlink to an autoload script results in two entries + 2502 9.0.0254 typo in function name + 1616 9.0.0255 build failure without the eval feature + 2188 9.0.0256 compiler warning for uninitialized variables + 1895 9.0.0257 "->" in ":scriptnames" output not tested yet + 2518 9.0.0258 MS-Windows installer skips syntax/shared + 5477 9.0.0259 crash with mouse click when not initialized + 2511 9.0.0260 using freed memory when using 'quickfixtextfunc' recursively + 4085 9.0.0261 bufload() reads a file even if the name is not a file name + 1367 9.0.0262 build failure without the +quickfix feature + 19310 9.0.0263 too many #ifdefs + 2628 9.0.0264 CI still runs on Ubuntu 18.04 + 32267 9.0.0265 no good reason why the "gf" command isn't in the tiny version + 1874 9.0.0266 compiler warning for unused argument + 1374 9.0.0267 Coverity workflow still uses Ubuntu 18.04 + 1546 9.0.0268 build error without the +eval feature + 10096 9.0.0269 getscriptinfo() does not include the version + 20354 9.0.0270 some values of 'path' and 'tags' invalid in the tiny version + 2819 9.0.0271 using INIT() in non-header files + 4566 9.0.0272 BufReadCmd not triggered when loading a "nofile" buffer + 3480 9.0.0273 Konsole termresponse not recognized + 4905 9.0.0274 netrw plugin does not show remote files + 2497 9.0.0275 BufEnter not triggered when using ":edit" in "nofile" buffer + 5701 9.0.0276 'buftype' values not sufficiently tested + 1876 9.0.0277 Coverity CI: update-alternatives not needed with Ubuntu 20.04 + 11316 9.0.0278 the +wildignore feature is nearly always available + 22379 9.0.0279 the tiny version has the popup menu but not 'wildmenu' + 13858 9.0.0280 the builtin termcap list depends on the version + 2212 9.0.0281 build failure without the +eval feature + 2709 9.0.0282 a nested timout stops the previous timeout + 4048 9.0.0283 cannot complete "syn list @cluster" + 5126 9.0.0284 using static buffer for multiple completion functions + 12614 9.0.0285 it is not easy to change the command line from a plugin + 6956 9.0.0286 using freed memory when location list changed in autocmd + 10182 9.0.0287 Irix systems no longer exist + 26570 9.0.0288 when 'cmdheight' is zero some messages are not displayed + 2637 9.0.0289 invalid memory write + 2739 9.0.0290 compiler warning for variable set but not used + 1475 9.0.0291 test failing + 1891 9.0.0292 test causes another test to fail + 2452 9.0.0293 messages window not hidden when starting a command line + 5546 9.0.0294 crash when 'cmdheight' is 0 and popup_clear() used + 2056 9.0.0295 GUI drop files test sometimes fails + 4522 9.0.0296 message in popup is shortened unnecessary + 6894 9.0.0297 cursor position wrong after right aligned virtual text + 1687 9.0.0298 compiler warning for size_t to int conversion + 3958 9.0.0299 error messages for setcmdline() could be better + 8873 9.0.0300 'cpoptions' tests are flaky + 1923 9.0.0301 the message window popup is delayed after an error message + 1673 9.0.0302 CI for Coverity is bothered by deprecation warnings + 12644 9.0.0303 it is not easy to get information about a script + 4880 9.0.0304 WinScrolled is not triggered when only skipcol changes + 1864 9.0.0305 CI lists useless deprecation warnings + 3492 9.0.0306 buffer write message is two lines in message popup window + 5221 9.0.0307 :echomsg doesn't work properly with cmdheight=0 + 2493 9.0.0308 when cmdheight is zero the attention prompt doesn't show + 2070 9.0.0309 invalid memory access when cmdheight is zero + 2186 9.0.0310 output of :messages dissappears when cmdheight is zero + 1495 9.0.0311 test for hit-Enter prompt fails + 1458 9.0.0312 test for cmdheight zero fails + 20026 9.0.0313 using common name in tests leads to flaky tests + 2196 9.0.0314 VDM files are not recognized + 2325 9.0.0315 shell command is displayed in message window + 4143 9.0.0316 screen flickers when 'cmdheight' is zero + 7030 9.0.0317 when updating the whole screen a popup may not be redrawn + 14668 9.0.0318 clearing screen causes flicker + 2314 9.0.0319 Godot shader files are not recognized + 7900 9.0.0320 command line type of CmdlineChange differs from getcmdtype() + 14484 9.0.0321 cannot use the message popup window directly + 2301 9.0.0322 crash when no errors and 'quickfixtextfunc' is set +121190 9.0.0323 using common name in tests leads to flaky tests + 7684 9.0.0324 MS-Windows: resolve() test fails + 2966 9.0.0325 MS-Windows: completion test fails + 2011 9.0.0326 some changes for cmdheight=0 are not needed + 8874 9.0.0327 items() does not work on a list + 9308 9.0.0328 OLD_DIGRAPHS is unused + 2410 9.0.0329 ":highlight" hangs when 'cmdheight' is zero + 2910 9.0.0330 method tests fail + 11851 9.0.0331 cannot use items() on a string + 3042 9.0.0332 overwrite check may block BufWriteCmd + 2328 9.0.0333 method test fails + 1797 9.0.0334 test does not properly clean up + 46698 9.0.0335 checks for Dictionary argument often give a vague error + 60128 9.0.0336 tests are flaky because of using a common file name + 1480 9.0.0337 flicker when resetting cmdline_row after updating the screen + 6289 9.0.0338 return value of list_append_list() not always checked + 2092 9.0.0339 no check if the return value of XChangeGC() is NULL + 38773 9.0.0340 the 'cmdheight' zero support causes too much trouble + 4041 9.0.0341 mapset() does not restore <Nop> mapping properly + 11317 9.0.0342 ":wincmd =" equalizes in two directions + 3601 9.0.0343 ColorScheme autocommand triggered when colorscheme not found + 2907 9.0.0344 MS-Windows: background color wrong in Console + 22292 9.0.0345 error message for list argument could be clearer + 4941 9.0.0346 :horizontal modifier not fully supported + 5486 9.0.0347 MS-Windows: cannot set cursor shape in Windows Terminal + 3960 9.0.0348 MS-Windows: GUI mouse move event test is flaky + 5394 9.0.0349 filetype of *.sil files not well detected + 9580 9.0.0350 :echowindow does not work in a compiled function + 4158 9.0.0351 message window may obscure the command line + 3141 9.0.0352 using :echowindow in a timer clears part of message + 1359 9.0.0353 missing entry in switch + 1768 9.0.0354 MS-Windows: starting a python server for test sometimes fails + 2781 9.0.0355 check for uppercase char in autoload name is wrong + 3771 9.0.0356 :echowindow sets the in_echowindow flag too early + 6055 9.0.0357 'linebreak' interferes with text property highlight + 4452 9.0.0358 'breakindent' does not indent non-lists + 28606 9.0.0359 error message for wrong argument type is not specific + 2741 9.0.0360 crash when invalid line number on :for is ignored + 3593 9.0.0361 removing a listener may result in a memory leak + 3554 9.0.0362 expanding ":e %" does not work for remote files +138526 9.0.0363 common names in test files causes tests to be flaky + 6137 9.0.0364 clang static analyzer gives warnings + 2234 9.0.0365 file name used in test is unusual + 4430 9.0.0366 cannot use import->Func() in lambda + 3837 9.0.0367 Coverity complains about dropping sign of character + 1418 9.0.0368 old Coverity warning for using NULL pointer + 3607 9.0.0369 a failing flaky test doesn't mention the time + 44716 9.0.0370 cleaning up afterwards can make a function messy + 1721 9.0.0371 compiler warning for uninitialized variable + 2872 9.0.0372 MS-Windows: "%T" time format does not appear to work + 2620 9.0.0373 Coverity warns for NULL check and unused return value + 4174 9.0.0374 Coverity still complains about dropping sign of character + 9141 9.0.0375 the footer feature is unused + 7546 9.0.0376 clang warns for dead assignments + 1474 9.0.0377 argument assignment does not work + 1579 9.0.0378 compiler warning for uninitialized variable + 20849 9.0.0379 cleaning up after writefile() is a hassle + 24808 9.0.0380 deleting files in tests is a hassle + 1810 9.0.0381 writefile test leaves files behind + 2314 9.0.0382 freeing the wrong string on failure + 2230 9.0.0383 Coverity complains about unused value + 2611 9.0.0384 Covertity still complains about using return value of getc() + 1839 9.0.0385 GUI: when CTRL-D is mapped in Insert mode it gets inserted + 13495 9.0.0386 some code blocks are nested too deep + 7860 9.0.0387 repeat <ScriptCmd> mapping doesn't use right script context + 19268 9.0.0388 the do_arg_all() function is too long + 2957 9.0.0389 crash when 'tagfunc' closes the window + 5208 9.0.0390 cannot use a partial with :defer + 14502 9.0.0391 using separate delete() call instead of writefile() 'D' flag + 2145 9.0.0392 inverted condition is a bit confusing + 3728 9.0.0393 signals test often fails on FreeBSD + 3364 9.0.0394 Cygwin: multibyte characters may be broken in terminal window + 1518 9.0.0395 clang warnings for function prototypes + 2583 9.0.0396 :findrepl does not escape '&' and '~' properly + 12285 9.0.0397 :defer not tested with exceptions and ":qa!" + 45368 9.0.0398 members of funccall_T are inconsistently named + 6152 9.0.0399 using :defer in expression funcref not tested + 2081 9.0.0400 GUI test sometimes hangs on CI + 3132 9.0.0401 CI uses older clang version + 2823 9.0.0402 javascript module files are not recoginzed + 2770 9.0.0403 'equalalways' may be off when 'laststatus' is zero + 3587 9.0.0404 crash when passing invalid arguments to assert_fails() + 10100 9.0.0405 arguments in a partial not used by a :def function + 6599 9.0.0406 deferred functions not invoked when partial func exits + 4141 9.0.0407 matchstr() does match column offset + 1499 9.0.0408 GUI test sometimes fails on MS-Windows + 2760 9.0.0409 #{g:x} was seen as a curly-braces expression + 1911 9.0.0410 struct member cts_lnum is unused + 16064 9.0.0411 only created files can be cleaned up with one call + 1454 9.0.0412 compiler warning for unused argument + 1981 9.0.0413 ASAN reports a memory leak + 3680 9.0.0414 matchstr() still does not match column offset + 4598 9.0.0415 on MS-Windows some tests are flaky + 3613 9.0.0416 ml_get error when appending lines in popup window + 2142 9.0.0417 Jsonnet files are not recognized + 55521 9.0.0418 manually deleting temp test files + 18265 9.0.0419 the :defer command does not check the function arguments + 1909 9.0.0420 function went missing + 5398 9.0.0421 MS-Windows makefiles are inconsistently named + 5509 9.0.0422 not enough testing of the :all command + 4742 9.0.0423 "for" and "while" not recognized after :vim9cmd and :legacy + 3382 9.0.0424 gitattributes files are not recognized + 2312 9.0.0425 autocmd test is a bit flaky on MS-Windows + 1935 9.0.0426 failed flaky tests report only start time + 7066 9.0.0427 Drupal theme files are not recognized + 8383 9.0.0428 autocmd test uses common file name + 6733 9.0.0429 not all keys are tested for the MS-Windows GUI + 10107 9.0.0430 cannot use repeat() with a blob + 2905 9.0.0431 current mode shows in message window + 4425 9.0.0432 crash when using for loop variable in closure + 2249 9.0.0433 Coverity warns for not checking allocation failure + 3938 9.0.0434 gitignore files are not recognized + 1488 9.0.0435 compiler warning for uninitialized variable + 19155 9.0.0436 CI: running tests in parallel causes flakiness + 3634 9.0.0437 no error when custom completion function returns wrong type + 24613 9.0.0438 cannot put virtual text above a line + 3606 9.0.0439 cursor wrong if inserting before line with virtual text above + 13683 9.0.0440 crash when using mkdir() with "R" flag in compiled function + 1751 9.0.0441 closure in for loop test fails on some systems + 6910 9.0.0442 virtual text "above" doesn't handel line numbers + 2761 9.0.0443 blueprint files are not recognized + 10590 9.0.0444 trying to declare g:variable gives confusing error + 20440 9.0.0445 when opening/closing window text moves up/down + 2512 9.0.0446 message window may be positioned too low + 7933 9.0.0447 using :echowin while at the hit-enter prompt causes problems + 2151 9.0.0448 SubRip files are not recognized + 14239 9.0.0449 there is no easy way to translate a key code into a string + 5741 9.0.0450 return value of argument check functions is inconsistent + 9832 9.0.0451 virtual text "above" does not work with 'nowrap' + 8727 9.0.0452 Visual highlighting extends into virtual text prop + 20323 9.0.0453 on an AZERTY keyboard digit keys get the shift modifier + 2537 9.0.0454 incorrect color for modeless selection with GTK + 7400 9.0.0455 a few problems with 'splitscroll' + 1563 9.0.0456 function called at debug prompt is also debugged + 3188 9.0.0457 substitute prompt does not highlight an empty match + 4858 9.0.0458 splitting a line with a text prop "above" moves it down + 4237 9.0.0459 Vim9: block in for loop doesn't behave like a code block + 10731 9.0.0460 loop variable can't be found + 2896 9.0.0461 'scroll' is not always updated + 1593 9.0.0462 ASAN warning for integer overflow + 2544 9.0.0463 command line test leaves directory behind + 3720 9.0.0464 with virtual text "above" indenting doesn't work well + 2960 9.0.0465 cursor moves when cmdwin is closed when 'splitscroll' is off + 8559 9.0.0466 virtual text wrong after adding line break after line + 1877 9.0.0467 build failure + 1498 9.0.0468 exectution stack underflow without the +eval feature + 3213 9.0.0469 cursor moves if cmdwin is closed when 'splitscroll' is off + 36637 9.0.0470 in :def function all closures in loop get the same variables + 2340 9.0.0471 no test for what patch 9.0.0469 fixes + 3010 9.0.0472 virtual text "below" doesn't show in list mode + 7607 9.0.0473 fullcommand() only works for the current script version + 1735 9.0.0474 fullcommand() test failure + 17026 9.0.0475 not using deferred delete in tests + 6049 9.0.0476 varargs does not work for replacement function of substitute() + 2580 9.0.0477 missing dependency may cause crashes on incomplete build + 13833 9.0.0478 test for 'splitscroll' takes too much time + 2079 9.0.0479 Valve Date Format files are not recognized + 2648 9.0.0480 cannot use a :def varargs function with substitute() + 34795 9.0.0481 in :def function all closures in loop get the same variables + 8567 9.0.0482 "g0" moves to wrong location with virtual text "above" + 2832 9.0.0483 illegal memory access when replacing in virtualedit mode + 14182 9.0.0484 in :def function all closures in loop get the same variables + 14923 9.0.0485 in :def function all closures in loop get the same variables + 4175 9.0.0486 text scrolled with 'nosplitscroll', autocmd win and help + 5318 9.0.0487 using freed memory with combination of closures + 2797 9.0.0488 cursor wrong with virtual text "above" and 'showbreak' + 4184 9.0.0489 using "end_lnum" with virtual text causes problems + 2988 9.0.0490 using freed memory with cmdwin and BufEnter autocmd +184992 9.0.0491 no good reason to build without the float feature + 1442 9.0.0492 cmdwin test fails on MS-Windows + 1424 9.0.0493 Perl test fails + 1620 9.0.0494 small build misses float function declaraitons + 2933 9.0.0495 closure doesn't work properly in nested loop + 29507 9.0.0496 no good reason to keep supporting Windows-XP + 2026 9.0.0497 LyRiCs files are not recognized + 7048 9.0.0498 various small issues + 2145 9.0.0499 in :def function list created after const is locked + 6401 9.0.0500 when quitting cmdline window with CTRL-C it remains visible + 2109 9.0.0501 warning for using uninitialized value in mouse test + 53374 9.0.0502 a closure in a nested loop in a :def function does not work + 2485 9.0.0503 build failure + 3179 9.0.0504 still a build failure + 8175 9.0.0505 various problems with 'nosplitscroll' + 2364 9.0.0506 line number argument for :badd does not work + 3311 9.0.0507 cmdline cleared when using :redrawstatus in CmdlineChanged + 3765 9.0.0508 when the channel test fails there is no clue why + 3075 9.0.0509 confusing error for "saveas" command with "nofile" buffer + 2001 9.0.0510 Chatito files are not recognized + 3877 9.0.0511 unnecessary scrolling for message of only one line + 4147 9.0.0512 cannot redraw the status lines when editing a command + 3391 9.0.0513 may not be able to use a pattern ad the debug prompt + 1945 9.0.0514 terminal test sometimes hangs + 31656 9.0.0515 virtual text highlight starts too early when 'number' is set + 16914 9.0.0516 virtual text "above" highlights gap after it + 6543 9.0.0517 when at the command line :redrawstatus does not work well + 4905 9.0.0518 virtual text highlight starts too early with 'nowrap' + 28323 9.0.0519 the win_line() function is much too long + 5674 9.0.0520 declaring a loop variable at the start of a block is clumsy + 1602 9.0.0521 compiler warns for unused argument in small version + 1572 9.0.0522 build fails on Appveyor + 1944 9.0.0523 more compiler warnings for arguments in small version + 10035 9.0.0524 build instructions for MS-Windows are outdated + 31804 9.0.0525 manually deleting temp test files + 3185 9.0.0526 MS-Windows: still some support for XP and old compilers + 3003 9.0.0527 long sign text may overflow buffer + 6979 9.0.0528 MS-Windows: no batch files for more recent MSVC versions + 1880 9.0.0529 appveyor setup contains outdated lines + 2786 9.0.0530 using freed memory when autocmd changes mark + 27822 9.0.0531 the win_line() function is much too long + 10830 9.0.0532 edit test is flaky when run under valgrind + 14739 9.0.0533 the win_line() function is much too long + 14926 9.0.0534 line number is displayed at virtual text "above" + 4280 9.0.0535 closure gets wrong value in for loop with two loop variables + 1670 9.0.0536 CI: codecov action update available + 28246 9.0.0537 the do_set() function is much too long + 23687 9.0.0538 manually deleting test temp files + 1862 9.0.0539 long message test can be flaky + 6536 9.0.0540 assigning stack variable to argument confuses Coverity + 1845 9.0.0541 terminal pwd test fails with a very long path name +381180 9.0.0542 MSVC build still has support for 2012 edition + 5607 9.0.0543 insufficient testing for assert and test functions + 3662 9.0.0544 minor issues with setting a string option + 3964 9.0.0545 when a test is slow and CI times out there is no time info + 33364 9.0.0546 supporting Ruby 1.8 makes code complicated + 2645 9.0.0547 looping over empty out_loop[] entries + 10294 9.0.0548 reduce() with a compiled lambda could be faster + 4584 9.0.0549 duplicated code in calling a :def function + 4594 9.0.0550 crash when closing a tabpage and buffer is NULL + 2356 9.0.0551 mode message is delayed when :echowin was used + 2710 9.0.0552 crash when using NUL in buffer that uses :source + 2986 9.0.0553 no error for "|" after "{" in lamda + 4521 9.0.0554 using freed memory when command follows lambda + 5644 9.0.0555 scrolling with 'nosplitscroll' in callback changing curwin + 1457 9.0.0556 leaking memory with nested functions + 3437 9.0.0557 valgrind reports possibly leaked memory + 1691 9.0.0558 Coverity warns for possibly using NULL pointer + 1885 9.0.0559 timer test may get stuck at hit-enter prompt + 10335 9.0.0560 elapsed time since testing started is not visible + 2335 9.0.0561 when a test gets stuck it just hangs forever + 1959 9.0.0562 HSL playlist files are not recognized + 2975 9.0.0563 timer_info() test fails + 5357 9.0.0564 a few tests keep failing on MacOS M1 + 1914 9.0.0565 cscope test causes problems with test timeout timer + 2312 9.0.0566 Nim files are not recognized + 4245 9.0.0567 'completeopt' "longest" is not used for complete() + 13084 9.0.0568 autocmd code is indented more than needed + 3445 9.0.0569 cannot easily get out when using "vim file | grep word" + 1749 9.0.0570 CI for Windows is still using codecov action 3.1.0 + 3247 9.0.0571 MS-Windows: CTRL-C can make Vim exit + 2549 9.0.0572 insert complete tests leave a mapping behind + 1399 9.0.0573 outdated dependencies go unnoticed + 1678 9.0.0574 timer garbage collect test hangs on Mac M1 + 3412 9.0.0575 the getchar() function behaves strangely with bracketed paste + 2292 9.0.0576 unused loop variables + 26127 9.0.0577 buffer underflow with unexpected :finally + 1393 9.0.0578 one timer test fails on Mac M1 + 7070 9.0.0579 using freed memory when 'tagfunc' wipes out buffer + 1925 9.0.0580 no CI running for MacOS on M1 + 1642 9.0.0581 adding a character for incsearch fails at end of line + 1793 9.0.0582 channel cwd test fails on Cirrus CI + 2388 9.0.0583 only recognizing .m3u8 files is inconsistent + 5103 9.0.0584 cscope test with wrong executable name fails + 1373 9.0.0585 when long message test fails the error message is not visible + 2237 9.0.0586 missing change in test + 13050 9.0.0587 Unicode tables are outdated + 1480 9.0.0588 MorphOS build is broken + 1907 9.0.0589 on AmigaOS4 the pid is available but the task address is used + 5395 9.0.0590 after exiting Insert mode spelling not checked in next line + 2596 9.0.0591 message window popup shows on only one tab page + 9411 9.0.0592 display not cleared when scrolling back in messages + 2638 9.0.0593 CI actions have too many permissions + 1617 9.0.0594 Makefile error message causes a shell error + 9695 9.0.0595 extra newline in messages after a verbose shell message + 1700 9.0.0596 CI on Mac M1 has the channel feature disabled + 2222 9.0.0597 cannot close a tab page with the middle mouse button + 2730 9.0.0598 using negative array index with negative width window + 2364 9.0.0599 latexmkrc files are not recognized + 1970 9.0.0600 GYP files are not recognized + 16421 9.0.0601 too much indent + 3714 9.0.0602 new TypeScript extensions are not recognized + 17743 9.0.0603 with 'nosplitscroll' folds are not handled correctly + 2210 9.0.0604 luacheckrc file is not recognized + 2210 9.0.0605 dump file missing + 1926 9.0.0606 system() opens a terminal window when "!" is in 'guioptions' + 2482 9.0.0607 verbose echo message test fails on Mac OS + 5539 9.0.0608 with spelling, deleting a full stop does not update next line + 2463 9.0.0609 blockedit test fails because of wrong indent + 2615 9.0.0610 global interrupt test fails when run under valgrind + 38835 9.0.0611 tests delete files with a separate delete() call + 3632 9.0.0612 blockedit test passes with wrong result + 6924 9.0.0613 running source tests leaves file behind + 3093 9.0.0614 SpellFileMissing autocmd may delete buffer + 6698 9.0.0615 using reduce() on a list from range() is a bit slow + 1666 9.0.0616 spell test fails because error message changed + 4125 9.0.0617 calling function for reduce() has too much overhead + 18102 9.0.0618 calling function for reduce() has too much overhead + 21042 9.0.0619 too many delete() calls in tests + 31200 9.0.0620 matchaddpos() can only add up to 8 matches + 1599 9.0.0621 filetype test leaves file behind + 7942 9.0.0622 matchaddpos() can get slow when adding many matches + 29942 9.0.0623 error for modifying a const is not detected at compile time + 1659 9.0.0624 leaking argument type array + 25852 9.0.0625 too many delete() calls in tests + 34764 9.0.0626 too many delete() calls in tests + 9737 9.0.0627 "const" and "final" both make the type a constant + 2159 9.0.0628 Coverity warns for not checking return value + 15922 9.0.0629 get an error for using const only when executing + 2659 9.0.0630 in Vim9 script a numbered function cannot be called + 70969 9.0.0631 too many delete() calls in tests + 12167 9.0.0632 calling a function from an "expr" option has overhead + 1584 9.0.0633 FEAT_TITLE was removed but is still used + 34670 9.0.0634 evaluating "expr" options has more overhead than needed + 2376 9.0.0635 build error and compiler warnings + 2507 9.0.0636 underline color may not work in some terminals + 8394 9.0.0637 syntax of commands in Vim9 script depends on +eval feature + 10454 9.0.0638 popup menu highlight wrong on top of preview popup + 6591 9.0.0639 checking for popup in screen_char() is too late + 24804 9.0.0640 cannot scroll by screen line if a line wraps + 1285 9.0.0641 missing part of the new option code + 1777 9.0.0642 breakindent test fails + 1759 9.0.0643 smoothscroll test fails + 5141 9.0.0644 'smoothscroll' is not copied to a new window on :split + 2747 9.0.0645 CTRL-Y does not stop at line 1 + 7806 9.0.0646 with 'smoothscroll' CTRL-E is wrong when 'foldmethod' set + 50958 9.0.0647 the 'splitscroll' option is not a good name + 7514 9.0.0648 when using powershell input redirection does not work + 6670 9.0.0649 no indication the first line is broken for 'smoothscroll' + 8417 9.0.0650 some tests are failing + 1521 9.0.0651 build fails without the +conceal feature + 10143 9.0.0652 'smoothscroll' not tested with 'number' and "n" in 'cpo' + 3528 9.0.0653 BS and DEL do not work properly in an interacive shell + 2094 9.0.0654 breakindent test fails + 4830 9.0.0655 passing modifier codes to a shell running in the GUI + 17786 9.0.0656 cannot specify another character to use instead of '@' + 73298 9.0.0657 too many #ifdefs + 1504 9.0.0658 tiny build fails on Mac OS + 1757 9.0.0659 wrong type of comment in SetSyn() function + 2422 9.0.0660 mapping with CTRL keys does not work in the GUI + 4452 9.0.0661 multi-byte "lastline" in 'fillchars' does not work properly + 3664 9.0.0662 concealed characters do not work correctly + 4694 9.0.0663 tests check for +cmdwin feature which is always present + 6316 9.0.0664 bad redrawing with spell checking, using "C" and "$" in 'cpo' + 4408 9.0.0665 setting 'cmdheight' has no effect if last window was resized + 13734 9.0.0666 spacing-combining characters handled as composing + 2575 9.0.0667 ml_get error when 'splitkeep' is "screen" + 2139 9.0.0668 CI on Mac M1 only uses clang + 43322 9.0.0669 too many delete() calls in tests + 4492 9.0.0670 no space for command line when there is a tabline + 7090 9.0.0671 negative topline using CTRL-Y with 'smoothscroll' and 'diff' + 6788 9.0.0672 line partly shows with 'smoothscroll' and 'scrolloff' zero + 4657 9.0.0673 first line wong with 'smoothscroll' and 'scrolloff' zero + 1600 9.0.0674 build error with tiny version + 2009 9.0.0675 search test screendump is outdated + 2574 9.0.0676 CI on Mac M1 with gcc actually uses clang + 4766 9.0.0677 breakindent test accepts wrong result + 8428 9.0.0678 using exclamation marks on :function + 2261 9.0.0679 tests failing with 'smoothscroll', 'number' and "n" in 'cpo' + 2219 9.0.0680 tests failing with 'breakindent', 'number' and "n" in 'cpo' + 3259 9.0.0681 "<<<" shows for 'smoothscroll' even when 'showbreak is set + 4054 9.0.0682 crash when popup with deleted timer is closed + 22129 9.0.0683 cannot specify a time for :echowindow + 2037 9.0.0684 skipped :exe command fails compilation on MS-Windows + 2316 9.0.0685 FORTIFY_SOURCE causes a crash in Vim9 script + 1857 9.0.0686 the right ALT key does not work on some MS-Windows keyboards + 12188 9.0.0687 "export def" does not work in a nested block + 2505 9.0.0688 debugger does not display the whole command + 1581 9.0.0689 compiler warning for unused function + 2020 9.0.0690 buffer size for expanding tab not correctly computed + 4206 9.0.0691 lalloc(0) error in listchars test + 1963 9.0.0692 PoE filter files are not recognized + 1841 9.0.0693 browse() first argument cannot be a bool + 17159 9.0.0694 no native sound support on Mac OS + 2759 9.0.0695 failing check for dictionary type for const any + 1754 9.0.0696 it is unclear if the +rightleft and +arabic features are used + 11218 9.0.0697 cursor in wrong position with Visual substitute +185711 9.0.0698 VisVim is outdated, does not work with current Visual Studio + 1443 9.0.0699 tiny build fails + 33631 9.0.0700 there is no real need for a "big" build + 8331 9.0.0701 with 'smoothscroll' cursor position not adjusted in long line + 5538 9.0.0702 incomplete testing cursor position with 'linebreak' set + 24166 9.0.0703 failing check for argument type for const any + 2348 9.0.0704 CI runs "tiny" and "small" builds, which are the same + 4892 9.0.0705 virtual text truncation does not take padding into account + 1555 9.0.0706 :help in a narrow window always opens at the top + 8191 9.0.0707 with 'smoothscroll' cursor position not adjusted in long line + 15032 9.0.0708 :confirm does not work properly for a terminal buffer + 8523 9.0.0709 virtual text "after" not correct with 'nowrap' + 6676 9.0.0710 quitting/unloading/hiding a terminal does not work properly + 2119 9.0.0711 SubStation Alpha files are not recognized + 6563 9.0.0712 wrong column when calling setcursorcharpos() with zero lnum + 2735 9.0.0713 <amatch> of MenuPopup event is expanded like a file name + 5862 9.0.0714 with 'nowrap' two virtual text below not displayed correctly + 2327 9.0.0715 wrong argument for append() gives two error messages + 10149 9.0.0716 with 'nowrap' virtual text "after" does not scroll left + 2222 9.0.0717 compiler warning for unused variable in tiny build + 3645 9.0.0718 extra empty line between two virtual text "below" + 93680 9.0.0719 too many delete() calls in tests + 3255 9.0.0720 MS-Windows GUI may have pixel dust from antialiasing + 4965 9.0.0721 virtual text "above" with padding not displayed correctly + 5794 9.0.0722 virtual text "after" does not show with 'list' set + 3699 9.0.0723 extra empty line below virtual text when 'list' is set + 7387 9.0.0724 closure in compiled function gets same variable in block + 4585 9.0.0725 virtual text "after" wraps to next line when 'wrap' is off + 2940 9.0.0726 looping over list of lists works in script, not in function + 72218 9.0.0727 help in the repository differs from patched version too much + 2036 9.0.0728 extend() test fails + 3036 9.0.0729 the rightleft and arabic features are disabled + 1905 9.0.0730 startup test fails with right-left feature + 2303 9.0.0731 clang-tidy configuration files are not recognized + 3043 9.0.0732 no check for white space before and after "=<<" + 4948 9.0.0733 use of strftime() is not safe + 11913 9.0.0734 cursor position invalid when scrolling with 'smoothscroll' + 2324 9.0.0735 breakindent and scrolloff tests fail + 14099 9.0.0736 quickfix listing does not handle very long messages + 9733 9.0.0737 Lisp word only recognized when a space follows + 5701 9.0.0738 cannot suppress completion "scanning" messages + 6502 9.0.0739 mouse column not correctly used for popup_setpos + 3974 9.0.0740 prop_add_list() gives multiple errors for invalid argument + 5709 9.0.0741 cannot specify an ID for each item with prop_add_list() + 8373 9.0.0742 reading past end of the line when compiling a function + 1968 9.0.0743 starting cscope on Unix does not quote the arguments right + 3923 9.0.0744 in script in autoload dir exported variable is not found + 7523 9.0.0745 wrong cursor position when using "gj" and "gk" in a long line + 12953 9.0.0746 breakindent test cases are commented out + 36080 9.0.0747 too many #ifdefs + 5454 9.0.0748 Kitty may send key without modifiers with CSI u code + 10870 9.0.0749 alloc/free of buffer for each quickfix entry is inefficient + 4024 9.0.0750 crash when popup closed in callback + 14245 9.0.0751 'scrolloff' does not work well with 'smoothscroll' + 2995 9.0.0752 Rprofile files are not recognized + 6086 9.0.0753 some Ex commands are not in the help index + 2715 9.0.0754 'indentexpr' overrules lisp indenting in one situation + 1820 9.0.0755 huge build on macos always fails on CI + 5798 9.0.0756 no autocmd event for changing text in a terminal window + 4321 9.0.0757 line number not visisble with 'smoothscroll', 'nu' and 'rnu' + 4353 9.0.0758 "precedes" from 'listchars' overwritten by <<< + 1852 9.0.0759 huge build on macos does not use Perl + 1807 9.0.0760 display test for 'listchars' "precedes" fails + 12998 9.0.0761 cannot use 'indentexpr' for Lisp indenting + 1514 9.0.0762 build failure + 1441 9.0.0763 MS-Windows: warning for using int for size_t + 2328 9.0.0764 indent and option tests fail + 2356 9.0.0765 with a Visual block a put command column may go negative + 66370 9.0.0766 too many delete() calls in tests + 84754 9.0.0767 too many delete() calls in tests + 30413 9.0.0768 too many delete() calls in tests + 19609 9.0.0769 too many delete() calls in tests + 2778 9.0.0770 quickfix commands may keep memory allocated + 2031 9.0.0771 cannot always tell the difference beween tex and rexx files + 29673 9.0.0772 the libvterm code is outdated + 2153 9.0.0773 huge build on macos uses dynamic Perl + 82901 9.0.0774 the libvterm code is outdated + 13727 9.0.0775 MS-Windows: mouse scrolling not supported in the console + 13452 9.0.0776 MSVC can't have field name "small" + 22669 9.0.0777 code is indented too much + 4584 9.0.0778 indexing of unknown const type fails during compilation + 5256 9.0.0779 lsl and lm3 file extensions are not recognized + 1999 9.0.0780 'scroll' value computed in unexpected location + 13795 9.0.0781 workaround to rename "small" to "smallfont" is clumsy + 2298 9.0.0782 OpenVPN files are not recognized + 4194 9.0.0783 ":!" doesn't do anything but does update the previous command + 5943 9.0.0784 text prop "above" not right with 'number' and "n" in 'cpo' + 1552 9.0.0785 memory leak with empty shell command + 2750 9.0.0786 user command does not get number from :tab modifier + 2163 9.0.0787 mouse scrolling in terminal misbehaves without dll + 2887 9.0.0788 ModeChanged autocmd not executed when Visual ends with CTRL-C + 2449 9.0.0789 dummy buffer ends up in a window + 1801 9.0.0790 test for dummy buffer does not always produce the E86 error + 4171 9.0.0791 at the hit-Enter prompt the End and Home keys may not work + 2031 9.0.0792 MS-Windows: compiler complains about unused function + 4958 9.0.0793 MS-Windows: mouse scroll events only work with the dll + 7012 9.0.0794 there is no way to find out if modifyOtherKeys has been seen + 11700 9.0.0795 readblob() always reads the whole file + 2290 9.0.0796 mapping test fails in some situations + 3480 9.0.0797 order of assert function arguments is reverted + 2296 9.0.0798 clang format configuration files are not recognized + 3071 9.0.0799 in compiled function ->() on next line not recognized + 1366 9.0.0800 compiler complains about repeated typedef + 2075 9.0.0801 the modifyOtherKeys flag is set when it should not + 3737 9.0.0802 MS-Windows: cannot map console mouse scroll events + 4453 9.0.0803 readblob() cannot read from character device + 2833 9.0.0804 crash when trying to divide a number by -1 + 2483 9.0.0805 filetype autocmd may cause freed memory access + 4065 9.0.0806 'langmap' works differently when there are modifiers + 6922 9.0.0807 with 'smoothscroll' typing "0" may not go to the first column + 2800 9.0.0808 jsonnet filetype detection has a typo + 1995 9.0.0809 test for job writing to buffer fails + 4716 9.0.0810 readblob() returns empty when trying to read too much + 2291 9.0.0811 error if :echowin is preceded by a command modifier + 2382 9.0.0812 GUI mouse scrollwheel mappings don't work + 9540 9.0.0813 Kitty terminal is not recognized + 2981 9.0.0814 aws config files are not recognized + 477 9.0.0815 ":!" does not switch to the alternate screen + 7365 9.0.0816 CTRL-Z at end of file is always dropped + 346 9.0.0817 build error + 365 9.0.0818 "!ls" does not work + 5613 9.0.0819 still a build error, tests are failing + 2542 9.0.0820 memory leak with empty shell command + 3493 9.0.0821 crash when using win_move_statusline() in another tab page + 6795 9.0.0822 crash when dragging the statusline with a mapping + 3461 9.0.0823 mouse drag test fails + 4296 9.0.0824 crash when using win_move_separator() in other tab page + 9381 9.0.0825 cannot drag an entry in the tabpage line + 10599 9.0.0826 if 'endofline' is set CTRL-Z may be written in a wrong place + 1815 9.0.0827 <Home> key in tmux doesn't work when 'term' set to "xterm" + 53763 9.0.0828 various typos + 1648 9.0.0829 wrong counts in macro comment + 1541 9.0.0830 compiling with Perl on Mac 12 fails + 1392 9.0.0831 compiler warning for redefining HAVE_DUP + 1545 9.0.0832 deprecation warning causes build failure + 1621 9.0.0833 Mac: no +sound feature in huge build + 2056 9.0.0834 warning for missing return type + 2709 9.0.0835 the window title is not redrawn when 'endoffile' changes + 5620 9.0.0836 wrong error when using extend() with funcref + 9800 9.0.0837 append() reports failure when not appending anything + 3775 9.0.0838 compiler warnings for unused variables + 1682 9.0.0839 test may fail depending on sequence of events + 2437 9.0.0840 cannot change a slice of a const list + 4209 9.0.0841 deletebufline() does not always return 1 on failure + 2874 9.0.0842 Unicode range for Apple SF symbols is outdated + 2372 9.0.0843 VHS tape files are not recognized + 14682 9.0.0844 handling 'statusline' errors is spread out + 3536 9.0.0845 shell command with just space gives strange error + 2953 9.0.0846 using assert_fails() may cause hit-enter prompt + 2615 9.0.0847 CI: not totally clear what MS-Windows version is used + 1774 9.0.0848 help item for --log argument is not aligned nicely + 9217 9.0.0849 terminal mouse test is a bit flaky + 19592 9.0.0850 MS-Windows Terminal has unstable color control + 1702 9.0.0851 terminal mouse test is still flaky + 2945 9.0.0852 crypt test is skipped if xxd is not found + 6039 9.0.0853 terminal mouse test is still flaky on MacOS M1 + 2438 9.0.0854 no proper test for what 9.0.0846 fixes + 1610 9.0.0855 comment not located above the code it refers to + 3488 9.0.0856 MS-Windows: executable not found when running test + 1748 9.0.0857 selecting MSVC 2017 does not set $PLATFORM + 4357 9.0.0858 "!!sort" in a closed fold sorts too many lines + 1452 9.0.0859 compiler warning for unused variable + 1447 9.0.0860 MS-Windows: windres fails with clang 15.0.4 + 9023 9.0.0861 solution for "!!sort" in closed fold is not optimal + 3334 9.0.0862 default value of 'endoffile' is wrong + 15740 9.0.0863 col() and charcol() only work for the current window + 3370 9.0.0864 crash when using "!!" without a previous shell command + 3418 9.0.0865 duplicate arguments are not always detected + 2288 9.0.0866 no test for what patch 8.2.2207 fixes + 17133 9.0.0867 wildmenu redrawing code is spread out + 6919 9.0.0868 MS-Windows: after Vim exits console resizing problem + 2773 9.0.0869 bogus error when string used after :elseif + 3172 9.0.0870 get E967 when using text property in quickfix window + 4228 9.0.0871 using freed memory when clearing augroup at more prompt + 8665 9.0.0872 code is indented more than needed + 4999 9.0.0873 using freed memory when executing mapclear at more prompt + 4581 9.0.0874 using freed memory when executing unmenu at more prompt + 6267 9.0.0875 using freed memory when executing delfunc at more prompt + 8530 9.0.0876 code is indented more than needed + 5872 9.0.0877 using freed memory with :comclear while listing commands + 1823 9.0.0878 Coverity warns for dead code + 1618 9.0.0879 unnecessary nesting in makefile + 12543 9.0.0880 preprocessor indenting is off + 8313 9.0.0881 cannot get the currently showing mouse shape + 2517 9.0.0882 using freed memory after SpellFileMissing autocmd uses bwipe + 2477 9.0.0883 a silent mapping may cause dots on the command line + 3820 9.0.0884 mouse shape remains in op-pending mode after failed change + 2032 9.0.0885 informational message has an error message number + 20507 9.0.0886 horizontal mouse scroll only works in the GUI + 10111 9.0.0887 cannot easily try out what codes various keys produce + 2707 9.0.0888 MS-Windows GUI: CTRL-] does not work on Swiss keyboard + 14964 9.0.0889 keycode check script has a few flaws + 4277 9.0.0890 no test for what patch 9.0.0827 fixes + 13194 9.0.0891 virtual text below after match has wrong highlight + 5879 9.0.0892 may redraw when not needed + 5729 9.0.0893 'smoothscroll' cursor calculations wrong when 'number' is set + 5100 9.0.0894 virtual text property highlight ignores window background + 1676 9.0.0895 file renamed twice in test, missing feature check + 3371 9.0.0896 test for home key fails when 'term' is "tmux" + 2303 9.0.0897 Clinical Quality Language files are not recognized + 4074 9.0.0898 with 'smoothscroll' cursor is one screen line too far down + 42751 9.0.0899 the builtin terminals are in one long list + 14743 9.0.0900 cursor moves too far with 'smoothscroll' + 7730 9.0.0901 setting w_leftcol and handling side effects is confusing + 30317 9.0.0902 some mouse scroll code is not in a good place + 10000 9.0.0903 key code checker doesn't check modifyOtherKeys resource + 16523 9.0.0904 various comment and indent flaws + 3684 9.0.0905 virtual text after the line wraps when 'wrap' is off + 10218 9.0.0906 mouse scroll code is not optimal + 8219 9.0.0907 restoring window after WinScrolled may fail + 14961 9.0.0908 with 'smoothscroll' cursor may end up in wrong position + 7001 9.0.0909 error message for layout change does not match action + 3574 9.0.0910 setting lines in another buffer may not work well + 5547 9.0.0911 with 'smoothscroll' set mouse click position may be wrong + 11512 9.0.0912 libvterm with modifyOtherKeys level 2 does not match xterm + 10168 9.0.0913 only change in current window triggers the WinScrolled event + 8339 9.0.0914 deletebufline() may move marks in the wrong window + 8232 9.0.0915 WinScrolled may trigger immediately when defined + 9192 9.0.0916 getbufline() is inefficient for getting a single line + 31022 9.0.0917 the WinScrolled autocommand event is not enough + 5015 9.0.0918 MS-Windows: modifier keys do not work with mouse scroll event + 6721 9.0.0919 build failure with tiny features + 2710 9.0.0920 cannot find an import prefixed with "s:" + 5975 9.0.0921 missing defined(PROTO) in #ifdef + 2486 9.0.0922 Mermaid files are not recognized + 3691 9.0.0923 second SIGWINCH signal may be ignored + 1651 9.0.0924 the first termcap entry of a builtin termcap is not used + 8191 9.0.0925 two conditions are always false + 1677 9.0.0926 Coverity warns for not using return value of dict_add() + 1517 9.0.0927 Coverity warns for using a NULL pointer + 3320 9.0.0928 using Ruby LDFLAGS may cause build problems + 1501 9.0.0929 build failure with tiny version + 37601 9.0.0930 cannot debug the Kitty keyboard protocol with TermDebug + 4393 9.0.0931 MS-Windows: mouse column limited to 223 + 2305 9.0.0932 Oblivion files are not recognized + 1627 9.0.0933 Kitty shows "already at oldest change" on startup + 8116 9.0.0934 various code formatting issues + 3075 9.0.0935 when using dash it may not be recognize as filetype "sh" + 2244 9.0.0936 wrong type for "isunnamed" returned by getreginfo() + 3439 9.0.0937 forked repositories send out useless email + 1489 9.0.0938 MS-Windows: debug executable not found when running test + 9897 9.0.0939 still using simplified mappings when using kitty protocol + 2690 9.0.0940 crash when typing a letter in a terminal window + 2674 9.0.0941 CI failures in sound dummy + 2037 9.0.0942 Workflow Description Language files are not recognized + 2694 9.0.0943 pretending to go out of Insert mode when Esc is received + 7508 9.0.0944 'cursorline' causes virtual text highlight to continue + 2565 9.0.0945 failures in the cursorline test + 4904 9.0.0946 CI: Error in Coverity flow is not reported + 5009 9.0.0947 invalid memory access in substitute with function + 8713 9.0.0948 'ttyfast' is set for arbitrary terminals + 34680 9.0.0949 crash when unletting a variable while listing variables + 6732 9.0.0950 the pattern "\_s\zs" matches at EOL + 5462 9.0.0951 trying every character position for a match is inefficient + 2937 9.0.0952 Eclipse preference files are not recognized + 1901 9.0.0953 part of making search more efficient is missing + 34769 9.0.0954 cannot detect whether modifyOtherKeys is enabled + 12644 9.0.0955 libvterm does not support the XTQMODKEYS request + 5568 9.0.0956 terminal tests fail when using key with modifier + 4513 9.0.0957 tests fail without the terminal feature + 3700 9.0.0958 messages test is flaky + 1712 9.0.0959 error when using the "File Settings / Text Width" menu + 2915 9.0.0960 error when using the "Spelling / Find More Languages" menu + 2537 9.0.0961 using deletebufline() may jump to another window + 5562 9.0.0962 virtual text below cannot be placed below empty lines + 4144 9.0.0963 function name does not match autocmd event name + 3220 9.0.0964 status line not redrawn when 'splitkeep' is "screen" + 55529 9.0.0965 using one window for executing autocommands is insufficient + 1810 9.0.0966 some compilers don't allow a declaration after a label + 6928 9.0.0967 leaking memory from autocmd windows + 3429 9.0.0968 GUI mouse event test is a bit flaky + 4950 9.0.0969 matchparen highlight is not updated when switching buffers + 1579 9.0.0970 Coverity warns for uninitialized variable + 8206 9.0.0971 escape sequences not recognized without termresponse feature + 13919 9.0.0972 build failure on some systems + 3912 9.0.0973 Kitty keyboard protocol key with NumLock not decoded + 4608 9.0.0974 even when Esc is encoded a timeout is used + 3196 9.0.0975 virtual text below empty line misplaced when 'number' set + 4061 9.0.0976 enabling the kitty keyboard protocol uses push/pop + 44129 9.0.0977 it is not easy to see what client-server commands are doing + 5428 9.0.0978 build errors without the +channel feature + 2949 9.0.0979 ch_log() text can be hard to find in the log file + 17841 9.0.0980 the keyboard state response may end up in a shell command + 1329 9.0.0981 build error in tiny version + 15447 9.0.0982 'cursorline' not drawn before virtual text below + 1562 9.0.0983 stray characters displayed when starting the GUI + 2477 9.0.0984 GUI: remote_foreground() does not always work + 16603 9.0.0985 when using kitty keyboard protocol function keys may not work + 1738 9.0.0986 build failure with tiny version + 1441 9.0.0987 file missing from list of distributed files + 4902 9.0.0988 using feedkeys() does not show up in a channel log + 2343 9.0.0989 popupwin test is more flaky on MacOS + 10013 9.0.0990 callback name argument is changed by setqflist() + 4158 9.0.0991 crash when reading help index with various options set + 2255 9.0.0992 Vim9 script: get E1096 when comment follows return + 14593 9.0.0993 display errors when adding or removing text property type + 3825 9.0.0994 tests for empty prop type name fail + 9164 9.0.0995 padding before virtual text is highlighted + 1984 9.0.0996 if 'keyprotocol' is empty "xterm" still uses modifyOtherKeys + 1654 9.0.0997 Coverity warns for dead code + 4856 9.0.0998 "gk" may reset skipcol when not needed + 1422 9.0.0999 memory may leak + 3551 9.0.1000 with 'smoothscroll' skipcol may be reset unnecessarily + 52789 9.0.1001 classes are not documented or implemented yet + 1477 9.0.1002 command list test fails + 1523 9.0.1003 tiny build fails + 1945 9.0.1004 suspend test sometimes fails on MacOS + 8662 9.0.1005 a failed test may leave a swap file behind + 2002 9.0.1006 suspend test still sometimes fails on MacOS + 21303 9.0.1007 there is no way to get a list of swap file names + 2777 9.0.1008 test for swapfilelist() fails on MS-Windows + 1444 9.0.1009 test for catch after interrupt is flaky on MS-Windows + 2549 9.0.1010 stray warnings for existing swap files + 2140 9.0.1011 ml_get error when using screenpos() + 1918 9.0.1012 tests may get stuck in buffer with swap file + 2408 9.0.1013 suspend test often fails on Mac OS + 2658 9.0.1014 zir files are not recognized + 2972 9.0.1015 without /dev/urandom srand() seed is too predictable + 2226 9.0.1016 screenpos() does not count filler lines for diff mode + 2310 9.0.1017 test for srand() fails on MS-Windows + 2181 9.0.1018 suspend test still fails on Mac OS + 20179 9.0.1019 'smoothscroll' and virtual text above don't work together + 1900 9.0.1020 tests call GetSwapFileList() before it is defined + 1317 9.0.1021 test trips over g:name + 2610 9.0.1022 suspend test fails on Mac OS when suspending Vim + 5046 9.0.1023 MS-Windows: dynamic loading of libsodium doesn't work + 1694 9.0.1024 CI doesn't use the latest FreeBSD version + 12645 9.0.1025 WinScrolled is not triggered when filler lines change + 2041 9.0.1026 type of w_last_topfill is wrong + 1640 9.0.1027 LGTM is soon shutting down + 9473 9.0.1028 mouse shape test is flaky, especially on Mac OS + 1500 9.0.1029 autoload directory missing from distribution + 5547 9.0.1030 using freed memory with the cmdline popup menu + 68685 9.0.1031 Vim9 class is not implemented yet + 1387 9.0.1032 test fails when terminal feature is missing + 1525 9.0.1033 tiny build fails because of conflicting typedef + 1568 9.0.1034 reporting swap file when windows are split + 19685 9.0.1035 object members are not being marked as used + 4742 9.0.1036 undo misbehaves when writing from an insert mode mapping + 2427 9.0.1037 lalloc(0) error for a class without members + 4091 9.0.1038 function name does not match what it is used for + 4861 9.0.1039 using a <Cmd> mapping CmdlineChanged may be triggered twice + 2367 9.0.1040 test for <Cmd> mapping with CmdlineChanged fails + 34754 9.0.1041 cannot define a method in a class + 1969 9.0.1042 ASAN gives false alarm about array access. + 6350 9.0.1043 macro has confusing name and is duplicated + 2716 9.0.1044 setting window height using Python may cause errors + 24554 9.0.1045 in a class object members cannot be initialized + 1741 9.0.1046 class method disassemble test fails on MS-Windows + 4885 9.0.1047 matchparen is slow + 7613 9.0.1048 with "screenline" in 'culopt' cursorline highlight is wrong + 2118 9.0.1049 crash when opening a very small terminal window + 2916 9.0.1050 using freed memory when assigning to variable twice + 2594 9.0.1051 after a failed CTRL-W ] next command splits window + 3901 9.0.1052 using freed memory on exit when EXITFREE is defined + 22945 9.0.1053 default constructor arguments are not optional + 8623 9.0.1054 object member can't get type from initializer + 1686 9.0.1055 Coverity warns for using uninitialized memory + 4841 9.0.1056 leaking memory when disassembling an object method + 2955 9.0.1057 conflict between supercollider and scala filetype detection + 4005 9.0.1058 string value of class and object do not have information + 3186 9.0.1059 build failure with some compilers + 10743 9.0.1060 private and public object members are not implemented yet + 16670 9.0.1061 cannot display 'showcmd' somewhere else + 4285 9.0.1062 some test function names do not match what they are doing + 2432 9.0.1063 when using Kitty a shell command may mess up the key state + 8990 9.0.1064 code for making 'shortmess' temporarily empty is repeated + 8027 9.0.1065 a shell command switching screens may still have a problem + 2169 9.0.1066 test function name is wrong + 6283 9.0.1067 in diff mode virtual text is highlighted incorrectly + 4244 9.0.1068 no information about whether request term codes has an effect + 2031 9.0.1069 diff mode highlight fails for special characters + 3370 9.0.1070 reading beyond array size + 2461 9.0.1071 Codecov action version is too specific + 3493 9.0.1072 screenpos() column result in fold may be too small + 5765 9.0.1073 using "xterm-kitty" for 'term' causes problems + 52002 9.0.1074 class members are not supported yet + 3542 9.0.1075 build fails if compiler doesn't allow declaration after case + 2010 9.0.1076 ASAN complains about NULL argument + 7282 9.0.1077 can add text property with negative ID before virtual text + 2573 9.0.1078 with the +vartabs feature indent folding may use wrong 'ts' + 3826 9.0.1079 leaking memory when defining a user command fails + 6684 9.0.1080 the "kitty" terminfo entry is not widespread + 4099 9.0.1081 using "->" with split lines does not always work + 4099 9.0.1082 some jsonc files are not recognized + 2369 9.0.1083 empty and comment lines in a class cause an error + 72522 9.0.1084 code handling low level MS-Windows events cannot be tested + 2473 9.0.1085 compiler warns for uninitialized variable + 4073 9.0.1086 display wrong in Windows terminal after exiting Vim + 1624 9.0.1087 autocommand test sometimes fails + 1825 9.0.1088 clang warns for unused variable + 1404 9.0.1089 unnessary assignment + 2015 9.0.1090 FHIR Shorthand files are not recognized + 3245 9.0.1091 assignment to non-existing member causes a crash + 7222 9.0.1092 search error message doesn't show used pattern + 3186 9.0.1093 using freed memory of object member + 1523 9.0.1094 compiler warning when HAS_MESSAGE_WINDOW is not defined + 2329 9.0.1095 using freed memory when declaration fails + 1435 9.0.1096 reallocating hashtab when the size didn't change + 1787 9.0.1097 tests are failing + 18179 9.0.1098 code uses too much indent + 1825 9.0.1099 trying to resize a hashtab may cause a problem + 2890 9.0.1100 a hashtab with many removed items is not cleaned up + 1707 9.0.1101 unused global variable + 1698 9.0.1102 complicated use of #ifdef + 2075 9.0.1103 jq files are not recognized + 2550 9.0.1104 invalid memory access when checking function argument types + 14738 9.0.1105 code is indented too much + 2861 9.0.1106 not all postfix files are recognized + 2740 9.0.1107 float constant not recognized as float + 26788 9.0.1108 type error when using "any" type and adding to float + 1426 9.0.1109 leaking allocated type + 3121 9.0.1110 build fails on Mac OS X 10.4/10.5 + 4520 9.0.1111 termcap entries for RGB colors are not set automatically + 40649 9.0.1112 test_mswin_event() can hang + 1553 9.0.1113 users cannot easily try out a PR + 1892 9.0.1114 CI does not use the latest Python version + 28319 9.0.1115 code is indented more than needed + 1557 9.0.1116 compiler may complain about an unused function + 3951 9.0.1117 terminfo entries for bracketed paste are not used + 2668 9.0.1118 sporadic test failures when using a terminal window + 5133 9.0.1119 type of arguments not checked when calling a partial + 2644 9.0.1120 tex filetype detection not sufficiently tested + 17738 9.0.1121 cursor positioning and display problems with 'smoothscroll' + 2336 9.0.1122 class member access is not fully tested yet + 15554 9.0.1123 class function not implemented yet + 3479 9.0.1124 virtual text at a column position is truncated + 1686 9.0.1125 memory leak when using class functions + 9363 9.0.1126 bracketed paste can be enabled when it is not recognized + 10202 9.0.1127 no error if function argument shadows class member + 2686 9.0.1128 build failure + 2633 9.0.1129 sporadic Test_range() failure + 5538 9.0.1130 unexpected output when autoloading a script + 2614 9.0.1131 build failure without the +eval feature + 52006 9.0.1132 code is indented more than needed + 28798 9.0.1133 error message names do not match the items + 12691 9.0.1134 comparing objects uses identity instead of equality + 1857 9.0.1135 missing function argument + 1458 9.0.1136 memory leak when getting class member type from expr + 2357 9.0.1137 some conditions are always false + 3384 9.0.1138 crash when expecting varargs but it is something else + 4762 9.0.1139 cannot create a new object in a compiled function + 10405 9.0.1140 cannot call an object method in a compiled function + 4701 9.0.1141 'cursorcolumn' and 'colorcolumn' wrong after concealing + 3603 9.0.1142 crash and/or memory leak when redefining function + 2094 9.0.1143 invalid memory access with bad 'statusline' value + 3839 9.0.1144 reading beyond text + 2220 9.0.1145 invalid memory access with recursive substitute expression + 18651 9.0.1146 MS-Windows: various special keys/modifiers are not mappable + 4227 9.0.1147 cannot access a class member in a compiled function + 1500 9.0.1148 cmdline test fails in the GUI + 3523 9.0.1149 class members may be garbage collected + 22923 9.0.1150 :interface is not implemented yet + 2109 9.0.1151 build failure + 14924 9.0.1152 class "implements" argument not implemented + 1689 9.0.1153 build error with some compilers + 1817 9.0.1154 Coverity warns for dead code + 3352 9.0.1155 cannot use a class as a type + 1722 9.0.1156 tests fail because of a different error message + 5132 9.0.1157 "implements" only handles one interface name +104529 9.0.1158 code is indented more than necessary + 16298 9.0.1159 extends argument for class not implemented yet + 4261 9.0.1160 ASAN error for ufunc_T allocated with wrong size + 2073 9.0.1161 Coverity warns for using strcpy() + 4487 9.0.1162 configure does not handle all FORTIFY_SOURCE variants + 1876 9.0.1163 compiler warning for implicit size_t/int conversion + 2357 9.0.1164 evaluating string expression advances function line + 7132 9.0.1165 tests using IPv6 sometimes fail + 71279 9.0.1166 code is indented more than necessary + 3586 9.0.1167 EditorConfig files do not have their own filetype + 8422 9.0.1168 code to enable/disable mouse is not from terminfo/termcap + 25135 9.0.1169 some key+modifier tests fail on some AppVeyor images + 4834 9.0.1170 LGTM badge no longer works + 3512 9.0.1171 screen is not redrawn after using setcellwidths() + 2386 9.0.1172 when 'selection' is "exclusive" then "1v" is one char short + 1659 9.0.1173 compiler warning for unused variable on non-Unix systems + 2098 9.0.1174 smali files are not recognized + 14197 9.0.1175 the set_ref_in_item() function is too long + 3110 9.0.1176 smithy files are not recognized + 3779 9.0.1177 AppVeyor uses some older tools + 14601 9.0.1178 a child class cannot override functions from a base class + 5372 9.0.1179 not all errors around inheritance are tested + 3058 9.0.1180 compiler warnings without the +job feature + 5335 9.0.1181 class inheritance and typing insufficiently tested + 2078 9.0.1182 go checksum files are not recognized + 29160 9.0.1183 code is indented more than necessary + 6037 9.0.1184 interface of an object is not recognized when checking type + 7056 9.0.1185 using class from imported script not tested + 2346 9.0.1186 imported class does not work when used twice in a line + 1622 9.0.1187 test for using imported class fails + 5834 9.0.1188 return value of type() for class and object unclear + 2168 9.0.1189 invalid memory access with folding and using "L" + 9139 9.0.1190 AppVeyor runs much slower with MSVC 2022 + 2659 9.0.1191 some Bazel files are not recognized + 3259 9.0.1192 no error when class function argument shadows a member + 3391 9.0.1193 cannot map <Esc> when using the Kitty key protocol + 1808 9.0.1194 compiler warning for comparing pointer with int + 11657 9.0.1195 restoring KeyTyped when building statusline not tested + 56012 9.0.1196 code is indented more than necessary + 1394 9.0.1197 dump file missing from patch + 4690 9.0.1198 abstract class not supported yet + 3210 9.0.1199 crash when using kitty and using a mapping with <Esc> + 3141 9.0.1200 AppVeyor builds with an old Python version + 4108 9.0.1201 assignment with operator doesn't work in object method + 2584 9.0.1202 crash when iterating over list of objects + 7599 9.0.1203 return type of values() is always list<any> + 4417 9.0.1204 expression compiled the wrong way after using an object + 2853 9.0.1205 crash when handling class that extends another class + 5694 9.0.1206 testing with Python on AppVeyor does not work properly + 2884 9.0.1207 error when object type is expected but getting "any" +106340 9.0.1208 code is indented more than necessary + 14140 9.0.1209 getting interface member does not always work + 1614 9.0.1210 compiler complains about declaration after label + 6796 9.0.1211 storing value in interface member does not always work + 8468 9.0.1212 cannot read back what setcellwidths() has done + 4548 9.0.1213 adding a line below the last one does not expand fold + 1350 9.0.1214 file left behind after running tests + 3102 9.0.1215 using isalpha() adds dependency on current locale + 1897 9.0.1216 Coverity warns for ignoring return value + 2207 9.0.1217 using an object member in a closure doesn't work + 2210 9.0.1218 completion includes functions that don't work + 4577 9.0.1219 handling of FORTIFY_SOURCE flags doesn't match Fedora usage + 5273 9.0.1220 termcap/terminfo entries do not indicate possible modifiers + 63563 9.0.1221 code is indented more than necessary + 3430 9.0.1222 terminal tests are flaky on MacOS + 6587 9.0.1223 cannot use setcellwidths() below 0x100 + 24030 9.0.1224 cannot call a :def function with a number for float argument + 2385 9.0.1225 reading past the end of a line when formatting text + 4383 9.0.1226 spurious empty line when using text properties + 8179 9.0.1227 no cmdline completion for :runtime + 2843 9.0.1228 fuzzy menu completion is only tested in the GUI + 2275 9.0.1229 Cap'n Proto files are not recognized + 2119 9.0.1230 Apache thrift files are not recognized + 21477 9.0.1231 completion of :runtime does not handle {where} argument + 8307 9.0.1232 ColorTable saving and restoring does not work properly + 2341 9.0.1233 search() loops forever if "skip" is TRUE for all matches + 49698 9.0.1234 the code style has to be checked manually + 3802 9.0.1235 MS-Windows console: not flushing termguicolors + 2096 9.0.1236 code in same_leader() can be simplified + 82217 9.0.1237 code is indented more than necessary + 20339 9.0.1238 :runtime completion can be further improved + 2895 9.0.1239 cannot have a line break before an object member access + 3830 9.0.1240 cannot access a private object member in a lambda + 1593 9.0.1241 Coverity warns for not checking function return value + 6488 9.0.1242 code for :runtime completion is not consistent + 13480 9.0.1243 :setglobal cannot use script-local function for "expr" option + 2191 9.0.1244 cursor displayed in wrong position when leaving Insert mode + 69126 9.0.1245 code is indented more than necessary + 45824 9.0.1246 code is indented more than necessary + 3302 9.0.1247 divide by zero with 'smoothscroll' set and a narrow window + 2692 9.0.1248 cannot export an interface + 4145 9.0.1249 cannot export an abstract class + 13907 9.0.1250 cannot use an object method with :defer + 9117 9.0.1251 checking returned value of ga_grow() is inconsistent + 7988 9.0.1252 MS-Windows: scrollback cropped off on Vim exit + 1673 9.0.1253 CI adds repository unnecessarily + 21462 9.0.1254 calling a method on an interface does not work + 2405 9.0.1255 changing 'virtualedit' does not have immediate effect + 2953 9.0.1256 NetworkManager connection files are not recognized + 90498 9.0.1257 code style is not check in test scripts + 4335 9.0.1258 code style test fails + 4061 9.0.1259 diffmode test fails + 1785 9.0.1260 Coverity warns for possible NULL pointer usage + 1978 9.0.1261 Elsa files are not recognized +108325 9.0.1262 the did_set_string_option function is too long + 2070 9.0.1263 KDL files are not recognized + 1527 9.0.1264 Motif: compiler warning for unused argument + 2789 9.0.1265 using an interface method may give a compilation error + 4607 9.0.1266 error for space before ": type" is inconsistent + 45803 9.0.1267 the did_set_string_option function is too long + 4297 9.0.1268 .clangd and .stylelintrc files don't get a filetype + 2164 9.0.1269 channel test often fails on Mac OS + 2619 9.0.1270 crash when using search stat in narrow screen + 7365 9.0.1271 using sizeof() and subtract array size is tricky + 3272 9.0.1272 typo in pattern for filetype detection + 2482 9.0.1273 "1v" may select block with wrong size + 1944 9.0.1274 FIRRTL files are not recognized + 33922 9.0.1275 the code for setting options is too complicated + 6682 9.0.1276 some mappings with Meta and Shift do not work + 3741 9.0.1277 cursor may move with autocmd in Visual mode + 2651 9.0.1278 go.work.sum files are not recognized + 3741 9.0.1279 display shows lines scrolled down erroneously + 2452 9.0.1280 inssufficient testing for what 9.0.1265 fixes + 2009 9.0.1281 Cadence files are not recognized + 2298 9.0.1282 Ron files are not recognized + 23372 9.0.1283 the code for setting options is too complicated + 2237 9.0.1284 compiler warnings for uninitialized variables + 4511 9.0.1285 various small problems + 2757 9.0.1286 Coverity warns for using a NULL pointer + 1583 9.0.1287 with the Kitty key protocl Esc with NumLock cannot be mapped + 1973 9.0.1288 FunC files are not recognized + 3126 9.0.1289 a newer version of clang can be used for CI + 3352 9.0.1290 CTRL-N and -P on cmdline don't trigger CmdlineChanged + 2579 9.0.1291 Move language files are not recognized + 10731 9.0.1292 :defer may call the wrong method for an object + 27843 9.0.1293 the set_num_option() is too long + 36538 9.0.1294 the set_bool_option() function is too long + 24726 9.0.1295 the option initialization function is too long + 3302 9.0.1296 calling an object method with arguments does not work + 1982 9.0.1297 wrong value for $LC_CTYPE makes the environ test fail + 4437 9.0.1298 inserting register on the cmdline does not trigger incsearch + 4064 9.0.1299 change for triggering incsearch not sufficiently tested + 10452 9.0.1300 'statusline' only supports one "%=" item + 10876 9.0.1301 virtual text below empty line not displayed + 2739 9.0.1302 on a Belgian keyboard CTRL-] does not work + 3208 9.0.1303 Motif: scrollbar width/height wrong when maximized + 5471 9.0.1304 "$" for 'list' option displayed in wrong position + 3442 9.0.1305 cursor in wrong line with virtual text above + 3334 9.0.1306 no regression test for solved problem of #11959 + 6853 9.0.1307 setting 'formatoptions' with :let doesn't check for errors + 30751 9.0.1308 the code for setting options is too complicated + 17056 9.0.1309 scrolling two lines with even line count and 'scrolloff' set + 2204 9.0.1310 'splitkeep' test has failures + 1455 9.0.1311 Coverity warns for using a NULL pointer + 3770 9.0.1312 Cursor position wrong when splitting window in insert mode + 8934 9.0.1313 some settings use the current codepage instead of 'encoding' + 6431 9.0.1314 :messages behavior depends on 'fileformat' of current buffer + 3972 9.0.1315 escaping for completion of map command not properly tested + 3699 9.0.1316 MS-Windows: vimfiles dir created with admin group + 4096 9.0.1317 crash when using an unset object variable + 1914 9.0.1318 code style test fails + 1978 9.0.1319 PRQL files are not recognized + 21416 9.0.1320 checking the type of a null object causes a crash + 1613 9.0.1321 vimscript test fails where using {expr} syntax + 8302 9.0.1322 crash when indexing "any" which is an object + 1725 9.0.1323 build failure with +eval feature + 3412 9.0.1324 "gj" and "gk" do not move correctly over a closed fold + 10274 9.0.1325 'colorcolumn' highlight wrong with virtual text above + 4782 9.0.1326 relative line number not updated with virtual text above + 3553 9.0.1327 cursor in wrong position below line with virtual text below + 2888 9.0.1328 error when using "none" for GUI color is confusing + 2935 9.0.1329 completion of map includes simplified ones +334145 9.0.1330 handling new value of an option has a long "else if" chain + 2273 9.0.1331 illegal memory access when using :ball in Visual mode + 2423 9.0.1332 crash when using buffer-local user command in cmdline window + 2563 9.0.1333 when redo'ing twice <ScriptCmd> may not get the script ID + 26315 9.0.1334 using tt_member for the class leads to mistakes + 3265 9.0.1335 no test for bad use of spaces in help files + 33216 9.0.1336 functions without arguments are not always declared properly + 1980 9.0.1337 yuck files are not recognized + 15614 9.0.1338 :defcompile and :disassemble can't find class method + 2243 9.0.1339 no test for :disassemble with class function diff --git a/debian/clean b/debian/clean new file mode 100644 index 0000000..cf543f0 --- /dev/null +++ b/debian/clean @@ -0,0 +1,15 @@ +debian/helpztags.1 +debian/policy/vim-policy.html/ +debian/policy/vim-policy.txt +debian/tmplogo.* +runtime/doc/*.html +runtime/doc/*.log +runtime/doc/doctags +runtime/doc/tags +runtime/doc/tags.ref +src/auto/config.h +src/auto/config.mk +src/po/vim.pot +src/pixmaps +src/runtime +*-stamp diff --git a/debian/control b/debian/control new file mode 100644 index 0000000..41debf3 --- /dev/null +++ b/debian/control @@ -0,0 +1,265 @@ +Source: vim +Section: editors +Priority: optional +Maintainer: Debian Vim Maintainers <team+vim@tracker.debian.org> +Uploaders: + James McCoy <jamessan@debian.org>, +Standards-Version: 4.6.1 +Rules-Requires-Root: no +Build-Depends: + autoconf, + cscope <!nocheck>, + debhelper-compat (= 13), + libacl1-dev, + libcanberra-dev, + libgpmg1-dev [linux-any], + libgtk-3-dev, + liblua5.2-dev, + libmotif-dev, + libperl-dev, + libselinux1-dev [linux-any], + libsodium-dev, + libncurses-dev, +# Needed to run libvterm's tests + libtool-bin <!nocheck>, + lua5.2, + procps <!nocheck>, + python3-dev, + ruby [!alpha !ia64] <!pkg.vim.noruby>, + ruby-dev [!alpha !ia64] <!pkg.vim.noruby>, + tcl-dev, +Build-Conflicts: + autoconf2.13, +Build-Depends-Indep: + docbook-utils, + docbook-xml, + ghostscript, +# Explicitly depend on lynx since docbook2txt requires it, even though its +# Depends suggests otherwise (c.f., #387035) + lynx, + pdf2svg, +Vcs-Git: https://salsa.debian.org/vim-team/vim.git +Vcs-Browser: https://salsa.debian.org/vim-team/vim +Homepage: https://www.vim.org/ + +Package: vim-common +Priority: important +Architecture: all +Multi-Arch: foreign +Depends: + ${misc:Depends}, +Recommends: + xxd, + vim | vim-gtk3 | vim-motif | vim-nox | vim-tiny, +Description: Vi IMproved - Common files + Vim is an almost compatible version of the UNIX editor Vi. + . + This package contains files shared by all non GUI-enabled vim variants + available in Debian. Examples of such shared files are: manpages and + configuration files. + +Package: vim-gui-common +Architecture: all +Multi-Arch: foreign +Recommends: + vim-gtk3 | vim-motif, +Depends: + ${misc:Depends}, +Description: Vi IMproved - Common GUI files + Vim is an almost compatible version of the UNIX editor Vi. + . + This package contains files shared by all GUI-enabled vim + variants available in Debian. Examples of such shared files are: + gvimtutor, icons, and desktop environments settings. + +Package: vim-runtime +Architecture: all +Multi-Arch: foreign +Depends: + ${misc:Depends}, +Breaks: + vim-tiny (<< ${source:Version}), +Recommends: + vim | vim-gtk3 | vim-motif | vim-nox | vim-tiny, +Enhances: + vim-tiny, +Description: Vi IMproved - Runtime files + Vim is an almost compatible version of the UNIX editor Vi. + . + This package contains vimtutor and the architecture independent runtime + files, used, if available, by all vim variants available in Debian. + Example of such runtime files are: online documentation, rules for + language-specific syntax highlighting and indentation, color schemes, + and standard plugins. + +Package: vim-doc +Section: doc +Architecture: all +Multi-Arch: foreign +Depends: + ${misc:Depends}, +Description: Vi IMproved - HTML documentation + Vim is an almost compatible version of the UNIX editor Vi. + . + This package contains the HTML version of the online documentation. It is + built from the runtime/doc directory of the source tree. + +Package: vim-tiny +Priority: important +Architecture: any +Depends: + vim-common (= ${source:Version}), + ${misc:Depends}, + ${shlibs:Depends}, +Suggests: + indent, +Provides: + editor, +Description: Vi IMproved - enhanced vi editor - compact version + Vim is an almost compatible version of the UNIX editor Vi. + . + This package contains a minimal version of Vim compiled with no GUI and + a small subset of features. This package's sole purpose is to provide + the vi binary for base installations. + . + If a vim binary is wanted, try one of the following more featureful + packages: vim, vim-nox, vim-motif, or vim-gtk3. + +Package: vim +Architecture: any +Depends: + vim-common (= ${source:Version}), + vim-runtime (= ${source:Version}), + ${misc:Depends}, + ${shlibs:Depends}, +Suggests: + ctags, + vim-doc, + vim-scripts, +Provides: + editor, +Description: Vi IMproved - enhanced vi editor + Vim is an almost compatible version of the UNIX editor Vi. + . + Many new features have been added: multi level undo, syntax + highlighting, command line history, on-line help, filename + completion, block operations, folding, Unicode support, etc. + . + This package contains a version of vim compiled with a rather + standard set of features. This package does not provide a GUI + version of Vim. See the other vim-* packages if you need more + (or less). + +Package: vim-gtk3 +Architecture: any +Depends: + vim-common (= ${source:Version}), + vim-gui-common (= ${source:Version}), + vim-runtime (= ${source:Version}), + ${misc:Depends}, + ${shlibs:Depends}, +Suggests: + cscope, + fonts-dejavu, + gnome-icon-theme, + vim-doc, +Provides: + editor, + gvim (= ${binary:Version}), + vim (= ${binary:Version}), + vim-lua (= ${binary:Version}), + vim-perl (= ${binary:Version}), + vim-python3 (= ${binary:Version}), + ${vim:Ruby-Provides}, + vim-tcl (= ${binary:Version}), +Description: Vi IMproved - enhanced vi editor - with GTK3 GUI + Vim is an almost compatible version of the UNIX editor Vi. + . + Many new features have been added: multi level undo, syntax + highlighting, command line history, on-line help, filename + completion, block operations, folding, Unicode support, etc. + . + This package contains a version of vim compiled with a GTK3 GUI + and support for scripting with Lua, Perl, Python 3,${vim:Ruby-Desc} and Tcl. + +Package: vim-nox +Architecture: any +Depends: + vim-common (= ${source:Version}), + vim-runtime (= ${source:Version}), + ${misc:Depends}, + ${shlibs:Depends}, +Suggests: + cscope, + vim-doc, +Provides: + editor, + vim (= ${binary:Version}), + vim-lua (= ${binary:Version}), + vim-perl (= ${binary:Version}), + vim-python3 (= ${binary:Version}), + ${vim:Ruby-Provides}, + vim-tcl (= ${binary:Version}), +Description: Vi IMproved - enhanced vi editor - with scripting languages support + Vim is an almost compatible version of the UNIX editor Vi. + . + Many new features have been added: multi level undo, syntax + highlighting, command line history, on-line help, filename + completion, block operations, folding, Unicode support, etc. + . + This package contains a version of vim compiled with support for + scripting with Lua, Perl, Python 3,${vim:Ruby-Desc} and Tcl but no GUI. + +Package: vim-motif +Architecture: any +Depends: + vim-common (= ${source:Version}), + vim-gui-common (= ${source:Version}), + vim-runtime (= ${source:Version}), + ${misc:Depends}, + ${shlibs:Depends}, +Suggests: + cscope, + vim-doc, +Provides: + editor, + gvim (= ${binary:Version}), + vim (= ${binary:Version}), + vim-lua (= ${binary:Version}), + vim-perl (= ${binary:Version}), + vim-python3 (= ${binary:Version}), + ${vim:Ruby-Provides}, + vim-tcl (= ${binary:Version}), +Description: Vi IMproved - enhanced vi editor - with Motif GUI + Vim is an almost compatible version of the UNIX editor Vi. + . + Many new features have been added: multi level undo, syntax + highlighting, command line history, on-line help, filename + completion, block operations, folding, Unicode support, etc. + . + This package contains a version of vim compiled with a Motif GUI + and support for scripting with Lua, Perl, Python 3,${vim-Ruby-Desc} and Tcl. + +Package: vim-athena +Architecture: all +Depends: + vim-motif, + ${misc:Depends}, +Section: oldlibs +Description: Vi IMproved - enhanced vi editor (dummy package) + This is a transitional package to install the vim-motif package. You may + remove this package if nothing depends on it. + +Package: xxd +Architecture: any +Multi-Arch: foreign +Depends: + ${misc:Depends}, + ${shlibs:Depends}, +Breaks: + vim-common (<< 2:7.4.2347-1~), +Replaces: + vim-common (<< 2:7.4.2347-1~), +Description: tool to make (or reverse) a hex dump + xxd creates a hex dump of a given file or standard input. It can also convert + a hex dump back to its original binary form. diff --git a/debian/copyright b/debian/copyright new file mode 100644 index 0000000..33d9d96 --- /dev/null +++ b/debian/copyright @@ -0,0 +1,610 @@ +Format: https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/ +Upstream-Name: vim +Source: https://github.com/vim/vim + +Files: * +Copyright: 2001-2022 Bram Moolenaar <Bram@vim.org> + 2006 Benji Fisher <benji@member.ams.org> + 1999-2021 Charles E. Campbell, Jr. <drchip@campbellfamily.biz> + 2003 Fred Barnes + 2003 Mario Schweigler + 2004-2008 Michael Geddes + 2006 Martin Krischik + 2015 Christian Brabandt + 2014 David Necas (Yeti) + 2009-2013 Steven Oliver + 2012 Hong Xu + 2001-2022 MURAOKA Taro <koron.kaoriya@gmail.com> + 2001 Bohdan Vlasyuk <bohdan@vstu.edu.ua> + 2003-2022 Ernest Adrogué <eadrogue@gmx.net> + 2005,2006,2008,2010 Kevin Patrick Scannell <kscanne@gmail.com> + 1997 Olaf Seibert + 2002 E. I. DuPont de Nemours and Company, Inc + Pablo Ariel Kohan + 2017 Eugene Ciurana + 2017 Ken Takata + 2019 Agilent Technologies, Inc. +License: Vim + +Files: runtime/doc/* +Copyright: 1988-2003 Bram Moolenaar <Bram@vim.org> +License: OPL-1+ +Comment: No license options are exercised. See https://bugs.debian.org/384019 + for discussions confirming DFSG-ness of this license when no options are + exercised. + +Files: + runtime/indent/cmake.vim + runtime/indent/elm.vim + runtime/syntax/cmake.vim + runtime/syntax/elm.vim + runtime/syntax/go.vim + runtime/syntax/proto.vim + runtime/syntax/tpp.vim +Copyright: Andy Cedilnik <andy.cedilnik@kitware.com> + Karthik Krishnan <kartik.krishnan@kitware.com> + Dimitri Merejkowsky <d.merej@gmail.com> + Gerfried Fuchs <alfie@ist.org> + Joseph Hager <ajhager@gmail.com> + 2008 Google Inc. + 2009 The Go Authors +License: BSD-3-clause + +Files: + runtime/ftplugin/jsonc.vim + runtime/ftplugin/julia.vim + runtime/ftplugin/wast.vim + runtime/indent/julia.vim + runtime/indent/wast.vim + runtime/syntax/bitbake.vim + runtime/syntax/json.vim + runtime/syntax/jsonc.vim + runtime/syntax/julia.vim + runtime/syntax/nix.vim + runtime/syntax/wast.vim +Copyright: + 2013 Jeroen Ruigrok van der Werven, Eli Parra + 2016 rhysd + 2021 Izhak Jakov + 2012-2016 Carlo Baldassi + 2004 Chris Larson + 2008 Ricardo Salveti + 2022 Daiderd Jordan + 2022 James Fleming +License: Expat + +Files: runtime/syntax/tmux.vim +Copyright: Eric Pruitt <eric.pruitt@gmail.com> +License: BSD-2-clause + +Files: runtime/syntax/rust.vim + runtime/autoload/rust.vim + runtime/autoload/rustfmt.vim + runtime/ftplugin/rust.vim + runtime/indent/rust.vim + runtime/compiler/cargo.vim +Copyright: 2015 The Rust Project Developers +License: Apache or Expat + +Files: runtime/tools/efm_perl.pl +Copyright: 2001 Joerg Ziefle <joerg.ziefle@gmx.de> +License: GPL-1+ or Artistic-1 + +Files: src/libvterm/* +Copyright: 2008 Paul Evans <leonerd@leonerd.org.uk> +License: Expat + +Files: src/regexp_bt.c +Copyright: 1986 University of Toronto +License: Vim-Regexp + +Files: src/if_xcmdsrv.c +Copyright: Copyright (c) 1989-1993 The Regents of the University of California. +License: UC + +Files: src/tee/tee.c +Copyright: 1996, Paul Slootman +License: public-domain + +Files: src/xxd/* +Copyright: 1990-1998 by Juergen Weigert (jnweiger@informatik.uni-erlangen.de) +License: Expat or GPL-2 + +Files: src/install-sh +Copyright: 1987, 1988, 1994 X Consortium +License: X11 + +Files: src/gui_gtk_vms.h +Copyright: 2000 Compaq Computer Corporation +License: Compaq + +Files: src/pty.c +Copyright: 1993 Juergen Weigert (jnweiger@immd4.informatik.uni-erlangen.de) + 1993 Michael Schroeder (mlschroe@immd4.informatik.uni-erlangen.de) + 1987 Oliver Laumann +License: GPL-2+ + +Files: src/iscygpty.* +Copyright: 2015-2017 K.Takata +License: Expat or Vim + +Files: src/xpm/* +Copyright: 1989-95 GROUPE BULL +License: XPM + +Files: src/xdiff/* +Copyright: 2003-2016 Davide Libenzi, Johannes E. Schindelin +License: LGPL-2.1+ + +Files: src/xdiff/xhistogram.c +Copyright: 2010 Google Inc. and other copyright owners as documented in JGit's IP log +License: EDL-1 + +Files: + runtime/compiler/powershell.vim + runtime/doc/ft_ps1.txt + runtime/ftplugin/ps1.vim + runtime/ftplugin/ps1xml.vim + runtime/ftplugin/swift.vim + runtime/ftplugin/swiftgyb.vim + runtime/indent/ps1.vim + runtime/syntax/ps1.vim + runtime/syntax/ps1xml.vim + runtime/syntax/sil.vim + runtime/syntax/swift.vim + runtime/syntax/swiftgyb.vim +Copyright: + 2014-2020 Apple Inc. and the Swift project authors + 2005-2021 Peter Provost +License: Apache + +Files: runtime/syntax/poke.vim +Copyright: 2021 Matthew T. Ihlenfield +License: GPL-3+ + +License: Vim + I) There are no restrictions on distributing unmodified copies of Vim except + that they must include this license text. You can also distribute + unmodified parts of Vim, likewise unrestricted except that they must + include this license text. You are also allowed to include executables + that you made from the unmodified Vim sources, plus your own usage + examples and Vim scripts. + . + II) It is allowed to distribute a modified (or extended) version of Vim, + including executables and/or source code, when the following four + conditions are met: + 1) This license text must be included unmodified. + 2) The modified Vim must be distributed in one of the following five ways: + a) If you make changes to Vim yourself, you must clearly describe in + the distribution how to contact you. When the maintainer asks you + (in any way) for a copy of the modified Vim you distributed, you + must make your changes, including source code, available to the + maintainer without fee. The maintainer reserves the right to + include your changes in the official version of Vim. What the + maintainer will do with your changes and under what license they + will be distributed is negotiable. If there has been no negotiation + then this license, or a later version, also applies to your changes. + The current maintainer is Bram Moolenaar <Bram@vim.org>. If this + changes it will be announced in appropriate places (most likely + vim.sf.net, www.vim.org and/or comp.editors). When it is completely + impossible to contact the maintainer, the obligation to send him + your changes ceases. Once the maintainer has confirmed that he has + received your changes they will not have to be sent again. + b) If you have received a modified Vim that was distributed as + mentioned under a) you are allowed to further distribute it + unmodified, as mentioned at I). If you make additional changes the + text under a) applies to those changes. + c) Provide all the changes, including source code, with every copy of + the modified Vim you distribute. This may be done in the form of a + context diff. You can choose what license to use for new code you + add. The changes and their license must not restrict others from + making their own changes to the official version of Vim. + d) When you have a modified Vim which includes changes as mentioned + under c), you can distribute it without the source code for the + changes if the following three conditions are met: + - The license that applies to the changes permits you to distribute + the changes to the Vim maintainer without fee or restriction, and + permits the Vim maintainer to include the changes in the official + version of Vim without fee or restriction. + - You keep the changes for at least three years after last + distributing the corresponding modified Vim. When the maintainer + or someone who you distributed the modified Vim to asks you (in + any way) for the changes within this period, you must make them + available to him. + - You clearly describe in the distribution how to contact you. This + contact information must remain valid for at least three years + after last distributing the corresponding modified Vim, or as long + as possible. + e) When the GNU General Public License (GPL) applies to the changes, + you can distribute the modified Vim under the GNU GPL version 2 or + any later version. + 3) A message must be added, at least in the output of the ":version" + command and in the intro screen, such that the user of the modified Vim + is able to see that it was modified. When distributing as mentioned + under 2)e) adding the message is only required for as far as this does + not conflict with the license used for the changes. + 4) The contact information as required under 2)a) and 2)d) must not be + removed or changed, except that the person himself can make + corrections. + . + III) If you distribute a modified version of Vim, you are encouraged to use + the Vim license for your changes and make them available to the + maintainer, including the source code. The preferred way to do this is + by e-mail or by uploading the files to a server and e-mailing the URL. + If the number of changes is small (e.g., a modified Makefile) e-mailing a + context diff will do. The e-mail address to be used is + <maintainer@vim.org> + . + IV) It is not allowed to remove this license from the distribution of the Vim + sources, parts of it or from a modified version. You may use this + license for previous Vim releases instead of the license that they came + with, at your option. + +License: OPL-1+ + I. REQUIREMENTS ON BOTH UNMODIFIED AND MODIFIED VERSIONS + . + The Open Publication works may be reproduced and distributed in whole or in + part, in any medium physical or electronic, provided that the terms of this + license are adhered to, and that this license or an incorporation of it by + reference (with any options elected by the author(s) and/or publisher) is + displayed in the reproduction. + . + Proper form for an incorporation by reference is as follows: + . + Copyright (c) <year> by <author's name or designee>. This material may be + distributed only subject to the terms and conditions set forth in the Open + Publication License, vX.Y or later (the latest version is presently + available at http://www.opencontent.org/openpub/). + . + The reference must be immediately followed with any options elected by the + author(s) and/or publisher of the document (see section VI). + . + Commercial redistribution of Open Publication-licensed material is permitted. + . + Any publication in standard (paper) book form shall require the citation of the + original publisher and author. The publisher and author's names shall appear on + all outer surfaces of the book. On all outer surfaces of the book the original + publisher's name shall be as large as the title of the work and cited as + possessive with respect to the title. + . + . + II. COPYRIGHT + . + The copyright to each Open Publication is owned by its author(s) or designee. + . + . + III. SCOPE OF LICENSE + . + The following license terms apply to all Open Publication works, unless + otherwise explicitly stated in the document. + . + Mere aggregation of Open Publication works or a portion of an Open Publication + work with other works or programs on the same media shall not cause this + license to apply to those other works. The aggregate work shall contain a + notice specifying the inclusion of the Open Publication material and + appropriate copyright notice. + . + SEVERABILITY. If any part of this license is found to be unenforceable in any + jurisdiction, the remaining portions of the license remain in force. + . + NO WARRANTY. Open Publication works are licensed and provided "as is" without + warranty of any kind, express or implied, including, but not limited to, the + implied warranties of merchantability and fitness for a particular purpose or a + warranty of non-infringement. + . + . + IV. REQUIREMENTS ON MODIFIED WORKS + . + All modified versions of documents covered by this license, including + translations, anthologies, compilations and partial documents, must meet the + following requirements: + . + 1. The modified version must be labeled as such. + 2. The person making the modifications must be identified and the + modifications dated. + 3. Acknowledgement of the original author and publisher if applicable must + be retained according to normal academic citation practices. + 4. The location of the original unmodified document must be identified. + 5. The original author's (or authors') name(s) may not be used to assert or + imply endorsement of the resulting document without the original author's + (or authors') permission. + . + . + V. GOOD-PRACTICE RECOMMENDATIONS + . + In addition to the requirements of this license, it is requested from and + strongly recommended of redistributors that: + . + 1. If you are distributing Open Publication works on hardcopy or CD-ROM, you + provide email notification to the authors of your intent to redistribute + at least thirty days before your manuscript or media freeze, to give the + authors time to provide updated documents. This notification should + describe modifications, if any, made to the document. + 2. All substantive modifications (including deletions) be either clearly + marked up in the document or else described in an attachment to the + document. + 3. Finally, while it is not mandatory under this license, it is considered + good form to offer a free copy of any hardcopy and CD-ROM expression of + an Open Publication-licensed work to its author(s). + . + . + VI. LICENSE OPTIONS + . + The author(s) and/or publisher of an Open Publication-licensed document may + elect certain options by appending language to the reference to or copy of the + license. These options are considered part of the license instance and must be + included with the license (or its incorporation by reference) in derived works. + . + A. To prohibit distribution of substantively modified versions without the + explicit permission of the author(s). "Substantive modification" is defined as + a change to the semantic content of the document, and excludes mere changes in + format or typographical corrections. + . + To accomplish this, add the phrase `Distribution of substantively modified + versions of this document is prohibited without the explicit permission of the + copyright holder.' to the license reference or copy. + . + B. To prohibit any publication of this work or derivative works in whole or in + part in standard (paper) book form for commercial purposes is prohibited unless + prior permission is obtained from the copyright holder. + . + To accomplish this, add the phrase 'Distribution of the work or derivative of + the work in any standard (paper) book form is prohibited unless prior + permission is obtained from the copyright holder.' to the license reference or + copy. + +License: GPL-2 + On Debian systems, the complete text of the GPL version 2 license can be + found in `/usr/share/common-licenses/GPL-2'. + +License: GPL-2+ + On Debian systems, the complete text of the GPL version 2 license can be + found in `/usr/share/common-licenses/GPL-2'. + +License: GPL-3+ + On Debian systems, the complete text of the GPL version 3 license can be + found in `/usr/share/common-licenses/GPL-3'. + +License: GPL-1+ + On Debian systems, the complete text of the GPL version 1 license can be + found in `/usr/share/common-licenses/GPL-1'. + +License: LGPL-2.1+ + On Debian systems, the complete text of the LGPL version 2 license can be + found in `/usr/share/common-licenses/LGPL-2.1'. + +License: Artistic-1 + On Debian systems, the complete text of the Artistic version 1 license + can be found in `/usr/share/common-licenses/Artistic'. + +License: Vim-Regexp + Permission is granted to anyone to use this software for any + purpose on any computer system, and to redistribute it freely, + subject to the following restrictions: + . + 1. The author is not responsible for the consequences of use of + this software, no matter how awful, even if they arise + from defects in it. + . + 2. The origin of this software must not be misrepresented, either + by explicit claim or by omission. + . + 3. Altered versions must be plainly marked as such, and must not + be misrepresented as being the original software. + +License: Apache + On Debian systems, the complete text of the Apache version 2.0 license can be + found in `/usr/share/common-licenses/Apache-2.0'. + +License: Expat + Permission is hereby granted, free of charge, to any person obtaining a copy + of this software and associated documentation files (the "Software"), to + deal in the Software without restriction, including without limitation the + rights to use, copy, modify, merge, publish, distribute, sublicense, and/or + sell copies of the Software, and to permit persons to whom the Software is + furnished to do so, subject to the following conditions: + . + The above copyright notice and this permission notice shall be included in + all copies or substantial portions of the Software. + . + THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, + EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF + MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND + NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS + BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN + ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN + CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE + SOFTWARE. + +License: X11 + Permission is hereby granted, free of charge, to any person obtaining a copy + of this software and associated documentation files (the "Software"), to deal + in the Software without restriction, including without limitation the rights + to use, copy, modify, merge, publish, distribute, sublicense, and/or sell + copies of the Software, and to permit persons to whom the Software is + furnished to do so, subject to the following conditions: + . + The above copyright notice and this permission notice shall be included in all + copies or substantial portions of the Software. + . + THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR + IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, + FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE X + CONSORTIUM BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN + ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION + WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. + . + Except as contained in this notice, the name of the X Consortium shall not be + used in advertising or otherwise to promote the sale, use or other dealings in + this Software without prior written authorization from the X Consortium. + +License: UC + Permission is hereby granted, without written agreement and without + license or royalty fees, to use, copy, modify, and distribute this + software and its documentation for any purpose, provided that the + above copyright notice and the following two paragraphs appear in + all copies of this software. + . + IN NO EVENT SHALL THE UNIVERSITY OF CALIFORNIA BE LIABLE TO ANY PARTY FOR + DIRECT, INDIRECT, SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES ARISING OUT + OF THE USE OF THIS SOFTWARE AND ITS DOCUMENTATION, EVEN IF THE UNIVERSITY OF + CALIFORNIA HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. + . + THE UNIVERSITY OF CALIFORNIA SPECIFICALLY DISCLAIMS ANY WARRANTIES, + INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY + AND FITNESS FOR A PARTICULAR PURPOSE. THE SOFTWARE PROVIDED HEREUNDER IS + ON AN "AS IS" BASIS, AND THE UNIVERSITY OF CALIFORNIA HAS NO OBLIGATION TO + PROVIDE MAINTENANCE, SUPPORT, UPDATES, ENHANCEMENTS, OR MODIFICATIONS. + +License: public-domain + This source code is released into the public domain. It is provided on an + as-is basis and no responsibility is accepted for its failure to perform + as expected. It is worth at least as much as you paid for it! + +License: Compaq + 1. GRANT + Compaq Computer Corporation ("COMPAQ") grants you the right to use, + modify, and distribute the following source code (the "Software") + on any number of computers. You may use the Software as part of + creating a software program or product intended for commercial or + non-commercial distribution in machine-readable source code, binary, + or executable formats. You may distribute the Software as + machine-readable source code provided this license is not removed + from the Software and any modifications are conspicuously indicated. + 2. COPYRIGHT + The Software is owned by COMPAQ and its suppliers and is protected by + copyright laws and international treaties. Your use of the Software + and associated documentation is subject to the applicable copyright + laws and the express rights and restrictions of these terms. + 3. RESTRICTIONS + You may not remove any copyright, trademark, or other proprietary + notices from the Software or the associated + You are responsible for compliance with all applicable export or + re-export control laws and regulations if you export the Software. + This license is governed by and is to be construed under the laws + of the State of Texas. + . + DISCLAIMER OF WARRANTY AND LIABILITY + Compaq shall not be liable for technical or editorial errors or + omissions contained herein. The information contained herein is + subject to change without notice. + . + THIS SOFTWARE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. + THE ENTIRE RISK ARISING OUT OF THE USE OF THIS SOFTWARE REMAINS WITH + RECIPIENT. IN NO EVENT SHALL COMPAQ BE LIABLE FOR ANY DIRECT, + CONSEQUENTIAL, INCIDENTAL, SPECIAL, PUNITIVE OR OTHER DAMAGES + WHATSOEVER (INCLUDING WITHOUT LIMITATION DAMAGES FOR LOSS OF BUSINESS + PROFITS, BUSINESS INTERRUPTION, OR LOSS OF BUSINESS INFORMATION), + EVEN IF COMPAQ HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES + AND WHETHER IN AN ACTION OF CONTRACT OR TORT INCLUDING NEGLIGENCE. + +License: XPM + Permission is hereby granted, free of charge, to any person obtaining a copy + of this software and associated documentation files (the "Software"), to + deal in the Software without restriction, including without limitation the + rights to use, copy, modify, merge, publish, distribute, sublicense, and/or + sell copies of the Software, and to permit persons to whom the Software is + furnished to do so, subject to the following conditions: + . + The above copyright notice and this permission notice shall be included in + all copies or substantial portions of the Software. + . + THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR + IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, + FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL + GROUPE BULL BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN + AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN + CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. + . + Except as contained in this notice, the name of GROUPE BULL shall not be + used in advertising or otherwise to promote the sale, use or other dealings + in this Software without prior written authorization from GROUPE BULL. + +License: BSD-3-clause + Redistribution and use in source and binary forms, with or without + modification, are permitted provided that the following conditions + are met: + . + * Redistributions of source code must retain the above copyright + notice, this list of conditions and the following disclaimer. + . + * Redistributions in binary form must reproduce the above copyright + notice, this list of conditions and the following disclaimer in the + documentation and/or other materials provided with the distribution. + . + * Neither the name of Kitware, Inc. nor the names of Contributors + may be used to endorse or promote products derived from this + software without specific prior written permission. + . + THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS + "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT + LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR + A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT + HOLDER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, + SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT + LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, + DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY + THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT + (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE + OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. + +License: BSD-2-clause + Redistribution and use in source and binary forms, with or without + modification, are permitted provided that the following conditions are met: + . + 1. Redistributions of source code must retain the above copyright notice, this + list of conditions and the following disclaimer. + . + 2. Redistributions in binary form must reproduce the above copyright notice, + this list of conditions and the following disclaimer in the documentation + and/or other materials provided with the distribution. + . + THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND + ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED + WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE + DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE + FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL + DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR + SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER + CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, + OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE + OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. + +License: EDL-1 + This program and the accompanying materials are made available + under the terms of the Eclipse Distribution License v1.0 which + accompanies this distribution, is reproduced below, and is + available at http://www.eclipse.org/org/documents/edl-v10.php + . + All rights reserved. + . + Redistribution and use in source and binary forms, with or + without modification, are permitted provided that the following + conditions are met: + . + - Redistributions of source code must retain the above copyright + notice, this list of conditions and the following disclaimer. + . + - Redistributions in binary form must reproduce the above + copyright notice, this list of conditions and the following + disclaimer in the documentation and/or other materials provided + with the distribution. + . + - Neither the name of the Eclipse Foundation, Inc. nor the + names of its contributors may be used to endorse or promote + products derived from this software without specific prior + written permission. + . + THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND + CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, + INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES + OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE + ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR + CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, + SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT + NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; + LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER + CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, + STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) + ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF + ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. diff --git a/debian/gbp.conf b/debian/gbp.conf new file mode 100644 index 0000000..deb4a83 --- /dev/null +++ b/debian/gbp.conf @@ -0,0 +1,8 @@ +[DEFAULT] +upstream-tag = v%(version)s +debian-tag = debian/%(version)s +debian-branch = debian/sid + +[pq] +patch-numbers = False +drop = True diff --git a/debian/helpztags b/debian/helpztags new file mode 100755 index 0000000..425d37e --- /dev/null +++ b/debian/helpztags @@ -0,0 +1,92 @@ +#!/usr/bin/perl +# +# helpztags generates tags for Vim helpfiles, for both .txt and .txt.gz files +# Author: Jakub Turski <yacoob@chruptak.plukwa.net> +# Artur R. Czechowski <arturcz@hell.pl> +# Version: 0.4 + +# Please use following command for generate a manual file: +# pod2man -c "User Commands" -s 1 -q none -r "vim 6.2" -d "September 2003" helpztags helpztags.1 + +=head1 NAME + +helpztags - generate the help tags file for directory + +=head1 SYNOPSIS + +helpztags F<DIRS>... + +=head1 DESCRIPTION + +F<helpztags> scans given directories for F<*.txt> and F<*.txt.gz> files. +Each file is scanned for tags used in F<vim> help files. For each directory +proper F<tags> file is generated. + +There should be at least one directory given. In other case program exits +with error. + +=head1 AUTHORS + +Written by Jakub Turski and Artur R. Czechowski based on idea +contained in C<vim> sources for its C<:helptags command>. + +=head1 REPORTING BUGS + +Please use a Debian C<reportbug> command or procedure described at +C<http://bugs.debian.org/>. + +=head1 SEE ALSO + +Read C<:help helptags> in F<vim> for detailed information about helptags. + +=cut + +use strict; +use warnings; +use File::Glob ':globally'; +use POSIX qw(getcwd); + +die "Error: no directories given. Check manpage for details.\n" unless @ARGV; + +my $startdir=getcwd(); +my %tags; + +foreach my $dir (@ARGV) { + chdir $dir or next; + print "Processing ".$dir."\n"; + foreach my $file (<*.{gz,txt,??x}>) { + next unless $file =~ m/^[\w.-]+\.(?:txt|([[:alpha:]]{2})x)(?:.gz)?$/; + my $suffix = ''; + if ($1) { + $suffix = "-$1"; + } + my $open = ($file =~ /\.gz$/) ? open(GZ, '-|', 'zcat', $file) : open(GZ, $file); + if (!$open) { + chdir $startdir; + next; + } + while (<GZ>) { + # From vim73/src/ex_cmds.c, helptags_one, lines 6443-6445 + # + # Only accept a *tag* when it consists of valid + # characters, there is white space before it and is + # followed by a white character or end-of-line. + while (/(?:(?<=^)|(?<=\s))\*([^*\s|]+?)\*(?:(?=\s)|(?=$))/g) { + $tags{"tags$suffix"}{$1}=$file; + } + } + close(GZ); + } + while (my ($tagfile, $tags) = each %tags) { + next unless %{$tags}; + open(TAGSFILE, '>', $tagfile) || die "Error: Cannot open $dir/$tagfile for writing.\n"; + foreach my $tag (sort keys %{$tags}) { + print TAGSFILE "$tag\t$tags->{$tag}\t/*"; + $tag =~ s/\\/\\\\/g; + $tag =~ s@/@\/@g; + print TAGSFILE "$tag*\n"; + } + close TAGSFILE; + } + chdir $startdir; +} diff --git a/debian/patches/Fix-GH-267-where-indent-after-a-sub-would-not-work.patch b/debian/patches/Fix-GH-267-where-indent-after-a-sub-would-not-work.patch new file mode 100644 index 0000000..8124aea --- /dev/null +++ b/debian/patches/Fix-GH-267-where-indent-after-a-sub-would-not-work.patch @@ -0,0 +1,22 @@ +From: Andy Lester <andy@petdance.com> +Date: Tue, 26 Apr 2022 20:07:43 -0500 +Subject: Fix GH#267 where indent after a sub would not work + +Closes: #1034529 +Signed-off-by: James McCoy <jamessan@debian.org> +--- + runtime/indent/perl.vim | 1 + + 1 file changed, 1 insertion(+) + +diff --git a/runtime/indent/perl.vim b/runtime/indent/perl.vim +index 4c91fa1..bd2a1a9 100644 +--- a/runtime/indent/perl.vim ++++ b/runtime/indent/perl.vim +@@ -133,6 +133,7 @@ function! GetPerlIndent() + \ || synid == "perlHereDoc" + \ || synid == "perlBraces" + \ || synid == "perlStatementIndirObj" ++ \ || synid == "perlSubDeclaration" + \ || synid =~ "^perlFiledescStatement" + \ || synid =~ '^perl\(Sub\|Block\|Package\)Fold' + let brace = strpart(line, bracepos, 1) diff --git a/debian/patches/debian/Add-recognition-of-more-LaTeX-commands-for-tex-filetype-d.patch b/debian/patches/debian/Add-recognition-of-more-LaTeX-commands-for-tex-filetype-d.patch new file mode 100644 index 0000000..2d703d1 --- /dev/null +++ b/debian/patches/debian/Add-recognition-of-more-LaTeX-commands-for-tex-filetype-d.patch @@ -0,0 +1,27 @@ +From: Stefano Zacchiroli <zack@debian.org> +Date: Fri, 25 Aug 2006 13:33:04 +0200 +Subject: Add recognition of more LaTeX commands for tex filetype detection + +Since filetype detection of TeX files defaults to plaintex, we've added +detection of some additional LaTeX commands to help sway the detection +to LaTeX. + +Closes: #384479 +Signed-off-by: James McCoy <jamessan@debian.org> +--- + runtime/autoload/dist/ft.vim | 2 +- + 1 file changed, 1 insertion(+), 1 deletion(-) + +diff --git a/runtime/autoload/dist/ft.vim b/runtime/autoload/dist/ft.vim +index bfc325d..7d1e15f 100644 +--- a/runtime/autoload/dist/ft.vim ++++ b/runtime/autoload/dist/ft.vim +@@ -935,7 +935,7 @@ export def FTtex() + var firstNC = search('^\s*[^[:space:]%]', 'c', 1000) + if firstNC > 0 + # Check the next thousand lines for a LaTeX or ConTeXt keyword. +- var lpat = 'documentclass\>\|usepackage\>\|begin{\|newcommand\>\|renewcommand\>' ++ var lpat = 'documentclass\>\|usepackage\>\|begin{\|newcommand\>\|renewcommand\>\|renewcommand\>\|part\>\|chapter\>\|section\>\|subsection\>\|subsubsection\>\|paragraph\>\|subparagraph\>\|subsubparagraph' + var cpat = 'start\a\+\|setup\a\+\|usemodule\|enablemode\|enableregime\|setvariables\|useencoding\|usesymbols\|stelle\a\+\|verwende\a\+\|stel\a\+\|gebruik\a\+\|usa\a\+\|imposta\a\+\|regle\a\+\|utilisemodule\>' + var kwline = search('^\s*\\\%(' .. lpat .. '\)\|^\s*\\\(' .. cpat .. '\)', + 'cnp', firstNC + 1000) diff --git a/debian/patches/debian/Detect-the-rst-filetype-using-the-contents-of-the-file.patch b/debian/patches/debian/Detect-the-rst-filetype-using-the-contents-of-the-file.patch new file mode 100644 index 0000000..f535de8 --- /dev/null +++ b/debian/patches/debian/Detect-the-rst-filetype-using-the-contents-of-the-file.patch @@ -0,0 +1,28 @@ +From: James Vega <jamessan@debian.org> +Date: Fri, 18 Aug 2006 09:06:20 -0400 +Subject: Detect the rst filetype using the contents of the file + +Closes: #382541 +--- + runtime/autoload/dist/script.vim | 8 ++++++++ + 1 file changed, 8 insertions(+) + +diff --git a/runtime/autoload/dist/script.vim b/runtime/autoload/dist/script.vim +index f86c428..a1162b1 100644 +--- a/runtime/autoload/dist/script.vim ++++ b/runtime/autoload/dist/script.vim +@@ -380,6 +380,14 @@ def DetectFromText(line1: string) + elseif line1 =~ 'exec\s\+\S*scheme' || line2 =~ 'exec\s\+\S*scheme' + set ft=scheme + ++ # rst files ++ elseif line1 =~ '^\.\.\s\|^\s*restindex\s*$' ++ || line2 =~ '^\.\.\s\|^\s*restindex\s*$' ++ || line3 =~ '^\.\.\s\|^\s*restindex\s*$' ++ || line4 =~ '^\.\.\s\|^\s*restindex\s*$' ++ || line5 =~ '^\.\.\s\|^\s*restindex\s*$' ++ set ft=rst ++ + # Git output + elseif line1 =~ '^\(commit\|tree\|object\) \x\{40,\}\>\|^tag \S\+$' + set ft=git diff --git a/debian/patches/debian/Document-Debian-s-decision-to-disable-modelines-by-defaul.patch b/debian/patches/debian/Document-Debian-s-decision-to-disable-modelines-by-defaul.patch new file mode 100644 index 0000000..6be3a21 --- /dev/null +++ b/debian/patches/debian/Document-Debian-s-decision-to-disable-modelines-by-defaul.patch @@ -0,0 +1,29 @@ +From: James Vega <jamessan@debian.org> +Date: Thu, 27 Mar 2008 03:42:02 +0000 +Subject: Document Debian's decision to disable modelines by default + +Modelines have historically been a source of vulnerabilities in Vim. +As long as it remains a "blacklist suspected/proven dangerous options" +instead of a "whitelist allowed options" piece of functionality, +Debian's system-wide vimrc will maintain this setting. As such, the +documentation needs to be updated to reflect the induced behavior. + +Closes: #472522 +Signed-off-by: James McCoy <jamessan@debian.org> +--- + runtime/doc/options.txt | 2 +- + 1 file changed, 1 insertion(+), 1 deletion(-) + +diff --git a/runtime/doc/options.txt b/runtime/doc/options.txt +index 4f0ac45..29991e2 100644 +--- a/runtime/doc/options.txt ++++ b/runtime/doc/options.txt +@@ -5510,7 +5510,7 @@ A jump table for the options with a short description can be found at |Q_op|. + + *'modeline'* *'ml'* *'nomodeline'* *'noml'* + 'modeline' 'ml' boolean (Vim default: on (off for root), +- Vi default: off) ++ Debian: off, Vi default: off) + local to buffer + If 'modeline' is on 'modelines' gives the number of lines that is + checked for set commands. If 'modeline' is off or 'modelines' is zero diff --git a/debian/patches/debian/Support-sourcing-a-vimrc.tiny-when-Vim-is-invoked-as-vi.patch b/debian/patches/debian/Support-sourcing-a-vimrc.tiny-when-Vim-is-invoked-as-vi.patch new file mode 100644 index 0000000..74c2f85 --- /dev/null +++ b/debian/patches/debian/Support-sourcing-a-vimrc.tiny-when-Vim-is-invoked-as-vi.patch @@ -0,0 +1,101 @@ +From: James McCoy <jamessan@debian.org> +Date: Tue, 6 Oct 2015 23:46:30 -0400 +Subject: Support sourcing a vimrc.tiny when Vim is invoked as vi + +This is used only in the vim-tiny package to allow a specific +configuration for vim-tiny's vi. The vim-tiny package is substantially +different from other Vim packages, so it does not make sense to +share the same config. + +Closes: #222138 +Signed-off-by: Stefano Zacchiroli <zack@debian.org> +Signed-off-by: James Vega <jamessan@debian.org> +--- + src/main.c | 23 ++++++++++++++++++++++- + src/os_unix.h | 3 +++ + src/structs.h | 3 +++ + 3 files changed, 28 insertions(+), 1 deletion(-) + +diff --git a/src/main.c b/src/main.c +index d1c42ed..c3e6bda 100644 +--- a/src/main.c ++++ b/src/main.c +@@ -1929,6 +1929,10 @@ parse_command_name(mparm_T *parmp) + } + else if (STRNICMP(initstr, "vim", 3) == 0) + initstr += 3; ++#ifdef SYS_TINYRC_FILE ++ else if (STRNICMP(initstr, "vi", 2) == 0) ++ parmp->vi_mode = TRUE; ++#endif + + // Catch "[r][g]vimdiff" and "[r][g]viewdiff". + if (STRICMP(initstr, "diff") == 0) +@@ -3224,7 +3228,12 @@ source_startup_scripts(mparm_T *parmp) + * Get system wide defaults, if the file name is defined. + */ + #ifdef SYS_VIMRC_FILE +- (void)do_source((char_u *)SYS_VIMRC_FILE, FALSE, DOSO_NONE, NULL); ++# if defined(SYS_TINYRC_FILE) && defined(TINY_VIMRC) ++ if (parmp->vi_mode) ++ (void)do_source((char_u *)SYS_TINYRC_FILE, FALSE, DOSO_NONE, NULL); ++ else ++# endif ++ (void)do_source((char_u *)SYS_VIMRC_FILE, FALSE, DOSO_NONE, NULL); + #endif + #ifdef MACOS_X + (void)do_source((char_u *)"$VIMRUNTIME/macmap.vim", FALSE, +@@ -3263,13 +3272,25 @@ source_startup_scripts(mparm_T *parmp) + #ifdef USR_EXRC_FILE2 + && do_source((char_u *)USR_EXRC_FILE2, FALSE, + DOSO_NONE, NULL) == FAIL ++#endif ++#if defined(SYS_TINYRC_FILE) && defined(TINY_VIMRC) ++ && !parmp->vi_mode + #endif + && !has_dash_c_arg) + { + // When no .vimrc file was found: source defaults.vim. + if (do_source((char_u *)VIM_DEFAULTS_FILE, FALSE, DOSO_NONE, + NULL) == FAIL) ++ { ++ /* ++ * If running as the vim.tiny executable, regardless how what argv[0] is, we ++ * don't want to error due to missing defaults.vim. That's provided by ++ * vim-runtime, which isn't typically installed with vim-tiny. ++ */ ++#ifndef TINY_VIMRC + emsg(e_failed_to_source_defaults); ++#endif ++ } + } + } + +diff --git a/src/os_unix.h b/src/os_unix.h +index d87ec90..3f5ce0f 100644 +--- a/src/os_unix.h ++++ b/src/os_unix.h +@@ -205,6 +205,9 @@ typedef struct dsc$descriptor DESC; + /* + * Unix system-dependent file names + */ ++#ifndef SYS_TINYRC_FILE ++# define SYS_TINYRC_FILE "$VIM/vimrc.tiny" ++#endif + #ifndef SYS_VIMRC_FILE + # define SYS_VIMRC_FILE "$VIM/vimrc" + #endif +diff --git a/src/structs.h b/src/structs.h +index 46a71cb..ac661a6 100644 +--- a/src/structs.h ++++ b/src/structs.h +@@ -4468,6 +4468,9 @@ typedef struct + #ifdef FEAT_DIFF + int diff_mode; // start with 'diff' set + #endif ++#ifdef SYS_TINYRC_FILE ++ int vi_mode; /* started as "vi" */ ++#endif + } mparm_T; + + /* diff --git a/debian/patches/patch-9.0.1499-using-uninitialized-memory-with-fuzzy-matc.patch b/debian/patches/patch-9.0.1499-using-uninitialized-memory-with-fuzzy-matc.patch new file mode 100644 index 0000000..92bc3b1 --- /dev/null +++ b/debian/patches/patch-9.0.1499-using-uninitialized-memory-with-fuzzy-matc.patch @@ -0,0 +1,147 @@ +From: Bram Moolenaar <Bram@vim.org> +Date: Sat, 29 Apr 2023 21:38:04 +0100 +Subject: patch 9.0.1499: using uninitialized memory with fuzzy matching + +Problem: Using uninitialized memory with fuzzy matching. +Solution: Initialize the arrays used to store match positions. + +Closes: #1035323 +--- + src/quickfix.c | 5 ++++- + src/search.c | 17 +++++++---------- + src/testdir/test_matchfuzzy.vim | 27 +++++++++++++++++++++++++++ + src/version.c | 2 ++ + 4 files changed, 40 insertions(+), 11 deletions(-) + +diff --git a/src/quickfix.c b/src/quickfix.c +index 63dd541..799c243 100644 +--- a/src/quickfix.c ++++ b/src/quickfix.c +@@ -6058,6 +6058,8 @@ vgr_match_buflines( + long lnum; + colnr_T col; + int pat_len = (int)STRLEN(spat); ++ if (pat_len > MAX_FUZZY_MATCHES) ++ pat_len = MAX_FUZZY_MATCHES; + + for (lnum = 1; lnum <= buf->b_ml.ml_line_count && *tomatch > 0; ++lnum) + { +@@ -6066,7 +6068,7 @@ vgr_match_buflines( + { + // Regular expression match + while (vim_regexec_multi(regmatch, curwin, buf, lnum, +- col, NULL) > 0) ++ col, NULL) > 0) + { + // Pass the buffer number so that it gets used even for a + // dummy buffer, unless duplicate_name is set, then the +@@ -6112,6 +6114,7 @@ vgr_match_buflines( + int_u sz = ARRAY_LENGTH(matches); + + // Fuzzy string match ++ CLEAR_FIELD(matches); + while (fuzzy_match(str + col, spat, FALSE, &score, matches, sz) > 0) + { + // Pass the buffer number so that it gets used even for a +diff --git a/src/search.c b/src/search.c +index 1e4464b..619032c 100644 +--- a/src/search.c ++++ b/src/search.c +@@ -4422,14 +4422,14 @@ fuzzy_match_recursive( + // Found match + if (vim_tolower(c1) == vim_tolower(c2)) + { +- int_u recursiveMatches[MAX_FUZZY_MATCHES]; +- int recursiveScore = 0; +- char_u *next_char; +- + // Supplied matches buffer was too short + if (nextMatch >= maxMatches) + return 0; + ++ int recursiveScore = 0; ++ int_u recursiveMatches[MAX_FUZZY_MATCHES]; ++ CLEAR_FIELD(recursiveMatches); ++ + // "Copy-on-Write" srcMatches into matches + if (first_match && srcMatches) + { +@@ -4438,10 +4438,7 @@ fuzzy_match_recursive( + } + + // Recursive call that "skips" this match +- if (has_mbyte) +- next_char = str + (*mb_ptr2len)(str); +- else +- next_char = str + 1; ++ char_u *next_char = str + (has_mbyte ? (*mb_ptr2len)(str) : 1); + if (fuzzy_match_recursive(fuzpat, next_char, strIdx + 1, + &recursiveScore, strBegin, strLen, matches, + recursiveMatches, +@@ -4506,8 +4503,8 @@ fuzzy_match_recursive( + * Uses char_u for match indices. Therefore patterns are limited to + * MAX_FUZZY_MATCHES characters. + * +- * Returns TRUE if 'pat_arg' matches 'str'. Also returns the match score in +- * 'outScore' and the matching character positions in 'matches'. ++ * Returns TRUE if "pat_arg" matches "str". Also returns the match score in ++ * "outScore" and the matching character positions in "matches". + */ + int + fuzzy_match( +diff --git a/src/testdir/test_matchfuzzy.vim b/src/testdir/test_matchfuzzy.vim +index 502d136..43eca8f 100644 +--- a/src/testdir/test_matchfuzzy.vim ++++ b/src/testdir/test_matchfuzzy.vim +@@ -2,6 +2,7 @@ + + source shared.vim + source check.vim ++source term_util.vim + + " Test for matchfuzzy() + func Test_matchfuzzy() +@@ -253,4 +254,30 @@ func Test_matchfuzzy_limit() + call assert_equal([{'id': 5, 'val': 'crayon'}], l->matchfuzzy('c', #{key: 'val', limit: 1})) + endfunc + ++" This was using uninitialized memory ++func Test_matchfuzzy_initialized() ++ CheckRunVimInTerminal ++ ++ " This can take a very long time (esp. when using valgrind). Run in a ++ " separate Vim instance and kill it after two seconds. We only check for ++ " memory errors. ++ let lines =<< trim END ++ lvimgrep [ss [fg* ++ END ++ call writefile(lines, 'XTest_matchfuzzy', 'D') ++ ++ let buf = RunVimInTerminal('-u NONE -X -Z', {}) ++ call term_sendkeys(buf, ":source XTest_matchfuzzy\n") ++ call TermWait(buf, 2000) ++ ++ let job = term_getjob(buf) ++ if job_status(job) == "run" ++ call job_stop(job, "int") ++ call TermWait(buf, 50) ++ endif ++ ++ " clean up ++ call StopVimInTerminal(buf) ++endfunc ++ + " vim: shiftwidth=2 sts=2 expandtab +diff --git a/src/version.c b/src/version.c +index c93499c..0e83a6f 100644 +--- a/src/version.c ++++ b/src/version.c +@@ -695,6 +695,8 @@ static char *(features[]) = + + static int included_patches[] = + { /* Add new patch number below this line */ ++/**/ ++ 1499, + /**/ + 1378, + /**/ diff --git a/debian/patches/series b/debian/patches/series new file mode 100644 index 0000000..6746de8 --- /dev/null +++ b/debian/patches/series @@ -0,0 +1,6 @@ +debian/Support-sourcing-a-vimrc.tiny-when-Vim-is-invoked-as-vi.patch +debian/Detect-the-rst-filetype-using-the-contents-of-the-file.patch +debian/Add-recognition-of-more-LaTeX-commands-for-tex-filetype-d.patch +debian/Document-Debian-s-decision-to-disable-modelines-by-defaul.patch +patch-9.0.1499-using-uninitialized-memory-with-fuzzy-matc.patch +Fix-GH-267-where-indent-after-a-sub-would-not-work.patch diff --git a/debian/policy/Makefile b/debian/policy/Makefile new file mode 100644 index 0000000..e5d7311 --- /dev/null +++ b/debian/policy/Makefile @@ -0,0 +1,23 @@ + +NULL = +INSTALL_STUFF = \ + vim-policy.html/ \ + vim-policy.txt \ + $(NULL) + +all: html text + +html: vim-policy.html/index.html +text: vim-policy.txt + +export LC_ALL=C.UTF-8 + +vim-policy.html/index.html: vim-policy.xml *.xml + docbook2html $< -o $(dir $@) +vim-policy.txt: vim-policy.xml *.xml + docbook2txt $< + +clean: + $(RM) -rf $(INSTALL_STUFF) + +.PHONY: html text diff --git a/debian/policy/authors.xml b/debian/policy/authors.xml new file mode 100644 index 0000000..f1d2a8b --- /dev/null +++ b/debian/policy/authors.xml @@ -0,0 +1,8 @@ +<author> + <affiliation> + <orgname>Debian VIM Maintainers</orgname> + <address> + <email>team+vim@tracker.debian.org</email> + </address> + </affiliation> +</author> diff --git a/debian/policy/legal.xml b/debian/policy/legal.xml new file mode 100644 index 0000000..e42705f --- /dev/null +++ b/debian/policy/legal.xml @@ -0,0 +1,34 @@ +<copyright> + <year>2007</year> + <year>2008</year> + <holder>Stefano Zacchiroli</holder> +</copyright> +<copyright> + <year>2021</year> + <holder>James McCoy</holder> +</copyright> +<legalnotice> + <para> + This manual is free software; you can redistribute it and/or modify + it under the terms of the GNU General Public License as published by + the Free Software Foundation; either version 2 of the License, or + (at your option) any later version. + </para> + <para> + This is distributed in the hope that it will be useful, but WITHOUT + ANY WARRANTY; without even the implied warranty of MERCHANTABILITY + or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public + License for more details. + </para> + <para> + A copy of the GNU General Public License is available as + <filename>/usr/share/common-licenses/GPL-2</filename> in the Debian + GNU/Linux distribution or on the World Wide Web at <ulink + url="https://www.gnu.org/licenses/old-licenses/gpl-2.0.html">The GNU Public + License</ulink>. + </para> + <para> + You can also obtain it by writing to the Free Software Foundation, + Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA. + </para> +</legalnotice> diff --git a/debian/policy/pages.yml b/debian/policy/pages.yml new file mode 100644 index 0000000..6134582 --- /dev/null +++ b/debian/policy/pages.yml @@ -0,0 +1,20 @@ +pages: + stage: publish + image: debian:unstable + needs: [] + before_script: + - apt-get -q update + - env DEBIAN_FRONTEND=noninteractive apt-get -q -y install docbook-utils docbook-xml make lynx + script: + - make -C debian/policy + - mkdir -p public + - cp -r debian/policy/vim-policy.txt public/ + - cp -r debian/policy/vim-policy.html/* public/ + rules: + - if: '$CI_PIPELINE_SOURCE == "push" && $CI_COMMIT_BRANCH == "debian/sid"' + changes: + - debian/policy/**/* + when: always + artifacts: + paths: + - public diff --git a/debian/policy/vim-policy.xml b/debian/policy/vim-policy.xml new file mode 100644 index 0000000..03e1408 --- /dev/null +++ b/debian/policy/vim-policy.xml @@ -0,0 +1,228 @@ +<?xml version="1.0"?> +<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" +"/usr/share/sgml/docbook/dtd/xml/4.3/docbookx.dtd" [ + <!ENTITY vim-version "8.2"> + <!ENTITY vim "<application>Vim</application>"> + <!ENTITY debian "Debian"> + + <!ENTITY authors SYSTEM "authors.xml"> + <!ENTITY legal SYSTEM "legal.xml"> +]> + +<article> + <articleinfo> + <title>Debian Packaging Policy for &vim;</title> + <releaseinfo>Version 2.0</releaseinfo> + &authors; + &legal; + </articleinfo> + + <section id="nutshell"> + <title>&vim; Addon Packaging in a Nutshell</title> + + <warning> <para> This section contains a brief howto of what to do to + package a &vim; addon (plugin, syntax definition, ...) in &debian;. + This section is not the full policy nor the guidelines for doing that; + have a look at the remainder of this document for such information. + </para> </warning> + + <para> So you've found on <ulink url="https://www.vim.org">vim.org</ulink> a + cool extra feature for your beloved editor (&vim;) and you want it to be + packaged in &debian;. It's as easy as implementing the following 4 steps: + + <orderedlist numeration="arabic"> + + <listitem> <para> create an <code>architecture: all</code> + <filename>.deb</filename> binary package called + <application>vim-<replaceable>ADDON</replaceable></application>, + where <replaceable>ADDON</replaceable> is the addon name. See <xref + linkend="addon-packages" /> for more info on this. </para> + </listitem> + + <listitem> <para> make your package ship all the files composing your + addon (usually <filename>.vim</filename> and + <filename>.txt</filename> files) under + <filename>/usr/share/vim-<replaceable>ADDON</replaceable>/</filename>. The files should be + shipped as a file and directory tree isomorphic to what you want to + see in a runtime &vim; directory. So if for example the addon + documentation says that something should be installed as + <filename>plugin/foo.vim</filename> then you should ship it as + <filename>/usr/share/vim-<replaceable>ADDON</replaceable>/plugin/foo.vim</filename>. See <xref + linkend="addon-structure" /> for more info on this. </para> + </listitem> + + <listitem> <para>create a + <filename>debian/vim-<replaceable>ADDON</replaceable>.vim-addon</filename> + specifying the files and/or directories making up the addon. If neovim is also supported, create + a corresponding <filename>debian/vim-<replaceable>ADDON</replaceable>.neovim-addon</filename> + for it, or a symlink if the same set of files are used. + + See the <command>dh_vim-addon</command> manual page, in the <application>dh-vim-addon</application> + package, for more details. </para> </listitem> + + <listitem> <para>add <code>Depends: ${vim-addon:Depends}</code> to the binary package stanzas.</para> </listitem> + + </orderedlist> + + That's it! Easy, isn't it? </para> + + </section> + + <section id="legacy-packaging"> + <title>&vim; Packaging</title> + + <para> Here you can find a brief overview of how the &vim; editor is + packaged in &debian; and a few concepts useful later; if you are + just interested in the guidelines for packaging addons skip to + <xref linkend="addon-packaging" />. </para> + + <para> The &vim; editor is split in &debian; as several binary + packages. The key splitting is according to variants, a &vim; + <emphasis>variant</emphasis> is a particular version of the + <filename>/usr/bin/vim</filename> executable built with a given + set of (<application>configure</application>) option. Examples of + variants provided in &debian; are: <ulink + url="https://packages.debian.org/unstable/editors/vim-tiny"><application>vim-tiny</application></ulink>, + <ulink + url="https://packages.debian.org/unstable/editors/vim"><application>vim</application></ulink>, + <ulink + url="https://packages.debian.org/unstable/editors/vim-nox"><application>vim-nox</application></ulink>, + <ulink + url="https://packages.debian.org/unstable/editors/vim-gtk3"><application>vim-gtk3</application></ulink>. + Have a look at their full descriptions for their characteristics. + The actual <filename>/usr/bin/vim</filename> file is managed via + the alternative mechanism and point to one of the variants. + </para> + + <para> Another relevant binary package is <ulink + url="https://packages.debian.org/unstable/editors/vim-runtime"><application>vim-runtime</application></ulink> + which ships the &vim; runtime environment distributed upstream together + with the editor. Almost all third party extensions to &vim; come as + additional pieces of this runtime environment, how to package them is the + main topic of this document. </para> + + <para> To be working properly extensions should be located somewhere where + &vim; can find them. This "somewhere" is expressed in &vim; as a list of + directories to be looked for in turn when looking for extensions. Such a + list is the <emphasis>&vim; runtime path</emphasis>, and is kept in the + &vim; global variable <envar>runtimepath</envar>; you can inspect it + executing <command>:set runtimepath?</command> inside &vim;. See <ulink + url="https://vimhelp.org/options.txt.html#'runtimepath'"><command>:help + 'runtimepath'</command></ulink> in the &vim; online help for more + information, including the relevant subdirectories which &vim; will look + for inside <emphasis>each</emphasis> component of the runtime path. + </para> + + <para> &vim; also has a concept of <emphasis>packages</emphasis>. A package + must follow a specific directory structure and be located in one of the + directories defined in the <envar>packpath</envar> option. Within each + package, there are two relevant directories: <variablelist> + + <varlistentry><term><emphasis>start</emphasis></term> + <listitem><para>All addons in this directory will automatically + be added to <envar>runtimepath</envar> and loaded like any other + addon that comes with &vim;. These are called + <emphasis>automatic</emphasis> addons.</para> </listitem> </varlistentry> + + <varlistentry><term><emphasis>opt</emphasis></term> + <listitem><para>Any addons in this directory must explicitly + be enabled by executing <command>:packadd! <replaceable>ADDON</replaceable></command> + in the user's vimrc. These are called <emphasis>optional</emphasis> addons. + </para> </listitem> </varlistentry> + </variablelist> </para> + </section> + + <section id="addon-packaging"> + <title>Packaging of &vim; Addons</title> + + <para> With the term (&vim;) <emphasis>addon</emphasis> we refer to an + extension for the &vim; editor which is not shipped with the editor + itself. Examples of addons which can be frequently found on the Internet + are color schemes, syntax and corresponding higlighting definitions for + new languages, indentation definitions, generic and filetype-specific + plugins, ... </para> + + <section id="addon-structure"> + <title>Addon Structure</title> + + <para> An addon is usually composed of a set of <filename>.vim</filename> + files; other kind of files, for example <filename>.txt</filename> files + for documentation purposes, can be provided as well. + + For instance, the following files compose the <ulink + url="https://www.vim.org/scripts/script.php?script_id=90"><application>vcscommand</application></ulink> + addon, providing plugins, syntax higlighting definitions, and + documentation: + + <example> <title>Files composing the + <application>vcscommand</application> addon</title> + <programlisting>doc/tags +doc/vcscommand.txt +plugin/vcsbzr.vim +plugin/vcscommand.vim +plugin/vcscvs.vim +plugin/vcsgit.vim +plugin/vcshg.vim +plugin/vcssvk.vim +plugin/vcssvn.vim +syntax/cvsannotate.vim +syntax/gitannotate.vim +syntax/hgannotate.vim +syntax/svkannotate.vim +syntax/svnannotate.vim +syntax/vcscommit.vim</programlisting> + </example> + + </para> + + <para> For an addon to work properly (and its plugins being automatically + loaded by &vim;) all its files should be installed under a unique directory + which will be added to &vim;'s pack path. In the example above, if + <filename>/usr/share/vim-vcscommand/</filename> is the chosen directory, + then <filename>SVNAnnotate.vim</filename> should be installed as + <filename>/usr/share/vim-vcscommand/syntax/SVNAnnotate.vim</filename>, + <filename>vcssvn.vim</filename> as + <filename>/usr/share/vim-vcscommand/plugin/vcssvn.vim</filename>, and so + on. </para> + + </section> + + <section id="addon-packages"> + <title>Addon Packages</title> + + <para> Each addon should be packaged and distributed in &debian; + as a separate package. It is recommended that the package is + named according to the naming convention + <application>vim-<replaceable>ADDON</replaceable> </application> + where <replaceable>ADDON</replaceable> is a name identifying the + packaged addon. </para> + + <para> Each binary package should contain a single addon installed as an + <emphasis>automatic</emphasis> addon. If the addon requires + heavy customization or is noticeably intrusive, it may be preferable + to install it as an <emphasis>optional</emphasis> addon.</para> + + <para> In some cases, it may make sense to aggregate multiple &vim; addons in + a single &debian; package. An example of such a suite is distributed as + the <ulink url="https://packages.qa.debian.org/vim-scripts"> + <application>vim-scripts</application> package</ulink>. + + In such cases, the addons should be installed as <emphasis>optional</emphasis> + addons so the user can choose which ones to enable. </para> + + </section> + </section> + + <section id="tools"> + <title>Tools</title> + + <para> <command>dh_vim-addons</command> is the tool used by maintainers + to install &vim; addons into the appropriate runtime path. It is shipped in the <ulink + url="https://packages.qa.debian.org/dh-vim-addon"><application>dh-vim-addon</application></ulink> + package. It will ensure that the addons are installed in to the correct + <envar>packpath</envar>, based on whether it is an <emphasis>automatic</emphasis> + or <emphasis>optional</emphasis> addon, and which editors are supported. </para> + + </section> + +</article> diff --git a/debian/rules b/debian/rules new file mode 100755 index 0000000..4c4f8e6 --- /dev/null +++ b/debian/rules @@ -0,0 +1,348 @@ +#!/usr/bin/make -f + +export DH_OPTIONS + +# Upstream handles the _FORTIFY_SOURCE flag on their own +DEB_BUILD_MAINT_OPTIONS = hardening=+all,-fortify future=+lfs + +include /usr/share/dpkg/default.mk + +BUILDER = team+vim@tracker.debian.org + +MAKETEST = no +ifeq ($(DEB_HOST_GNU_TYPE),$(DEB_BUILD_GNU_TYPE)) + ifeq (,$(filter nocheck,$(DEB_BUILD_OPTIONS))) + MAKETEST = yes + endif +endif + +ifneq (,$(filter parallel=%,$(DEB_BUILD_OPTIONS))) + NUMJOBS = $(patsubst parallel=%,%,$(filter parallel=%,$(DEB_BUILD_OPTIONS))) + MAKEFLAGS += -j$(NUMJOBS) +endif + +ifneq (,$(filter pkg.vim.noruby,$(DEB_BUILD_PROFILES))) + RUBY_SUBSTVARS = -Vvim:Ruby-Provides= -Vvim:Ruby-Desc= + RUBY_CFGFLAGS = --disable-ruby +else ifneq (,$(filter alpha ia64,$(DEB_HOST_ARCH))) + # Disable ruby on these architectures at the request of porters (c.f., #983308) + RUBY_SUBSTVARS = -Vvim:Ruby-Provides= -Vvim:Ruby-Desc= + RUBY_CFGFLAGS = --disable-rubyinterp +else + RUBY_SUBSTVARS = -Vvim:Ruby-Provides='vim-ruby (= $${binary:Version})' -Vvim:Ruby-Desc=' Ruby,' + RUBY_CFGFLAGS = --enable-rubyinterp +endif + +CFGFLAGS = --prefix=/usr --mandir='$${prefix}'/share/man --without-local-dir +CFGFLAGS += --with-modified-by="$(BUILDER)" +CFGFLAGS += --with-compiledby="$(BUILDER)" +CFGFLAGS += --enable-fail-if-missing +CFGFLAGS += --with-global-runtime='/var/lib/vim/addons,/etc/vim,$$VIM/vimfiles' + +TINYFLAGS = --with-features=small +TINYFLAGS += --disable-gui +TINYFLAGS += --disable-xsmp +TINYFLAGS += --disable-xsmp-interact +TINYFLAGS += --disable-netbeans +TINYFLAGS += --disable-gpm +TINYFLAGS += --enable-nls +TINYFLAGS += --enable-acl +TINYFLAGS += --disable-terminal +TINYFLAGS += --disable-canberra +TINYFLAGS += --disable-libsodium + +OPTFLAGS = --enable-cscope +ifeq ($(DEB_HOST_ARCH_OS),linux) + OPTFLAGS += --enable-gpm + OPTFLAGS += --enable-selinux --disable-smack + TINYFLAGS += --enable-selinux --disable-smack +else + OPTFLAGS += --disable-gpm +endif +OPTFLAGS += --with-features=huge +OPTFLAGS += --enable-acl +OPTFLAGS += --enable-terminal +OPTFLAGS += --enable-libsodium + +NOXFLAGS = --without-x +NOXFLAGS += --enable-gui=no +NOXFLAGS += --disable-canberra + +GUIFLAGS = --with-x +GUIFLAGS += --enable-xim +GUIFLAGS += --enable-canberra + +GTK3FLAGS = --enable-gui=gtk3 +GTK3FLAGS += --enable-gtk3-check +GTK3FLAGS += --disable-gnome-check +GTK3FLAGS += --disable-motif-check +GTK3FLAGS += --disable-motif-check +GTK3FLAGS += --disable-fontset + +MOTIFFLAGS = --enable-gui=motif +MOTIFFLAGS += --disable-gtk2-check +MOTIFFLAGS += --disable-gtk3-check +MOTIFFLAGS += --disable-gnome-check +MOTIFFLAGS += --disable-motif-check +MOTIFFLAGS += --enable-motif-check +MOTIFFLAGS += --enable-fontset + +NOINTERPFLAGS = --disable-luainterp +NOINTERPFLAGS += --disable-mzschemeinterp +NOINTERPFLAGS += --disable-perlinterp +ifeq ($(DEB_VENDOR),Ubuntu) + NOINTERPFLAGS += --enable-python3interp --with-python3-config-dir=$(shell python3-config --configdir) + NOINTERPFLAGS += --disable-pythoninterp +else + NOINTERPFLAGS += --disable-pythoninterp + NOINTERPFLAGS += --disable-python3interp +endif +NOINTERPFLAGS += --disable-rubyinterp +NOINTERPFLAGS += --disable-tclinterp + +ALLINTERPFLAGS = --enable-luainterp +ALLINTERPFLAGS += --disable-mzschemeinterp +ALLINTERPFLAGS += --enable-perlinterp +ALLINTERPFLAGS += --enable-python3interp --with-python3-config-dir=$(shell python3-config --configdir) +ALLINTERPFLAGS += --disable-pythoninterp +ALLINTERPFLAGS += --enable-tclinterp +ALLINTERPFLAGS += --with-tclsh=/usr/bin/tclsh + +# Each vim-xxx package is said to be a vim variant and contains only a vim +# binary built with some compile-time options. Makefile VARIANTS below are +# one-to-one with those packages with the exception of "vim-basic". In this +# Makefile vim-basic is used to build 4 packages: "vim", "vim-runtime", +# "vim-common", "vim-gui-common". "vim-tiny" is the only variant package not +# depending on vim-runtime. + +VARIANTS += vim-tiny +VARIANTS += vim-gtk3 +VARIANTS += vim-motif +VARIANTS += vim-nox +VARIANTS += vim-basic + +ifneq ($(origin VARIANT), undefined) + VARIANTS = $(VARIANT) vim-basic +endif + +CFLAGS += -DSYS_VIMRC_FILE="'\"/etc/vim/vimrc\"'" -DSYS_GVIMRC_FILE="'\"/etc/vim/gvimrc\"'" + +CFLAGS_vim-basic = $(CFLAGS) +CFGFLAGS_vim-basic = $(CFGFLAGS) $(OPTFLAGS) $(NOXFLAGS) $(NOINTERPFLAGS) + +CFLAGS_vim-tiny = $(CFLAGS) -DTINY_VIMRC -DSYS_TINYRC_FILE="'\"/etc/vim/vimrc.tiny\"'" +CFGFLAGS_vim-tiny = $(CFGFLAGS) $(TINYFLAGS) + +CFLAGS_vim-gtk3 = $(CFLAGS) +CFGFLAGS_vim-gtk3 = $(CFGFLAGS) $(OPTFLAGS) $(GUIFLAGS) $(ALLINTERPFLAGS) $(GTK3FLAGS) $(RUBY_CFGFLAGS) + +CFLAGS_vim-motif = $(CFLAGS) +CFGFLAGS_vim-motif = $(CFGFLAGS) $(OPTFLAGS) $(GUIFLAGS) $(MOTIFFLAGS) $(ALLINTERPFLAGS) $(RUBY_CFGFLAGS) + +CFLAGS_vim-nox = $(CFLAGS) +CFGFLAGS_vim-nox = $(CFGFLAGS) $(OPTFLAGS) $(NOXFLAGS) $(ALLINTERPFLAGS) $(RUBY_CFGFLAGS) + +NAME = vim +# Convert x.y.z to x.y +VERSION = $(basename $(DEB_VERSION_UPSTREAM)) +VIMCUR = $(NAME)$(subst .,,$(VERSION)) +LANGS = da de fr it ja pl ru tr + +DOT_IN_DEPS = debian/vim-runtime.postrm +DOT_IN_DEPS += debian/vim-runtime.preinst +DOT_IN_DEPS_TINY = debian/tiny/vimrc.tiny + +foreach-variant = \ + set -e; for v in $(VARIANTS); do \ + $1; \ + done + +%: + dh $@ + +update-changelog: + dh_testdir + wget -O debian/changelog.upstream http://ftp.vim.org/pub/vim/patches/$(VERSION)/README + +override_dh_auto_clean: + [ ! -f src/auto/config.cache ] || make distclean + [ ! -f debian/configure.dist ] || mv debian/configure.dist src/auto/configure + find src/testdir -name '*.pyc' -delete + for v in $(VARIANTS); do \ + if [ "$${v}" = vim-basic ]; then \ + [ ! -L src/"$${v}"/po ] || $(MAKE) -C src/"$${v}"/po clean; \ + fi; \ + rm -rf src/"$${v}"; \ + done + rm -f $(DOT_IN_DEPS) + rm -f $(DOT_IN_DEPS_TINY) + +override_dh_auto_configure-indep: autoconf-stamp + $(MAKE) -f debian/rules configure-vim-basic + +override_dh_auto_configure-arch: autoconf-stamp + $(call foreach-variant, $(MAKE) -f debian/rules configure-"$${v}") + +override_dh_auto_build-indep: autoconf-stamp +override_dh_auto_build-indep: + $(MAKE) -f debian/rules build-vim-basic + $(MAKE) -C runtime/doc html + $(MAKE) -C debian/policy text html + $(MAKE) -C src/po vim.pot VIM=$(CURDIR)/src/vim-basic/vim + +override_dh_auto_build-arch: autoconf-stamp + $(call foreach-variant, $(MAKE) -f debian/rules build-"$${v}") + $(MAKE) -C src/vim-basic xxd/xxd + +override_dh_auto_test-indep: + +override_dh_auto_test-arch: + $(call foreach-variant, $(MAKE) -f debian/rules test-"$${v}") + +autoconf-stamp: + dh_testdir + [ -f debian/configure.dist ] || cp src/auto/configure debian/configure.dist +# The autoconf target generates a new configure, and touches some other +# configure-related things. Need to run scratch afterward or timestamps +# will be off and the next make that runs will think it needs to run +# configure. This breaks parallel builds since two configures are being run +# in the same directory at the same time instead of in their own shadow +# directories. + $(MAKE) -C src autoconf + $(MAKE) -C src scratch + touch $@ + +src/vim-%: VARIANT=vim-$* +src/vim-%: + $(MAKE) -C src shadow SHADOWDIR=$(VARIANT) + +configure-vim-%: VARIANT=vim-$* +configure-vim-%: autoconf-stamp +configure-vim-%: + $(MAKE) -f debian/rules src/$(VARIANT) + cd src/$(VARIANT) && LDFLAGS="$(LDFLAGS)" CPPFLAGS="$(CPPFLAGS)" CFLAGS="$(CFLAGS_$(VARIANT))" ./configure $(CFGFLAGS_$(VARIANT)) + +build-vim-%: VARIANT=vim-$* +build-vim-%: configure-$(VARIANT) +build-vim-%: + $(MAKE) -C src/$(VARIANT) + $(MAKE) -C runtime/doc tags VIMEXE=$(CURDIR)/src/$(VARIANT)/vim + +test-vim-%: VARIANT=vim-$* +test-vim-%: + : +ifeq (yes,$(MAKETEST)) +# Sanitize LC_* env so they don't leak through to child processes and cause problems in build chroots (e.g., missing locales) +# and set sane values for TERM/LC_ALL/LANG + for e in ADDRESS COLLATE CTYPE IDENTIFICATION MEASUREMENT MESSAGES MONETARY NAME NUMERIC PAPER TELEPHONE TIME; do \ + unset LC_$${e}; \ + done; \ + env TERM=xterm LC_ALL=C.UTF-8 LANG=C.UTF-8 $(MAKE) -j1 -C src/$(VARIANT) test +endif + +override_dh_auto_install-arch: + +# Use UTF-8 manpages for all languages +# If a .UTF-8 directory doesn't exist, then the $L directory is already UTF-8. +define munge-man-directories +for L in $(LANGS); do \ + if [ -d "$(DESTDIR)/usr/share/man/$$L.UTF-8" ]; then \ + rm -rf "$(DESTDIR)/usr/share/man/$$L"; \ + mv "$(DESTDIR)/usr/share/man/$$L.UTF-8" "$(DESTDIR)/usr/share/man/$$L"; \ + fi; \ + rm -rf "$(DESTDIR)/usr/share/man/$$L."*; \ +done +endef + +override_dh_auto_install-indep: DESTDIR=$(CURDIR)/debian/tmp +override_dh_auto_install-indep: + $(MAKE) -f debian/rules build-vim-basic + mkdir -p "$(DESTDIR)/usr/bin" + # installruntime requires a "vim" in /usr/bin + cp src/vim-basic/vim "$(DESTDIR)/usr/bin" + $(MAKE) -C src/vim-basic "DESTDIR=$(DESTDIR)" \ + installtutorbin \ + installgtutorbin \ + installruntime \ + install-languages \ + install-icons + rm -f "$(DESTDIR)/usr/bin/vim" + +override_dh_install-indep: DESTDIR=$(CURDIR)/debian/tmp +override_dh_install-indep: + $(MAKE) -f debian/rules $(DOT_IN_DEPS) + $(munge-man-directories) + + # rm stuff handled by alternatives or our own symlinks + find "$(DESTDIR)/usr/share/man" \( -name view.1 -o -name ex.1 -o -name rvim.1 -o -name rview.1 \) -delete + + # helpztags manpage + pod2man -c "User Commands" -s 1 -q none -r "vim $(VERSION)" \ + -d "August 2010" debian/helpztags debian/helpztags.1 + + # Icons + gs -sDefaultCMYKProfile=ps_cmyk.icc -sOutputICCProfile=ps_rgb.icc \ + -dSAFER -dEPSCrop -dBATCH -dNOPAUSE \ + -sDEVICE=ps2write -sOutputFile=debian/tmplogo.ps runtime/vimlogo.eps + ps2pdf debian/tmplogo.ps debian/tmplogo.pdf + pdf2svg debian/tmplogo.pdf debian/vim-common/usr/share/icons/hicolor/scalable/apps/gvim.svg + + env VIMCUR=$(VIMCUR) dh_install -X vim2html.pl -X 'README*.txt' -X README.el.txt -X README.el.cp737.txt + # adjust things for vim-gui-common + cp debian/vim-common/usr/share/man/man1/vim.1 \ + debian/vim-gui-common/usr/share/man/man1/gvim.1 + cp debian/vim-common/usr/share/man/man1/vimdiff.1 \ + debian/vim-gui-common/usr/share/man/man1/gvimdiff.1 + cp debian/vim-runtime/usr/share/man/man1/vimtutor.1 \ + debian/vim-gui-common/usr/share/man/man1/gvimtutor.1 + for L in $(LANGS); do \ + DIR=usr/share/man/$$L; \ + [ ! -e "debian/vim-common/$$DIR/man1/vim.1" ] || \ + cp debian/vim-common/$$DIR/man1/vim.1 \ + debian/vim-gui-common/$$DIR/man1/gvim.1; \ + [ ! -e "debian/vim-common/$$DIR/man1/vimdiff.1" ] || \ + cp debian/vim-common/$$DIR/man1/vimdiff.1 \ + debian/vim-gui-common/$$DIR/man1/gvimdiff.1; \ + [ ! -e "debian/vim-runtime/$$DIR/man1/vimtutor.1" ] || \ + cp debian/vim-runtime/$$DIR/man1/vimtutor.1 \ + debian/vim-gui-common/$$DIR/man1/gvimtutor.1; \ + done + +override_dh_installchangelogs: + dh_installchangelogs -A debian/changelog.upstream + +install-xxd: DESTDIR=$(CURDIR)/debian/xxd +install-xxd: + $(MAKE) -C src/vim-basic STRIP=: DESTDIR=$(DESTDIR) installtools install-tool-languages + rm -r $(DESTDIR)/usr/share/vim + $(munge-man-directories) + # No xxd.1 translations for these languages yet + for lang in da de tr.ISO8859-9 tr.UTF-8 tr; do \ + rmdir $(DESTDIR)/usr/share/man/$$lang/man1 $(DESTDIR)/usr/share/man/$$lang; \ + done + +override_dh_auto_install-arch: + $(MAKE) -f debian/rules install-xxd + +override_dh_bugfiles: + $(call foreach-variant, dh_bugfiles -A -p "$${v%-basic}") + +install-vim-%: SHADOWDIR=vim-$* +install-vim-%: VARIANT=$* +install-vim-%: BIN=$(subst -,.,vim-$(VARIANT)) +install-vim-%: + cp src/$(SHADOWDIR)/vim src/$(SHADOWDIR)/$(BIN) + [ $(VARIANT) != tiny ] || $(MAKE) -f debian/rules $(DOT_IN_DEPS_TINY) + +override_dh_install-arch: + $(call foreach-variant, $(MAKE) -f debian/rules install-$${v}) + env VIMCUR=$(VIMCUR) dh_install + +$(DOT_IN_DEPS) $(DOT_IN_DEPS_TINY): %: %.in + cat $< | sed 's/@VIMCUR@/$(VIMCUR)/' > $@ + +override_dh_gencontrol: + dh_gencontrol -- $(RUBY_SUBSTVARS) + +.NOTPARALLEL: +# vim: set foldmethod=marker: diff --git a/debian/runtime/debian.vim b/debian/runtime/debian.vim new file mode 100644 index 0000000..0856148 --- /dev/null +++ b/debian/runtime/debian.vim @@ -0,0 +1,50 @@ +" Normally we use vim-extensions. If you want true vi-compatibility +" remove change the following statements +set nocompatible " Use Vim defaults instead of 100% vi compatibility +set backspace=indent,eol,start " more powerful backspacing + +" Now we set some defaults for the editor +set history=50 " keep 50 lines of command line history +set ruler " show the cursor position all the time + +" modelines have historically been a source of security/resource +" vulnerabilities -- disable by default, even when 'nocompatible' is set +set nomodeline + +" Suffixes that get lower priority when doing tab completion for filenames. +" These are files we are not likely to want to edit or read. +set suffixes=.bak,~,.swp,.o,.info,.aux,.log,.dvi,.bbl,.blg,.brf,.cb,.ind,.idx,.ilg,.inx,.out,.toc + +" We know xterm-debian is a color terminal +if &term =~ "xterm-debian" || &term =~ "xterm-xfree86" + set t_Co=16 + set t_Sf=[3%dm + set t_Sb=[4%dm +endif + +" Some Debian-specific things +if has('gui') + " Must define this within the :if so it does not cause problems with + " vim-tiny (which does not have +eval) + function! <SID>MapExists(name, modes) + for mode in split(a:modes, '\zs') + if !empty(maparg(a:name, mode)) + return 1 + endif + endfor + return 0 + endfunction + + " Make shift-insert work like in Xterm + autocmd GUIEnter * if !<SID>MapExists("<S-Insert>", "nvso") | execute "map <S-Insert> <MiddleMouse>" | endif + autocmd GUIEnter * if !<SID>MapExists("<S-Insert>", "ic") | execute "map! <S-Insert> <MiddleMouse>" | endif +endif + +" Set paper size from /etc/papersize if available (Debian-specific) +if filereadable("/etc/papersize") + let s:papersize = matchstr(readfile('/etc/papersize', '', 1), '\p*') + if strlen(s:papersize) + exe "set printoptions+=paper:" . s:papersize + endif +endif + diff --git a/debian/runtime/gvimrc b/debian/runtime/gvimrc new file mode 100644 index 0000000..3aaea15 --- /dev/null +++ b/debian/runtime/gvimrc @@ -0,0 +1,17 @@ +" Make external commands work through a pipe instead of a pseudo-tty +"set noguipty + +" You can also specify a different font, overriding the default font +"if has('gui_gtk') +" set guifont=Bitstream\ Vera\ Sans\ Mono\ 12 +"else +" set guifont=-misc-fixed-medium-r-normal--14-130-75-75-c-70-iso8859-1 +"endif + +" If you want to run gvim with a dark background, try using a different +" colorscheme or running 'gvim -reverse'. + +" Source a global configuration file if available +if filereadable("/etc/vim/gvimrc.local") + source /etc/vim/gvimrc.local +endif diff --git a/debian/runtime/vimrc b/debian/runtime/vimrc new file mode 100644 index 0000000..21b7c1c --- /dev/null +++ b/debian/runtime/vimrc @@ -0,0 +1,62 @@ +" $VIMRUNTIME refers to the versioned system directory where Vim stores its +" system runtime files -- /usr/share/vim/vim<version>. +" +" Vim will load $VIMRUNTIME/defaults.vim if the user does not have a vimrc. +" This happens after /etc/vim/vimrc(.local) are loaded, so it will override +" any settings in these files. +" +" If you don't want that to happen, uncomment the below line to prevent +" defaults.vim from being loaded. +" let g:skip_defaults_vim = 1 +" +" If you would rather _use_ default.vim's settings, but have the system or +" user vimrc override its settings, then uncomment the line below. +" source $VIMRUNTIME/defaults.vim + +" All Debian-specific settings are defined in $VIMRUNTIME/debian.vim and +" sourced by the call to :runtime you can find below. If you wish to change +" any of those settings, you should do it in this file or +" /etc/vim/vimrc.local, since debian.vim will be overwritten everytime an +" upgrade of the vim packages is performed. It is recommended to make changes +" after sourcing debian.vim so your settings take precedence. + +runtime! debian.vim + +" Uncomment the next line to make Vim more Vi-compatible +" NOTE: debian.vim sets 'nocompatible'. Setting 'compatible' changes +" numerous options, so any other options should be set AFTER changing +" 'compatible'. +"set compatible + +" Vim5 and later versions support syntax highlighting. Uncommenting the next +" line enables syntax highlighting by default. +"syntax on + +" If using a dark background within the editing area and syntax highlighting +" turn on this option as well +"set background=dark + +" Uncomment the following to have Vim jump to the last position when +" reopening a file +"au BufReadPost * if line("'\"") > 1 && line("'\"") <= line("$") | exe "normal! g'\"" | endif + +" Uncomment the following to have Vim load indentation rules and plugins +" according to the detected filetype. +"filetype plugin indent on + +" The following are commented out as they cause vim to behave a lot +" differently from regular Vi. They are highly recommended though. +"set showcmd " Show (partial) command in status line. +"set showmatch " Show matching brackets. +"set ignorecase " Do case insensitive matching +"set smartcase " Do smart case matching +"set incsearch " Incremental search +"set autowrite " Automatically save before commands like :next and :make +"set hidden " Hide buffers when they are abandoned +"set mouse=a " Enable mouse usage (all modes) + +" Source a global configuration file if available +if filereadable("/etc/vim/vimrc.local") + source /etc/vim/vimrc.local +endif + diff --git a/debian/salsa-ci.yml b/debian/salsa-ci.yml new file mode 100644 index 0000000..ffb1ebe --- /dev/null +++ b/debian/salsa-ci.yml @@ -0,0 +1,8 @@ +include: + - local: '/debian/policy/pages.yml' + - remote: 'https://salsa.debian.org/salsa-ci-team/pipeline/raw/master/recipes/debian.yml' + +variables: + SALSA_CI_DISABLE_REPROTEST: 1 + SALSA_CI_BLHC_ARGS: --ignore-flag -D_FORTIFY_SOURCE=2 --ignore-line .*doctags.* + SALSA_CI_DISABLE_CROSSBUILD_ARM64: 1 diff --git a/debian/source/format b/debian/source/format new file mode 100644 index 0000000..163aaf8 --- /dev/null +++ b/debian/source/format @@ -0,0 +1 @@ +3.0 (quilt) diff --git a/debian/source/lintian-overrides b/debian/source/lintian-overrides new file mode 100644 index 0000000..d93d373 --- /dev/null +++ b/debian/source/lintian-overrides @@ -0,0 +1,4 @@ +# vim-tiny provides stub help.txt/tags which are diverted when vim-runtime is +# installed +vim source: binaries-have-file-conflict vim-runtime vim-tiny usr/share/vim/vim*/doc/help.txt +vim source: binaries-have-file-conflict vim-runtime vim-tiny usr/share/vim/vim*/doc/tags diff --git a/debian/tests/control b/debian/tests/control new file mode 100644 index 0000000..fd5ed50 --- /dev/null +++ b/debian/tests/control @@ -0,0 +1,15 @@ +Test-Command: ./debian/tests/variants --version +Depends: @ +Restrictions: superficial + +Test-Command: ./debian/tests/upstreamtest /usr/bin/vim +Depends: vim, cscope, procps, python3, xxd +Restrictions: needs-root, allow-stderr, flaky + +Test-Command: ./debian/tests/upstreamtest /usr/bin/vim +Depends: vim-nox, cscope, procps, xxd +Restrictions: needs-root, allow-stderr, flaky + +Test-Command: ./debian/tests/upstreamtest /usr/bin/vi +Depends: vim-tiny, xxd +Restrictions: needs-root, allow-stderr, flaky diff --git a/debian/tests/upstreamtest b/debian/tests/upstreamtest new file mode 100755 index 0000000..6dc0a8d --- /dev/null +++ b/debian/tests/upstreamtest @@ -0,0 +1,11 @@ +#!/bin/sh +set -e + +if [ -z "$AUTOPKGTEST_NORMAL_USER" ]; then + adduser --quiet --disabled-login --gecos '' vim-ci + AUTOPKGTEST_NORMAL_USER=vim-ci +fi + +cp -a "$(pwd)" "$AUTOPKGTEST_TMP"/vim +chown -R "$AUTOPKGTEST_NORMAL_USER" "$AUTOPKGTEST_TMP"/vim +runuser -u "$AUTOPKGTEST_NORMAL_USER" -- env TERM=xterm make -C "$AUTOPKGTEST_TMP"/vim/src/testdir VIMPROG="$1" XXDPROG=/usr/bin/xxd SCRIPTSOURCE="$(pwd)"/runtime diff --git a/debian/tests/variants b/debian/tests/variants new file mode 100755 index 0000000..71e4164 --- /dev/null +++ b/debian/tests/variants @@ -0,0 +1,7 @@ +#!/bin/sh +set -eu + +for variant in /usr/bin/vim.* +do + $variant "$@" +done diff --git a/debian/tiny/doc/README.Debian b/debian/tiny/doc/README.Debian new file mode 100644 index 0000000..7e7bfc3 --- /dev/null +++ b/debian/tiny/doc/README.Debian @@ -0,0 +1,7 @@ + +This directory contains Debian-specific fake help files and tags used by +the "vim-tiny" package. Their only purpose is to tell the user how to +install the real VIM online help on Debian if she wants to (i.e. +installing the "vim-runtime" package). + + -- Stefano Zacchiroli <zack@debian.org> Thu, 03 Nov 2005 22:16:23 +0100 diff --git a/debian/tiny/doc/help.txt b/debian/tiny/doc/help.txt new file mode 100644 index 0000000..49970b8 --- /dev/null +++ b/debian/tiny/doc/help.txt @@ -0,0 +1,37 @@ +*help.txt* Vim + + VIM - fake help file for vim-tiny + +The Vim online help is not installed on this Debian GNU/Linux system. + +WHY ? + +Because only the "vim-tiny" package is installed, whose sole purpose is to +provide the vi command for base installations. As such, it contains a minimal +version of Vim compiled with no graphical user interface and a small subset of +features, in order to keep the package size small. + +Since the "vim-runtime" package is rather huge when compared to "vim-tiny", +installing the latter does not automatically install the former. + +HOW TO GET A BETTER VIM + +To get a more featureful Vim binary (and a vim command, rather than just vi), +install one of the following packages: vim, vim-nox, vim-motif, or vim-gtk3. + +HOW TO OBTAIN HELP + +Either browse the Vim online help via web starting at + + https://vimhelp.org/ + +or ask your administrator to install the "vim-doc" package, which contains the + HTML version of the online help and browse it starting at + + /usr/share/doc/vim/html/index.html + +or ask your administrator to install the "vim-runtime" package, re-run vi, and + access the online help again. Note that all the above mentioned Vim + variants other than "vim-tiny" automatically install the "vim-runtime" + package. If you don't suffer from disk space shortage using one of them is + recommended. diff --git a/debian/tiny/doc/tags b/debian/tiny/doc/tags new file mode 100644 index 0000000..f57fbe5 --- /dev/null +++ b/debian/tiny/doc/tags @@ -0,0 +1 @@ +help.txt help.txt /*help.txt* diff --git a/debian/tiny/vimrc.tiny.in b/debian/tiny/vimrc.tiny.in new file mode 100644 index 0000000..eac14a2 --- /dev/null +++ b/debian/tiny/vimrc.tiny.in @@ -0,0 +1,13 @@ +" Vim configuration file, in effect when invoked as "vi". The aim of this +" configuration file is to provide a Vim environment as compatible with the +" original vi as possible. Note that ~/.vimrc configuration files as other +" configuration files in the runtimepath are still sourced. +" When Vim is invoked differently ("vim", "view", "evim", ...) this file is +" _not_ sourced; /etc/vim/vimrc and/or /etc/vim/gvimrc are. + +" Debian system-wide default configuration Vim +set runtimepath=~/.vim,/var/lib/vim/addons,/usr/share/vim/vimfiles,/usr/share/vim/@VIMCUR@,/usr/share/vim/vimfiles/after,/var/lib/vim/addons/after,~/.vim/after + +set compatible + +" vim: set ft=vim: diff --git a/debian/vim-common.dirs b/debian/vim-common.dirs new file mode 100644 index 0000000..6e4c8d7 --- /dev/null +++ b/debian/vim-common.dirs @@ -0,0 +1,15 @@ +/etc/ +/usr/bin/ +/usr/share/applications/ +/usr/share/icons/hicolor/48x48/apps/ +/usr/share/icons/hicolor/scalable/apps/ +/usr/share/icons/locolor/16x16/apps/ +/usr/share/icons/locolor/32x32/apps/ +/usr/share/man/da/man1/ +/usr/share/man/fr/man1/ +/usr/share/man/it/man1/ +/usr/share/man/ja/man1/ +/usr/share/man/man1/ +/usr/share/man/pl/man1/ +/usr/share/man/ru/man1/ +/var/lib/vim/addons/ diff --git a/debian/vim-common.install b/debian/vim-common.install new file mode 100644 index 0000000..fb67e07 --- /dev/null +++ b/debian/vim-common.install @@ -0,0 +1,22 @@ +debian/helpztags usr/bin/ +debian/runtime/debian.vim usr/share/vim/${env:VIMCUR}/ +debian/runtime/vimrc etc/vim/ +usr/share/applications/vim.desktop +usr/share/icons/ +usr/share/man/da/man1/vim.1 +usr/share/man/da/man1/vimdiff.1 +usr/share/man/de/man1/vim.1 +usr/share/man/fr/man1/vim.1 +usr/share/man/fr/man1/vimdiff.1 +usr/share/man/it/man1/vim.1 +usr/share/man/it/man1/vimdiff.1 +usr/share/man/ja/man1/vim.1 +usr/share/man/ja/man1/vimdiff.1 +usr/share/man/man1/vim.1 +usr/share/man/man1/vimdiff.1 +usr/share/man/pl/man1/vim.1 +usr/share/man/pl/man1/vimdiff.1 +usr/share/man/ru/man1/vim.1 +usr/share/man/ru/man1/vimdiff.1 +usr/share/man/tr/man1/vim.1 +usr/share/man/tr/man1/vimdiff.1 diff --git a/debian/vim-common.links b/debian/vim-common.links new file mode 100644 index 0000000..d55b48c --- /dev/null +++ b/debian/vim-common.links @@ -0,0 +1,16 @@ +usr/share/man/da/man1/vim.1 usr/share/man/da/man1/rview.1 +usr/share/man/da/man1/vim.1 usr/share/man/da/man1/rvim.1 +usr/share/man/de/man1/vim.1 usr/share/man/de/man1/rview.1 +usr/share/man/de/man1/vim.1 usr/share/man/de/man1/rvim.1 +usr/share/man/fr/man1/vim.1 usr/share/man/fr/man1/rview.1 +usr/share/man/fr/man1/vim.1 usr/share/man/fr/man1/rvim.1 +usr/share/man/it/man1/vim.1 usr/share/man/it/man1/rview.1 +usr/share/man/it/man1/vim.1 usr/share/man/it/man1/rvim.1 +usr/share/man/ja/man1/vim.1 usr/share/man/ja/man1/rview.1 +usr/share/man/ja/man1/vim.1 usr/share/man/ja/man1/rvim.1 +usr/share/man/man1/vim.1 usr/share/man/man1/rview.1 +usr/share/man/man1/vim.1 usr/share/man/man1/rvim.1 +usr/share/man/pl/man1/vim.1 usr/share/man/pl/man1/rview.1 +usr/share/man/pl/man1/vim.1 usr/share/man/pl/man1/rvim.1 +usr/share/man/ru/man1/vim.1 usr/share/man/ru/man1/rview.1 +usr/share/man/ru/man1/vim.1 usr/share/man/ru/man1/rvim.1 diff --git a/debian/vim-common.lintian-overrides b/debian/vim-common.lintian-overrides new file mode 100644 index 0000000..b378380 --- /dev/null +++ b/debian/vim-common.lintian-overrides @@ -0,0 +1,5 @@ +# Provided by vim (virtual) packages +vim-common binary: desktop-command-not-in-package vim [usr/share/applications/vim.desktop] + +# Provided by vim (virtual) packages +vim-common binary: spare-manual-page diff --git a/debian/vim-common.manpages b/debian/vim-common.manpages new file mode 100644 index 0000000..81e7645 --- /dev/null +++ b/debian/vim-common.manpages @@ -0,0 +1 @@ +debian/helpztags.1 diff --git a/debian/vim-common.mime b/debian/vim-common.mime new file mode 100644 index 0000000..b2b30dd --- /dev/null +++ b/debian/vim-common.mime @@ -0,0 +1,4 @@ +text/plain; view %s; edit=vim %s; compose=vim %s; test=test -x /usr/bin/vim; needsterminal; priority=4 +text/*; view %s; edit=vim %s; compose=vim %s; test=test -x /usr/bin/vim; needsterminal; priority=2 +text/plain; view %s; edit=vi %s; compose=vi %s; needsterminal; priority=3 +text/*; view %s; edit=vi %s; compose=vi %s; needsterminal; priority=1 diff --git a/debian/vim-doc.doc-base.referencemanual b/debian/vim-doc.doc-base.referencemanual new file mode 100644 index 0000000..613a141 --- /dev/null +++ b/debian/vim-doc.doc-base.referencemanual @@ -0,0 +1,11 @@ +Document: vim-referencemanual +Title: Vim reference manual +Author: Bram Moolenaar <bram@vim.org> +Section: Editors +Abstract: The Vim reference manual + This document contains a detailed list of all commands for + each mode as well as all configurable options. + +Format: html +Index: /usr/share/doc/vim/html/index.html +Files: /usr/share/doc/vim/html/*.html diff --git a/debian/vim-doc.doc-base.usermanual b/debian/vim-doc.doc-base.usermanual new file mode 100644 index 0000000..02f83e0 --- /dev/null +++ b/debian/vim-doc.doc-base.usermanual @@ -0,0 +1,11 @@ +Document: vim-usermanual +Title: Vim user manual +Author: Bram Moolenaar <bram@vim.org> +Section: Editors +Abstract: The Vim user manual. + Contains task oriented explanations from simplex to complex + on using Vim. + +Format: html +Index: /usr/share/doc/vim/html/usr_toc.html +Files: /usr/share/doc/vim/html/usr_*.html diff --git a/debian/vim-doc.docs b/debian/vim-doc.docs new file mode 100644 index 0000000..2be9981 --- /dev/null +++ b/debian/vim-doc.docs @@ -0,0 +1,3 @@ +debian/FAQ +debian/policy/vim-policy.html +debian/policy/vim-policy.txt diff --git a/debian/vim-doc.install b/debian/vim-doc.install new file mode 100644 index 0000000..eb40aeb --- /dev/null +++ b/debian/vim-doc.install @@ -0,0 +1 @@ +runtime/doc/*.html usr/share/doc/vim/html/ diff --git a/debian/vim-gtk3.alternatives b/debian/vim-gtk3.alternatives new file mode 100644 index 0000000..0a173e5 --- /dev/null +++ b/debian/vim-gtk3.alternatives @@ -0,0 +1,114 @@ +Name: editor +Link: /usr/bin/editor +Alternative: /usr/bin/vim.gtk3 +Dependents: + /usr/share/man/man1/editor.1.gz editor.1.gz /usr/share/man/man1/vim.1.gz + /usr/share/man/da/man1/editor.1.gz editor.da.1.gz /usr/share/man/da/man1/vim.1.gz + /usr/share/man/de/man1/editor.1.gz editor.de.1.gz /usr/share/man/de/man1/vim.1.gz + /usr/share/man/fr/man1/editor.1.gz editor.fr.1.gz /usr/share/man/fr/man1/vim.1.gz + /usr/share/man/it/man1/editor.1.gz editor.it.1.gz /usr/share/man/it/man1/vim.1.gz + /usr/share/man/ja/man1/editor.1.gz editor.ja.1.gz /usr/share/man/ja/man1/vim.1.gz + /usr/share/man/pl/man1/editor.1.gz editor.pl.1.gz /usr/share/man/pl/man1/vim.1.gz + /usr/share/man/ru/man1/editor.1.gz editor.ru.1.gz /usr/share/man/ru/man1/vim.1.gz + /usr/share/man/tr/man1/editor.1.gz editor.tr.1.gz /usr/share/man/tr/man1/vim.1.gz +Priority: 50 + +Name: eview +Link: /usr/bin/eview +Alternative: /usr/bin/vim.gtk3 +Priority: 50 + +Name: evim +Link: /usr/bin/evim +Alternative: /usr/bin/vim.gtk3 +Priority: 50 + +Name: ex +Link: /usr/bin/ex +Alternative: /usr/bin/vim.gtk3 +Dependents: + /usr/share/man/man1/ex.1.gz ex.1.gz /usr/share/man/man1/vim.1.gz + /usr/share/man/da/man1/ex.1.gz ex.da.1.gz /usr/share/man/da/man1/vim.1.gz + /usr/share/man/de/man1/ex.1.gz ex.de.1.gz /usr/share/man/de/man1/vim.1.gz + /usr/share/man/fr/man1/ex.1.gz ex.fr.1.gz /usr/share/man/fr/man1/vim.1.gz + /usr/share/man/it/man1/ex.1.gz ex.it.1.gz /usr/share/man/it/man1/vim.1.gz + /usr/share/man/ja/man1/ex.1.gz ex.ja.1.gz /usr/share/man/ja/man1/vim.1.gz + /usr/share/man/pl/man1/ex.1.gz ex.pl.1.gz /usr/share/man/pl/man1/vim.1.gz + /usr/share/man/ru/man1/ex.1.gz ex.ru.1.gz /usr/share/man/ru/man1/vim.1.gz + /usr/share/man/tr/man1/ex.1.gz ex.tr.1.gz /usr/share/man/tr/man1/vim.1.gz +Priority: 50 + +Name: gview +Link: /usr/bin/gview +Alternative: /usr/bin/vim.gtk3 +Priority: 50 + +Name: gvim +Link: /usr/bin/gvim +Alternative: /usr/bin/vim.gtk3 +Priority: 50 + +Name: gvimdiff +Link: /usr/bin/gvimdiff +Alternative: /usr/bin/vim.gtk3 +Priority: 50 + +Name: rgview +Link: /usr/bin/rgview +Alternative: /usr/bin/vim.gtk3 +Priority: 50 + +Name: rgvim +Link: /usr/bin/rgvim +Alternative: /usr/bin/vim.gtk3 +Priority: 50 + +Name: rview +Link: /usr/bin/rview +Alternative: /usr/bin/vim.gtk3 +Priority: 50 + +Name: rvim +Link: /usr/bin/rvim +Alternative: /usr/bin/vim.gtk3 +Priority: 50 + +Name: vi +Link: /usr/bin/vi +Alternative: /usr/bin/vim.gtk3 +Dependents: + /usr/share/man/man1/vi.1.gz vi.1.gz /usr/share/man/man1/vim.1.gz + /usr/share/man/da/man1/vi.1.gz vi.da.1.gz /usr/share/man/da/man1/vim.1.gz + /usr/share/man/de/man1/vi.1.gz vi.de.1.gz /usr/share/man/de/man1/vim.1.gz + /usr/share/man/fr/man1/vi.1.gz vi.fr.1.gz /usr/share/man/fr/man1/vim.1.gz + /usr/share/man/it/man1/vi.1.gz vi.it.1.gz /usr/share/man/it/man1/vim.1.gz + /usr/share/man/ja/man1/vi.1.gz vi.ja.1.gz /usr/share/man/ja/man1/vim.1.gz + /usr/share/man/pl/man1/vi.1.gz vi.pl.1.gz /usr/share/man/pl/man1/vim.1.gz + /usr/share/man/ru/man1/vi.1.gz vi.ru.1.gz /usr/share/man/ru/man1/vim.1.gz + /usr/share/man/tr/man1/vi.1.gz vi.tr.1.gz /usr/share/man/tr/man1/vim.1.gz +Priority: 50 + +Name: view +Link: /usr/bin/view +Alternative: /usr/bin/vim.gtk3 +Dependents: + /usr/share/man/man1/view.1.gz view.1.gz /usr/share/man/man1/vim.1.gz + /usr/share/man/da/man1/view.1.gz view.da.1.gz /usr/share/man/da/man1/vim.1.gz + /usr/share/man/de/man1/view.1.gz view.de.1.gz /usr/share/man/de/man1/vim.1.gz + /usr/share/man/fr/man1/view.1.gz view.fr.1.gz /usr/share/man/fr/man1/vim.1.gz + /usr/share/man/it/man1/view.1.gz view.it.1.gz /usr/share/man/it/man1/vim.1.gz + /usr/share/man/ja/man1/view.1.gz view.ja.1.gz /usr/share/man/ja/man1/vim.1.gz + /usr/share/man/pl/man1/view.1.gz view.pl.1.gz /usr/share/man/pl/man1/vim.1.gz + /usr/share/man/ru/man1/view.1.gz view.ru.1.gz /usr/share/man/ru/man1/vim.1.gz + /usr/share/man/tr/man1/view.1.gz view.tr.1.gz /usr/share/man/tr/man1/vim.1.gz +Priority: 50 + +Name: vim +Link: /usr/bin/vim +Alternative: /usr/bin/vim.gtk3 +Priority: 50 + +Name: vimdiff +Link: /usr/bin/vimdiff +Alternative: /usr/bin/vim.gtk3 +Priority: 50 diff --git a/debian/vim-gtk3.install b/debian/vim-gtk3.install new file mode 100644 index 0000000..02727e7 --- /dev/null +++ b/debian/vim-gtk3.install @@ -0,0 +1 @@ +src/vim-gtk3/vim.gtk3 usr/bin/ diff --git a/debian/vim-gtk3.lintian-overrides b/debian/vim-gtk3.lintian-overrides new file mode 100644 index 0000000..dc14f4b --- /dev/null +++ b/debian/vim-gtk3.lintian-overrides @@ -0,0 +1,2 @@ +# vim.xxx files are alternatives for (g)vim, which has a manpage in vim(-gui)-common +no-manual-page [usr/bin/vim.gtk3] diff --git a/debian/vim-gui-common.dirs b/debian/vim-gui-common.dirs new file mode 100644 index 0000000..9ed0431 --- /dev/null +++ b/debian/vim-gui-common.dirs @@ -0,0 +1,11 @@ +/etc/ +/usr/bin/ +/usr/share/applications/ +/usr/share/man/da/man1/ +/usr/share/man/de/man1/ +/usr/share/man/fr/man1/ +/usr/share/man/it/man1/ +/usr/share/man/ja/man1/ +/usr/share/man/man1/ +/usr/share/man/pl/man1/ +/usr/share/man/ru/man1/ diff --git a/debian/vim-gui-common.install b/debian/vim-gui-common.install new file mode 100644 index 0000000..303d757 --- /dev/null +++ b/debian/vim-gui-common.install @@ -0,0 +1,10 @@ +debian/runtime/gvimrc etc/vim/ +usr/bin/gvimtutor +usr/share/applications/gvim.desktop +usr/share/man/fr/man1/evim.1 +usr/share/man/it/man1/evim.1 +usr/share/man/ja/man1/evim.1 +usr/share/man/man1/evim.1 +usr/share/man/pl/man1/evim.1 +usr/share/man/ru/man1/evim.1 +usr/share/man/tr/man1/evim.1 diff --git a/debian/vim-gui-common.links b/debian/vim-gui-common.links new file mode 100644 index 0000000..3f41f78 --- /dev/null +++ b/debian/vim-gui-common.links @@ -0,0 +1,31 @@ +etc/vim/gvimrc usr/share/vim/gvimrc +usr/share/man/da/man1/gvim.1 usr/share/man/da/man1/gview.1 +usr/share/man/da/man1/gvim.1 usr/share/man/da/man1/rgview.1 +usr/share/man/da/man1/gvim.1 usr/share/man/da/man1/rgvim.1 +usr/share/man/de/man1/gvim.1 usr/share/man/de/man1/gview.1 +usr/share/man/de/man1/gvim.1 usr/share/man/de/man1/rgview.1 +usr/share/man/de/man1/gvim.1 usr/share/man/de/man1/rgvim.1 +usr/share/man/fr/man1/evim.1 usr/share/man/fr/man1/eview.1 +usr/share/man/fr/man1/gvim.1 usr/share/man/fr/man1/gview.1 +usr/share/man/fr/man1/gvim.1 usr/share/man/fr/man1/rgview.1 +usr/share/man/fr/man1/gvim.1 usr/share/man/fr/man1/rgvim.1 +usr/share/man/it/man1/evim.1 usr/share/man/it/man1/eview.1 +usr/share/man/it/man1/gvim.1 usr/share/man/it/man1/gview.1 +usr/share/man/it/man1/gvim.1 usr/share/man/it/man1/rgview.1 +usr/share/man/it/man1/gvim.1 usr/share/man/it/man1/rgvim.1 +usr/share/man/ja/man1/evim.1 usr/share/man/ja/man1/eview.1 +usr/share/man/ja/man1/gvim.1 usr/share/man/ja/man1/gview.1 +usr/share/man/ja/man1/gvim.1 usr/share/man/ja/man1/rgview.1 +usr/share/man/ja/man1/gvim.1 usr/share/man/ja/man1/rgvim.1 +usr/share/man/man1/evim.1 usr/share/man/man1/eview.1 +usr/share/man/man1/gvim.1 usr/share/man/man1/gview.1 +usr/share/man/man1/gvim.1 usr/share/man/man1/rgview.1 +usr/share/man/man1/gvim.1 usr/share/man/man1/rgvim.1 +usr/share/man/pl/man1/evim.1 usr/share/man/pl/man1/eview.1 +usr/share/man/pl/man1/gvim.1 usr/share/man/pl/man1/gview.1 +usr/share/man/pl/man1/gvim.1 usr/share/man/pl/man1/rgview.1 +usr/share/man/pl/man1/gvim.1 usr/share/man/pl/man1/rgvim.1 +usr/share/man/ru/man1/evim.1 usr/share/man/ru/man1/eview.1 +usr/share/man/ru/man1/gvim.1 usr/share/man/ru/man1/gview.1 +usr/share/man/ru/man1/gvim.1 usr/share/man/ru/man1/rgview.1 +usr/share/man/ru/man1/gvim.1 usr/share/man/ru/man1/rgvim.1 diff --git a/debian/vim-gui-common.lintian-overrides b/debian/vim-gui-common.lintian-overrides new file mode 100644 index 0000000..2dcb89f --- /dev/null +++ b/debian/vim-gui-common.lintian-overrides @@ -0,0 +1,5 @@ +# Provided by gvim (virtual) packages +vim-gui-common binary: desktop-command-not-in-package gvim [usr/share/applications/gvim.desktop] + +# Provided by gvim (virtual) packages +vim-gui-common binary: spare-manual-page diff --git a/debian/vim-gui-common.mime b/debian/vim-gui-common.mime new file mode 100644 index 0000000..43607a7 --- /dev/null +++ b/debian/vim-gui-common.mime @@ -0,0 +1,2 @@ +text/plain; gview -f %s; edit=gvim -f %s; compose=gvim -f %s; test=test "$DISPLAY" != ""; priority=4 +text/*; gview -f %s; edit=gvim -f %s; compose=gvim -f %s; test=test "$DISPLAY" != "" ; priority=2 diff --git a/debian/vim-motif.alternatives b/debian/vim-motif.alternatives new file mode 100644 index 0000000..df58a5b --- /dev/null +++ b/debian/vim-motif.alternatives @@ -0,0 +1,114 @@ +Name: editor +Link: /usr/bin/editor +Alternative: /usr/bin/vim.motif +Dependents: + /usr/share/man/man1/editor.1.gz editor.1.gz /usr/share/man/man1/vim.1.gz + /usr/share/man/da/man1/editor.1.gz editor.da.1.gz /usr/share/man/da/man1/vim.1.gz + /usr/share/man/de/man1/editor.1.gz editor.de.1.gz /usr/share/man/de/man1/vim.1.gz + /usr/share/man/fr/man1/editor.1.gz editor.fr.1.gz /usr/share/man/fr/man1/vim.1.gz + /usr/share/man/it/man1/editor.1.gz editor.it.1.gz /usr/share/man/it/man1/vim.1.gz + /usr/share/man/ja/man1/editor.1.gz editor.ja.1.gz /usr/share/man/ja/man1/vim.1.gz + /usr/share/man/pl/man1/editor.1.gz editor.pl.1.gz /usr/share/man/pl/man1/vim.1.gz + /usr/share/man/ru/man1/editor.1.gz editor.ru.1.gz /usr/share/man/ru/man1/vim.1.gz + /usr/share/man/tr/man1/editor.1.gz editor.tr.1.gz /usr/share/man/tr/man1/vim.1.gz +Priority: 50 + +Name: eview +Link: /usr/bin/eview +Alternative: /usr/bin/vim.motif +Priority: 50 + +Name: evim +Link: /usr/bin/evim +Alternative: /usr/bin/vim.motif +Priority: 50 + +Name: ex +Link: /usr/bin/ex +Alternative: /usr/bin/vim.motif +Dependents: + /usr/share/man/man1/ex.1.gz ex.1.gz /usr/share/man/man1/vim.1.gz + /usr/share/man/da/man1/ex.1.gz ex.da.1.gz /usr/share/man/da/man1/vim.1.gz + /usr/share/man/de/man1/ex.1.gz ex.de.1.gz /usr/share/man/de/man1/vim.1.gz + /usr/share/man/fr/man1/ex.1.gz ex.fr.1.gz /usr/share/man/fr/man1/vim.1.gz + /usr/share/man/it/man1/ex.1.gz ex.it.1.gz /usr/share/man/it/man1/vim.1.gz + /usr/share/man/ja/man1/ex.1.gz ex.ja.1.gz /usr/share/man/ja/man1/vim.1.gz + /usr/share/man/pl/man1/ex.1.gz ex.pl.1.gz /usr/share/man/pl/man1/vim.1.gz + /usr/share/man/ru/man1/ex.1.gz ex.ru.1.gz /usr/share/man/ru/man1/vim.1.gz + /usr/share/man/tr/man1/ex.1.gz ex.tr.1.gz /usr/share/man/tr/man1/vim.1.gz +Priority: 50 + +Name: gview +Link: /usr/bin/gview +Alternative: /usr/bin/vim.motif +Priority: 50 + +Name: gvim +Link: /usr/bin/gvim +Alternative: /usr/bin/vim.motif +Priority: 50 + +Name: gvimdiff +Link: /usr/bin/gvimdiff +Alternative: /usr/bin/vim.motif +Priority: 50 + +Name: rgview +Link: /usr/bin/rgview +Alternative: /usr/bin/vim.motif +Priority: 50 + +Name: rgvim +Link: /usr/bin/rgvim +Alternative: /usr/bin/vim.motif +Priority: 50 + +Name: rview +Link: /usr/bin/rview +Alternative: /usr/bin/vim.motif +Priority: 50 + +Name: rvim +Link: /usr/bin/rvim +Alternative: /usr/bin/vim.motif +Priority: 50 + +Name: vi +Link: /usr/bin/vi +Alternative: /usr/bin/vim.motif +Dependents: + /usr/share/man/man1/vi.1.gz vi.1.gz /usr/share/man/man1/vim.1.gz + /usr/share/man/da/man1/vi.1.gz vi.da.1.gz /usr/share/man/da/man1/vim.1.gz + /usr/share/man/de/man1/vi.1.gz vi.de.1.gz /usr/share/man/de/man1/vim.1.gz + /usr/share/man/fr/man1/vi.1.gz vi.fr.1.gz /usr/share/man/fr/man1/vim.1.gz + /usr/share/man/it/man1/vi.1.gz vi.it.1.gz /usr/share/man/it/man1/vim.1.gz + /usr/share/man/ja/man1/vi.1.gz vi.ja.1.gz /usr/share/man/ja/man1/vim.1.gz + /usr/share/man/pl/man1/vi.1.gz vi.pl.1.gz /usr/share/man/pl/man1/vim.1.gz + /usr/share/man/ru/man1/vi.1.gz vi.ru.1.gz /usr/share/man/ru/man1/vim.1.gz + /usr/share/man/tr/man1/vi.1.gz vi.tr.1.gz /usr/share/man/tr/man1/vim.1.gz +Priority: 50 + +Name: view +Link: /usr/bin/view +Alternative: /usr/bin/vim.motif +Dependents: + /usr/share/man/man1/view.1.gz view.1.gz /usr/share/man/man1/vim.1.gz + /usr/share/man/da/man1/view.1.gz view.da.1.gz /usr/share/man/da/man1/vim.1.gz + /usr/share/man/de/man1/view.1.gz view.de.1.gz /usr/share/man/de/man1/vim.1.gz + /usr/share/man/fr/man1/view.1.gz view.fr.1.gz /usr/share/man/fr/man1/vim.1.gz + /usr/share/man/it/man1/view.1.gz view.it.1.gz /usr/share/man/it/man1/vim.1.gz + /usr/share/man/ja/man1/view.1.gz view.ja.1.gz /usr/share/man/ja/man1/vim.1.gz + /usr/share/man/pl/man1/view.1.gz view.pl.1.gz /usr/share/man/pl/man1/vim.1.gz + /usr/share/man/ru/man1/view.1.gz view.ru.1.gz /usr/share/man/ru/man1/vim.1.gz + /usr/share/man/tr/man1/view.1.gz view.tr.1.gz /usr/share/man/tr/man1/vim.1.gz +Priority: 50 + +Name: vim +Link: /usr/bin/vim +Alternative: /usr/bin/vim.motif +Priority: 50 + +Name: vimdiff +Link: /usr/bin/vimdiff +Alternative: /usr/bin/vim.motif +Priority: 50 diff --git a/debian/vim-motif.install b/debian/vim-motif.install new file mode 100644 index 0000000..460a8f0 --- /dev/null +++ b/debian/vim-motif.install @@ -0,0 +1 @@ +src/vim-motif/vim.motif usr/bin/ diff --git a/debian/vim-motif.lintian-overrides b/debian/vim-motif.lintian-overrides new file mode 100644 index 0000000..12279ec --- /dev/null +++ b/debian/vim-motif.lintian-overrides @@ -0,0 +1,2 @@ +# vim.xxx files are alternatives for (g)vim, which has a manpage in vim(-gui)-common +no-manual-page [usr/bin/vim.motif] diff --git a/debian/vim-nox.alternatives b/debian/vim-nox.alternatives new file mode 100644 index 0000000..a72eef6 --- /dev/null +++ b/debian/vim-nox.alternatives @@ -0,0 +1,79 @@ +Name: editor +Link: /usr/bin/editor +Alternative: /usr/bin/vim.nox +Dependents: + /usr/share/man/man1/editor.1.gz editor.1.gz /usr/share/man/man1/vim.1.gz + /usr/share/man/da/man1/editor.1.gz editor.da.1.gz /usr/share/man/da/man1/vim.1.gz + /usr/share/man/de/man1/editor.1.gz editor.de.1.gz /usr/share/man/de/man1/vim.1.gz + /usr/share/man/fr/man1/editor.1.gz editor.fr.1.gz /usr/share/man/fr/man1/vim.1.gz + /usr/share/man/it/man1/editor.1.gz editor.it.1.gz /usr/share/man/it/man1/vim.1.gz + /usr/share/man/ja/man1/editor.1.gz editor.ja.1.gz /usr/share/man/ja/man1/vim.1.gz + /usr/share/man/pl/man1/editor.1.gz editor.pl.1.gz /usr/share/man/pl/man1/vim.1.gz + /usr/share/man/ru/man1/editor.1.gz editor.ru.1.gz /usr/share/man/ru/man1/vim.1.gz + /usr/share/man/tr/man1/editor.1.gz editor.tr.1.gz /usr/share/man/tr/man1/vim.1.gz +Priority: 40 + +Name: ex +Link: /usr/bin/ex +Alternative: /usr/bin/vim.nox +Dependents: + /usr/share/man/man1/ex.1.gz ex.1.gz /usr/share/man/man1/vim.1.gz + /usr/share/man/da/man1/ex.1.gz ex.da.1.gz /usr/share/man/da/man1/vim.1.gz + /usr/share/man/de/man1/ex.1.gz ex.de.1.gz /usr/share/man/de/man1/vim.1.gz + /usr/share/man/fr/man1/ex.1.gz ex.fr.1.gz /usr/share/man/fr/man1/vim.1.gz + /usr/share/man/it/man1/ex.1.gz ex.it.1.gz /usr/share/man/it/man1/vim.1.gz + /usr/share/man/ja/man1/ex.1.gz ex.ja.1.gz /usr/share/man/ja/man1/vim.1.gz + /usr/share/man/pl/man1/ex.1.gz ex.pl.1.gz /usr/share/man/pl/man1/vim.1.gz + /usr/share/man/ru/man1/ex.1.gz ex.ru.1.gz /usr/share/man/ru/man1/vim.1.gz + /usr/share/man/tr/man1/ex.1.gz ex.tr.1.gz /usr/share/man/tr/man1/vim.1.gz +Priority: 40 + +Name: rview +Link: /usr/bin/rview +Alternative: /usr/bin/vim.nox +Priority: 40 + +Name: rvim +Link: /usr/bin/rvim +Alternative: /usr/bin/vim.nox +Priority: 40 + +Name: vi +Link: /usr/bin/vi +Alternative: /usr/bin/vim.nox +Dependents: + /usr/share/man/man1/vi.1.gz vi.1.gz /usr/share/man/man1/vim.1.gz + /usr/share/man/da/man1/vi.1.gz vi.da.1.gz /usr/share/man/da/man1/vim.1.gz + /usr/share/man/de/man1/vi.1.gz vi.de.1.gz /usr/share/man/de/man1/vim.1.gz + /usr/share/man/fr/man1/vi.1.gz vi.fr.1.gz /usr/share/man/fr/man1/vim.1.gz + /usr/share/man/it/man1/vi.1.gz vi.it.1.gz /usr/share/man/it/man1/vim.1.gz + /usr/share/man/ja/man1/vi.1.gz vi.ja.1.gz /usr/share/man/ja/man1/vim.1.gz + /usr/share/man/pl/man1/vi.1.gz vi.pl.1.gz /usr/share/man/pl/man1/vim.1.gz + /usr/share/man/ru/man1/vi.1.gz vi.ru.1.gz /usr/share/man/ru/man1/vim.1.gz + /usr/share/man/tr/man1/vi.1.gz vi.tr.1.gz /usr/share/man/tr/man1/vim.1.gz +Priority: 40 + +Name: view +Link: /usr/bin/view +Alternative: /usr/bin/vim.nox +Dependents: + /usr/share/man/man1/view.1.gz view.1.gz /usr/share/man/man1/vim.1.gz + /usr/share/man/da/man1/view.1.gz view.da.1.gz /usr/share/man/da/man1/vim.1.gz + /usr/share/man/de/man1/view.1.gz view.de.1.gz /usr/share/man/de/man1/vim.1.gz + /usr/share/man/fr/man1/view.1.gz view.fr.1.gz /usr/share/man/fr/man1/vim.1.gz + /usr/share/man/it/man1/view.1.gz view.it.1.gz /usr/share/man/it/man1/vim.1.gz + /usr/share/man/ja/man1/view.1.gz view.ja.1.gz /usr/share/man/ja/man1/vim.1.gz + /usr/share/man/pl/man1/view.1.gz view.pl.1.gz /usr/share/man/pl/man1/vim.1.gz + /usr/share/man/ru/man1/view.1.gz view.ru.1.gz /usr/share/man/ru/man1/vim.1.gz + /usr/share/man/tr/man1/view.1.gz view.tr.1.gz /usr/share/man/tr/man1/vim.1.gz +Priority: 40 + +Name: vim +Link: /usr/bin/vim +Alternative: /usr/bin/vim.nox +Priority: 40 + +Name: vimdiff +Link: /usr/bin/vimdiff +Alternative: /usr/bin/vim.nox +Priority: 40 diff --git a/debian/vim-nox.install b/debian/vim-nox.install new file mode 100644 index 0000000..537d067 --- /dev/null +++ b/debian/vim-nox.install @@ -0,0 +1 @@ +src/vim-nox/vim.nox usr/bin/ diff --git a/debian/vim-nox.lintian-overrides b/debian/vim-nox.lintian-overrides new file mode 100644 index 0000000..23f90fc --- /dev/null +++ b/debian/vim-nox.lintian-overrides @@ -0,0 +1,2 @@ +# vim.xxx files are alternatives for (g)vim, which has a manpage in vim(-gui)-common +no-manual-page [usr/bin/vim.nox] diff --git a/debian/vim-runtime.dirs b/debian/vim-runtime.dirs new file mode 100644 index 0000000..b4f9ea8 --- /dev/null +++ b/debian/vim-runtime.dirs @@ -0,0 +1,10 @@ +/usr/bin/ +/usr/share/man/da/man1/ +/usr/share/man/fr/man1/ +/usr/share/man/it/man1/ +/usr/share/man/ja/man1/ +/usr/share/man/man1/ +/usr/share/man/pl/man1/ +/usr/share/man/ru/man1/ +/usr/share/vim/addons/ +/usr/share/vim/registry/ diff --git a/debian/vim-runtime.install b/debian/vim-runtime.install new file mode 100644 index 0000000..e24dd32 --- /dev/null +++ b/debian/vim-runtime.install @@ -0,0 +1,10 @@ +usr/bin/vimtutor +usr/share/man/da/man1/vimtutor.1 +usr/share/man/fr/man1/vimtutor.1 +usr/share/man/it/man1/vimtutor.1 +usr/share/man/ja/man1/vimtutor.1 +usr/share/man/man1/vimtutor.1 +usr/share/man/pl/man1/vimtutor.1 +usr/share/man/ru/man1/vimtutor.1 +usr/share/man/tr/man1/vimtutor.1 +usr/share/vim/ diff --git a/debian/vim-runtime.lintian-overrides b/debian/vim-runtime.lintian-overrides new file mode 100644 index 0000000..8cf9655 --- /dev/null +++ b/debian/vim-runtime.lintian-overrides @@ -0,0 +1,9 @@ +# These are intentionally in non-UTF-8 encodings +national-encoding [usr/share/vim/vim*/keymap/*] +national-encoding [usr/share/vim/vim*/lang/*] +national-encoding [usr/share/vim/vim*/tutor/*] + +# This is Vim's builtin help +package-contains-documentation-outside-usr-share-doc [usr/share/vim/vim*/doc/*] + +repeated-path-segment dvorak [usr/share/vim/vim*/pack/dist/opt/dvorak/dvorak/] diff --git a/debian/vim-runtime.postinst b/debian/vim-runtime.postinst new file mode 100644 index 0000000..34b221d --- /dev/null +++ b/debian/vim-runtime.postinst @@ -0,0 +1,34 @@ +#!/bin/sh +set -e + +basedir=/usr/share/vim/@VIMCUR@/doc + +rm_diversion() { + dpkg-divert --package vim-runtime --rename --remove "$1" +} + +# Used to remove the previous diversion when upgrading from one major release +# to the next +remove_previous_diversions() { + for v in vim71 vim72a vim72b vim72c; do + oldpath="$(echo $1 | sed s/@VIMCUR@/$v/)" + if dpkg-divert --list 2>/dev/null | grep -q "$oldpath"; then + rm_diversion $oldpath + fi + done +} + +# Need to run helpztags since we're overwriting /u/s/v/a/d/tags whenever +# vim-runtime is install/upgraded which breaks the help for other vim addons +if which helpztags >/dev/null 2>&1; then + helpztags /usr/share/vim/addons/doc +fi + +if [ "$1" = "configure" ]; then + remove_previous_diversions $basedir/help.txt + remove_previous_diversions $basedir/tags +fi + +#DEBHELPER# + +exit 0 diff --git a/debian/vim-runtime.postrm.in b/debian/vim-runtime.postrm.in new file mode 100644 index 0000000..6536648 --- /dev/null +++ b/debian/vim-runtime.postrm.in @@ -0,0 +1,28 @@ +#!/bin/sh +set -e + +vimcur="@VIMCUR@" +basedir=/usr/share/vim/$vimcur/doc + +rm_diversion() { + dpkg-divert --package vim-runtime --rename --remove "$1" +} + +# When upgrading to a new major upstream release, we need to remove the old +# vim-tiny help(tags) diversions +major_upgrade() { + newver="${1#?:}" + newver="vim$(echo ${newver%.*-*} | sed 's/\.//g')" + [ "$newver" != "$vimcur" ] +} + +rm -f /usr/share/vim/addons/doc/tags +if [ "$1" = "remove" -o "$1" = "abort-install" -o "$1" = "disappear" ] \ + || ([ "$1" = "upgrade" ] && major_upgrade $2); then + rm_diversion $basedir/help.txt + rm_diversion $basedir/tags +fi + +#DEBHELPER# + +exit 0 diff --git a/debian/vim-runtime.preinst.in b/debian/vim-runtime.preinst.in new file mode 100644 index 0000000..9e5df5f --- /dev/null +++ b/debian/vim-runtime.preinst.in @@ -0,0 +1,27 @@ +#!/bin/sh +set -e + +vimcur="@VIMCUR@" +basedir=/usr/share/vim/$vimcur/doc + +add_diversion() { + dpkg-divert --package vim-runtime --add --rename \ + --divert "$1.vim-tiny" "$1" +} + +major_upgrade() { + oldver="${1#?:}" + oldver="vim$(echo ${oldver%.*-*} | sed 's/\.//g')" + [ "$oldver" != "$vimcur" ] +} + +# Add diversions for any non-upgrade operation or when upgrading across major +# upstream versions. +if [ "$1" != "upgrade" ] || major_upgrade $2; then + add_diversion $basedir/help.txt + add_diversion $basedir/tags +fi + +#DEBHELPER# + +exit 0 diff --git a/debian/vim-tiny.alternatives b/debian/vim-tiny.alternatives new file mode 100644 index 0000000..2f4877f --- /dev/null +++ b/debian/vim-tiny.alternatives @@ -0,0 +1,64 @@ +Name: editor +Link: /usr/bin/editor +Alternative: /usr/bin/vim.tiny +Dependents: + /usr/share/man/man1/editor.1.gz editor.1.gz /usr/share/man/man1/vim.1.gz + /usr/share/man/da/man1/editor.1.gz editor.da.1.gz /usr/share/man/da/man1/vim.1.gz + /usr/share/man/de/man1/editor.1.gz editor.de.1.gz /usr/share/man/de/man1/vim.1.gz + /usr/share/man/fr/man1/editor.1.gz editor.fr.1.gz /usr/share/man/fr/man1/vim.1.gz + /usr/share/man/it/man1/editor.1.gz editor.it.1.gz /usr/share/man/it/man1/vim.1.gz + /usr/share/man/ja/man1/editor.1.gz editor.ja.1.gz /usr/share/man/ja/man1/vim.1.gz + /usr/share/man/pl/man1/editor.1.gz editor.pl.1.gz /usr/share/man/pl/man1/vim.1.gz + /usr/share/man/ru/man1/editor.1.gz editor.ru.1.gz /usr/share/man/ru/man1/vim.1.gz + /usr/share/man/tr/man1/editor.1.gz editor.tr.1.gz /usr/share/man/tr/man1/vim.1.gz +Priority: 15 + +Name: ex +Link: /usr/bin/ex +Alternative: /usr/bin/vim.tiny +Dependents: + /usr/share/man/man1/ex.1.gz ex.1.gz /usr/share/man/man1/vim.1.gz + /usr/share/man/da/man1/ex.1.gz ex.da.1.gz /usr/share/man/da/man1/vim.1.gz + /usr/share/man/de/man1/ex.1.gz ex.de.1.gz /usr/share/man/de/man1/vim.1.gz + /usr/share/man/fr/man1/ex.1.gz ex.fr.1.gz /usr/share/man/fr/man1/vim.1.gz + /usr/share/man/it/man1/ex.1.gz ex.it.1.gz /usr/share/man/it/man1/vim.1.gz + /usr/share/man/ja/man1/ex.1.gz ex.ja.1.gz /usr/share/man/ja/man1/vim.1.gz + /usr/share/man/pl/man1/ex.1.gz ex.pl.1.gz /usr/share/man/pl/man1/vim.1.gz + /usr/share/man/ru/man1/ex.1.gz ex.ru.1.gz /usr/share/man/ru/man1/vim.1.gz + /usr/share/man/tr/man1/ex.1.gz ex.tr.1.gz /usr/share/man/tr/man1/vim.1.gz +Priority: 15 + +Name: rview +Link: /usr/bin/rview +Alternative: /usr/bin/vim.tiny +Priority: 15 + +Name: vi +Link: /usr/bin/vi +Alternative: /usr/bin/vim.tiny +Dependents: + /usr/share/man/man1/vi.1.gz vi.1.gz /usr/share/man/man1/vim.1.gz + /usr/share/man/da/man1/vi.1.gz vi.da.1.gz /usr/share/man/da/man1/vim.1.gz + /usr/share/man/de/man1/vi.1.gz vi.de.1.gz /usr/share/man/de/man1/vim.1.gz + /usr/share/man/fr/man1/vi.1.gz vi.fr.1.gz /usr/share/man/fr/man1/vim.1.gz + /usr/share/man/it/man1/vi.1.gz vi.it.1.gz /usr/share/man/it/man1/vim.1.gz + /usr/share/man/ja/man1/vi.1.gz vi.ja.1.gz /usr/share/man/ja/man1/vim.1.gz + /usr/share/man/pl/man1/vi.1.gz vi.pl.1.gz /usr/share/man/pl/man1/vim.1.gz + /usr/share/man/ru/man1/vi.1.gz vi.ru.1.gz /usr/share/man/ru/man1/vim.1.gz + /usr/share/man/tr/man1/vi.1.gz vi.tr.1.gz /usr/share/man/tr/man1/vim.1.gz +Priority: 15 + +Name: view +Link: /usr/bin/view +Alternative: /usr/bin/vim.tiny +Dependents: + /usr/share/man/man1/view.1.gz view.1.gz /usr/share/man/man1/vim.1.gz + /usr/share/man/da/man1/view.1.gz view.da.1.gz /usr/share/man/da/man1/vim.1.gz + /usr/share/man/de/man1/view.1.gz view.de.1.gz /usr/share/man/de/man1/vim.1.gz + /usr/share/man/fr/man1/view.1.gz view.fr.1.gz /usr/share/man/fr/man1/vim.1.gz + /usr/share/man/it/man1/view.1.gz view.it.1.gz /usr/share/man/it/man1/vim.1.gz + /usr/share/man/ja/man1/view.1.gz view.ja.1.gz /usr/share/man/ja/man1/vim.1.gz + /usr/share/man/pl/man1/view.1.gz view.pl.1.gz /usr/share/man/pl/man1/vim.1.gz + /usr/share/man/ru/man1/view.1.gz view.ru.1.gz /usr/share/man/ru/man1/vim.1.gz + /usr/share/man/tr/man1/view.1.gz view.tr.1.gz /usr/share/man/tr/man1/vim.1.gz +Priority: 15 diff --git a/debian/vim-tiny.dirs b/debian/vim-tiny.dirs new file mode 100644 index 0000000..74760d3 --- /dev/null +++ b/debian/vim-tiny.dirs @@ -0,0 +1 @@ +/usr/share/vim diff --git a/debian/vim-tiny.install b/debian/vim-tiny.install new file mode 100644 index 0000000..4944900 --- /dev/null +++ b/debian/vim-tiny.install @@ -0,0 +1,3 @@ +src/vim-tiny/vim.tiny usr/bin/ +debian/tiny/doc/ usr/share/vim/${env:VIMCUR}/ +debian/tiny/vimrc.tiny etc/vim/ diff --git a/debian/vim-tiny.lintian-overrides b/debian/vim-tiny.lintian-overrides new file mode 100644 index 0000000..fd285d9 --- /dev/null +++ b/debian/vim-tiny.lintian-overrides @@ -0,0 +1,2 @@ +# vim.xxx files are alternatives for (g)vim, which has a manpage in vim(-gui)-common +no-manual-page [usr/bin/vim.tiny] diff --git a/debian/vim.alternatives b/debian/vim.alternatives new file mode 100644 index 0000000..6710051 --- /dev/null +++ b/debian/vim.alternatives @@ -0,0 +1,79 @@ +Name: editor +Link: /usr/bin/editor +Alternative: /usr/bin/vim.basic +Dependents: + /usr/share/man/man1/editor.1.gz editor.1.gz /usr/share/man/man1/vim.1.gz + /usr/share/man/da/man1/editor.1.gz editor.da.1.gz /usr/share/man/da/man1/vim.1.gz + /usr/share/man/de/man1/editor.1.gz editor.de.1.gz /usr/share/man/de/man1/vim.1.gz + /usr/share/man/fr/man1/editor.1.gz editor.fr.1.gz /usr/share/man/fr/man1/vim.1.gz + /usr/share/man/it/man1/editor.1.gz editor.it.1.gz /usr/share/man/it/man1/vim.1.gz + /usr/share/man/ja/man1/editor.1.gz editor.ja.1.gz /usr/share/man/ja/man1/vim.1.gz + /usr/share/man/pl/man1/editor.1.gz editor.pl.1.gz /usr/share/man/pl/man1/vim.1.gz + /usr/share/man/ru/man1/editor.1.gz editor.ru.1.gz /usr/share/man/ru/man1/vim.1.gz + /usr/share/man/tr/man1/editor.1.gz editor.tr.1.gz /usr/share/man/tr/man1/vim.1.gz +Priority: 30 + +Name: ex +Link: /usr/bin/ex +Alternative: /usr/bin/vim.basic +Dependents: + /usr/share/man/man1/ex.1.gz ex.1.gz /usr/share/man/man1/vim.1.gz + /usr/share/man/da/man1/ex.1.gz ex.da.1.gz /usr/share/man/da/man1/vim.1.gz + /usr/share/man/de/man1/ex.1.gz ex.de.1.gz /usr/share/man/de/man1/vim.1.gz + /usr/share/man/fr/man1/ex.1.gz ex.fr.1.gz /usr/share/man/fr/man1/vim.1.gz + /usr/share/man/it/man1/ex.1.gz ex.it.1.gz /usr/share/man/it/man1/vim.1.gz + /usr/share/man/ja/man1/ex.1.gz ex.ja.1.gz /usr/share/man/ja/man1/vim.1.gz + /usr/share/man/pl/man1/ex.1.gz ex.pl.1.gz /usr/share/man/pl/man1/vim.1.gz + /usr/share/man/ru/man1/ex.1.gz ex.ru.1.gz /usr/share/man/ru/man1/vim.1.gz + /usr/share/man/tr/man1/ex.1.gz ex.tr.1.gz /usr/share/man/tr/man1/vim.1.gz +Priority: 30 + +Name: rview +Link: /usr/bin/rview +Alternative: /usr/bin/vim.basic +Priority: 30 + +Name: rvim +Link: /usr/bin/rvim +Alternative: /usr/bin/vim.basic +Priority: 30 + +Name: vi +Link: /usr/bin/vi +Alternative: /usr/bin/vim.basic +Dependents: + /usr/share/man/man1/vi.1.gz vi.1.gz /usr/share/man/man1/vim.1.gz + /usr/share/man/da/man1/vi.1.gz vi.da.1.gz /usr/share/man/da/man1/vim.1.gz + /usr/share/man/de/man1/vi.1.gz vi.de.1.gz /usr/share/man/de/man1/vim.1.gz + /usr/share/man/fr/man1/vi.1.gz vi.fr.1.gz /usr/share/man/fr/man1/vim.1.gz + /usr/share/man/it/man1/vi.1.gz vi.it.1.gz /usr/share/man/it/man1/vim.1.gz + /usr/share/man/ja/man1/vi.1.gz vi.ja.1.gz /usr/share/man/ja/man1/vim.1.gz + /usr/share/man/pl/man1/vi.1.gz vi.pl.1.gz /usr/share/man/pl/man1/vim.1.gz + /usr/share/man/ru/man1/vi.1.gz vi.ru.1.gz /usr/share/man/ru/man1/vim.1.gz + /usr/share/man/tr/man1/vi.1.gz vi.tr.1.gz /usr/share/man/tr/man1/vim.1.gz +Priority: 30 + +Name: view +Link: /usr/bin/view +Alternative: /usr/bin/vim.basic +Dependents: + /usr/share/man/man1/view.1.gz view.1.gz /usr/share/man/man1/vim.1.gz + /usr/share/man/da/man1/view.1.gz view.da.1.gz /usr/share/man/da/man1/vim.1.gz + /usr/share/man/de/man1/view.1.gz view.de.1.gz /usr/share/man/de/man1/vim.1.gz + /usr/share/man/fr/man1/view.1.gz view.fr.1.gz /usr/share/man/fr/man1/vim.1.gz + /usr/share/man/it/man1/view.1.gz view.it.1.gz /usr/share/man/it/man1/vim.1.gz + /usr/share/man/ja/man1/view.1.gz view.ja.1.gz /usr/share/man/ja/man1/vim.1.gz + /usr/share/man/pl/man1/view.1.gz view.pl.1.gz /usr/share/man/pl/man1/vim.1.gz + /usr/share/man/ru/man1/view.1.gz view.ru.1.gz /usr/share/man/ru/man1/vim.1.gz + /usr/share/man/tr/man1/view.1.gz view.tr.1.gz /usr/share/man/tr/man1/vim.1.gz +Priority: 30 + +Name: vim +Link: /usr/bin/vim +Alternative: /usr/bin/vim.basic +Priority: 30 + +Name: vimdiff +Link: /usr/bin/vimdiff +Alternative: /usr/bin/vim.basic +Priority: 30 diff --git a/debian/vim.dirs b/debian/vim.dirs new file mode 100644 index 0000000..415f082 --- /dev/null +++ b/debian/vim.dirs @@ -0,0 +1 @@ +/usr/bin diff --git a/debian/vim.install b/debian/vim.install new file mode 100644 index 0000000..df66a6a --- /dev/null +++ b/debian/vim.install @@ -0,0 +1 @@ +src/vim-basic/vim.basic usr/bin/ diff --git a/debian/vim.lintian-overrides b/debian/vim.lintian-overrides new file mode 100644 index 0000000..2b495f6 --- /dev/null +++ b/debian/vim.lintian-overrides @@ -0,0 +1,2 @@ +# vim.xxx files are alternatives for (g)vim, which has a manpage in vim(-gui)-common +no-manual-page [usr/bin/vim.basic] diff --git a/debian/watch b/debian/watch new file mode 100644 index 0000000..096644e --- /dev/null +++ b/debian/watch @@ -0,0 +1,4 @@ +version=4 +opts=filenamemangle=s%(?:.*?)?v(\d[\d.]+)\.tar\.gz%vim-$1.tar.gz% \ + https://github.com/vim/vim/tags \ + (?:.*?)?v(\d[\d.]+)\.tar\.gz |