hiro-sun / vscode-emacs Goto Github PK

Is anyone else having trouble with this? I guess it could be my desktop environment:

Other reference:
https://youtu.be/SYRwSyjD8oI?t=1m36s

I could do "box selection" but not "add a cursor", for instance.

With ersion 1.10.2 on macOS I receive:

command 'workbench.action.files.openFolder' not found

It should probably address workbench.action.files.openFileFolder instead

hi.
this is an awesome package. almost everything works fine. but there is one problem accured to me when i use this package.
Problem is that when i type ctrl+space to mark some text, there are no highliting on the marked text. and alt-w triggers a copy error.

my environment:
vscode version 1.8.1
ubuntu kylin 16.04

thanks!

title says it all.

microsoft/vscode#18592 (comment)
I also met this problem. It seems to be related to the extension vscode-emacs.

After I installed and enabled the extension, once I type in Chinese by Microsoft Pinyin, it will delete the former character before cursor if able, and put the first English character in, and then finally works expected.

for example:
if I have some code like print(""), and I move the cursor between the double quote, then type in 你好, it will finally get the result print(n你好")

This problem disappear after I disable the extension or change to other input method like Sogou Input Method.

I usually use open-line(C-o).
http://www.gnu.org/software/emacs/manual/html_node/emacs/Blank-Lines.html

'C-g' should cancel current command (including keybinding in progress, if any) and return to normal input [mode]. Ideally, it should also preserve current selection, like Emacs does.

You still have to press Esc to get out of a lot of places, does not really feel fluid.

In original Emacs, if you are in selection mode and you select some text and you press RETURN to delete the selected text, the selection mode will turn off. It doesn't work with this plugin and this is so confusing for real Emacs users. I always delete the selected text but then I will eventually forget that the selection mode is still active and only realize when I move my cursor again. This is kind of disturbing. Also I think ALT+RETURN have to delete the previous word.

h, u not work with amvim.
and how to open the command line( c-p )

I just del the h,u define in package.json. it's not a good idea.

Hi,

I am quite accustomed to using c-l to recenter the window as described in the emacs manual. I think it would be great if this could be added. Currently, the key combination seems to not be bound to anything.

Hello,

First of all, thank you very much for your job on this extension guys, I love it very much.

I think because #5 is not merged yet, https://github.com/hiro-sun/vscode-emacs/blob/master/src/operation.ts#L19 does not do Open action like it should. IMHO it's a good idea to open the explorer and choose the new working folder with C-x C-f because there is no shortcut to do it and I miss it a lot.

The C-o key-binding overrides the original
{ "key": "ctrl+o", "command": "workbench.action.files.openFile" } key-binding.

Do you think C-o is really necessary?

Please implement C-M-f and C-M-b to move forth and back over balanced expression (https://www.gnu.org/software/emacs/manual/html_node/emacs/Expressions.html). Other related keybindings (e.g. C-M-k) would be great too.

This is actually a feature request.

vscode-emacs works great, but there is a problem - when I accidentally entered mark mode (with the Yank text appearing on status bar) and I want to quit the mark-yank workflow, I have to actually copy or cut the selection to return to normal mode. Did I miss something?

Maybe we could use Esc to break the workflow like in search mode?

Hello!
I am user Vim. Now I am switching from VIM to vscode+emacs. I`m used to using hjkl to move forward, but how i can remap C-fbnp to ALT-hjkl.
In this package

So this is a big problem, unlike normal emacs, where hitting C-Space would Set the Mark for highlighting, the mark is set by default and again unlike emacs, it refuses to get deactivated when I do C-Space a second time. Please sort this issue, because everything else is great but this is a deal buster!

I suggest updating the conflict list by adding Ctrl-w to it and changing the 'Close Editor' shortcut to Ctrl-x k

Any realistic Emacs workflow inevitably comprises Rectangle operations.
We should be able to support at least the following Rectangle-related keybindings:

It seems dead. is there anyone can accept PR ?
if so, I will create PR. or I create another project.

Ctrl+Shift+Backspace (delete entire line) is a popular keybinding and we should support it.
Emulate Emacs behavior with respect to existing selection, i.e. if multiple lines are selected while Ctrl+Shift+Backspace has been pressed:

• Remove the selection
• Delete only one [current] line

Type: Bug

Input multi-bytes chinese words will causes previous letter has be deleted

Extension version: 0.1.1
VS Code version: Code 1.73.1 (6261075646f055b99068d3688932416f2346dd3b, 2022-11-09T04:27:29.066Z)
OS version: Windows_NT x64 10.0.22621
Modes:
Sandboxed: No

vsliv368:30146709
vsreu685:30147344
python383cf:30185419
vspor879:30202332
vspor708:30202333
vspor363:30204092
vslsvsres303:30308271
pythonvspyl392:30443607
vserr242:30382549
pythontb:30283811
vsjup518:30340749
pythonptprofiler:30281270
vshan820:30294714
vstes263:30335439
pythondataviewer:30285071
vscod805cf:30301675
binariesv615:30325510
bridge0708:30335490
bridge0723:30353136
cmake_vspar411:30581797
vsaa593:30376534
pythonvs932:30410667
cppdebug:30492333
vscaat:30438848
vsclangdc:30486549
c4g48928:30535728
dsvsc012:30540252
azure-dev_surveyone:30548225
vscccc:30610679
pyindex848cf:30577861
nodejswelcome1cf:30587006
fc301958:30595537
2e4cg342:30602488
gswce1:30612156
3d0df643:30613357
dbltrim-noruby:30604474
89544117:30613380

It appends the paste after the selected region instead.

On Windows, C-y doesn't paste from the clipboard. Since C-v is taken, there is no other way to paste from the clipboard.

In emacs, starting an isearch via C-s, typing a few things, and then hitting a movement key such as C-f or C-n causes isearch to end and for the point to move based on wherever it was during the isearch operation. This isn't the behaviour of vs-code's search; the regular keybindings aren't available while in isearch (hitting C-n opens a new tab, for example), and the search window is "sticky"; hitting C-s again even after manually clicking to a window searches again for whatever one was searching for last.

Is there a way to have emac's styling tabbing? In emacs instead of inserting a tab, it sets the indentation on that line to the correct spot:

Hi, I'm on the VS Code team. We recently released support for Remote Development and I noticed that your may extension need a small change to ensure users have a good experience when using it remote workspaces.

What is the issue?

To make remote development as transparent as possible to users, VS Code distinguishes two classes of extensions:

• UI Extensions: These extensions make contributions to the VS Code user interface and are always run on the user's local machine. UI Extensions cannot directly access files in the workspace, or run scripts/tools installed in that workspace or on the machine. Example UI Extensions include: themes, snippets, language grammars, and keymaps.

• Workspace Extensions: These extensions are run on the same machine as where the workspace is located. When in a local workspace, Workspace Extensions are run on the local machine. When in a remote workspace, Workspace Extensions are run on the remote machine. Workspace Extensions can access files in the workspace to provide rich, multi-file language services, debugger support, or perform complex operations on multiple files in workspace (either themselves or by invoking scripts/tools).

You can find more details about this architecture here.

VS Code currently infers that your extension is a Workspace Extension. This means that users who have your extension installed must also install it to the remote in order to use it in remote workspaces. I believe that your extension should probably be a UI extension instead. That way your extension will always be enabled for users who install it, even if they open a remote workspace.

How do I fix this?

To tell VS Code that your extension is a UI extension, just add "extensionKind": "ui" to your extension's package.json.

UI Extensions always run on the user's local machine, even when they open a remote workspace.

I'll submit a PR that does this. Please let me know if you have any questions or concerns about the issue. We've also put together a guide to help you test your extension in remote workspaces

PS: As a temporary workaround for a few popular extensions, we've automatically added your extension to an internal whitelist so that is always treated as a UI extension

Would be cool if this key combination would work here, too.
Using Ctrl-Pos1 to get the same result is not so intuitive,
because it is not available in emacs / jmacs, which I am using, when only a small editor for a single file is needed.

Ubuntu 18.04.2

VScode 1.32.3

Workaround: switch VS Code to dispatch based on key code again. Add the following setting:
"keyboard.dispatch": "keyCode" and restart VS Code

Like many Emacs users, I use esc as the Meta key. When vscode-emacs is running, this intercepts the usual role of esc within VSCode. In nearly all circumstances that's fine, and I'll use M-g to 'cancel', simulating the traditional VSCode use of esc. The one place where I want to cancel without a separate keystroke, however, is in dismissing IntelliSense: I'd prefer to dismiss it faster via only the esc key. Once I hit the esc key, however, now VSCode is waiting for me to complete the chord.

Is there any way to not have the Meta-key binding to esc while in specific contexts, e.g. here within an IntelliSense code-completion context?

After paging up or down with Ctrl-V or M-V, the editor view changes accordingly, but the cursor stays on the same line, so that if I do Ctrl-N after that the editor view jumps back to the original page. I have to mouse-click somewhere after Ctrl/M-V to change the position of the cursor.

Can you push the last changes to the VSCode extension market please?

This probably is tricky to implement the proper way, but right now the second kill command doesn't kill the emty line and add it to clipboard, and subsequent yank does entirely something strange (try it!). It would be nice to have the ability to do multiple kills and paste them in a single yank.

In emacs, you can do M-e and M-a to move forward/backward by a sentence unit, respectively. This seems to be missing.