I just installed the new Windows Terminal from Windows stores. I also have installed Ubuntu 18.04 WSL. But I am getting only two types of terminal options in Windows Terminal. How I can get the option of Ubuntu terminal in it. Also, I want cmd to be my default terminal in it rather than PowerShell.
You need to change settings
Click "Settings" in right top corner of above image, the file profile.json file will be opened. Then inside the word "profiles" in profile.json file, add below snippet.
{
"guid": "{78e390db-1bff-4533-9d7c-20f53d8bafa1}",
"name": "WSL",
"colorscheme": "Campbell",
"historySize": 9001,
"snapOnInput": true,
"cursorColor": "#FFFFFF",
"cursorShape": "bar",
"commandline": "wsl ~",
"fontFace": "Consolas",
"fontSize": 12,
"acrylicOpacity": 0.75,
"useAcrylic": true,
"closeOnExit": false,
"padding": "0, 0, 0, 0"
}
Near the word "schemes" in profile.json file, you need to update below:
"schemes": [
{
"name": "Campbell",
"foreground": "#A7B191",
"background": "#0C0C0C",
"colors": [
"#0C0C0C",
"#C50F1F",
"#13A10E",
"#C19C00",
"#0037DA",
"#881798",
"#3A96DD",
"#CCCCCC",
"#767676",
"#E74856",
"#16C60C",
"#F9F1A5",
"#3B78FF",
"#B4009E",
"#61D6D6",
"#F2F2F2"
]
}
The complete setting file (profile.json) which can be obtained here.
Actually, the WSL here is Ubuntu.
Besides, you can add icons to different types of tabs.
You can add icons for the Ubuntu profile to this folder:
$env:LOCALAPPDATA\Packages\Microsoft.WindowsTerminal_8wekyb3d8bb\RoamingState
I put some 32x32 PNG in this folder, and then in profile.json I can reference the image resource with the path starting with ms-appdata:// .
The icon is available here:
Icons
Then replace the contents of the new profile-withIcons.json file below with the previous settings.
profile-withIcons.json
After finishing the contents of the folder is like this:
The final result is:
An even easier option: Go to Settings -> Apps -> Apps and features -> find 'Windows Terminal' in the list -> select 'Advanced options' then choose reset.
For me after installing Ubuntu from Microsoft Store it is appeared like this, it should also work.
{
"guid": "{2c4de342-38b7-51cf-b940-2309a097f518}",
"hidden": false,
"name": "Ubuntu",
"source": "Windows.Terminal.Wsl",
}
Default there will be a penguin icon, you can add your own like this;
"icon": "ms-appdata:///roaming/ubuntu_32px.png"
You can place your icon file here like mentioned above.
$env:LOCALAPPDATA\packages\Microsoft.WindowsTerminal_8wekyb3d8bbwe\RoamingState
I noticed that installing Windows Terminal when the Ubuntu WSL is already installed automatically adds the Ubuntu profile to the WT. So reinstalling WT might be the quickest solution.
If Windows Terminal is already installed prior to Ubuntu WSL form the app store, open the Ubuntu app, let it install, enter a new username and password. This will automatically add an Ubuntu profile to Windows Terminal.
Related
The default vscode configuration for debugging ASP.NET core contains the following:
"configurations": [
{
"name": ".NET Core Launch (web)",
"type": "coreclr",
"request": "launch",
"preLaunchTask": "build",
...
The preLaunchTask fails for me with the following error:
The terminal process failed to launch: Path to shell executable "dotnet" is not a file of a symlink.
I have had this problem before, not on the preLaunchTask but on the main program execution. That I could work around by doing a replace all "dotnet" -> "/usr/bin/dotnet" in ~/.vscode/extensions/ms-dotnettools.csharp-1.**.*/dist/extensions.js + a vscode restart. However, this workaround doesn't work for the preLaunchTask. (And having to do this for every update of that extension in annoying).
Given that I'm a linux noob, it's probably not omnisharp/vscode related but could be something I did wrong in Ubuntu 18.04.
Does anybody know what the error means, and how to fix it? Or even how to debug this problem?
I've already reinstalled vscode, .net5, and my global $PATH env does contain /home/<username>/.dotnet/tools:/usr/bin/dotnet. Other than that I don't know what to do.
in tasks.json file change from
"type": "process" to "type": "shell"
I have created .testcaferc.json, I mentioned the browser and src in it. so I should be able to run tests without putting this in the command line.
But it does not seem to be reading my config file from the project folder.
{
"src": "c:/Testcafe/Login.js",
"browsers": "firefox",
"reporter": {
"name": "html",
"output": "reports/report.html"
},
"takeScreenshotsOnFails": true,
"screenshotPath": "/screenshots/"
}
Actual:
Using locally installed version of TestCafe.
ERROR No browser selected to test against.
Type "testcafe -h" for help.
Expected:
I should not ask for browser and test file parameter as both are provided in config file.
The configuration file is a feature added in v1.0.0. If you upgrade from 0.20.5 to 1.0.0 or later, you will be able to use the configuration file for your tests.
Release Notes:
https://github.com/DevExpress/testcafe/releases/tag/v1.0.0
I have configured cumulocity.json as below:
{
"name": "Cumulocityexercises",
"availability": "PRIVATE",
"contextPath": "cumulocityexercises",
"key": "cumulocityexercises-appkey",
"resourcesUrl": "/",
"type": "HOSTED",
"tabsHorizontal": true,
"imports": [
"core/c8yBranding",
"cumulocityexercises/myplugin",
"cumulocityexercises/docsplugin"
]
}
but when I am trying to build the plugin:my plugin, I am getting an error like plugin not found. Can anyone help me with this please?
This is most likely linked to your project structure. It should look similar to the screenshot below and then you would need to run the command from the root level (cumulocity-enhanced-ui in the screenshot).
You need to run the following command to build a single plugin
c8y build:plugin <<pluginFolderName>>
c8y build:plugin dashboardUtils
Same goes for the manifest declarations. They need to match the plugin folder names (case sensitive)
What's exactly the command you are using to build the plugin?
If it is something like this:
$ c8y build:plugin docsplugin
docsplugin plugin not found
then you may check that your plugin directory has the same name as specified in the JSON file, i.e. cumulocity.json manifest file in the main app directory. A second manifest file goes in the plugin directory.
Note that you must execute the build command from the main app directory which in your case is cumulocityexercises, otherwise you will get the same error message.
Environment: Ubuntu 16.04, .NET Core SDK Preview 2.0.0 (006497), VSC 1.14.2
Things used to work fine under .net core 1. Now, I have upgraded my system to .net core 2.
From the command line, I created a new project and ran it:
$ dotnet new mvc
$ dotnet run
The webpage works as expected.
Now, I open the folder in VSC and tried to debug the app. First time, VCS helps create launch.json and tasks.json. Here is my tasks.json contents:
"version": "2.0.0",
"tasks": [
{
"taskName": "build",
"command": "dotnet",
"type": "shell",
"group": "build",
"presentation": {
"reveal": "silent"
},
"problemMatcher": "$msCompile"
}
]
}
In the terminal view, I see that VCS tries to run the build command as dotnet <. This throws an error that preLaunchTask "build" exited with error code 129.
I tried to fix this by adding args: ["build"] to the task. This seems to fix the build but I now get another error about launch.json not being configured properly.
Wondering if there is some step that I simply missed. Regards.
The answer was provided by mvermef in his comment. I am just adding a new post here so I can mark it as an answer.
The problems with VSC are explained at https://github.com/dotnet/core/blob/master/release-notes/2.0/2.0.0-preview2-known-issues.md. The most important thing is that you remove your existing C# extension and replace it with the latest beta version. Now, if you create a new project from the command line and load it in VSC, you should be able to debug it.
I'm new to Atom, the text edit, and I installed many packages, including Linter
https://github.com/AtomLinter/Linter
But it's not showing errors or highlighting code, it's just getting ignored.
Do any of you know what I should do to get this to work?
You have to additionally install a linter package for your desired language.
Here is a list: https://atomlinter.github.io/
I needed to remove atom config and start from scratch to make linter working
mv ~/.atom ~/.atom.bak
Instead of opening atom from the terminal like I normally do, I opened it from the application icon. Then atom asks if it was ok to install linter dependencies and presto it was working.
Hope this helps.
My problem with linter-eslint was because I accidentally installed eslint 8 which is not yet supported by atom linter or linter-eslint. After I installed eslint ^7.32.0 and typed npm i, restarted Atom and changed ecmaversion from 13 to 12 everything started working fine!
When I start Atom up, the small UI panel in bottom left is present, but shows zero values for the 3 severities.
If I then do a CTRL-s/save (even with no changes), it starts working..
In my package settings, I have "Lint on Open" (which doesn't seem to work at all) and "Lint on Change" (which is "only for supported providers" so could be that) ticked.
Here is my .eslintrc. Hope it helps.
module.exports = {
root: true,
"parserOptions": {
"ecmaVersion": 7,
"sourceType": "module",
"ecmaFeatures": {
"jsx": true,
}
},
"extends" : "rallycoding",
"rules": {
"react/require-extension": "off"
}
};
I had to add the path of my project's node_modules dir to the Atom's eslint package settings, as well as create an .eslinterc.json file in my project. After doing both those, I had to restart Atom (I started it from the command line $ atom .) and it started working.