Remove trailing space in documents
This commit is contained in:
parent
5f58d1e747
commit
08ad2bc007
4 changed files with 8 additions and 8 deletions
4
FAQ
4
FAQ
|
|
@ -23,11 +23,11 @@ Solutions:
|
|||
|
||||
* Enforce the usage of a stabilized API (practically, API 25) with::
|
||||
|
||||
env CFLAGS=-DFUSE_USE_VERSION=25 python setup.py build
|
||||
env CFLAGS=-DFUSE_USE_VERSION=25 python setup.py build
|
||||
|
||||
* Upgrade your FUSE installation. As of writing this, 2.6.0-pre3 is available.
|
||||
|
||||
When I use a dedicated file class, how can I tell apart the cases when an instance of it is instantiated from a ``CREATE`` callback and when it's instantiated from an ``OPEN`` callback?
|
||||
When I use a dedicated file class, how can I tell apart the cases when an instance of it is instantiated from a ``CREATE`` callback and when it's instantiated from an ``OPEN`` callback?
|
||||
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
|
||||
|
||||
If your file class is instantiated via ``FUSE_OPEN``, then it's
|
||||
|
|
|
|||
4
INSTALL
4
INSTALL
|
|
@ -3,8 +3,8 @@ REQUIREMENTS:
|
|||
- In general, Python 2.3 or newer.
|
||||
Version specific notes:
|
||||
- 2.4: this is the version the code is developed with, so you can
|
||||
expect this one to work the most smoothly.
|
||||
- 2.3: in general, it seems to be useable. However, the optparse
|
||||
expect this one to work the most smoothly.
|
||||
- 2.3: in general, it seems to be useable. However, the optparse
|
||||
module of Python 2.3 is out of date. This doesn't have fatal
|
||||
consequences, but if you want nice help optput / version info,
|
||||
you should either use optparse.py from 2.4 or install a recent
|
||||
|
|
|
|||
|
|
@ -37,11 +37,11 @@ Updated 13-Dec-2003 by David McNab <david@rebirthing.co.nz>
|
|||
|
||||
- added 'code.leo' file for convenience of those who use the Leo
|
||||
code editor (leo.sf.net)
|
||||
|
||||
|
||||
- added support for 'statfs' and 'fsync' methods (refer xmp.py)
|
||||
|
||||
Updated Dec 2003 by David McNab <david@rebirthing.co.nz>:
|
||||
|
||||
|
||||
- added support for 'release' events (ie when file gets closed)
|
||||
- added __init__ to base class, which picks off parameters and
|
||||
stores them as instance attributes:
|
||||
|
|
|
|||
|
|
@ -111,7 +111,7 @@ Let's see how these are implemented.
|
|||
out of Python's, so raising an exception makes no sense. We could
|
||||
wrap some fs methods into format valifiers; currently we don't do
|
||||
that.)
|
||||
|
||||
|
||||
|
||||
FUSE and the command line
|
||||
-------------------------
|
||||
|
|
@ -316,7 +316,7 @@ options (which are not understood by the lib, according to the help
|
|||
message), and also purges out these from self, so the remainder can be
|
||||
safely passed down to FUSE.
|
||||
|
||||
.. [#] We can argue that it's not that sad. We just pass on to FUSE
|
||||
.. [#] We can argue that it's not that sad. We just pass on to FUSE
|
||||
what we get from the user and that either eats it or blows up. Why
|
||||
would we want more sophistication?
|
||||
|
||||
|
|
|
|||
Loading…
Reference in a new issue