Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 163669 - Can't insert files starting with dot in the filename
Summary: Can't insert files starting with dot in the filename
Alias: None
Product: Fedora
Classification: Fedora
Component: evolution
Version: 4
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Dave Malcolm
QA Contact:
Depends On:
TreeView+ depends on / blocked
Reported: 2005-07-20 05:19 UTC by Joachim Backes
Modified: 2007-11-30 22:11 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2005-07-20 18:02:03 UTC

Attachments (Terms of Use)

Description Joachim Backes 2005-07-20 05:19:12 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.8) Gecko/20050524 Fedora/1.0.4-4 Firefox/1.0.4

Description of problem:
I was composing an email, and I tried to insert a file in my home dir starting with a dot (".") in its name, but the file selector did not present this file.
Additionally, I could not insert any arbitrary file by entering its complete name.

It should be possible to insert each text file by directly entering the file name including the complete path.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1.Compose new email by evolution.
2.Insert->Text file ...

Actual Results:  The file selector was presented without the presenting the dot files.

Expected Results:  All files are presented.

Additional info:

Comment 1 Dave Malcolm 2005-07-20 18:02:03 UTC
You can type arbitrary filenames by pressing Ctrl-L; it will offer suggestions
based on all files in the current directory that complete the text you have
typed so far.

Hope this helps.

Arguably this feature should be easier to discover, though I'm going to resolve
this as NOTABUG for now.

Note You need to log in before you can comment on or make changes to this bug.