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

--- Comment #6 from ady <[email protected]> ---
Although I could be wrong – apologies if I am – this is possibly related to
some requests to skip the Import Text dialog under some situations (so it does
not show up with ctrl+v anymore) which (at least initially) hinted that the
Import Text dialog was somewhat superfluous under certain conditions, and that
skipping it should be the default.

If, under any circumstance, the Import Text dialog should be considered
redundant, IMNSHO that change should never be the default. The default should
always be to show it (i.e. maintain the old prior behavior), and only the user
should be able to manually change the case to skip it. The user should be
completely aware that he is the one in control and that the old dialog "almost
always bothers him", so he decides to skip it "permanently" under "XYZ" case.

For some reason some users now find that the Import Text procedure (or when
opening some CSV-like file) is different than it was before, and they don't
understand the reason, nor how to solve it.

There is a chance that manually triggering some dummy csv file import once
(i.e. at least 2 rows of dummy data) and (during the Open File dialog) changing
the checkbox "Edit filter settings" might restore the old behavior for the OP.
I am not saying it surely will, but it is easy to test.

I am aware that opening a csv file is not exactly the same as pasting with
ctrl+v, but the Import Text dialog can be involved in both of them.

Alternatively, try to ctrl+v text that ends with at least one CR/LF or that has
at least 2 lines of text; it might be different than one line of text. Not sure
it will help, but (again) it is easy to test.

<https://wiki.documentfoundation.org/ReleaseNotes/25.8#Calc>

"Text Import dialog, that is used in CSV import…"

I do not recall the specific tdf report / commit that initially introduced the
"skip the Import Text dialog when ctrl+v" modification.

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

Reply via email to