هالة ديب

اولا اعتذر عن هذا الانقطاع الطويل تسبيا و لكن كنت مشغولة بحضور دورة تدريبية مكثفة عن Open Bsd

المهم وقعت بيدي مقالة طريفة وقد وضعتها هنا بدون ترجمة ارجو ان تعجبكم

It so happens that there’s a man page for woman (found it in /usr/share/info), which explains a lot. A synopsis:

* First of all, you need Emacs to understand it. Systems not running Emacs will never get to see this manual.

Contrary to general believe, you can get Woman also when running Linux. She is even compatible with (a carefully installed, configured and tuned) Windows machine. The fact that it was primarily developed on MS Windows, however, makes it a dangerous product.

* Why should you use woman? She is much more direct, and does not require any external programs.

Disadvantages: Not a complete emulation, slightly slower.

* Why women can do more than one thing at the time: WoMan supports the use of compressed man files.

* The amount of information that WoMan caches (in main memory and, optionally, saved to disc) is controlled by the user option ‘woman-cache-level’. And also: The `woman’ command always performs a certain amount of caching in main memory.

This results in Woman remembering all kinds of stuff at the most embarassing of times, and also explaines why the excuse “It wasn’t me” does not work.

* Why they always start discussing off-subject matters: By default, the woman command uses the word nearest to point in the current buffer as a suggestion for the topic to look up.

* Why they do things even when you don’t ask them to: In GNU Emacs 21 and later these autoloads are predefined.

* A search path needs to be defined if you want the most friendly woman, which is recommended in general.

Woman will use MANPATH and man configuration files, provided she can find them. You may need to customize woman-manpath.

* You need to change the default configuration if you don’t want a woman group on your system.

* Accessing woman via the command line is also possible, but is an experts-only matter

* Woman is case dependent and will thus react differently in seemingly the same circumstances.

* For topic completion to work, WoMan must build a list of all the man files she can access, which can be very slow, especially if a network is involved. This process is speeded up using caching. Cache can get out of sync, but can be restored using a prefix argument which will force her to rebuild cache. Cache can be saved between sessions, however.

* Once WoMan is loaded (or if specially set up), various additional commands in this family are available.

That explains the phone bill and frequent visits to her mother and sisters.

* Woman can use the automatic interface, but this must be configured explicitly.

But: This use of WoMan does not seem to be particularly advantageous, so it is not really supported.

* If you want things nice and clean on your system, use the woman-use-own-frame option.

* If it all seems suspiciously easy: check the woman-topic-at-point option, which may default to the value confirm.

* If she starts taking up too much space, set woman-fill-frame to nil.

Check the woman-ignore option if she’s uncooperative.

* Did you know you can set faces? There is even the woman-unknown-face, sounds kinky to me!

* And last but not least, why things never work out: woman is still under development and was never made to actually replace man. And even if you did read the manual, it was written by a man…