After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 672323 - Problem with export csv
Problem with export csv
Status: RESOLVED FIXED
Product: Gnumeric
Classification: Applications
Component: import/export other
1.11.x
Other Linux
: Normal normal
: ---
Assigned To: Morten Welinder
Jody Goldberg
Depends on:
Blocks:
 
 
Reported: 2012-03-18 01:48 UTC by David Ronis
Modified: 2012-08-05 01:20 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description David Ronis 2012-03-18 01:48:24 UTC
I have a project (say project.gumeric) that requires me to export a spreadsheet to a csv file (say foo.csv), process it externally (to create bar.csv) and then add the results to the original project.   Several things don't seem right:

1.   When I export to foo.csv, the original project is renamed to "foo.csv - gnumeric" (at least that's what the window title becomes).    To be sure I'm prompted for a new file name when/if I try to save the original spreadsheet, but I don't think that I should have to do this.  I've exported the data, the GUI contains the original project (5 sheets).

2.  One of the project has a spreadsheet containg data from bar.csv (e.g., like =[bar.csv]Sheet1!A1).   I open gnumeric as:

gnumeric project.gnumeric bar.csv

Things work as expected but occasionally I've saved bar.csv (either intentionally or by accident).  The default seems to be to save it as bar.gnumeric.   When it does this it renames all the file references in project.gnumeric to [bar.gnumeric]Sheet1!A1, etc.   This is not what I want, since the external processing creates bar.csv.  Worse, if bar.gnumeric is deleted, the next invocation fails to fill in the spreadsheet correctly, even though bar.csv is present and updated.

3.  This may already exist, but I'd like a reload feature; namely,  if I update bar.csv externally, I'd like gnumeric to be able to read the new version.   The only way I've been able to do this is to read bar.csv multiple times.    What would be even better would be to have gnumeric "watch" the file and reload automatically, or at least present a popup asking if it should do so.
Comment 1 Andreas J. Guelzow 2012-03-18 01:56:40 UTC
Re 1: Users don't seem to agree on what they want: some would in fact prefer if we didn't even prompt them for a new file name, but automatically and silently continue to always save as a csv file.

Re 2: This as again one of the situations where different users expect different behaviours. If you have two related files open and change the name of one file some users will expect the references in the other file to change, Other users do not.

Re 3: this is enhancement request bug #74360
Comment 2 Andreas J. Guelzow 2012-08-05 01:20:33 UTC
This problem has been fixed in the development version. The fix will be available in the next major software release. Thank you for your bug report.