reset Dymola flags to default value from mos script - scripting

Is there a command to reset all Dymola flags to their default value from a .mos script?
The GUI has a button to do it, I basically need a mos command that does the same as the "Reset All Flags" button at the bottom left:

This command should reset all flags to default:
DymolaCommands.System.clearFlags()

Related

how to get CLion IdeaVIM ^O binding back to return from 'gd' goto def?

I'm on a new installation of CLion with the IdeaVIM plugin working in Rust.
I successfully used the 'gd' goto definition motion and the ^O to return once.
I was then immediately prompted with something like "vim key usage detected - I selected "IDE keys ( or something IDE...)", incorrectly guessing what it wanted. And now 'gd' works but I can't return via ^O.
What sticky settings have I put in place to break 'gd' ^O?
you can update this key in vim settings. For that click the vim icon in the status bar -> Settings...

How to make buffers writable in spacemacs?

Whenever I try to edit an existing file with spacemacs, I get "buffer is read-only". How do I give spacemacs the permission to edit any buffer on a Mac?
Press SPC SPC, type read-only-mode and select/call it. This will toggle the "read-only" status of the current buffer.
Alternatively, use shortcut SPC b w.
You can also try the following shortcut:
C-x C-q runs the command read-only-mode

Change Integrated Terminal title in vscode

We can open command prompt in vscode by using the Integrated Terminal feature in View menu.
We can even open multiple terminals as shown below:
Is there any way I can change the title of the terminal ?
1: cmd.exe will be build terminal
2: cmd.exe will be watch terminal
I have gone through the integrated terminal documentation but I didn't find a way to do that.
Press in windows Ctrl + Shift + P and after type: Terminal: Rename, there you can change the terminal name/title
In v1.61 there is the ability to set the terminal names using variables. See terminal custom titles in release notes.
Terminal names are traditonally the name of the process they're
associated with. Thus, it can be difficult to distinguish between
them.
We now support configuring both title and description to help with
this using variables described in terminal.integrated.tabs.title and
terminal.integrated.tabs.description settings.
The current default values are:
{
"terminal.integrated.tabs.title": "${process}",
"terminal.integrated.tabs.description": "${task}${separator}${local}${separator}${cwdFolder}"
}
Variables available are:
${cwd} - The terminal's current working directory
${cwdFolder} - The terminal's current working directory.
${workspaceFolder} - The workspace in which the terminal was launched.
${local} - Indicates a local terminal in a remote workspace.
${process} - The name of the terminal process.
${separator} - A conditional separator (" - ") that only shows when surrounded by variables with values or static text.
${sequence} - The name provided to xterm.js by the process.
${task} - Indicates this terminal is associated with a task.
It looks like the ${task} variable is what you are looking for.
Sometimes, plugins will remove default keyboard shortcut bindings.
Look for "terminal.rename" in keyboard shortcuts then edit the keyboard shortcut to your preferred shortcut.
To apply your shortcut, make sure your cursor is focus in edit part of the window before you key in. Not at the terminal part.
In v1.41 there is a new command which can be used like so:
{
"key": "ctrl+t",
"command": "workbench.action.terminal.renameWithArg",
"args": {
"name": "remote"
}
}
if you have some frequently used name, like "remote" or "build" that you use often.
With VSCode 1.63 (Nov. 2021), entering "<blank>" (ie., empty string) as name will restore the default name for that terminal.
See issue 134020
For instance:
If my setting is ${cwd}${separator}${process} and I name a terminal "foo".
How do I reset "foo" back to the value of ${cwd}${separator}${process}?
My suggestion was that if you attempted to submit a blank name that would automatically reset to the value of your setting.

shortcut key to get the previous command in ksh

Shortcut key to get the previous command in ksh
What is the shorcut key to get the previous command that was used in ksh?
I have tried using the history command but that is not my requirement.
I want to know the shortcut key.
If you first set the editor mode to "vi";
set -o vi
Then you can access history by entering command mode (press Esc key), and using either the up arrow or the 'k' key.
From there, vi editing syntax works - e.g. to edit the line enter insert mode ('i') etc. Hitting return will re-execute the command, and Ctrl-C will cancel.

how do you make Scite interactive?

Once I compile with Scite, my command prompt won't show up.
How do I set it up so I can accept inputs and outputs from the command prompt from my program using Scite?
In scite properties file Edit as below:
Change
command.go.*.c=$(FileName)
to
command.go.*.c=start $(FileName)
Pressing go opens the tatget file in new cmd window and is now interactable
Now you can give inputs
If you are using different language replace *.c with corrosponding one and put start before the command.