>The answer here is yes it should be (or more accurately, gmailfs relies >on it being on). It is by default and most people don't seem to change >it which is why we are seeing so few people reporting it. Hopefully >Magnus can confirm this when he's fixed the other problem. > >I haven't had time to test it by the intention of the snippet code is >that when the information can't fit into the snippet it falls back to >the body of the email. Therefore the patch someone posted earlier >which trapped the snippet error may be worth considering for the rare >cases where users have turned snippets off.
I've finally found the time to test the version of gmailfs currently in
Sid (0.7.2-2). Things seem to work better. I had some initial trouble
due to snippets not being on. The error message was less than helpful
("ls: reading directory gfs/: Invalid argument") but the discussion in
this thread pointed me to the solution.
% ls gfs
% touch gfs/hello
% ls
hello
% vim gfs/hello
# wrote a line, saved and excited
% cat gfs/hello
Hello, how are you doing?
Vim was complaining a bit but the changes seemed to stick nonetheless.
Vim error: "Write error in swap file"
gmailfs error:
TypeError: object doesn't support slice assignment
Traceback (most recent call last):
File "/usr/lib/python2.4/site-packages/gmailfs.py", line 1004, in write
written = f.write(buf,off)
File "/usr/lib/python2.4/site-packages/gmailfs.py", line 424, in write
self.buffer[self.currentOffset%self.blocksize:] =
buf[written:written+thiswrote]
TypeError: object doesn't support slice assignment
It looks like gmailfs could do with some TLC. :-)
/M
--
Magnus Therning (OpenPGP: 0xAB4DFBA4)
[EMAIL PROTECTED] Jabber: [EMAIL PROTECTED]
http://therning.org/magnus
Software is not manufactured, it is something you write and publish.
Keep Europe free from software patents, we do not want censorship
by patent law on written works.
Finagle's Fifth Law:
Always draw your curves, then plot your readings.
pgpzlbpzCVhd6.pgp
Description: PGP signature
