Login or Register to Ask a Question and Join Our Community

Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

xfmtype(1) [debian man page]

XFMTYPE(1)								XFM								XFMTYPE(1)

NAME

       xfmtype - xfm file type tester

SYNOPSIS

       xfmtype -m magic_file [-f] filename ...

DESCRIPTION

       The  xfmtype  program reads a magic configuration file and tests each file in its command line to tell its type according to the configura-
       tion file.

       The format of the configuration file is the similar to magic(5) with the differences described in 0

OPTIONS

       -f file
	   Consider the following argument as a file, even if it begins with `-'.

       -m file
	   Specifies a configuration file. You can specify more than one configuration file with several -m flags. They are read in the  order	in
	   which  they	are found. Configuration files do not have effect until they are encountered in the command line. So, files to test in the
	   command line before that switch will not be affected by it.

BUILT IN TYPES

       If no rule matches a specified field or the type cannot be determined because of other reasons, one of the  following  built  in  types	is
       returned:

       inode/x-unreadable The file could not be read.

       inode/x-empty File size is zero.

       text/plain The file looks like ACSII.
       xfm will look into xfm_mime.type(5) for more guessing.

       application/octet-stream Other regular file.
       xfm will look into xfm_mime.type(5) for more guessing.

       inode/directory A directory.

       inode/chardevice A character device.

       inode/blockdevice A block device.

       inode/pipe A names pipe (fifo).

       inode/socket A socket.

       inode/default None of the above.

BUGS

       Bad configuration lines cause undefined behavior. In general they are silently ignored, but that is not guaranteed.
       There are no warning or error message except for the regular expression syntax.
       There should be a syntax checking mode.
       All of the above apply to xfm too.

SEE ALSO

       xfm(1), xfm_magic(5), file(1), magic(5).

COPYRIGHT

       Copyright (c) 1995 CNM-US
       Copyright (c) 1995 Juan D. Martin

AUTHOR

       Juan D. Martin (juando@cnm.us.es)
       (but modified heavily by Bernhard R. Link)

xfm								  20 April, 2006							XFMTYPE(1)

Check Out this Related Man Page

XFMMAILCAP(1)								XFM							     XFMMAILCAP(1)

NAME

       xfmmailcap - show mailcap information as parsed by xfm

SYNOPSIS

       xfmmailcap --help

       xfmmailcap mime-type [(default|all|edit|view) [filename]]

DESCRIPTION

       xfmmailcap  parses  the	xfm(1)'s  mailcap file (see xfm_mailcap(5) for its format) and prints information about what command xfm would use
       when told to open a file of the given mime-type.

       If there is no second argument, the default it default.

       If there is a third argument, xfmmailcap will insert this filename into the action.  (This is not yet implemented)

ACTIONS

   all
       Show all information collected about this mime-type.

   default
       Show the action xfm(1) would start when confronted with this action, together with all debug output xfm would show when the  echoMimeSearch
       resource  represents  True.   It  first	tries  everything the edit action would show and if nothing is found there, then it tries the view
       action.

   edit
       Find the best (in the sense of highest priority) command to edit this mime type.

   view
       Find the best (in the sense of highest priority) command to view this mime type.  (There is yet no way to trigger that from within xfm).

CAVEAT

       xfmmailcap has the paths $HOME/.xfm/xfm_mailcap and /etc/X11/xfm/xfm_mailcap built in statically.  This differs from xfm(1), where  all	of
       these can be changed by means of X resources.

FILES

       $HOME/.xfm/xfm_mailcap
	      If this file exists, it is read and its content used as mailcap database.  See xfm_mailcap(5) for its format.

       /etc/X11/xfm/xfm_mailcap
	      If the previous file is not found, this one is used instead. Same format.

SEE ALSO

       xfm(1), xfm_mailcap(5).

COPYRIGHT

       Copyright (C) 2006 Bernhard R. Link
       This  is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICU-
       LAR PURPOSE.

xfm								  20 April, 2006						     XFMMAILCAP(1)
Man Page