This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 189286 - Get at a file open in the editor via the filesystem browser
Summary: Get at a file open in the editor via the filesystem browser
Status: RESOLVED DUPLICATE of bug 203457
Alias: None
Product: utilities
Classification: Unclassified
Component: Open File (show other bugs)
Version: 6.x
Hardware: Macintosh (x86) Mac OS X
: P3 normal (vote)
Assignee: Jaroslav Havlin
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-08-07 07:30 UTC by saltybanana
Modified: 2012-12-19 10:33 UTC (History)
0 users

See Also:
Issue Type: ENHANCEMENT
Exception Reporter:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description saltybanana 2010-08-07 07:30:30 UTC 
I would like a quick way to get at the file that is open in the editor via the native filesystem browser.  Here are some ideas:

1. Right-click on the tab, and offer to take me to the file using the native filesystem browser.  Ideally, it would take me to the directory where the file is and highlight the file.

2. Right-click on the tab, and offer to copy the full path of the file.  Then, at least I can paste it into a terminal window or the filesystem browser.

3. Make one or both of the above available in the Projects and Files window as well.
Comment 1 Jaroslav Havlin 2012-12-19 10:33:08 UTC 
> 1. Right-click on the tab, and offer to take me to the file using the native
> filesystem browser.  Ideally, it would take me to the directory where the file
> is and highlight the file.
> 3. Make one or both of the above available in the Projects and Files window as
> well.
Duplicate of bug 203457.

> 2. Right-click on the tab, and offer to copy the full path of the file.  Then,
> at least I can paste it into a terminal window or the filesystem browser.
Already fixed, see bug 153728.

Thanks for reporting.

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