Bug 11776 - Add Command+T command to open a new blank, unnamed, file.
Summary: Add Command+T command to open a new blank, unnamed, file.
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: General ()
Version: unspecified
Hardware: PC Mac OS
: --- enhancement
Target Milestone: ---
Assignee: Bugzilla
Depends on:
Reported: 2013-04-14 08:48 UTC by Jonathan Pryor
Modified: 2013-04-14 12:57 UTC (History)
1 user (show)

Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.

Please create a new report on Developer Community or GitHub with your current version information, steps to reproduce, and relevant error messages or log files if you are hitting an issue that looks similar to this resolved bug and you do not yet see a matching new report.

Related Links:

Description Jonathan Pryor 2013-04-14 08:48:55 UTC
(This is largely desired as a workaround for Bug #11775, but could be generally useful anyway.)

Because of #11775, I cannot search the Build output window. So if I want to search it, and stay within Xamarin Studio, the only alternative I know of is to:

1. Click in Build output panel
2. Command+A (select all)
3. Command+C (copy)
4. File > New > File...
5. Select a file type
6. THINK OF a file name
7. Unselect [ ] Add to project.
8. Command+V (paste)
9. Command+F (find), enter text to find.

This is really 7 steps too long; with 11775 it _should_ be:

1. Click in Build output panel
2. Command+F (find), enter text to find

Failing that, could we at least skip steps 4-7, and replace with these:

n4. Command+T.
  A new "tab" is created, with no file name, no file type,
  and has the insertion point.
n5. Command+V (paste)
n6. Command+F (find), enter text to find.

Steps 1-3 are basically muscle memory. Steps 4-7 are DISTRACTING and break thought. Steps n4-n6 could become muscle memory, removing distraction.

Fixing #11775 would be better, but lacking that could we PLEASE add a way to QUICKLY and EASILY create new text editing tabs?
Comment 1 Mikayla Hutchinson [MSFT] 2013-04-14 12:57:54 UTC
This command would be largely useless, since users vey rarely want to create a new file without a type and not bound to a project. Let's just leave this to bug 11775.