@Wildcard I've found the perl documentation format (POD) easier than man pages, so I usually write my man pages in that and then run them through pod2man. Of course, it helps that most of the stuff needing man pages is perl scripts and modules anyway.
OS exploits the memory that is not being used as file cache buffer. I have a question about how it handles the OS page buffer. More specifically, how it picks a victim page to evict from buffer when OS clean up the space?
Is it just a simple LRU or any other interesting technique is used?
@Wildcard you can also write in markdown, and use pandoc to convert to groff -man` (i.e. a file that you can drop into …/man/man1)
Markdown is roughly as expressive as POD. Roff is much more expressive but that's a whole new language to learn with zero utility outside man pages these days.
@FaheemMitha look at the question history: the question was migrated, but the migration was rejected
An instantly rejected migration means that the asker is blocked from asking questions on SO because they've been posting too many low-quality questions
The only person who can do anything about this is the asker, by improving their questions or waiting it out (and hopefully learning to write better questions)
@FaheemMitha “Post Locked” happens because of the migration. The migration itself doesn't appear because it's been rejected. “Post Locked” appears to have happened after “Post Unlocked”, that's because the two events have exactly the same timestamp (they happened within the same second) and SE sorts by timestamp, not by actual event order.
You have to know the system well to understand what happened.
OS exploits the memory that is not being used as file cache buffer. I have a question about how it handles the OS page buffer. More specifically, how it picks a victim page to evict from buffer when OS clean up the space?
Is it just a simple LRU or any other interesting technique is used?
