Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Vim.wasm

rhysd.github.io

Post reply on HN
Print view View original

241–250 of 291 posts

Re: Vim.wasm

#241

Post by jolmg »

mrzool wrote: post #174
dmitryminkovsky wrote: post #149

Earlier quoted context omitted.

Rebound my caps lock to escape and never looked back!

You should (look back). Mapping it to Ctrl is a much more sensible choice. Can’t imagine using backspace instead of Ctrl-h, or Ctrl-A/E to go to the beginning/end of line, or Ctrl-W to delete back one word etc. Of course, Ctrl-[ is also right under your finger tips with Caps Lock mapped to Ctrl.

> Ctrl-W to delete back one word

That's one of the most commonly used shortcuts I use. Not just in vim, but also in the shell. When I screw up on my typing, the mistake is often 3 or more letters back. Instead of hitting backspace a lot or moving the cursor and retyping mid-word, I prefer to say "screw it", hit Ctrl-w, and retype the word. It's faster. My brain is just not optimized to type pieces of words. I can't use muscle memory then.

Besides that, I don't know about you or dmitryminkovsky, but I remapped it to Caps system-wide, so by remapping to Ctrl, I'd be losing a lot more than those shortcuts you mentioned. On the other hand, CapsLock has always been a useless key to me. When I want to type in all-caps, it's less confusing/error-prone to just hold Shift with my pinky while typing. Also, Caps is in a much easier place to hit than Ctrl, so it's more fitting for a key that I hit a lot.

Re: Vim.wasm

#242

Post by ianmcgowan »

msla wrote: post #240
apetresc wrote: post #194

Earlier quoted context omitted.

You can also remap a key like Caps Lock to Escape, straight from System Preferences on macOS (unless you're already remapping it to Ctrl or something)

In Emacs, we remap Caps Lock to Ctrl. Does anyone actually like Caps Lock?

I PROGRAM IN A LEGACY ENVIRONMENT THAT USES CAPS ONLY. I LOVE CAPS LOCK AND FIND IT ANNOYING TO HAVE TO SWITCH BACK AND FORTH WITH SHIFT.

so emails and general writing tend to be all lower case and rely on the editor to upcase for me. mostly works.

Re: Vim.wasm

#243

Post by rdrey »

johnny22 wrote: post #124
tkinz27 wrote: post #93

I wonder if this will be useful for electron based editors like vscode's vim plugin. I know the plugin is "good" but I always find something that works in vim and doesn't in the plugin and end up going back to my terminal.

I heard that you could embed neovim for that sort of thing, since neovim has an ipc. I don't know how well the feature is maintained though.

I recently found Oni, which aims to be a web-tech UI for neovim. (The new version should even support the full VSCode extension API / ecosystem) https://github.com/onivim/oni2

Re: Vim.wasm

#244

Post by sitkack »

pjmlp wrote: post #162
sitkack wrote: post #122

Earlier quoted context omitted.

Wasm linear memory is a building block, if you want higher security boundaries, stitch together multiple Wasm envs and communicate via webworkers. Wasm is nearly identical, but different in the ways that matter. You are being blinded by being ahead of the curve, but the curve has moved now.

I am eagerly waiting for the first set of CVEs related to WASM, and the "you are holding it wrong" comments from WASM advocates.

It would be interesting to force Wasm through an asm.js polyfill for non tier-1 trusted sites. Then one would have higher assurance that malicious Wasm couldn't do anything that js couldn't do.

Wasm will be absolutely pervasive at all levels of the stack.

Re: Vim.wasm

#245

Post by yjftsjthsd-h »

rajeevk wrote: post #91
be_erik wrote: post #22

This is absolutely incredible. I never thought this would be possible-- wasm opens a new phase of software development and deployment.

Probably next step would be to run nginx/node in browser! This will enable doing full web development in browser only

Actually I wonder how hard it would be to run node in a browser, given that it's already JavaScript. You obviously have to have to implement some amount of API surface at a minimum and it's possible that browsers are geared to be servers and clients, but it certainly sounds plausible at a first pass.

Re: Vim.wasm

#246

Post by opan »

the_pwner224 wrote: post #188
aasasd wrote: post #135

Earlier quoted context omitted.

The actual issue is that Windows and Linux don't properly use a ‘super’ key―while the ‘Win’ key is sitting there uselessly. Ironically, MS' own ‘ergonomic’ (cough) keyboards have gigantic Win keys, right under the thumbs which are the strongest digits. These keys are great to use on Mac, it's an eye-opener as to how the historical keyboard mutations ended up in just the wrong way for two platforms (and for Emacs). I…

> The actual issue is that Windows and Linux don't properly use a ‘super’ key―while the ‘Win’ key is sitting there uselessly. Some people do use the super key. I have it bound to a huge number of actions (WASD to switch workspaces, Alt+WASD to move window to adjacent workspaces, C to close window, X to pause/unpause media, Z to show workspace overview, tab to switch between workspaces like alt-tab does for windows, P…

In both i3wm and awesomewm I use super as my main modifier for window management. I am also glad programs don't often touch it so that it's available for this.

Re: Vim.wasm

#248

Post by amenod »

TeMPOraL wrote: post #223
amenod wrote: post #218

Earlier quoted context omitted.

Ironically, these dangers are not thwarted by FSF licenses. Even more, the persistence with which FSF fights anything that would dare touch the pillars that they marked as "freedom" is holding back any meaningful discussion about alternatives. For example: https://www.fsf.org/blogs/licensing/recent-licensing-updates > We added the Commons Clause to our list of nonfree licenses... It's particularly nasty given that th…

They consider Commons Clause to be harmful for good reasons. To quote from https://www.gnu.org/licenses/license-list.html#comclause : > The “Commons Clause” is a nonfree license because it forbids selling copies of the program, and even running the program as part of implementing any commercial service. Adding insult to injury, it also twists the words “commons” and “sell.” RMS and FSF's stance on software freedom is…

Thank you for the downvotes - but winning the (down)voting game doesn't make you right.

> They consider Commons Clause to be harmful for good reasons.

Your quote only tells that they consider the license non-free. Which is true, if you subscribe to their definition of "freedom" [0] (which I don't - YMMV). Harmful though? I don't think so.

Have you looked around lately? Has opensource software won? Where it did, it did because it helped big tech companies to "commoditize their complements". Where it didn't, it is because by itself it doesn't provide hobby developers with any incentive to keep working once the maintaining stops being fun.

> RMS and FSF's stance on software freedom is ultimately straightforward: they want to protect end user's freedoms, and protecting this involves removing the ability for anyone in between to take away end user's freedoms.

Exactly. What they are missing however is that without developers' engagement you get the situation that we have now. And that some of the freedoms are more important than others - like freedom to repair, to run for every purpose, and... to actually have a polished piece of software. Do you still think opensource "won"?

In the end it's a free world, or it should be. Also free to decide which license to use. And free from hordes of preachers falling on every mention of Commons Clause.

[0] https://en.wikipedia.org/wiki/The_Free_Software_Definition#T...

Re: Vim.wasm

#249

Post by stevelosh »

dmitryminkovsky wrote: post #214
meestaahjoshee wrote: post #181

Earlier quoted context omitted.

you can do tap for esc, hold for ctrl

Tap what?

They mean remapping capslock to:

* Ctrl if held and used with other keys.

* Esc if pressed and released on its own.

There's no reason to press and release Ctrl on its own (minus games), and you never need to chord Esc with anything else, so they can both live on the same key.

Post reply on HN