Bug 404073

This assumes you want to overwrite your file or at least base your file naming on existing files, which FileWidgets can't guess for the users.
So I believe the behavior is fine.

Clicking on the desired file in the view would give the result you expect.

(In reply to Méven Car from comment #1)
> This assumes you want to overwrite your file or at least base your file
> naming on existing files, which FileWidgets can't guess for the users.
> So I believe the behavior is fine.

No. Otherwise also completing name without extension would meant that I want to overwrite existing name, because I can select name from a list of names already existing files, whereas I want only use part of this name.

I'm not sure, maybe I wasn't clear earlier. I meant that pup up list doesn't appear if I start typing in case if extension of file is present in field.


> Clicking on the desired file in the view would give the result you expect.
Yes. So why we have completing at all? We can click on file name on the list, ritght?

I would like to get suggestions of names just without take your hands off the keyboard. The same what I get if I start typing name when field is empty.

I see, just to rephrase, what you suggest would be to have completion disregarding extension.

And make the example more detailed:

In your example, in folder you have 

MyScreenshot_1.png

You have Screenshot_DATE_TIME.png in the text field with Screenshot_DATE_TIME selected.
You type "My", field text is now My.png all text unselected with cursor before .png .

At this point you would like to have the completion popup with "MyScreenshot_1.png" offered.

So it's a feature request to have smarter completion when saving files.

>> Clicking on the desired file in the view would give the result you expect.
> Yes. So why we have completing at all?
Completion match works currently by comparing the beginning of file names.
Removing the extension works too (typing four times Suppr key for instance)

But given our behavior of pre-selecting text excluding extension your suggestion makes sense.

> We can click on file name on the list, ritght?
Of course.

(In reply to Méven Car from comment #3)
> I see, just to rephrase, what you suggest would be to have completion
> disregarding extension.
> 
> And make the example more detailed:
> 
> In your example, in folder you have 
> 
> MyScreenshot_1.png
> 
> You have Screenshot_DATE_TIME.png in the text field with
> Screenshot_DATE_TIME selected.
> You type "My", field text is now My.png all text unselected with cursor
> before .png .
> 
> At this point you would like to have the completion popup with
> "MyScreenshot_1.png" offered.
> 
> So it's a feature request to have smarter completion when saving files.
Yes. I met such completion in some applications in Windows, so I thought would be nice to have it here in my favorite DE.

> >> Clicking on the desired file in the view would give the result you expect.
> > Yes. So why we have completing at all?
> Completion match works currently by comparing the beginning of file names.
> Removing the extension works too (typing four times Suppr key for instance)
> 
> But given our behavior of pre-selecting text excluding extension your
> suggestion makes sense.

Simple scenario. In spectacle I click in "Save as", get file save dialog, whereas file name is highlighted excluding extension I start typing, so name is removing and now even I enter begin of name as is present in other files in opened directory then nothing is completed. I need to remove extension to get completion. 
Having completed file name I can easy correct it and don't need neither to remove extension to get completion nor enter whole file name or even click.
This is obvious that completion of file name makes life easy in managing files.

> > We can click on file name on the list, ritght?
> Of course.

You can change it as feature request if this is possible here.

Merging with another bug report for the same behavior - thanks!

*** This bug has been marked as a duplicate of bug 452996 ***