Bug#271853: see fails on filenames with spaces within
#include <hallo.h>
* Rene Engelhard [Fri, Sep 17 2004, 10:55:38AM]:
> > OO starts but reports two errors with opening the file "/tmp/te" and
> > "st.ppt", so apparently there is some trouble with passing the
> > arguments. Maybe some broken script that deals not correctly with
> > filenames and splits the name into multiple arguments on spaces.
> >
> > Running ooffice itself on suche files seems to work.
>
> Did I miss something or why is it a bug in openoffice.org-debian-files when
> see (wtf is see?) works not and ooffice (which is
> openoffice.org-debian-files) works?
>
> o* btw does /usr/lib/openoffice/program/soffice "$@" so it should work(tm).
It does work. I found the error in ~/.mailcap which did not have quotes
signs. The funny things is: what created this file? I see lines like:
application/vnd.sun.xml.writer.global;/home/blade/.openoffice/1.1.1/soffice %s
application/vnd.stardivision.writer;/home/blade/.openoffice/1.1.1/soffice %s
application/vnd.stardivision.writer-global;/home/blade/.openoffice/1.1.1/soffice
%s
application/x-starwriter;/home/blade/.openoffice/1.1.1/soffice %s
So it looks like it was written by OO. But a) when? b) why? c) why is it
so broken?
Apparently, it was a work of version 1.1.1 but IMO you should warn your
users about such problematic cruft, left behind in their $HOMEs.
Another issue: when you open an empty (zero length) file, OO exists
immediately with error 1. Maybe it should display a message explaining
why it terminates now.
Regards,
Eduard.
--
"After watching my newly-retired dad spend two weeks learning how to
make a new folder, it became obvious that "intuitive" mostly means
"what the writer or speaker of intuitive likes".
- Bruce Ediger, bediger@teal.csn.org, on X the intuitiveness of a Mac interface
Reply to: