(→Combine quickfix steps: keep) |
(Change <tt> to <code>, perhaps also minor tweak.) |
||
| (3 intermediate revisions by 3 users not shown) | |||
| Line 1: | Line 1: | ||
__NOTOC__ |
__NOTOC__ |
||
| − | <big>'''New tips November 2010'''</big> |
+ | <big>'''New tips November 2010'''</big> <small>[[Vim Tips Wiki:New tips/201010|Previous]] • [[Vim Tips Wiki:New tips/201012|Next]]</small> |
For each proposed new tip: |
For each proposed new tip: |
||
| Line 20: | Line 20: | ||
|- |
|- |
||
| [[C++ code completiongoogle]] |
| [[C++ code completiongoogle]] |
||
| − | |align="center"| |
+ | |align="center"| Delete |
|- |
|- |
||
| [[Combine quickfix steps]] |
| [[Combine quickfix steps]] |
||
| − | |align="center"| |
+ | |align="center"| Kept as [[VimTip1667]] |
|- |
|- |
||
| [[How to create a dictionary for every .NET component - a project plan]] |
| [[How to create a dictionary for every .NET component - a project plan]] |
||
| − | |align="center"| |
+ | |align="center"| Delete |
|- |
|- |
||
| [[Quick switching two alternate commented out blocks in C++]] |
| [[Quick switching two alternate commented out blocks in C++]] |
||
| − | |align="center"| |
+ | |align="center"| Delete |
|} |
|} |
||
| − | '''Please add your comment (sign with < |
+ | '''Please add your comment (sign with <code><nowiki>~~~~</nowiki></code>) below the appropriate heading. Use <code><nowiki>----</nowiki></code> between comments.''' |
| − | |||
| − | ==General comments (not for a specific tip)== |
||
==[[C++ code completiongoogle]]== |
==[[C++ code completiongoogle]]== |
||
Delete. Don't bother with a redirect. --[[User:Fritzophrenic|Fritzophrenic]] 21:59, June 6, 2011 (UTC) |
Delete. Don't bother with a redirect. --[[User:Fritzophrenic|Fritzophrenic]] 21:59, June 6, 2011 (UTC) |
||
| + | :Agree. I have flagged the page for deletion in case someone is watching it, and we can delete it in a few days if no further discussion occurs. [[User:JohnBeckett|JohnBeckett]] 11:25, June 7, 2011 (UTC) |
||
==[[Combine quickfix steps]]== |
==[[Combine quickfix steps]]== |
||
Keep. Looks useful. Put in quickfix category if we have one. --[[User:Fritzophrenic|Fritzophrenic]] 22:16, June 6, 2011 (UTC) |
Keep. Looks useful. Put in quickfix category if we have one. --[[User:Fritzophrenic|Fritzophrenic]] 22:16, June 6, 2011 (UTC) |
||
| + | :Agree. We have some tips that mention <code>getqflist</code> ([[VimTip76|76]], [[VimTip203|203]], [[VimTip692|692]], [[VimTip1639|1639]]), but none duplicate this topic. I don't think we have a quickfix category; I'll think about that. [[User:JohnBeckett|JohnBeckett]] 11:25, June 7, 2011 (UTC) |
||
| + | ::[[:Category:Compiler]] is close enough for now. Maybe we ought to reword the category introduction...or just make a new category. Also added the above to a "see also" section. --[[User:Fritzophrenic|Fritzophrenic]] 04:05, October 7, 2011 (UTC) |
||
==[[How to create a dictionary for every .NET component - a project plan]]== |
==[[How to create a dictionary for every .NET component - a project plan]]== |
||
Delete. No real content useful to Vim users. This seems to be just a proposal for a plugin. The links have nothing to do with Vim. --[[User:Fritzophrenic|Fritzophrenic]] 22:04, June 6, 2011 (UTC) |
Delete. No real content useful to Vim users. This seems to be just a proposal for a plugin. The links have nothing to do with Vim. --[[User:Fritzophrenic|Fritzophrenic]] 22:04, June 6, 2011 (UTC) |
||
| + | :Agree. I have flagged the page for deletion in case someone is watching it, and we can delete it in a few days if no further discussion occurs. [[User:JohnBeckett|JohnBeckett]] 11:25, June 7, 2011 (UTC) |
||
==[[Quick switching two alternate commented out blocks in C++]]== |
==[[Quick switching two alternate commented out blocks in C++]]== |
||
Clever, but not much to do with Vim. Tentative '''delete''' per normal process. Possibly with a mapping to insert the construct it is worth keeping. It is easy enough to use blockwise visual selection to accomplish the task in a more reliable fashion anyway. --[[User:Fritzophrenic|Fritzophrenic]] 22:09, June 6, 2011 (UTC) |
Clever, but not much to do with Vim. Tentative '''delete''' per normal process. Possibly with a mapping to insert the construct it is worth keeping. It is easy enough to use blockwise visual selection to accomplish the task in a more reliable fashion anyway. --[[User:Fritzophrenic|Fritzophrenic]] 22:09, June 6, 2011 (UTC) |
||
| + | :Agree. I have flagged the page for deletion in case someone is watching it. I noted on the tip that it would be confusing if read by a programmer not familiar with the idea, and that there are plenty of comment/uncomment plugins (our tips are [[VimTip271|271]], [[VimTip369|369]], [[VimTip388|388]], [[VimTip660|660]], [[VimTip981|981]], [[VimTip1570|1570]], but I think there are good plugins for this). I don't see a need to wait for longer than a few days (and it can always be undeleted if someone raises an issue later than that), but if you want to wait with this one, that's fine. [[User:JohnBeckett|JohnBeckett]] 11:25, June 7, 2011 (UTC) |
||
---- |
---- |
||
Latest revision as of 08:37, 15 July 2012
New tips November 2010 Previous • Next
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 |
|---|---|
| C++ code completiongoogle | Delete |
| Combine quickfix steps | Kept as VimTip1667 |
| How to create a dictionary for every .NET component - a project plan | Delete |
| Quick switching two alternate commented out blocks in C++ | Delete |
Please add your comment (sign with ~~~~) below the appropriate heading. Use ---- between comments.
C++ code completiongoogle[]
Delete. Don't bother with a redirect. --Fritzophrenic 21:59, June 6, 2011 (UTC)
- Agree. I have flagged the page for deletion in case someone is watching it, and we can delete it in a few days if no further discussion occurs. JohnBeckett 11:25, June 7, 2011 (UTC)
Combine quickfix steps[]
Keep. Looks useful. Put in quickfix category if we have one. --Fritzophrenic 22:16, June 6, 2011 (UTC)
- Agree. We have some tips that mention
getqflist(76, 203, 692, 1639), but none duplicate this topic. I don't think we have a quickfix category; I'll think about that. JohnBeckett 11:25, June 7, 2011 (UTC)- Category:Compiler is close enough for now. Maybe we ought to reword the category introduction...or just make a new category. Also added the above to a "see also" section. --Fritzophrenic 04:05, October 7, 2011 (UTC)
How to create a dictionary for every .NET component - a project plan[]
Delete. No real content useful to Vim users. This seems to be just a proposal for a plugin. The links have nothing to do with Vim. --Fritzophrenic 22:04, June 6, 2011 (UTC)
- Agree. I have flagged the page for deletion in case someone is watching it, and we can delete it in a few days if no further discussion occurs. JohnBeckett 11:25, June 7, 2011 (UTC)
Quick switching two alternate commented out blocks in C++[]
Clever, but not much to do with Vim. Tentative delete per normal process. Possibly with a mapping to insert the construct it is worth keeping. It is easy enough to use blockwise visual selection to accomplish the task in a more reliable fashion anyway. --Fritzophrenic 22:09, June 6, 2011 (UTC)
- Agree. I have flagged the page for deletion in case someone is watching it. I noted on the tip that it would be confusing if read by a programmer not familiar with the idea, and that there are plenty of comment/uncomment plugins (our tips are 271, 369, 388, 660, 981, 1570, but I think there are good plugins for this). I don't see a need to wait for longer than a few days (and it can always be undeleted if someone raises an issue later than that), but if you want to wait with this one, that's fine. JohnBeckett 11:25, June 7, 2011 (UTC)