On Fri, 14 Sep 2018, Rin Okuyama wrote:
On 2018/09/14 20:37, Christos Zoulas wrote:
In article ,
Rin Okuyama wrote:
...
It would be better to fix our vi in accordance with POSIX. Thoughts?
I think it is better to keep the behavior (exit) and fix the man page.
vim exits too. It is usually
On Fri, 14 Sep 2018, Christos Zoulas wrote:
I think it is better to keep the behavior (exit) and fix the man page.
vim exits too. It is usually the case that the user does not want to
edit the file with the same name!
In my case, it was a typo. I meant -R vs -r, so yes I really did intend
On 2018/09/14 20:37, Christos Zoulas wrote:
In article ,
Rin Okuyama wrote:
...
It would be better to fix our vi in accordance with POSIX. Thoughts?
I think it is better to keep the behavior (exit) and fix the man page.
vim exits too. It is usually the case that the user does not want to
In article ,
Rin Okuyama wrote:
>Hi,
>
>On 2018/09/14 8:49, Paul Goyette wrote:
>> Current vi(1) man page says
>>
>>    -r    Recover the specified files, or, if no files are
>> specified,
>>           list the files that could be recovered. If no
>recoverable
>> Â Â Â
Hi,
On 2018/09/14 8:49, Paul Goyette wrote:
Current vi(1) man page says
-r Recover the specified files, or, if no files are specified,
list the files that could be recovered. If no recoverable
files by the specified name exist, the file is edited as if
Current vi(1) man page says
-r Recover the specified files, or, if no files are specified,
list the files that could be recovered. If no recoverable
files by the specified name exist, the file is edited as if
the -r option had not been specified.
