I was happily printlning to the Console Output in the Assistant Editor of a Swift/Xcode 6 Playground (see this SO thread for more info), until I decided to try clicking the [X] to close the Console Output.
How do I bring the Console Output back??
This eluded me for a while, too. You want View menu -> Assistant Editor -> Show Assistant Editor.
Once you see the pane that holds the console output, if you still aren't seeing the right thing, make any change that will cause a println() to fire and the console output should appear.
Just hover your mouse pointer over the value evaluation area (pane next to your coding area) and click on the plus sign to open the output pane. If you have closed the console output in the output pane, then click anywhere in the coding area and press enter. You will get your console output back.
If the View > Assistant Editor > Show Assistant Editor does not work, simple go to the bottom of the screen and drag the little footer up, so it looks like so:
Closing the Playground and reopening did not bring the Console Output back, but quitting Xcode and reopening did. If there's an answer that doesn't require restarting Xcode I'll go for that, but for now this seems to be the answer :/
Yay for beta software!
You can bring back the console frame by following the steps below:
Open the assistant editor. In the assistant editor, find the playground timeline screen.
In the playground timeline screen, find the bottom right corner box, where it contains "- 31 +" (In my case it says the time elapsed is 31; it can differ according to your code).
Click the "+" / "-" mark in the "- 31 +" box.
There your result, console frame along with the other frames could have come there.
The keyboard shortcut is Cmd + Shift + Y
If you've opened the Assistant editor, either by using Cmd+Option+Enter, or selecting the white/plus icon on the left of a line, and then removed the "Console output" there are some alternatives which may help you in getting it back:
Make sure you don't have any errors in your playground, as they stop execution and thusly any output to the Assistant Editor
Make a change so that playground is re-executed
Force a new run of the playground using Editor > Execute Playground
Change the timer in the lower right, as this also triggers a new run of the playground
Restart Xcode as the playground is a little buggy, and you sometimes just need to restart everything... :-(
Put a /* at the top line of your code area to comment out everything. The Console Output box will reappear at the top of the right-hand panel (the Assistant editor panel).
Some errors may show in the Console box. Ignore.
Now delete the /* and the Console box will stay put.
have just started xcode (version 7.0.1) using swift but had the same problem, to show how the code will appear in console I toggled the little triangle next to the play button on the bottom left of the screen
triangle toggle button
this then open a view in which I could see the results of the code
console opend
hope this helps
Related
I am trying to hide this blue line that just started showing up on the left side of my editor. When clicked, it has a "Search" and "Discard Changes" option.
Editor with Blue Line on left side
I'm not sure what I did to make it start showing up. I have looked through the View options but can't find anything to hide it. I don't even know what it is called and am having a hard time googling it.
UPDATE:
So I found out that I can click Source Control --> Commit to make the blue line go away... but every time I edit something it comes back. It wasn't like this before. I must have hit some shortcut combination to turn it on. Please help... Thanks in advance
In Xcode Preferences, go to the "Source Control" tab and you'll see this checkbox:
I am aware that command + ' brings you to the next issue, but is there a way to bring you to the next compiler error and ignore the warnings?
(xcode 9)
I don't think there is a way to do that, but the closest thing you could do to that is to filter the display of issues in the Issue Navigator so it only shows errors and no warnings. Do that with one click, on the icon at the bottom right of the Issue Navigator.
Once you have done that, then the up and down arrow keys navigate you within the Issue Navigator from error to error instead of issue to issue.
To expand on auspicious99's answer, after filtering on errors in the issues pane, you can use keyboard shortcuts end to end:
cmd-5 - selects the issues pane
up/down arrows - select the error you want
cmd-j, enter - move the focus to the editor
In the navigator (the left-hand pane), choose the right-most icon that looks like a speech bubble. You'll see the build results, and when you click on them you'll be taken to the error.
I'm pretty new to R programming. I'm using R studio, and all of a sudden it's no longer showing the workspace, it's only showing the console.
This is what it is supposed to look like
And this is what mine looks like now.
In Eclipse, whenever the workspace gets out of wack, I can just reset the perspective and everything it back to normal. I can't figure out how to do that in R Studio.
The default layout seemed to disappear after I restarted my computer.
Go to View > Panes > Show all panes
Opening a script file should split the windows horizontaly. If that doesn't work, click on the icon on the top-right corner of the RStudio window showing to windows:
This should at least show the console and file panels.
To restore the side panels, move your cursor to the extreme right of the window, until the cross arrows cursor appears (), and drag it to the middle of the screen.
For all panes to be shown, go to View-> Panes and tick show all panes.
Otherwise, ctrl+Shift+Alt+0 also worked for me.
Thank you.
Can you try saving an image of your workspace? Below are a couple of links that might help.
Workspace link 1
Workspace link 2
My computer is set up already in such a way that it automatically loads up the previous workspace I decided to save. A more qualified person would be able to tell you how and why it retrieves the previous saved image instead of a blank one like yours.
I also just got stuck for some time with the vertical split of the panes malfunctioning. I was always stuck with just 2 out of 4 panes.
I'm a pretty confident RStudio user and I tried many things like 'show all panes', moving panes around, clicking the 'hide-window', 'enlarge-window' and 'double-window' icons.
In the end I realised that the panes that were minimized didn't actually have the bar with the title. Instead these we only lines of 1 pixel height.
The solution for me was to expand the bottom panes and then hover near the 1 pixel height line at the top. This changed the cursor into the hand-cursor, which allowed me to drag the top window down, and back into view with the other pane.
In an Xcode Playground you can click the little circle next to the eye and it should show the console, however when I click mine it just shows the quick view box near the code. How can I correct this and set it back to default? I believe it originally worked like that but now does not.
Any suggestions
you can click the little circle next to the eye and it should show the console
I don't think that's right. I see the same result you do: clicking the eye pops open the Quick Look pane. This is exactly the same thing that happens when you point at a variable in a project while debugging: you can click the eye icon and see the contents of the variable in a Quick Look pane.
To open the console in a project or a playground, use the View->Debug Area->Activate Console command.
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.