Bug 165406 - oowriter cannot start from the shell given a new filename
Summary: oowriter cannot start from the shell given a new filename
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Fedora
Classification: Fedora
Component: openoffice.org
Version: 4
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Caolan McNamara
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2005-08-09 00:37 UTC by J. Erik Hemdal
Modified: 2007-11-30 22:11 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2005-08-09 06:47:49 UTC


Attachments (Terms of Use)


Links
System ID Priority Status Summary Last Updated
OpenOffice.org 53065 None None None Never

Description J. Erik Hemdal 2005-08-09 00:37:53 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.10) Gecko/20050720 Fedora/1.0.6-1.1.fc4 Firefox/1.0.6

Description of problem:
When I use a command such as

oowriter filename.odt &

at the command prompt, the program responds with a dialog box stating that the file does not exist.  Oowriter does not start in this situation.

Version-Release number of selected component (if applicable):
openoffice.org-writer-1.9.117-3.1.0.fc4

How reproducible:
Always

Steps to Reproduce:
1. Issue the oowriter command with the name of a new, nonexistent file as it's argument.
2.
3.
  

Actual Results:  Dialog box appeared telling me that the file does not exist.

Oowriter does not start.

Expected Results:  The program should have started, and created a new file for me given the filename, and it should take the file type based on the extension.  If there is no extension, assume the default file type.

Additional info:

This is perhaps a small item, but it is really helpful to be able to create a new file on the fly.  This would improve usability a lot for those who use the shell prompt.

Comment 1 Caolan McNamara 2005-08-09 06:47:49 UTC
Enhancement is more suitable for upstream, I've logged it as
http://www.openoffice.org/issues/show_bug.cgi?id=53065


Note You need to log in before you can comment on or make changes to this bug.