Ugh, all this crazy head-spinning cursor commotion... I'll just keep using ed, thank you very much.
COPY CON ...
on DOS, bro.
nuttin else comes close
or if ur 2 weak, edlin.
The POSIX specification of vi
21–30 of 50 posts
Re: The POSIX specification of vi
#22It's notable that vi has been specified by POSIX (along with ed and ex), but not emacs.
Re: The POSIX specification of vi
#23> Move Down
> Synopsis:
> [count] j
Why would you ever specify configurable shortcuts? Does is break posix when a user changes them?
Re: The POSIX specification of vi
#24Ugh, all this crazy head-spinning cursor commotion... I'll just keep using ed, thank you very much.
Always keep your copy of Ed Mastery on-hand:
Re: The POSIX specification of vi
#25It's notable that vi has been specified by POSIX (along with ed and ex), but not emacs.
vi was born on UNIX early enough that every UNIX wound up with it.
Emacs was born on mainframes and made its way to UNIX much later, after vi had already become the standard.
Re: The POSIX specification of vi
#26Re: The POSIX specification of vi
#27You can see all the userland utilities by removing the "vi.HTML" suffix from the URL. https://pubs.opengroup.org/onlinepubs/9799919799/utilities/
>mailx mbox should die; or maybe set as a legacy option. Current systems can handle thousands of email by using maildirs. Also, one day bsdgames will enter into POSIX maybe but as a test case, in order to be sure on how well the POSIX compatible API behaves. Phantasia(6) could be rewritten for balance and such...
>mbox should die;
Mbox is useful for backups and for migration between different email systems (that use different databases internally). Mbox is also fine if you only have a hundred or so email folders and only process a few dozen emails a day, say for personal use (e.g. Thunderbird or k9).
I agree that mbox is not okay for large scale mail servers. Maildir+ works much better in such cases.
Re: The POSIX specification of vi
#28Huawei EulerOS is one of the few POSIX compliant Linux distros, but it’s a commercial one [0] But it has a FOSS release, openEuler [1] I actually want to download it now to check if the vi there is really that POSIX version 0, https://www.opengroup.org/openbrand/register/brand3622.htm 1, https://www.openeuler.org/en/
I used to work for Huawei. From what I remember, vi was just vim.
Re: The POSIX specification of vi
#29Note that vim includes a useful tutorial you can invoke by "vimtutor" on the command line or from within vim with ":help tutor"; for neovim try ":Tutorial".
Re: The POSIX specification of vi
#30Earlier quoted context omitted.
>mailx mbox should die; or maybe set as a legacy option. Current systems can handle thousands of email by using maildirs. Also, one day bsdgames will enter into POSIX maybe but as a test case, in order to be sure on how well the POSIX compatible API behaves. Phantasia(6) could be rewritten for balance and such...
>mbox should die; Mbox is useful for backups and for migration between different email systems (that use different databases internally). Mbox is also fine if you only have a hundred or so email folders and only process a few dozen emails a day, say for personal use (e.g. Thunderbird or k9). I agree that mbox is not okay for large scale mail servers. Maildir+ works much better in such cases.
So does Maildir; reusing it between Mutt and GNUs or Claws Mail should be a child's play.
Once you have tar to preserve perms just in case, your are done.
Mbox on big mailboxes it's hell, anyone can understand that linear parsing will be slow as hell. It's like looking up a word file in a dictionary word by word from A to Z instead of directly heading to the first word letter...