https://bugs.documentfoundation.org/show_bug.cgi?id=89683

--- Comment #38 from Peter <[email protected]> ---
(In reply to Julien Nabet from comment #37)
> I know that most of the times, we open a csv with a spreadsheet application.
> (but as 
> In the current situation as V Stuart indicated
> - if LO is closed and you launch it with a csv, the by default application
> is Calc
> - if you have Writer and Calc in the same time, you just have to make Calc
> the active application and the csv will open in it.
> 
> now, let's say we change the behavior: if I want to open the csv in Writer
> for any reason, I'm stuck.
> 
> Finally, the debate has been already done and a decision was made, no need
> to reopen this one.

I think you have made an eloquent argument that this is a bug and you should
fix it.

I'm going to call it "writer mode" if a writer file is open. I don't if you
have an explicit modal design, so apologies if I am using the terminology
incorrectly.

Here are the ways to open a CSV file:

1. Double click in the finder: opens a calc file (even if a writer file is
open).
2. With no open windows, File Open->pick from file list. All file types are
available and open the appropriate module. csv loads in calc.
3. In writer mode, File Open->pick from file list: csv files are greyed out.
You cannot open it as a text file.
3. File->Recently Opened (in calc mode): .csv files show and load in calc. 

If you uncheck the option current module only, CSV files do appear. 

4. File->Recently Opened (in presentation mode): .csv files show and load in
calc
5. File->Recently Opened (in writer mode): .csv files show and load in writer

So it looks like the only way to open a CSV in text mode is open the csv file,
then close it, then open a text file, the use File->Recently Opened to open it
as text file.


Given that this bug has been reported several times and that no one has
complained about how difficult it is to open a csv as text file, I would argue
that this is correctly reported bug and it needs to be fixed.

-- 
You are receiving this mail because:
You are the assignee for the bug.

Reply via email to