tom-editor | 设置contentEditable '' true '' 作为文本编辑器，定位光标解决办法 | Editor library

Change trim_trailing_whitespace for C # to this "files.trimTrailingWhitespace"

and Make sure you are working on these steps:

Use the link below to install Visual Studio Code :-

https://visualstudio.microsoft.com/thank-you-downloading-visual-studio/?sku=BuildTools

It worked for me.

The nested pretags eg. contenteditable>pre do not seem like an ideal setup for events like 'keypress', 'keydown' and 'keyup' as they did respond to these events in my case. The 'click' event within pretags worked but did not process the if (e.key === 'Enter') check, so I did not follow that route.

Instead of listening to events for each pretag, I attached a listener to the container only and all of sudden my custom setting for enter-event was working inside and outside all pretags within container. Eventually I can get the empty lines within my pretags on pressing the Enter key.

In the "Known issues" section of the blog post @Wlad mentioned, there states

Accessing Linux files is treated the same as accessing a network resource, and any rules for accessing network resources will still apply e.g: When using CMD, cd \\wsl$\Ubuntu\home will not work (as CMD does not support UNC paths as current directories), however copy \\wsl$\Ubuntu\home\somefile.txt C:\dev\ will work

So as Atom may use cmd.exe to launch itself from the command line (maybe some batch file), and given the fact that cmd.exe cannot open network resources as current directory (which WSL directory is treated as), there came the failure as you attempted to launch Atom from WSL shell.

Actually, in VS Code there is a better solution to launch VS Code directly from the WSL shell: VS Code Remote.

You can take the following steps to enable VS Code to be directly launched from WSL shell：

1. Install the extension Remote - WSL to VS Code on the Windows side;
2. Then when you type code . in your WSL shell, VS Code Remote Server will be automatically installed, and VS Code will soon launch.

By using VS Code Remote, you can not only open the directory in VS Code, but can also be benefited in many other aspects: for example, you can use the WSL shell as the integrated shell in VS Code and run programs in WSL directly from VS Code.

Here is the official doc for VS Code Remote - WSL.

Finally after a lot of try and error approach supported with open source samples, I got solution to my problem in the following steps:

1. Implement custom editor normally as in any of the samples posted in the question (like Editor With Toolbox).
2. Inside the editor factory class (the class that implements IVsEditorFactory), inside the CreateEditorInstance function, you can make condition like this to limit the editor to JSON files with specific name:

It looks like you want the caption shortcode to be processed in the WYSIWYG editor? This is not the intended function inside the WYSIWYG, which is meant to show the raw shortcode. If it's not displaying correctly on the frontend (template) try wrapping your call to print the content of the editor in do_shortcode.

You could possibly try outputting your content into the editor using do_shortcode but that would only work once. I.e. once the shortcode is converted to HTML you'll have HTML floating around in your editor.

Actually, it is working, if you double click on the date input, or start typing there, it will show you the calendar to select the date. The issue is with react-data-grid and it seems like the default behavior of react-data-grid. You can see the examples here. The issue is already been created on the reach-data-grid github, Hopefully they will fix this issue.

See here, you can see easily that DateEditor component is working well. I just showed the component down there outside the react-data-grid component.

For now, I think it would be good to avoid react-data-grid and instead use table from semantic-ui-react.

Hope it will help.

Without seeing a screen shot I cannot be sure, but I am reasonably certain you are referring to the "preferredLineLength" marker. It is a line that shows where the end of a line would be if it were within the bounds of the preferredLineLength

https://flight-manual.atom.io/using-atom/sections/basic-customization/

The request url must be properly url escaped to work with urlopen.

In your example, this gives you a properly encoded url: