most recent 30 from vi.stackexchange.com 2025-08-08T00:44:59Z https://vi.stackexchange.com/feeds/question/14535 https://creativecommons.org/licenses/by-sa/4.0/rdf https://vi.stackexchange.com/q/14535 11 kAldown https://vi.stackexchange.com/users/15568 2025-08-08T11:33:05Z 2025-08-08T19:12:28Z

<p>Is there any way to jump to a buffer by entering buffer number right from <code>:ls</code>?</p> <p>I mean, why this command expect me to <code>Press ENTER or type command to continue</code>, if pressing for example <code>2</code>, wouldn't do anything?</p> <p>Obviously I won't any plugin to be installed, at least one little script in <code>.vimrc</code>.</p> <p>Thanks.</p>

https://vi.stackexchange.com/questions/14535/-/14536#14536 14 B Layer https://vi.stackexchange.com/users/11054 2025-08-08T11:55:45Z 2025-08-08T19:12:28Z

<p>Without changing anything the quickest way from that prompt is probably to press <code>:b</code> + number + <kbd>Enter</kbd>. But as a bit of a shortcut here's what I (and a lot of other people) use that gets me there from Normal mode:</p> <pre><code>:nnoremap &lt;leader&gt;ls :ls&lt;cr&gt;:b </code></pre> <p>You can replace <code>&lt;leader&gt;ls</code> with any unused Normal mode key combo. After pressing the keys you'll see the buffer list and you can enter the number + <kbd>Enter</kbd> without dealing with that <code>Press ENTER...</code> prompt.</p> <p><strong>Update:</strong> OP would like to override <code>:ls</code> altogether. That can be done with</p> <pre><code>:cnoremap ls ls&lt;cr&gt;:b </code></pre> <p>but this is not recommended since the mapping will happen anywhere &quot;ls&quot; is typed in a command or search term! (Thanks to <a href="https://vi.stackexchange.com/users/778/peter-rincker">Peter Rincker</a> for <a href="https://vi.stackexchange.com/questions/14535/jump-to-buffer-from-ls/14536?noredirect=1#comment24970_14536">the warning</a>.) While you can overcome this by typing <kbd>Ctrl</kbd>+<kbd>V</kbd> before typing &quot;ls&quot; anywhere (e.g. to search for &quot;hills&quot; you'd have to do <code>/hil^Vls</code>) that's hardly convenient. Better to choose a key-combo that is unlikely to occur in commands or search terms. In Vim help they have an example with &quot;_ls&quot; so <code>:cnoremap _ls ...</code>.</p> <p><strong>Update 2:</strong> I've since removed the <code>&lt;space&gt;</code> from my own mapping and edited the mappings above to reflect this. It's not necessary and, more importantly, I occasionally decide I want to unload a buffer from this point using <code>:bd</code> (aka <a href="https://vimhelp.org/windows.txt.html#:bdelete" rel="nofollow noreferrer"><code>:bdelete</code></a>). The <code>&lt;space&gt;</code> meant having to type <kbd>Backspace</kbd> before <kbd>d</kbd> and the buffer number.</p> <p>Also, there supposedly was going to be an update five months ago based on a suggestion in the comments from @Rich but that seems to have fallen through the cracks 'til now...</p> <p>He offers a more robust handling of a command-line override of <code>ls</code>. His version behaves slightly differently from the <code>:cnoremap</code> mapping above: the latter shows the buffer list after typing <code>ls</code> while the other waits until a subsequent press of <kbd>Enter</kbd>. It's trivial to adapt his solution to match the above. Which one to choose is simply a matter of taste. Both have the benefit of avoiding any Ctrl-V nonsense and only activating upon typing <code>ls</code>/<code>ls&lt;CR&gt;</code> right after the command-line's opening <code>:</code> versus activating inappropriately upon typing them somewhere else.</p> <p>Here's the improved mapping to replace the one above. Simply add <code>&lt;CR&gt;</code> after the first <code>ls</code> to get the other flavor.</p> <pre><code>cnoremap &lt;expr&gt; ls (getcmdtype() == ':' &amp;&amp; getcmdpos() == 1) ? &quot;ls\&lt;CR&gt;:b&quot; : &quot;ls&quot; </code></pre> <p>I recommend trying both and going with whatever suits you best but make sure you <code>:cunmap</code> one before trying the other.</p> <p>Or you can blow all of this off and just use <code>&lt;leader&gt;ls</code> from Normal mode like most people prefer to do. :)</p>

https://vi.stackexchange.com/questions/14535/-/22524#22524 2 Greg Nisbet https://vi.stackexchange.com/users/6420 2025-08-08T03:53:59Z 2025-08-08T03:53:59Z

<p>You can get a workflow that's close to what you want without configuring vim at all.</p> <p>You can jump to the nth buffer using <code>&lt;C-^&gt;</code> (<code>ctrl</code> + <code>6</code>).</p> <p>If you type a digit while viewing the output of <code>ls</code>, then that digit is stored and can be passed to the next command.</p> <p>In order to produce the fake vim screenshots, I increased the font size so I can only see a few lines, and set the following listchars.</p> <pre><code>execute("set listchars=eol:\xc2\xac,tab:&gt;\\ ,trail:\xe2\x81\x9b,extends:&gt;,precedes:&lt;,space:\\ ") </code></pre> <p>So, if you do</p> <pre><code>$ mkdir -p /tmp/vim-example $ cd /tmp/vim-example $ vim ./a ./b </code></pre> <p>Then your screen will look like this:</p> <pre><code>¬ ~ ~ ~ ~ ~ ./a 0,0-1 All "./a" [New File] </code></pre> <p>You can look at the files by pressing <code>:ls&lt;cr&gt;</code>.</p> <pre><code>:ls 1 %a "./a" line 1 2 "./b" line 0 Press ENTER or type command to con tinue </code></pre> <p>From there, if you type <code>2</code> and then <code>&lt;C-^&gt;</code> you will be taken to the next buffer.</p> <pre><code>¬ ~ ~ ~ ~ ~ ./b 0,0-1 All "./b" [New File] </code></pre>

百度