I've somehow turned off the feature in JupyterLab where when I highlight something say
1,2
And press the bracket (, {, [ it would automatically add the second bracket at the other end.
I don't know what this feature is called, but it's so helpful and I'm crazy annoyed it stopped working.
Restarted already, it still persists.
Can someone help me turn it back on?
The changelog of JupyterLab for 3.1 version, specifically the user-facing changes section, describes that:
The closing bracket is no longer automatically added by default; the old behaviour can be re-enabled from the menu bar (Settings -> Auto Close Brackets) or from the Advanced Settings Editor.
This is the seventh option in default JupyterLab 3.1 installations, and second from the bottom on the picture above. For more discussion and to provide constructive feedback please go to jupyterlab issue #5741.
For JupyterLab 3.1 onwards, the auto close brackets feature is not the default anymore.
Fortunately this could be easily toggled from the UI, see picture below:
Related
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:
When:
Live Preview is running
I'm writing CSS
& I hit Enter to use an auto-completion recommendation
Then:
The auto-completion occurs
The cursor skips down a line & indents
I usually work around this annoying cursor movement by closing Live Preview, but I'd really rather not. Is this a bug or am I missing something? How can I fix it to where it just simply fills in the auto-completion recommendation?
Thanks!
Brackets 0.41
Windows 7
Brackets doesn't normally behave this way - you may have an extension installed that's causing trouble. Try using Debug > Reload Without Extensions and see if the problem still happens. If that fixes it, you can systematically disable individual extensions until you find which one was causing the problem. I believe the "Emmet" extension has caused some similar issues in the past, so that might be a good one to check first.
Once you know which extension causes the problem, I can walk you though filing a bug with the extension's author so it can be fixed.
If you're seeing the issue even after Debug > Reload Without Extensions, then it would be good to get more specific with the steps that trigger the problem. For example:
Open the default "Getting Started" project and open its main.css file
Start Live Preview
Add a new line to the end of the body rule
Type font-w and press Enter
type b and press Enter
When I do these steps, no extra newline is inserted. What steps should I use instead to see the problem?
I found this as I was experiencing the exact same issue. Try disabling any scripts called in your html one by one to see if it goes away. My issue was a script I was loading from a Wu
So I recently moved all of the files that I want to keep onto a secondary hard drive in my laptop. This also included the workspace I use for Aptana Studio 3. As a result, there was a particular file that I had to delete and let the program recreate just to get the program to start up as well as re-import the projects I was working with.
The issue now, though, is that I cannot change or even bring up the themes in the preferences editor. When I first go to Window > Preferences > Aptana Studio > Themes, I get a message that reads:
The currently displayed page contains invalid values.
and doesn't show anything. On the rare occurrences that I AM able to get that particular window to show up, there's nothing there except an empty drop down menu. Anyone have any ideas on how to correct this? Thanks.
P.S. YES, I have Googled it and hence, since I didn't find anything, I'm asking the question here.
got this answer from another post...
I got the same problem. After updating Aptana to 3.5, whenever I looked at the themes settings, it crashed down saying.
"the currently displayed page contains invalid values"
Probably the new update has its own bugs for some reason.
the only way to fix the problem is to downgrade the version of Aptana studio.
https://wiki.appcelerator.org/display/tis/Reverting+to+a+Previous+Version#RevertingtoaPreviousVersion-AptanaStudio3.4.1
just Download 3.4.1 version and all things gonna be ok.
Add Eclipse Themes from http://eclipsecolorthemes.org/?view=plugin
Details to add themes on this post.
Edit: This does not seem to work :( only the bg changes. I never noticed that the font colors never changed. Have to wait for patches I guess. Don't want to downgrade though :-|
Over the last few days this issue has been popping up and it's really beginning to annoy me as I spend more time correcting it than actually coding.
periodically when I am working with my JavaScript (jQuery) when I type $ for say:
$('#something').html when I type $ the content assist box comes up, which is fine but when I press ( I get the following output:
$$()
instead of how it should look:
$()
Any idea's how to fix this without disabling content assist for JavaScript? Thanks.
As stated in a comment I have fixed this issue in 3.0.4 and before. Aptana Studio has bindings for auto-inserting the proposed code. To fix it, go to Windows -> preferences -> Aptana Studio -> Editors -> Javascript and delete the insert proposed which is by default: .( and that will fix your issue.
As Ingo Muschenetz states, 3.0.5 is supposed to have fixed this issue, but I have yet to actually try out that version to ensure that it does.
This is actually a known bug and fixed in the update to 3.0.5: http://preview.appcelerator.com
Running Analyze in Xcode 4.0.2 shows issues in the Issue Navigator. Clicking on an issue makes the appropriate file appear in the Editor pane, but nowhere does it show where in the code the issue occurs as I am used to from Xcode 3.x. Does anyone know how I can turn on this feature?
A couple of tips:
First, if you're looking for the view where Xcode annotates the project with arrows, bear in mind that you may need to expand the top-level analyser result in Xcode's Issue navigator and click the second-level issue in order to see those - see screenshots.
Screenshot 1: top-level issue selected - no arrows
Screenshot 2: second-level issue selected - arrows!
Second tip: if that stuff isn't working, try cleaning the project's build products folder. Hold down the Option (alt) key and choose Clean Build Folder... from the Product menu. (You need to hold down the Option key, otherwise you won't see that menu option.)
I've seen this happen before sometimes. I believe it's a bug in Xcode. Restart Xcode and try again.
One note. I'm seeing this for files that are referenced outside the current project. I currently have a library in which the files with missing annotations live and simply added them to my current project without copying them. Haven't done the project dependency setup yet, so if you're referring to files outside your project that could be why. (I opened the library project, did an analyze and the annotations showed up.)
Woohoo, I've nailed it! At least for me. I've been struggling with this problem for about 2 hours now, trying out all the things suggested here and more (Xcode 4.0.2, Snow Leopard). Bizarre thing was I had one file where the warning were correctly showing in the editor. Then I noticed the difference to all other files; in the File Inspector pane the location was specified as "Relative to Project" (warnings show correctly in the editor), all the other project files were "Relative to Group" (warnings not showing in the editor).
I took one of the problem files, switched it's location to "Relative to Project", reanalyzed and bingo! I've see it's warnings in the editor.
I guess this ties in a bit with David Goodine's answer refering to files outside the project.