vim.org maillists
A few notes about using the maillists:
Before sending a message check the archive (see below), search the Vim pages and the FAQ; your question may have been answered already. Do not send messages in HTML. You will be flamed! Every decent mail program has an option to switch off HTML. Attachments are allowed, but keep the total message size below 50 Kbytes. Otherwise upload your file somewhere and send the URL to the maillist The maillists are hosted by Google Groups. The @vim.org addresses are aliases. For some things you need to use the original @googlegroups.com address For subscribing and unsubscribing you can send an empty message to the address mentioned in the table below. You will get a message back with instructions how to confirm. Mention your full name, so that we know who we are talking with. Because it messes up the order in which people normally read text.
Why?
Please do not use top-posting when replying to a message.
That is: type your reply below the text you are replying to and remove irrelevant text from the original.
Purpose Announcements only. New releases, important patches and bug reports. Change of important mail and web addresses.
To Post You cannot post to this list, only Bram can.
Comments The vim-announce list is very low on traffic.
Mail sent to this list is also sent to subscribers of the vim, vim-dev, vim-mac and vim-multibyte lists, no need to subscribe twice.
Purpose This list is for Vim user support. You can send general questions to this list to be answered by other Vim users.
To Post email vim@vim.org; you must be subscribed to post!
Purpose Bugs, new features, and other development issues are discussed on this list.
Comments If you aren't writing bugfixes or extensions to vim, or at least reporting an apparent bug, this probably isn't the right list for you. Use questions should stick to vim@vim.org, above.
Purpose This list is for discussing the use and development of Vim on the Mac OS.
Comments This is for Mac-specific questions about using, compiling and coding. Generic use questions should stick to vim@vim.org, above.
Purpose This list is for discussing Vim support and development for multibyte encodings, such as Big5 and Unicode.
Comments Low traffic.
third-party lists
Please let us know of any Vim-related mailing lists that we've missed!
Purpose This list is for discussing the development of Vim on OpenVMS.
Comments This is for questions about compiling and coding for Vim on OpenVMS. Non VMS related use questions should stick to vim@vim.org, above.
Purpose This list is for Vim user support, in French. You can send general questions to this list to be answered by other Vim users. In other words, it's just like vim@vim.org, but in French.
Comments
Purpose This list is for the Vim taglist plugin. The taglist plugin is for browsing source code with Vim.
Comments
Purpose Development of extensions to Vim to allow SubEthaEdit functionality. This is editing the same file with several people.
Comments
maillist help
For help on using the Vim maillists go the to the "help" page, as mentioned in the table above.
You may wonder why the lists at Google Groups use an underscore, while the lists @vim.org use a dash. This is for historical reasons. The lists were first created on our own server, using dashes. When the server died we moved them to Google Groups. Unfortunately, some of the names were not available there. We used an underscore for all the lists, so that at least it is consistent.
Note that the aliases @vim.org support both a dash and an underscore, but if you send something to @googlegroups.com you need to use an underscore.