New tips September 2009
This is a place holder – not ready for use. Please wait until the end of September 2009 before editing this page because it is generated by a script, and any edits would be lost.
For each proposed new tip:
- Is it worth keeping as a separate tip?
- Should it be merged into an existing tip? Which?
- If it should be kept, is it ready for release? Which points need fixing? Should it be renamed?
Please edit this page (not the talk page) in the appropriate section below the following table.
Alternatively, comments can be posted on the mailing list.
|Proposed new tip||Current consensus|
|Auto closing an HTML tag||Keep|
|Auto execute yuicompressor||-|
|Reversing order of blocks of text||-|
Please add your comment (sign with ~~~~) below the appropriate heading. Use ---- between comments.
General comments (not for a specific tip)
Keep Agree. I have added the "see also" mentioned in the following. JohnBeckett 07:24, March 27, 2010 (UTC)
- I'd like to keep this, if only because I had no idea omnicompletion would autoclose tags in html. That tidbit alone is worth keeping the info for. The tip is small enough that a merge might be in order, but I don't know of any pressing reason to do so. I already have <C-X><C-O> mapped to <C-Space> so this one was instantly useful for me. We should put in "see also" links in Automatically append closing characters. --Fritzophrenic 19:41, November 3, 2009 (UTC)
This just seems like an example of recording a useful macro. We could merge the info to our macros tip, or mention that it can be done in that tip and/or the reordering lines tip, but I don't think that it needs a tip all to itself. --Fritzophrenic 19:41, November 3, 2009 (UTC)
- This is a problem because Macros is a bit long, and as an example of a macro, the proposed new tip is too complex and has details that are slightly hard to get your head around (if one were simply trying to get an idea of how macros can be used). Also, as this came from #vim I am inclined towards keeping it. We have a couple of tips claiming to be examples of macros (example), but they are really mappings. How about keeping this new tip as an example of a real macro (although as expressed, it is a bit artificial; how often would you want to exactly reverse the order of several contiguous div blocks?). We might hope in the future to have other macro-based reorder suggestions in it. JohnBeckett 07:24, March 27, 2010 (UTC)
- OK, I think you have a point. I agree with keeping this one, but it needs links to it added in several other tips, and probably links from here to other places as well. For instance, you could use a recursive macro with this, we could link that one. Obviously the other reordering tips should be cross-linked. And if we're keeping it as an example of a useful non-trivial recording, we should cross-link it with our macro tip. --Fritzophrenic 15:54, March 29, 2010 (UTC)