Re: [dev] how can I remap vis to bépo layout?
> Hello, Hello Damien, > Being a bépo user (a dvorak-inspired keyboard, > look at www.bepo.fr), I would like to remap some keys > in vis normal mode, namely ctrs to hjkl and hjkl to ctrs. The correct way to do that would be in config.h, you can use the keymaps string array in which you can define symbol pairs to remap original keys to your keys.
Re: [dev] how can I remap vis to bépo layout?
Hi,
Quoting Damien Thiriet (2019-10-31 13:27:28)
> Since there were announcement related to vis on that
> list, I'll give a try here.
> Being a bépo user (a dvorak-inspired keyboard,
> look at www.bepo.fr), I would like to remap some keys
> in vis normal mode, namely ctrs to hjkl and hjkl to ctrs.
> I tried this on my visrc.lua
>
> -- load standard vis module, providing parts of the Lua API
> require('vis')
>
> vis.events.subscribe(vis.events.INIT, function()
>-- Your global configuration options
>-- hjkl <=> ctrs
>vis:command('map! normal h c')
>vis:command('map! normal c h')
>vis:command('map! normal j t')
>vis:command('map! normal t j')
>vis:command('map! normal k s')
>vis:command('map! normal s k')
>vis:command('map! normal l r')
>vis:command('map! normal l r')
> end)
>
> vis.events.subscribe(vis.events.WIN_OPEN, function(win)
>-- Your per window configuration options e.g.
>vis:command('set number')
> end)
>
> As a result neither of these keys do work.
> This might be because mapping is recursive,
> or something connected to operators.
> What shall I do to switch those keys?
I'm not sure if you can do actual swaps. This works, though:
vis:map(vis.modes.NORMAL, 'r', '')
vis:map(vis.modes.NORMAL, 'j', '')
You can check :help in vis to find the other names to map to.
Sincerely,
Felix
[dev] how can I remap vis to bépo layout?
Hello,
Since there were announcement related to vis on that
list, I'll give a try here.
Being a bépo user (a dvorak-inspired keyboard,
look at www.bepo.fr), I would like to remap some keys
in vis normal mode, namely ctrs to hjkl and hjkl to ctrs.
I tried this on my visrc.lua
-- load standard vis module, providing parts of the Lua API
require('vis')
vis.events.subscribe(vis.events.INIT, function()
-- Your global configuration options
-- hjkl <=> ctrs
vis:command('map! normal h c')
vis:command('map! normal c h')
vis:command('map! normal j t')
vis:command('map! normal t j')
vis:command('map! normal k s')
vis:command('map! normal s k')
vis:command('map! normal l r')
vis:command('map! normal l r')
end)
vis.events.subscribe(vis.events.WIN_OPEN, function(win)
-- Your per window configuration options e.g.
vis:command('set number')
end)
As a result neither of these keys do work.
This might be because mapping is recursive,
or something connected to operators.
What shall I do to switch those keys?
Damien Thiriet
Re: [dev] unsubscribe
who are you to quit me? On Wed, 30 Oct 2019 at 19:33, Lukáš Hozda wrote: > > unsubscribe? >
Re: [dev] Re: Worse is better: Plan9 and Linux?
hello, (i really thing this shouldn't happen in a dev list) > > So my question to you is: > > how do you put Linux and Plan9 into this scala? > > (I get the feeling you deliberately don't want to understand my > > question.) you are (deliberately?) elusive with your question so Laslo was (deliberately?) elusive in his anwser. nevertheless, he already replied. so i try my way: you can compare those two OS only thru perspectives. * linux is a unix clone (so flaws in the design, including symlinks) are cloned too. * linux is a side project that became the most used unix kernel of the world, supporting a lot of hardware and providing a stable ABI no matter what (thanks to linus's opiniated point of view). so yes ... it has history and this shows on the codebase. plan9 was a research os to fix the design flaws of unix but didn't evolve that much since it was abandonned then publicly released. so ... * design and code are much more cleaner and consistent and remained that way. * tools are probably the state of art of 90's (good starting point to reinvent the computer tech because everything went terribly wrong since then) * on the other hand, it works on very few hardware and lack of tools for modern usage. the question is: what do you need to compare them? what's your goal? if it's considering using one or another, that's the way i would use plan9: * as a deskop os on tiny hardware if you don't mind the lack of tools * as a virtual machine in a qemu to provide distributed services also when i talk about plan9, i think about recent evolutions of it like harvey os or 9front (i have to admit i don't know about the others). > The same point applies to Linux: I use Linux on my personal computer > and OpenBSD on my servers. +1 > I think OpenBSD is the best trade-off +1 > however, even it fails to fit all my use-cases. can you be specific ? regards marc
Re: [dev] Re: Worse is better: Plan9 and Linux?
On Wed, 30 Oct 2019 17:48:09 +0100 Peter Wiehe wrote: Dear Peter, > So my question to you is: > how do you put Linux and Plan9 into this scala? > (I get the feeling you deliberately don't want to understand my > question.) I wanted to give you a general answer. Discussing Linux and Plan 9 involves many other topics, including the trade-off between practicability and elegance. Operating systems are a tool to do things, and to put it to an extreme, if one decides to develop suckless software on macOS, so be it. The same point applies to Linux: I use Linux on my personal computer and OpenBSD on my servers. There are many points of criticism against Linux and the accompanying ecosystem, the most prominent being the intoxication with systemd and general complexity. Still, for many applications and use-cases, there is no other choice. I must admit that I'm not a big fan of Plan 9, but maybe I've just spent too little time with it. With regard to elegance and simplicity I think OpenBSD is the best trade-off, however, even it fails to fit all my use-cases. To get back to your question: If we just think about data structures and simplicity, Plan 9 wins, as they revolutionized this field in many ways where unixoid operating systems are still stuck at to this day. Nevertheless, it doesn't help when it's residing in a niché. With best regards Laslo pgp7i2q93HU9o.pgp Description: OpenPGP digital signature
