Minor corrections and typos.
1 parent 2c89fe2 commit f6c167517753c9e1d6487c691028c600beaced36
@tundra tundra authored on 19 Dec 2006
Showing 1 changed file
View
26
twander.1
 
 
.SS Associations
 
Most X-Windows window managers and Microsoft Windows support the idea
Most X-Windows desktops and Microsoft Windows support the idea
of "associations". That is, based on the name of a file, they
"associate" an application that can handle it. So, for example, a
filename ending in ".txt" is handled by a text editor, a filename
ending in ".ps" is handled by a PostScript processing program, and so
on. This is handy inside of visual interfaces because you can
double-click on a file and the interface can infer which program to
load to process that file.
 
The problem is that the various window managers and Microsoft Windows don't
all handle associations the same way. Some lighter X-Windows window
managers may not even have associations at all. In order for to remain
The problem is that the various X desktops and Microsoft Windows don't
all handle associations the same way. Some lighter X-Windows desktop
may not even have associations at all. In order for to remain
portable across operating systems, and work more-or-less the same way
everywhere, association support has been implemented directly within
\fCtwander\fP itself.
 
.ft C \" courier
.nf
ASSOC *.pdf mypdfreader [SELECTION]
ASSOC *.ps mypostscriptprogram [SELECTION]
ASSOC * myfineeditor [SELECTION]
.fi
.ft \" revert
 
In this situation, if you double-click or press "Enter" on any file
ASSOC * myfineeditor [SELECTION] # Default association
.fi
.ft \" revert
 
In this example, if you double-click or press "Enter" on any file
not ending in either ".pdf" or ".ps", the default association action
will be taken: The file will be opened with \fCmyfineeditor\fP.
 
You can also define a list of file types to be
of the same type handled by the same application program. On Windows
systems, this has traditionally been the set of characters the follow
the period at the end of the filename. But this convention is not
consistently used on Unix-like systems. \fCtwander\fP lets you use a
fairly powerful "widcarding" system to define what is common about the
fairly powerful "wildcarding" system to define what is common about the
names of all files of a given type. Unix users will recognize this as
the shell \fCglobbing\fP wildcards. Here they are implemented for
both Windows and the Unix-like systems in the same way. The only
difference is that, on Windows, the check for a match ("is this file
between the Unix-like systems and Windows.
 
.IP \(bu 4
On Unix-like operating systems \fCtwander\fP ignores the underlying
associations (if any) of the system and/or window manager. It only
associations (if any) of the system and/or X desktop. It only
observes its own associations. That's because there is no consistent
association mechanism across the many OS and window manager variants
association mechanism across the many OS and desktop variants
in use on those platforms.
 
But Microsoft Windows is a different matter. All modern variants of
these systems have consistent built-in support for association.
.fi
.ft \" revert
 
.SH DOCUMENT REVISION INFORMATION
$Id: twander.1,v 1.141 2006/12/19 10:05:16 tundra Exp $
$Id: twander.1,v 1.142 2006/12/19 16:41:14 tundra Exp $