Re: :buffer command, #, $

On 2013-10-24 16:15, David Fishburn wrote:
> :$b
> E86: Buffer 48 does not exist
[snip output of :ls]
> Strange how 48 came along.

Could it be possible that you've opened 48 buffers, but closed/wiped
some since starting Vim? Though based on your next example, were you
on line 48 when you issued that?

> httpd.conf" 691 lines --91%--
> :$b
> E86: Buffer 691 does not exist

This one does seem suspect/buggy to me.

> :#b
> E488: Trailing characters

This one makes sense, since "#" is an Ex command to number the
current line, which I regularly use as ":g/pattern/#" to number the
lines matching a pattern. So it doesn't expect anything after that.
I think you're reaching for

:b#

> :^b
> E492: Not an editor command: ^b

This one makes sense to me too, at least as an omission, as Vim sees
the "^" and doesn't recognize it as a command or valid range, so the
E492 lets you know what it thinks is wrong. Not having meaning, it
*could* be overloaded in this context to mean something like ":0b"
but I'm not sure that has much value as you already have ":0b"

> Just a simple question, does it make sense to expect the usual
> buffer arguments to work for :buffer?

maybe :-)

-tim


--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.