In windows terminal (latest version) I am trying to open an Azure Cloud Shell. Functionality is working, however I am unable to read the display as when I set focus to the window, it becomes obscured (foreground shading is applied). When I select a different window, the terminal returns to normal.
Does anyone know how to change the theme to something useful or to turn off this foreground shading?
Regards
In writing out the bug as mentioned above I found I needed to delete my old settings file. Once I did this, and restarted terminal it started working.
I note when the azure shell is started, it briefly becomes transparent before updating itself.
Related
I try to run an windows 10 application inside a windows servercore container.
The app can run without user input via COM-Interface (and without visible GUI), but it seems that it needs to load a hidden window in the background. When I start it on docker, the application log file indicates that it's stuck on starting this window.
Is there a way to make the app assume it successfully loaded the window?
All information I found so far was about users who want to see the GUI or about Linux/Windows combinations. None of that helped me.
I am trying to understand why Mac terminal font is not sharp.
Mac terminal most of the time shows up like this:
Rarely it shows up like this:
Much sharper. I want to make it so it is always like the second image here, the sharper version.
What could be causing the fond to be not as sharp like shown in the first image?
I am running macOS 12.0 Monterey.
And this is my General and Profiles tabs:
That's the Antialias text option in Terminal's Preference->Profiles. My guess is that you sometimes switch between the predefined Basic profile, which has the option enabled, and the Homebrew profile, which has it disabled.
In the Preferences General tab, you can setup the Terminal to use a non-default profile on startup. If you do so, but at the same time have new windows open with the default profile, you get a different profile for every Terminal window but the first, which may be why you see these differences.
I've been moving step-by-step (as a webdev newbie) through the GatsbyJS installation via the Terminal. All looked great, except the Terminal appears "stuck" and I'm not sure how to resolve (i.e. whether to close Terminal app or let the process continue). It's been over an hour without any change in the Terminal prompt. Please see screenshot for detailed info. Any help would be much appreciated.
screenshot: Current state of Terminal app:
screenshot: Message when trying to close Terminal app:
Your terminal is not stuck. Everything works as it should.
It is listening to code changes which enables hot reloading. This way you can change code and you see the changes almost instantly in your browser. This makes for a pleasant developer experience and is industry standard.
Beware the old times when you had to manually restart your server everytime you made the tiniest code change.
Try opening a browser with url http://localhost:8000. Change some text inside your index.js. You should see it reload in the browser.
In the Google Cloud Platform Console, upon clicking "Activate Cloud Shell," the bar for the command line shows up and displays "Provisioning your Google Cloud Shell Machine" and "Establishing your connection to Google Cloud Shell," but after that the entire box for the command line goes blank. It still has the option bar that displays the project name, option to open the text editor, etc. I tried going to the text editor hoping that the command line would show itself there, but the whole box remained blank.
Even worse, I started one of my virtual machines and used the SSH option from the console to connect to it, and the SSH window similarly went totally blank. Any ideas what's going wrong here? I'm using Firefox on Windows 10 and haven't had any issues using the Cloud Shell for months.
This was a browser compatibility problem between FF64 and the Google Cloud Shell terminal emulator library. The SSH-in-the browser feature inside Cloud Console is using the same terminal emulator, so it was affected as well. Both have now been fixed.
I had a similar issue. Google cloud shell doesn't work with Firefox.
I waited for a whole thirty minutes and nothing happened. Thirty! I switched to Chrome and the issue was sorted out immediately.
I have found this site: https://developer.mozilla.org/en-US/docs/Mozilla/Debugging/HTTP_logging
My problem is: The settings for about:networking only work for the current session. And I have no interest to always start Firefox from the console. Is there a way to launch Firefox (under Mac OS X) via Finder and to permanently enable those logging features?
BG
I'm not a Mac user, so this might be not the best way. However, you might try using an approach similar to running Firefox with multiple profiles, as documented here on MDN. It suggests creating an Automator application that runs a shell script. You can follow this guide, which tells you to:
Open Automator
Go to File->New->Application
Choose Utilities group under Library
Drag Run Shell Script to the workflow pane on the right
Paste the script used to run Firefox with logging enabled
Choose Save As and store it somewhere
You should be good to go.