Please use vscode's config folder for .cmdline_history
See original GitHub issueIs this a BUG REPORT or FEATURE REQUEST? (choose one): Enhancement
- Extension (VsCodeVim) version: 0.14.1
- VSCode version: 1.24.1
- OS version: Arch Linux
vscode-vim has recently started creating a ~/.VSCodeVim folder in $HOME, which pollutes the home dir 😦
There already is a config folder for vscode in $XDG_CONFIG_HOME/Code
. Can you move that folder there instead please?
Issue Analytics
- State:
- Created 5 years ago
- Comments:13 (6 by maintainers)
Top Results From Across the Web
User and Workspace Settings - Visual Studio Code
To open the Settings editor, use the following VS Code menu command: ... Workspace Folder settings - Apply to a specific folder of...
Read more >Visual Studio Code - Where is the terminal history saved?
VSCode terminal use external shell. ... On Linux & MacOS, type the following command to display the path of the history file: echo...
Read more >Setting up your AWS credentials - AWS Toolkit for VS Code
Learn how to configure the AWS Toolkit for Visual Studio Code to use your AWS ... see Where Are Configuration Settings Stored? in...
Read more >Set up a workspace in VS Code
Using the ServiceNow Extensions for VS Code, create a project work folder to use as a workspace for ServiceNow applications. ... Click the...
Read more >10 Tricks in Visual Studio Code | Syncfusion Blogs
New Themes and Plugins; Command Line in VS Code; Edit Multiple Lines Simultaneously; Exclude Folders; Go to Definition. Command Palette. The ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Please don’t use ~/.vscode either as it doesn’t respect XDG. The vscode config is split right now and the “correct” one is in the XDG dir. Also see: https://github.com/Microsoft/vscode/issues/3884
Ok I decided to use a library for now, just tested it on 3 platforms with these results:
This issue will be closed and I will push a release. Please let me know if something still doesn’t seem right once you start using the new release!