I just had the strangest experience I can remember since I ran Windowsas my base OS....
Yesterday I was editing a file in the OO Writer (word processor). Today, it will not open. I copied it to a new file, and it opened fine. I edited it, updated it and closed it. Then I tried deleting the original file and copying the new one to the old name. Won't open. Renamed again, and it opens fine.
WTF???? Does OO and/or the writer have name prejudices that develop?
Thanks.
mhr
--- Mark Hull-Richter mhullrich@gmail.com wrote:
I just had the strangest experience I can remember since I ran Windowsas my base OS....
Yesterday I was editing a file in the OO Writer (word processor). Today, it will not open. I copied it to a new file, and it opened fine. I edited it, updated it and closed it. Then I tried deleting the original file and copying the new one to the old name. Won't open. Renamed again, and it opens fine.
WTF???? Does OO and/or the writer have name prejudices that develop?
Thanks.
mhr _______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
LOL! I must say you do have the strangest things happening to you.
Could it be all caused by operator error? Hmmmmmmmmm. What do you think?
Steven
Get your Art Supplies @ www.littleartstore.com
On 8/24/07, Steven Vishoot sir_funzone@yahoo.com wrote:
LOL! I must say you do have the strangest things happening to you.
Could it be all caused by operator error? Hmmmmmmmmm. What do you think?
I won't rule it out as yet.
However, when the file won't open (or writer even start up) from the command line using gnome-open <filename>, but it will with gnome-open <filename1>, when I open the writer from the applications menu and go to File->Open and select the file and it does not open but the renamed file does, and when I open a Nautilus window and have the exact same results, I have to wonder how much operator action could be involved.
FTR, I checked the file and directory permissions - identical and correct (well, yeah, if I just rename the file between the names and one works and the other doesn't...).
I know there's a funky permissions problem somewhere in some conf file or other on the machine because a lot of things don't work quite right at the moment, but so far I haven't heard a clue (e.g., previously posted issue with not being able to open pdfs, jpgs and certain other files directly from nautilus but okay with right-click->Open With), but at least they open one way or another - this one doesn't.
Besides, if the solution was that easy or obvious, I wouldn't have raised it here (not any more).
mhr
This was too stupid even for me. However, I plead a gaping lack of feature in OO, to whom I will address my complaint.
Never mind. Where's that hole I need to crawl into...?
mhr
On Fri, Aug 24, 2007 at 03:55:26PM -0700, Mark Hull-Richter alleged:
This was too stupid even for me. However, I plead a gaping lack of feature in OO, to whom I will address my complaint.
Never mind. Where's that hole I need to crawl into...?
I must have missed an email. What was the problem?
On 8/24/07, Garrick Staples garrick@usc.edu wrote:
On Fri, Aug 24, 2007 at 03:55:26PM -0700, Mark Hull-Richter alleged:
This was too stupid even for me. However, I plead a gaping lack of feature in OO, to whom I will address my complaint.
Never mind. Where's that hole I need to crawl into...?
I must have missed an email. What was the problem?
Pilot blind-spot - you didn't miss a thing....
On Friday 24 August 2007 18:55:13 Mark Hull-Richter wrote:
On 8/24/07, Steven Vishoot sir_funzone@yahoo.com wrote:
LOL! I must say you do have the strangest things happening to you.
Could it be all caused by operator error? Hmmmmmmmmm. What do you think?
I won't rule it out as yet.
However, when the file won't open (or writer even start up) from the command line using gnome-open <filename>, but it will with gnome-open <filename1>, when I open the writer from the applications menu and go to File->Open and select the file and it does not open but the renamed file does, and when I open a Nautilus window and have the exact same results, I have to wonder how much operator action could be involved.
FTR, I checked the file and directory permissions - identical and correct (well, yeah, if I just rename the file between the names and one works and the other doesn't...).
I know there's a funky permissions problem somewhere in some conf file or other on the machine because a lot of things don't work quite right at the moment, but so far I haven't heard a clue (e.g., previously posted issue with not being able to open pdfs, jpgs and certain other files directly from nautilus but okay with right-click->Open With), but at least they open one way or another - this one doesn't.
Besides, if the solution was that easy or obvious, I wouldn't have raised it here (not any more).
mhr _______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Lock file on the original file?
On 8/25/07, John Bowden j-alan@btconnect.com wrote:
Lock file on the original file?
Something like that (pilot error).
--- Mark Hull-Richter mhullrich@gmail.com wrote:
On 8/25/07, John Bowden j-alan@btconnect.com wrote:
Lock file on the original file?
Something like that (pilot error). _______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
come on we are chomping at the bits to know what went wrong? ;-0
Steven
Get your Art Supplies @ www.littleartstore.com
On 8/27/07, Steven Vishoot sir_funzone@yahoo.com wrote:
--- Mark Hull-Richter mhullrich@gmail.com wrote:
Lock file on the original file?
Something like that (pilot error).
come on we are chomping at the bits to know what went wrong? ;-0
Having watched (and occasionally delivered) some heavy-handed clue-by-four training to Mark, perhaps he simply wants to keep some dignity here by not admitting such an error and having half the mailing list laugh at him. I can completely understand the sentiment, and I respect his desire to keep his mistake to himself.
Having said that... this is the centos mailing list.....
OUT WITH IT MAN! WE WANT TO KNOW!!!!!!!111111eleventy111!!!
:-P
/God I'm a jerk
On 8/27/07, Jim Perrin jperrin@gmail.com wrote:
Having watched (and occasionally delivered) some heavy-handed clue-by-four training to Mark, perhaps he simply wants to keep some dignity here by not admitting such an error and having half the mailing list laugh at him. I can completely understand the sentiment, and I respect his desire to keep his mistake to himself.
Having said that... this is the centos mailing list.....
OUT WITH IT MAN! WE WANT TO KNOW!!!!!!!111111eleventy111!!!
:-P
/God I'm a jerk
Oh, fine,, I can't resist this one (LOL!).
I already had the file open, but minimized, where it is invisible entirely unless you are in the workspace where it is minimized, and then it is hard to see unless you (okay, me) are looking for it.
I did file a feature request with the OO folks that if a file that is already open is opened again that there be SOME response that is more than just nothing (preferred actionL restore the window in its own (or the current) workspace, alternatively flash something on the task bar).
I did say that I would not rule out operator error.
So much for my dignity. Thanks, Jim and everyone.
:-)
-
Garrick Staples -
Jim Perrin -
John Bowden -
Mark Hull-Richter -
Steven Vishoot