Some files have no extension, but the file type can be
discerned by simple examination. Consider for example a
file named @file{example} which contains XML. You may
reasonably expect it to be treated as an @file{.xml} file
rather than a generic file. For the purposes of applying
automatic preferences and syntax definitions, @code{ne}
provides a mechanism for overriding a wrong or missing
extension with a @dfn{virtual extension} based on a
document's contents. You do this by creating a
@file{~/.ne/.extensions} file which is fully described in
the @ref{Virtual Extensions} section.