How to disable green highlight in Spyder - spyder

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.

Related

Xcode 14: Does anyone know how to remove the blue tint on lines where changes have been made?

Problem
Within the Xcode 14 IDE, I have been facing an annoying issue where the lines I am editing tint blue. I have disabled Show Source Control changes within Preferences, yet it does not remove it. I have attached an image to show you what it looks like. I really hope you can help as I am finding the blue tints everywhere in my code very distracting and annoying.
Just ignore the code - it's just to show what happens when changes are made in the editor. 😊
There's a button next to where you can show the canvas, 2 arrows pointing in opposite directions. Try pressing it.
In case if the icon mentioned in accepted answer is missing, go to View in Xcode top navigation bar and click Show Code Review.

Why is my Octave GUI editor so buggy? How can I fix it?

The editor for the GUI is a complete mess. When I create a brand new script, the spacing and font are relatively ok.
However, if I open any existing function, it is shown with way too much space between lines, and spaces and tabs show way more space than they should. An example is shown below:
I tried selecting the Edit - Preferences - General - Use custom file editor options, and chose "notepad++ -n%l %f. I have notepad++ installed already on my computer.
When I selected this option and clicked ok, the Octave GUI crashed. When I tried to reopen a file now, I get the error "could not start custom file editor".
If I change the font, it temporarily fixes the issue. But none of the changes persist. Often clicking OK crashes octave. And any time it's reopened, the fonts revert to default, and the spacing problems returns.
How can I make the editor show an appropriate leading and space width?
I would also like to be able to further customize, if possible. For example I'd like it to use a dark theme. But for now just showing a reasonable space between lines would make this at least useable.
I'm using Windows 10, Octave version 6.4.0

How to edit tooltip opacity in vscode? (how to change the intellisense suggestions transparency)

I am a beginner in vscode.
When I write code the tooltip annoys me, because I use divided screen in macOS
so I want to make the tooltips semi-transparent without press ctrl
like this image:
Try this colorCustomization in your settings:
"workbench.colorCustomizations": {
"editorSuggestWidget.background": "#ff000060"
}
The last two digits, in this case 60 are opacity. There a few more editorSuggestWidget options to change too.
https://wannabedev.tistory.com/37
I found it, here is a screenshot:
Unfortunately, that's a visual studio feature not yet available in visual studio code.
At present, the only option is to disable the pop-up altogether, in which case you don't get the hinting, which is not ideal.
There are a lot of threads on GitHub about the position and opacity of the tool tip (search terms like 'tooltip intellisense position' you'll find a bunch). You can add your voice there.

How to configure spyder 4 to behave like spyder 3

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

TDBEdit/TEdit component borders disapear

I have a form that correctly displays component borders most of the time.
However when I tab out of the form’s first input field, the borders of all the form’s TDBEdit/TEdit components disappear. The component’s border’s reappear when moused over.
I can reset these at runtime by looping through the form’s components and setting TDBEdit/TEdit borders (BevelInner: bvLowered, BevelOuter: bvRaised).
Also, this issue appears to have something to do with the Enable runtime themes option in the Project Options. The issue only exists when this option is enabled and regardless of the Windows Theme that is being used.
CodeGear™ Delphi® 2007 for Win32® R2 Version 11.0.2902.10471
After some additional research it appears that this is a known issue and occurs predominantly when a user is using the ALT button.
Additional information pertaining to workarounds can be found at:
http://qc.embarcadero.com/wc/qcmain.aspx?d=37403

Resources