My textmate suddenly stopped recognizing comments in code and the shortcut for commenting out code (Command + /).
I have found Comments in the Bundle Editor for HTML, but it doesn't look like I can set an activation key for it or anything.
Does anyone have any experience with this part of TextMate?
cheers!
Maybe it went out of scope? Doesn't matter what caused it, it's easy enough to fix.
Open your Bundle Editor
ctrl-option-cmd-B
Make sure that the Menu button at the
top left-hand side of the Bundle
Editor displays Show All
If it doesn't then click the up/down
arrow and change it so that does
Scroll down until you find the
Source bundle
Click the arrow to the left of
Source to display the Bundle contents
looking at the Source Bundle items
with green "C"s next to them, find the item
called Comment Line/Selection
Click Comment Line/Selection
In the upper right-hand corner of the
Bundle Editor, click the Settings
button
Next to Activation, select the menu
item Key Equivalent
Whatever is in the text box to the
right, replace it with cmd-/ (with
your cursor in the text field, press
the keys "cmd" and then "forward
slash"
Verify that the item Scope Selector
text area is blank--nothing should be
in there
Exit the Bundle Editor, Restart
TextMate, open a new editor window
(cmd-N) then enter cmd-/ to verify
that it's working
This command is not limited by scope so it will work in any context/environment/language, but because it is not limited by scope it can be overridden by a Bundle-specific comment command (e.g., a comment command in the HTML Bundle, so, if after you've followed those steps, it's still not working, you just need to find that Bundle-specific comment command and either fix it (using the steps above as a template) or then use the steps above as a template) or deleting it.
While you're at it, you might as well fix the command in your HTML Bundle:
from your Bundle Editor, scroll down to the HTML Bundle then click on the Comment item (you said in your Q, you had located it). Click the Settings button on the upper right-hand corner, and verify that Activation is Key Equivalent and cmd-/ is in the adjacent text box. Next verify that Scope Selector is text.html
Related
Out of curiosity, when you open xCode and you want to run your app, you must to click "Play" button:
But when you hover this section, a little arrow appears (downright)
Does anybody know the meaning of that element, I thought it was a hidden menu.
When you click and hold on that button, a Menu will appear where you can switch the default action for this button.
You can see the other options here:
Note that you can modify these options by holding either shift (just build), alt (brings up the scheme selector for that scheme first) or ctrl (don't build, just run).
So, after struggling with horrible interface choices of Xcode 4, I'm finally on 5.1.1.
The tabs became almost usable. Double clicking can be configured to open a file in a new tab. Good. Double clicking another file opens it in a new tab. Good. Double clicking first file again switches to previously open tab. Good! Double clicking first file while it is open in current tab opens a second tab with that file. Ok, I can live with that, since from there on they just switch from one to another.
So far a surprisingly sane behavior.
Unless you make a single click in the navigation panel by mistake. Single click opens whatever you click in the current tab, all logic and reason be damned.
The question is, how to change single click behavior to "Use separate tab" (or however Xcode refers to that behavior)?
Is there any way to disable single clicks from doing anything at all aside from highlighting the selection?
There's no option to disable the single-click behavior. Two options that get you close to your desired behavior are:
Use a single separate window for most of your tabs. Use a "main" window that has the file navigator visible, and a separate "work" window with the file navigator hidden. If you want to add a tab to the work window, create it in the main window and then drag it's tab over to the work window. This is an extra step, but you'll never have a single click change any of the tabs that you care about (thought it'll still change the primary or focussed editor in the main window, depending on your settings).
Use separate windows for each file. There's a preference setting that lets you create windows instead of tabs when you double-click a file in the file navigator. Use Mission Control instead of the tab bar to navigate between your files.
I am very new to this, and my c9 terminal seems to be frozen. The cursor is blinking, but when I try to enter text, nothing shows up. I have tried exiting my workspace and reloading and it still will not work.
Opening a new terminal tab with the View menu or pressing ALT-T is the best bet to get a working terminal back (as mentioned in the comment above)... you may also find that having selected the broken terminal though, you can't click things in your menus anymore. I've found that pressing the Preview button and then closing it, seems to get the UI to be responsive again.
Supports official response is that you should perform workspace reset using ?reset=1 after your workspace url (which doesn't last or work very well in my experience).
This can happen after pressing ctrl-s, pressing ctrl-q should restore it. See https://unix.stackexchange.com/a/12108/41174 for explanation.
I tried ALT-T and ?reset=1. Nothing helped in my case.
I managed to bring my frozen terminal back to life by closing its tab. I ignored the warning that all processes would stop. Then I clicked on the rightmost tab with a plus sign. In the menu I selected "New Terminal".
You can click at the top right where CPU usage is shown. Then click on "Restart" when the menu appears.
I am trying to add a shortcut to the exectuable in the user's start menu.
There are many answer on StackOverflow that detail how to do this.
However, the all say something along the lines of 'Right click in the right-hand pane to...'
So I understand you all have an interface that looks something like:
I don't have the panel on the extredme right - entitled 'Name' containing the Primary Output.
I have gone through every menu option I can find to enable this pane, but can't find it.
Anyone know how to show this window?
I am wondering wether or not the splitter has been dragged all of the way to the right. Try collapsing all of your side menus like the solution / property / toolbox etc.. to make sure that the File System editor is filling the entire window then look if you can see a splitter to the right. I have not found any way to delete that panel yet. You can also try right clicking on the File system Tab and tell it to float then make it go full screen to see if the splitter is visible then.
I had the same problem, tried to find another splitter but couldn't, got the 2nd detail pane by opening Visual Studio 2010 using the 'Run as administrator' command.
I just got into the office, and booted up my computer to work on my current project.
I hopped into a class file, and selected (through mouse highlighting) a group of events to delete.
What happened though was it only erased one character. Wondering what happened, I clicked at the beginning of the selection and re-highlighted the text to delete it again.
So i just clicked randomly in the middle of the file, and it highlighted from the beginning of the first selection all the way to where I clicked in the middle.
I have rebooted both VS, the computer and insured that sticky keys and all other "accessibility" software was turned off.
UPDATE
When I click shift and try to manually highlight with my arrow keys, the cursor doesn't even move.
UPDATE
When I click escape from the selection it goes to the search drop down:
alt text http://img69.imageshack.us/img69/9591/searchbox.png
The same thing happened to me, I held down the shift key for a few seconds then while still holding it down I clicked anywhere in the open page in Visual Studio, and voilá, my mouse click was back to normal.
I imagine I had unwittingly activated some kind of keyboard shortcut but not sure which
I had this same problem too. I believe I found the solution: check your keyboard options.
Go under tools -> options, under the Environment subtree, click 'Keyboard'. Then, you will see a dropdown with the label "Apply the following additional keyboard mapping scheme". If you select "Brief" from this, you get the keyboard behavior as described. I'm not exactly sure what "Brief" refers to, but it certainly isn't familiar to me.
Change the keyboard layout back to (default) or another one to get the behavior you expect.
Reinstalled VS and now everything is better.