Ask Your Question
0

Wildcard support in the File Open name box in 4.2.2.1? [closed]

asked 2014-03-28 14:55:44 +0100

wd gravatar image

updated 2015-09-09 20:30:45 +0100

Alex Kemp gravatar image

The documentation says: "If you want, you can use wildcards in the File name box to filter the list of files that is displayed." - this used to work fine in older versions of LO, but I get only "does not exist" error messages in 4.2.2.1.

Is this a bug, or is there some config option to re-enable this feature?

I am using Fedora 20 Linux on x86_64: libreoffice-core-4.2.2.1-7.fc20.x86_64.

edit retag flag offensive reopen merge delete

Closed for the following reason the question is answered, right answer was accepted by Alex Kemp
close date 2016-02-20 16:14:05.970762

3 Answers

Sort by » oldest newest most voted
1

answered 2014-03-28 17:43:00 +0100

Pedro gravatar image

updated 2014-03-29 16:23:16 +0100

Still works perfectly under Windows XP (with LO 4.2.2.1 and newer) when using the Windows dialogs. Typing *.od* shows all Open Documents and typing *.doc* shows all MS Word documents...

The bug does occur in the 4.2 branch when using the LibreOffice dialogs (Tools > Options > LibreOffice > General > Open/Save dialogs > Use LibreOffice dialogs) which is not the default under Windows. I can confirm that it works as expected in the 4.1 branch so this is a regression.

Bug reported as fdo#76778

edit flag offensive delete link more

Comments

This is Fedora 20 Linux on x86_64: libreoffice-core-4.2.2.1-7.fc20.x86_64 etc.

wd gravatar imagewd ( 2014-03-28 19:50:57 +0100 )edit

@wd, can you try the latest RC ( http://www.libreoffice.org/download/l... If the bug still occurs you should report this regression at https://www.libreoffice.org/get-help/...

Pedro gravatar imagePedro ( 2014-03-28 20:21:45 +0100 )edit

@oweng and @wd, just confirmed this is a regression in the 4.2 branch under Windows as well when using the LibreOffice dialogs. I'm modifying my answer accordingly.

Pedro gravatar imagePedro ( 2014-03-29 16:04:28 +0100 )edit

@Pedro, thanks. It appears to be related to certain desktop environment / window managers. As my answer indicated, the lighter weight versions I use to not appear to support this at all. I certainly do not ever recall seeing it.

oweng gravatar imageoweng ( 2014-03-30 00:43:47 +0100 )edit
1

In case this is really dependent on the WM: I'm running fvwm2

wd gravatar imagewd ( 2014-03-30 12:22:22 +0100 )edit

I can confirm that this bug also occurrs in version 4.2.3.3 running on PCLOS 2014. I had to upgrade because text search function stopped working on my earlier version.

Greenwich Villager gravatar imageGreenwich Villager ( 2014-04-15 16:58:21 +0100 )edit

Bug 76778 - Wildcard support in the File Open dialog is broken
Status: RESOLVED FIXED
(LibreOffice 4.2.4 / 4.3.0)

manj_k gravatar imagemanj_k ( 2014-04-17 13:12:58 +0100 )edit
0

answered 2014-03-28 23:50:35 +0100

oweng gravatar image

updated 2014-03-29 00:13:05 +0100

I can confirm that neither Debian 7 + LXDE using v4.1.4.2 or Crunchbang 11 + Openbox using v4.2.2.1 (both website versions) offer wildcard support for the File Open dialog. The File name field only appears when the Tools > Options... > LibreOffice > General > Open/Save-dialogs section > "Use Libreoffice dialogs" option is checked. Regardless of whether the full path and wildcarded filename or just the filename is entered, the displayed list of files is unaffected.

Bugs fdo#46221 and fdo#61557 are related to getting this dialog simplified / cleaned-up however there is no report that I can find relating to wildcard support. Do you know in which prior version it was working?

EDIT: I have also tested Crunchbang 11 + Openbox using v3.5.7.2 (website version) and again there does not appear to be any wildcard support for this dialog. It is possible the help page information is Windows-specific, and that it is the documentation that requires amending.

edit flag offensive delete link more

Comments

1

I have a system where I'm still running 4.1.4.2 (also Fedora 20, i. e. libreoffice-core-4.1.4.2-5.fc20.x86_64 etc.), and there it is still working fine.

wd gravatar imagewd ( 2014-03-29 06:52:44 +0100 )edit

Thanks for confirming. It sounds like it may be related to the desktop environment / window manager in use.

oweng gravatar imageoweng ( 2014-03-29 10:08:17 +0100 )edit

Question Tools

2 followers

Stats

Asked: 2014-03-28 14:55:44 +0100

Seen: 293 times

Last updated: Mar 29 '14