I was playing around with the CSS in the Atom editor the other day, open it back up today and this is what I see.. Every time I try to close any of those 3 tabs it freezes up, I've even rebooted my computer to no avail.
Unchecking "Open Empty Editor On Start" and you know.. that worked for some reason.
Not sure why this happens, but I have encountered similar problem that was caused by tabs opened last time.
Usually, I solve the problem by opening with "Clear window state". The command (I see that you are using ubuntu?):
atom --clear-window-state
Reference
I am not sure what started it, but now suddenly when trying to use Atom (on Ubuntu Linux), it opens fine, but keeps focus on the upper-left text of the open tab. For instance, if I try to click somewhere else in the file to move, the cursor, the cursor jumps back to the beginning of the file. If I click on another tab to look at a different file, it immediately jumps back to the original tab, upper left corner of the text. If I hit ctrl-f to search for something, focus jumps back to the text editor. If I try to switch to a different application like Chrome or the terminal window, Atom immediately comes back into focus.
Has anyone else run into this behavior or maybe knows what's going on?
I tried purging and re-installing but am still running into the same behavior.
I figured out that the behavior presents itself any time I try to edit a .ts file, at which point it automatically opens a file "child.js" in the TypeScript plugin directory and begins to display this behavior. I updated the TypeScript plugin and that seemed to fix it. Maybe this can be of help to anyone else who runs into the issue. (Bug link: https://github.com/TypeStrong/atom-typescript/issues/1098)
I recently updated RStudio for Windows via download link mainly due to interest in the new features of the most recent version 0.99.878. Unfortunaly after the installation some important hotkeys behave different in the source editor, while they still work in the Console. I.e.
Ctrl+S starts an "isearch"
Ctrl+V jumps to the end of the document
When I enter Ctrl+X+(S or V) the hotkeys work as they should. The hotkeys can be customized, however when I open the Keyboard Shortcuts dialog it shows me the settings for the hotkeys. Also the cursor has turned to a shiny green rectangle (insert isn't activated).
The problems remains after switching the project. Also reinstalling Rstudio 0.99.878 didn't work out. I've seen a similar issue here, but think mine is different as it is installation related. I might have accidentally activated a special editor setting but couldn't find any.
It sounds like you may have (accidentally?) activated Emacs keybindings. If you go to Tools -> Global Options..., you can reset the preference here:
this is driving me crazy. Everytime I click on the terminal, I get text output but the click does not happen. I can't select anything, scroll on the terminal or perform any mouse operations.
For example, if I click I get things like "TB#TB", which is "TB" when I click and "#TB" when I release the click. If I scroll I get 'UC'` for every scroll of the wheel. Total rubbish.
I'm using cygwin to connect to a redhat machine and it happens only for this one machine. If I connect to a different one, also running redhat, it doesn't happen, so I think the issue is on the remote machine's side. It's also independent of what shell I'm using.
Any ideas?
EDIT: I discovered that pressing shift returns all the usual mouse functionality. I wonder why.
This is more like a "come down to your machine and solve problem"
You must have save default setting for that particular machine to direct it to shift option. As you said shift solves the problem.
You should reset the settings.
go here.
Putty configuration>windows>selection>click on shift overrides application's use of mouse
hope this helps
My NSLog messages no longer show up in my Debug Area. Anyone have an idea how the could have happened?
I can hit command-7 to bring of a list of logs in the left pane, select the latest one and view it in my editor window, but it is extremely annoying compared to having the console output in the debug area.
I had the same issue. Below are fix for this :
You console may be hidden. Press Show the console button present in right corner (blue coloured when console is open).
You may be displaying Debugger or Target output. Select All Output (Checkmark is displayed when selected).
a. Open Xcode preference (shortcut: cmd + ,).
b. Select Behaviours tab from pop-up.
c. From the Build sections select Succeeds.
d. Enable Show debugger with Current Views.
e. Select Console View from the drop-down list.
Not sure but may be you have clicked on one of the three buttons at the top right corner of the debug area that are used to either show only variables view, only the console or both.
if you want to display Debug area always, then follow these steps:
Goto XCode > Preferences > Behaviors > Succeeds >
Check checkbox of Show tab named
Type DEBUG in the textbox next to Show tab named
select separate window in dropdown next to Textbox
Now click checkbox before debugger with and select Console View in the dropdown
Now when you will run our app, console window will popout itself.
And shortcut key for this is command+shift+y
For me, the answer is to 'activate console'
Go to view -> Debug Area -> Activate Console
You have a few choices:
In the menus, select View -> Show Debug Area.
In the View selection controller in the upper right, enable the bottom view (the one in the middle).
If you'd like this to show automatically, go to Preferences -> Behaviors. Select "Run Starts" and enable "Show" Debug Area.
For Xcode 8
I set OS_ACTIVITY_MODE to disable to hide crazy logging message in simulator. But it will also hide NSLog output on my iPhone SE device (print function in swift still works).
Remove the environment variable makes NSLog work again.
Make Sure that in your Debugger Area >> Debugger Bar you have Selected ALL OUTPUT
I had an iOS universal app that would show debugger output for the iPhone version, but not for the iPad version.
I looked into editing the schemes ( commandSHIFT, ) and the iPad scheme had a different debugger than the iPhone scheme. I changed the iPad scheme's debugger to match the iPhone's (from LLDB ---> GDB)
Took me a while to figure this out... Here's a screenshot of Xcode 6.1.1. Make sure you have chosen All output at 1 and activated the output pane in 2. Somehow the output pane suddenly was gone for me and I just didn't see the icons at the bottom for like 2 hours.
Just confirm that you have Xcode open with similar rights as you have the ownership of the files you are trying to build/run and also make sure you have same rights to the build directory. I noticed Xcode won't show any debug output if rights were mismatched. I figured this after facing so much harassment. When this happened, utilities>console was still showing logs. I used that as a workaround.
Mine is: Xcode 4.2 Build 4D199 on OS X 10.7.2
For me, "Debug Executable" in Scheme Settings (Product-->Scheme-->Edit Scheme: Run) had been unchecked.
On an 12.1 Xcode version you can do either:
Option 1: View > Debug Area > Activate Console
Option 2: Shift + cmd + c (to activate console)
Option 3: (if your console is already activated) Shift + cmd + y
Here is a picture for you:
picture that shows menus and options
If you don't have anything displaying in the logs, the log view will unselect itself and not display itself. You could add a printf and verify this.