The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then publish the changes below to finish undoing the edit.
Latest revision | Your text | ||
Line 4: | Line 4: | ||
|previous=1107 |
|previous=1107 |
||
|next=1109 |
|next=1109 |
||
β | |created=2006 |
+ | |created=January 16, 2006 |
|complexity=basic |
|complexity=basic |
||
|author=l1th10n |
|author=l1th10n |
||
Line 13: | Line 13: | ||
}} |
}} |
||
{{dodgy|What exactly does this have to do with Vim? Please give a detailed example of how to use this in Vim (including before and after text)}} |
{{dodgy|What exactly does this have to do with Vim? Please give a detailed example of how to use this in Vim (including before and after text)}} |
||
β | When writing bash scripts and sudoers files, it can be tedious to determine the paths of the commands. Here is a procedure to use the < |
+ | When writing bash scripts and sudoers files, it can be tedious to determine the paths of the commands. Here is a procedure to use the <tt>which</tt> command to return the path of the selected word: |
<pre> |
<pre> |
||
Line 44: | Line 44: | ||
On Windows, you will have to translate ';' (instead of ':') into ',', and replace 'cat' by 'cat.exe'. |
On Windows, you will have to translate ';' (instead of ':') into ',', and replace 'cat' by 'cat.exe'. |
||
β | These solutions will work even without 'which' installed on the system. The path translation mechanism is wrapped in < |
+ | These solutions will work even without 'which' installed on the system. The path translation mechanism is wrapped in <tt>:SearchInPATH</tt> from {{script|id=229}}. |
---- |
---- |