I am importing a large code base from one repository to another. The primary editor my team will use is changing to vscode in this new repository. I want to format all the code in this new repository using vscode's built in code formatter (js-beautify). I'd like to write a node script to format this code. js-beautify has a nice api, but I'm having trouble figuring out exactly which js-beautify formatting options vscode is using by default. Is there a way I can export these options out if vscode?
Related
In a Python tutorial I'm following, the Python path is linked to the python.pythonPath setting in the settings.json file of Visual Studio Code. However, the python.pythonPath does not exist anymore.
I tried to find the python.pythonPath variable or alternatives in the default settings.json file, but I could not find one.
What is the alternative to this settings variable?
According to the documentation on Github, the python.pythonPath setting is indeed not used anymore.
Instead, a new settings with the name python.defaultInterpreterPath has been introduced.
Note, however, that this setting is not exactly the same. The way it is processed by Visual Studio Code is changed as well. See the documentation linked above, or the Python settings reference:
python.defaultInterpreterPath:
Path to the default Python interpreter to be used by the Python extension on the first time it loads for a workspace, or the path to a folder containing the Python interpreter.
Can use variables like ${workspaceFolder} and ${workspaceFolder}/.venv.
Using a path to a folder allows anyone working with a project to create an environment in the .venv folder as appropriate to their operating system, rather than having to specify an exact platform-dependent path. The settings.json file can then be included in a source code repository.
Note: Changes to this setting made after an interpreter has been selected for a workspace will not be applied or considered by the Python extension. The Python extension doesn't automatically add or change this setting.
Suppose that I have a map on my init.vim that I want to change the behaviour depending on the folder that I am. How could you do that?
A more concrete example: I have a map on my F12 that runs the project that I am. So if I am on a python project, this F12 will run an ipython on a floaternew window, with the current file already imported. Though, if I am on a cpp project, the same F12 will build using Make and running the binary on a floaternew window as well.
Nowadays, I have these two behaviours mapped on different key bindings. But It is going to very nice if I have only one binding to "run the project". Even if I need to open neovim with some parameter in each project, like neovim --local-config mylocalconfig.vim (extending init.vim with some behaviour)
I am kind inspired by a behaviour like direnv but with .vim files.
Any ideas?
There is an option in vim set exrc which enables reading vim config files from current directory, it also works in neovim.
From docs (:h exrc)
Enables the reading of .vimrc, .exrc and .gvimrc in the current
directory. If you switch this option on you should also consider
setting the 'secure' option (see |initialization|). Using a local
.exrc, .vimrc or .gvimrc is a potential security leak, use with care!
also see |.vimrc| and |gui-init|.
This option cannot be set from a |modeline| or in the |sandbox|, for
security reasons.
I use Visual Studio Code to work on projects that not only include program code, but also data files, e.g. in Excel format.
VSCode cannot edit such files, as they are binary. Attempting to do so shows a warning, and if you persist, the file is shown (as gibberish).
I've also tried to pass the file to the (CMD) terminal (right click, 'Open in Terminal'). In a regular CMD window that would invoke the default application, but that does not work in VSCode.
Is there a simple way that I can use from VSCode to open such files using the default applications?
The extension sandcastle.vscode-open does this. Install it, and you can open any file with its default application by right clicking on the filename in the explorer menu.
In v1.66 you can set a default editor for binary files and avoid the warning (see release notes: binary file):
Default binary editor
A new setting, workbench.editor.defaultBinaryEditor, lets you
circumvent the binary file warning and automatically open the editor
type of your choosing when a binary file is detected. You can select
the default binary editor from a dropdown in the Settings editor or
via IntelliSense in settings.json.
TBH, I am still investigating whether you can set this to some external application like Excel?
I'm attempting to put together a standard VS Code build for my company. I have a ps1 file that copies/installs extensions for VS Code after it's been installed but I can't seem to find how or even if it is possible to then configure VS Code settings to utilize those extensions.
For example, one of the extensions is "vscode-icons". I can install the extension just fine but then the user needs to setup his preferences manually to actually use the extension by going to the File->Preferences->File Icon Theme->VS Code Icons.
Is it possible to have my ps1 install file actually make configuration changes so any user who opens VS Code has the custom configuration settings?
The config settings for VS Code are JSON files - just needs to locate and edit them.
First check what manual change is doing then create part in the script to edit the settings.
https://code.visualstudio.com/docs/customization/userandworkspace
Libreoffice Impress Export as Images extension does not work. "Export as Images" Menu is not being added to File Menu.
Link- http://extensions-test.libreoffice.org/extension-center/export-as-images
I am using Libreoffice 3.4. Any suggestions would be helpful.
Quick workaround: start the Export as Images macro manually. It's located under My Macros -> ExportImages -> ExportImages. Look for a macro named ExportAsImages and run it. Once found and started, it works fine :) (i don't know why it doesn't show up in the File menu).
EDIT:
Editing the macro is possible using the built-in IDE: once it's installed, you can access its LibreOffice Basic source using Tools-> Macros -> Organize Macros... -> LibreOffice Basic.
It's also possible to run it from the command line, but in its current form, it requires user interaction to specify the output file name and graphics format. So i assume it isn't possible to run it completely in "headless" mode without modifying the source. To run it from the command line on Linux, converting the file /tmp/mypresentation.odp, use:
$ simpress /tmp/mypresentation.odp "vnd.sun.star.script:ExportImages.ExportImages.ExportAsImages?language=Basic&location=application"