Suggestion for a more detailed manual for vi

2013-05-03 Thread Xianwen Chen
Hi, I'm learning to use vi. I find that the buffer operation is different in vi than vim. For example, in vim, it is ':bn', ':bp', and ':bd' to go to next and previous buffer, and to close a buffer. Vi does not seem to have them implemented. Because of the popularity of vim, a lot of docu

Re: Suggestion for a more detailed manual for vi

2013-05-03 Thread Ted Unangst
On Fri, May 03, 2013 at 15:48, Xianwen Chen wrote: > I'm learning to use vi. I find that the buffer operation is different in > vi than vim. For example, in vim, it is ':bn', ':bp', and ':bd' to go > to next and previous buffer, and to close a buffer. Vi does not seem to > have them implemented.

Re: Suggestion for a more detailed manual for vi

2013-05-03 Thread Xianwen Chen
Ted Unangst wrote: I think the easiest option is to install vim and use that. I was going for that option. I asked the question on the list anyway. I thought I might have missed something. In general, our policy is to only document features that exist. The list of features that don't exist wou

Re: Suggestion for a more detailed manual for vi

2013-05-03 Thread Stefan Johnson
On Fri, May 3, 2013 at 9:38 AM, Xianwen Chen wrote: > In general, our policy is to only document features that exist. >> The list of features that don't exist would be a neverending list. If >> you are reading something other than official openbsd documentation, >> it's your responsibility to ve

Re: Suggestion for a more detailed manual for vi

2013-05-03 Thread Marc Espie
On Fri, May 03, 2013 at 03:48:15PM +0200, Xianwen Chen wrote: > Hi, > > I'm learning to use vi. I find that the buffer operation is > different in vi than vim. For example, in vim, it is ':bn', ':bp', > and ':bd' to go to next and previous buffer, and to close a buffer. > Vi does not seem to hav

Re: Suggestion for a more detailed manual for vi

2013-05-03 Thread Otto Moerbeek
On Fri, May 03, 2013 at 04:38:45PM +0200, Xianwen Chen wrote: > Ted Unangst wrote: > >I think the easiest option is to install vim and use that. > I was going for that option. I asked the question on the list > anyway. I thought I might have missed something. > >In general, our policy is to only