Vim Tips Wiki
Register
Advertisement

This is an archive – please don't edit.

Should be easy decision for following[]

Merged to 9 Displaying a variable/macro definition
  • Search all occurances of the word under cursor in all the open files
Redirect to renamed tip (116 below) that will be deleted.
Tip is wrong ([I does not do what tip claims).
Merged to 9 Displaying a variable/macro definition

--JohnBeckett 08:53, 18 May 2008 (UTC)

Assuming your reasons are correct (I haven't looked at them), I agree with the above 4 deletions. --Fritzophrenic 17:23, 6 June 2008 (UTC)

Tips now summarised in the documentation or scripts pages[]

I believe that all useful content from these tips has been summarised at Vim documentation or Vim scripts, and there is a fairly prominent link on the main page to those. Discussion on "Vim information" was invited via the vim-l mailing list, and there was one comment in agreement. --JohnBeckett 01:49, 22 June 2008 (UTC)


I looked at the two spellchecking tips here, and agree with their deletion. We need to make sure to keep tips on integrating with external spell checkers, though, because this task is probably a fairly common one. The scripts page should probably point to a few of these tips under its section on spell checking.

Other than that, I agree, though I haven't looked at all of the above-mentioned tips. --Fritzophrenic 17:12, 23 June 2008 (UTC)


Probably easy decisions for following[]

If you think one of these tips should be kept, please remove it from this section, and put it in a section on its own with your comment. --JohnBeckett 08:36, 8 June 2008 (UTC)

Merged to VimTip137.
Four confusing (and possibly misguided) :%s commands with no explanation.
Merged to VimTip94.
Link to a non-existent page; no content.
An unresolved problem, not a tip; no helpful content.
Merged to VimTip94.
A proposed fix for a script in 2003; obsolete; unhelpful.
Yet another vimrc example, naturally with no explanations, just mysteries.

Agree, but 1524 makes me sad. I almost had it two simple ways, but the formatexpr I finally fixed it with is way to complex and customized to be of much use here. --Fritzophrenic 17:15, 23 June 2008 (UTC)

Tips flagged for delete that perhaps should not be deleted[]

Please list any tips flagged for delete that you think should be kept below, and add a reason why you think it should be kept.

Question, not a tip.
If the comment about using :silent works, why not keep it? Or, as the delete comment says, at least create a new tip with this information first! --Fritzophrenic 17:18, 23 June 2008 (UTC)
I think the info is adequately covered in the following (16 and 642 are short and cover the issue):
So it should be ok to delete the tip. --JohnBeckett 03:54, 24 June 2008 (UTC)

Hmm...it looks like the tip content itself is covered elsewhere, but I am just realizing that the question posed at the beginning of the tip isn't even answered by the comments! The question isn't about the "hit enter to continue" prompt within Vim, but rather it is about the "hit any key to continue" displayed by the terminal window that pops up when you run an external command from Vim. This can be overcome by "!start" in Windows, as shown by Execute_external_programs_asynchronously_under_Windows. Since the tip has no real content at the moment, I suppose it can be deleted. We should probably mention the "press any key" message that pops up in a terminal window for external commands in VimTip16 and in Execute_external_programs_asynchronously_under_Windows, so that people can find these solutions by searching.

--Fritzophrenic 12:59, 30 June 2008 (UTC)

OK. I reworded 1549 Execute external programs asynchronously under Windows (and added a 'see also' in VimTip16) so the exact prompt is shown and explained. Therefore I will delete tip 307. --JohnBeckett 03:47, 1 July 2008 (UTC)

Comments were invited in the vim-l mailing list. No objections were made, so candidates have been/will be deleted. --JohnBeckett 03:19, 29 June 2008 (UTC)

Advertisement