Related
I accidentally used 'vertical split' and 'horizontal split' in the Spyder editor (View->Window Layouts->Vertical split DON'T CLICK THIS!), now there is no way for me to go back. Does anyone know how to unsplit windows in Spyder?
Never mind, I found the answer when looking at the keyboard shortcuts (as that's how I accidentally split the screen the first way): alt+shift+W
I was having trouble with an older version of Spyder v4 on Mac, and I got it to work by updating to Spyder v4.2.1, right-clicking on the tabs in the panel I wanted to close, and then clicking "Close this panel" closed the split panel.
does anybody knows how to disable the green highlight in Spyder editor as I show in the picture below?
Thanks
Spyder has many settings which the user can change.
In Preferences>Tools>Appearance>Edit Selected Scheme we can select the colors of several highlights, including current cell. (followed by OK then Apply, which can take a few seconds, then OK).
Setting this to #19232d (which seems to be the color of the overall dark theme background) at least gives the appearance of highlighting having been stopped.
There seems to be no way of setting such a color to transparent (in the CSS sense).
Under Tools>Preferences>Editor it seems as though we can unset highlighting of the current cell, but this appears to get overwritten by the Highlight Occurrences after selection, and setting that to something huge in the hopes it would not kick in did not seem to work.
However, I do not claim to be a Spyder expert and would welcome feedback from those who are and who perhaps know of ways of stopping highlighting in certain areas completely.
(Spyder maintainer here) This is caused by a bug in our code. It'll be fixed in our 4.2.0 version, to be released in November 2020.
In the meantime, the solution is to reactivate the option Highlight current line, present in the menu Tools > Preferences > Editor > Display.
I just installed spyder 4.0.1 and am overwhelmed by all the bells and whistles. Which settings should I change/uncheck in order to get back to spyder 3 default behaviour?
Two most pressing problems are with the auto-complete (using TAB) in the editor:
The first item is black on dark blue and therefore illegible. Can I adjust that?
There are way too many irrelevant suggestions. Can I adjust that?
(Python/anaconda/win7 in case it makes a difference.)
(Spyder maintainer here) My answers:
The first item is black on dark blue and therefore illegible. Can I adjust that?
No, but that dark blue color comes from the Windows classic theme, which is really ugly. In the normal Windows 10 theme things look as expected:
There are way too many irrelevant suggestions. Can I adjust that?
Yes. Please see my answer about that: https://stackoverflow.com/a/59724907/438386
In Eclipse, I can type Ctrl+M or click the maximize icon in the editor pane to make the editor pane take up the entire Eclipse window, and then again to restore the pane back to its previous size exposing the other panes.
Is it possible to perform the equivalent in IntelliJ IDEA?
To clarify, I'm asking about hiding all other tool panes to show only the editor pane. I'm not asking how to go to distraction-free mode, because this is mode is completely "full screen", hiding all toolbars, window decorations, etc.
The closest thing would be to hide all tool windows by invoking the Hide All Tool Windows action. The shortcut for that is Ctrl + Shift + F12 (Default keymap).
This will hide all tool windows, effectively maximizing the editor window (though not full screen). The IntelliJ menu bar, toolbar, breadcrumb and tab bar will still be visible.
I'm using IntelliJ 11.1.2 on Kubuntu 12.04 LTS with the Default keymap.
14.0.3 on MacOS X
It's Cmd + Shift + F12 in IntelliJ IDEA 14.0.3 on MacOS X.
UPDATE on 2015-03-24:
IntelliJ IDEA 14.1 now has support for Distraction Free Mode. You can invoke it by clicking View > Enter Distraction Free Mode. In this mode, IntelliJ hides everything but the menu. For more details, follow their video detailing the new feature: https://www.youtube.com/watch?v=uVwE8MFgYig.
If you want to maximize a pane , select that pane (by clicking inside or on its title bar) and then use the shortcut "Ctrl+Shift+Quotes"
You can double click anywhere on the tab title bar of the editor pane.
All answers work for only hiding other tools. If you have more than one editor pane and you want to maximize only one editor pane (hide all tolls and hide all other editor panes), it is not possible right now.
PyCharm version: 2018.2.7
I use Ctrl-Shift-F12("Hide All Windows") toggle between maximum and normal modes of the editor.
Using IntelliJ 14.1.5
If you want to maximize the editor window AND full-screen the app, you can create a macro with the following two commands:
Toggle Full Screen Mode
Hide All Tool Windows
And then assign a hotkey to the macro. Here's how I did this:
File > Settings > Keymap
Use the search bar to search for the two commands above. Assign obscure hotkeys to those.
Edit > Macros > Start macro recording
Hit the two obscure hotkeys you just assigned: this should max the editor and full-screen the app
Stop recording. Name the macro
Open File > Settings > Keymap again. Find the Macros section, find your macro, assign a nice hotkey to it.
I just assigned ^M(ctrl+M) to Main menu | Window | Active Tool Window | Hide All Tool Windows under preferences(by clicking cmd,). This worked for me exactly like eclipse.
something similar can be achieved by opening your tab in a new window.
The default hotkey for that is shift+f4.
the editor tab remains in the main app window as well, and the new window appears on top of the main app window.
This has already been answered, but since when I google "android studio maximize tab" this is the first answer I see, I'm going to add my two cents.
I hate the keyboard shortcuts since, at any given time, I have 1 hand on my keyboard and 1 hand on my mouse. Having to let go of my mouse to hit a 3-key combination to maximize the current tab is not a shortcut. What I was looking for was an Eclipse-style behavior: double-click the tab to maximize. Here's how to do that:
In Android Studio, under Preferences, go to Keymap->Main Menu->Window->Active Tool Window. Right-click the "Maximize tool window" mapping and select "Add mouse shortcut."
For "Click Count" pick "Double Click" and then double-click on the "Click Pad" mouse icon.
Click OK out of the menus and you should now be able to double-click on any tab and it will be maximized. Double-clicking again will minimize it.
Coming from Eclipse to IntelliJ, this was one of the most frustrating aspects I've had to deal with.
full screen plugin is availble for IntelliJ Idea...
https://github.com/jfim/ideafullscreen
If you need to use the same shortcut like Eclipse Ctrl+M, to minimize/maximize the active editor window,
You can follow the below steps:
Open (File > Settings...) or click ( Ctrl+Alt+s )
Select Keymap
Search for "Hide All Tool Windows"
Change the default shortcut to Ctrl+M
Then you will be able to use the same shortcut as Eclipse.
This is quite an old question and the distraction free mode wasn't exactly what I wanted. This is because it does not hide other editor windows. With 2021.1 EAP this issue has been resolved and maximising the editor hides all other editors but the active one.
For people using IdeaVim trying to emulate the <leader> z behavior of tmux, you can use the following mapping:
map <leader>zz <Action>(MaximizeEditorInSplit)
I searched for something like ctrl+b zin tmux. For me, the similar task solved by key combination shift+f4. It opens your tab in the separated window (which can be closed as usual, alt+f4). My PyCharm version:
PyCharm 2019.2 (Professional Edition)
Build #PY-192.5728.105, built on July 23, 2019
Runtime version: 11.0.3+12-b304.10 amd64
VM: OpenJDK 64-Bit Server VM by JetBrains s.r.o
Windows 10 10.0
GC: ParNew, ConcurrentMarkSweep
Memory: 725M
Cores: 8
Registry:
Non-Bundled Plugins:
This is more of a general annoyance. Every time after stopping the simulator, Xcode jumps to main.m for some reason. On the left nav, it jumps to the Debug Navigator.
Is there a way to fix this?
It's annoying because I might be testing a certain line of code, and now each time, I need to make a couple of clicks just to go back to that code.
This problem is not new, seems to get worse though. At the time of writing this, I was on the GM seed, but this problem persists in XCode 4.2 final. This was not a problem in previous versions of XCode.
When we start debug from xcode, the debugger sets itself up to monitor signals from OS. When we press stop button in XCode (or hit cmd + R - which first stops existing instance running and then try to start new one, somewhat equalant to we press manually stop first and then run) SIGKILL is sent to the debugger.
Whenever the cause of interruption is from outside the app (in other words all cases where SIGKILL is sent, like stop button press) , debugger jumps to main, since main is the root of the app and the place where your app meets the OS. Debugger has no way to identify why this SIGKILL is issued (pressing stop button in xcode/ press cmd + R/ delete app from multitasking bar etc), but it treats SIGKILL as outside interrupt, and nothing related with your code. So it jumps to main.
If the cause of interruption is from inside the app (like app crash/SIGABRT) debugger handles it and jumps to the place of crash, which we normally see.
I do not consider this as an xcode bug, rather a normal way of handling SIGKILL. But if you want to stay at your code and do not want to jump to main you can do two things
You can do as Gabe suggested. As BBonified said, it is like a band-aide,
but I think it should work (personally I never tried that)
Report a bug/request for a feature here. Let me tell you you
are not the first one to do so. Already a bug has been reported. See
this and this. But I don't have much hope of a positive action from Apple
And I agree with you, it is sometimes annoying. Especially if you have experienced differently in previous XCode versions. But we can only take what they give here.
I guess it's fair to call it a bug, Xcode 3 specifically suppressed this useless artefact.
I've had success (four times and counting) with this one-liner in ~/.gdbinit:
handle SIGKILL nostop noprint nopass
Taken from this gdb manual:
http://www.delorie.com/gnu/docs/gdb/gdb_39.html
Not sure if it applies to lldb as well.
I tried what David suggested but that didn't work for me, so I tried something similar:
Open Preferences, select Behaviors tab.
Select "Run exits unexpectedly" from left column.
Select "Show debugger with current views".
I'm using Xcode version 4.2 build 4D199.
EDIT: That worked for about 15 minutes. Then it reverted to bringing up main.m in the editor again.
I had the same problem and it WAS really annoying, especially when you were in the middle of debugging, stopping/launching the app several times in a row after small modifications.
Everything is solvable through settings in Xcode user preferences:
Just go to "run completes"
There find the "Show" line and click the checkbox
On the same line modify target to go to "Current" in the dropdown menu.
There you go. Xcode will not move your editing view from now on. Enjoy.
PS: Xcode version 4.2 Build 4C199
Go to Preferences -> Behaviors. Choose "Run Completes" in the left hand side. Check the box next to "Show Tab" and enter a tab name. I use "Edit". This way whenever you stop, you will always be back at a tab called Edit.
None of the other solutions listed were suitable for me, so I made a macro (using an external hotkey utility).
(wait 0.1 second after each step)
command-period
command-1
down arrow
up arrow
command-j
enter
Use this key instead of the normal stop, and you end up with your cursor positioned where you left it. Very nice.
Xcode -> Preferences
Under Behaviors
Click on Run Starts
Checkbox for [Show] debugger with [Current Views]
...worked for me.
None of the preference adjustments seem to work for me.
I have been able to track the offending sequence of events. The SIGKILL error message will occur when you run your app and use multiple threads. For instance, when using UIWebView in my app it will abort to main.m. I verified that when UIWebView is not called, XCode can be stopped without the SIGKILL error message returning the user to main.m
It looks like there are at least two threads that get started when initializing a UIWebView.
However, any threads created by you during the running of your app will cause the SIGKILL to improperly notify XCODE to return to the main.
You can see this in the GDB that there is a switch just before SIGKILL:
[Switching to process 24957 thread 0x2103]
[Switching to process 24957 thread 0x7403]
[Switching to process 24957 thread 0x207]
Program ended with exit code: 0
It is definitely still a bug with XCODE that will hopefully be fixed.
For now, if you avoid executing code that launches a separate thread, it will not change the view back to main.m For code that does launch additional threads, I would recommend quitting the simulator to return to edit mode in XCODE.
None of these solutions worked for me and I find the behavior too intrusive to put up with.
I get round it by using the 'Assistant Editor' instead of the editor as my main editing window. You access the Assistant Editor using the tiny little bow tie button at the top right of the single window.
You can set then it to 'Manual'. Click on the button that is the far left crumb of the breadcrumb trail at the top of the Assistant Editor frame and select Manual from the pop-up menu that appears. The Manual setting allows you to select the file you're editing by clicking on the second to last crumb of the breadcrumb trail and selecting the file from the pop-up that appears.
I then just minimize the size of the main editor - or use it as a secondary editing window, useful given that you can't split the editors into multiple frames any more. Far from ideal - but that's XCode 4 for you.
This might not be much. I was able to avoid this problem 99% of the time by waiting for 2 seconds or so after stopping the app, before relaunching it.
UPDATE: After upgrading to the latest Xcode, I am prompted to use LLDB instead of GDB. The problem seems to be gone now.
I was trying to find the offending line when my code was breaking, so what I did was:
Go to where you define your breakpoints (breakpoint navigator, according to the documentation)
Click in the "+" sign in the left bottom corner of the navigation area
Click on Add Exception breakpoint
You click Done
Run your app
Xcode shows you the offending line.