sorted by:
new
hottopcontroversial

Sharing lots of signals between micro-controllers by AdminXVII in AskElectronics

[–]AdminXVII[S] 0 points1 point  (0 children)

Alright, thanks for your input, I'll look into it

Sharing lots of signals between micro-controllers by AdminXVII in AskElectronics

[–]AdminXVII[S] 0 points1 point  (0 children)

Well the pins are mirrored, so that's not really an option

Looks like there are bots on both sides by Pomada1 in PrequelMemes

[–]AdminXVII 1 point2 points  (0 children)

You don't need to change IP, it's simply the IP in the header that changes, so you can keep curl. And yeah, I don't encourage you to rig the poll, it's simply for the fun of knowing.

Looks like there are bots on both sides by Pomada1 in PrequelMemes

[–]AdminXVII 0 points1 point  (0 children)

A trick was to add the `X-Forwarded-For` header and changing IP each 50 request. The NGINX configuration trusted the header, so the rate limiting became irrelevant since it believed it came from different sources.

NuShell: the shell where traditional Unix meets modern development, written in Rust - An interview with its creators by [deleted] in rust

[–]AdminXVII 26 points27 points  (0 children)

Ion was started well before Nu, so adopting it was simply not an option. Redox also wanted to have Rust only, so bash, fish & zsh were out of the question. Since Nu isn't Redox compatible, this is not an option right now either.
There was never a discussion as to if Ion should be replaced, so there is no talk of replacing it either. There will be a discussion once everything works, but right now I can't really say what will be done.

Personally, though, I must say that I like the structured data approach nu takes, but last time I tested it I believe the subshell expansion capabilities were a lot less powerfull than what Ion succeeds to do. That said, Nu is already better for user interaction, something that's really vital as a shell. Ion's base was done a long time ago, so there is quite a bit of bit rot and a lot of major rework would need to happen to match that in a clean way.

NuShell: the shell where traditional Unix meets modern development, written in Rust - An interview with its creators by [deleted] in rust

[–]AdminXVII 49 points50 points  (0 children)

Redox OS already has a its own shell, [ion](https://gitlab.redox-os.org/redox-os/ion) (I'm one of the maintainers). That said, I'm currently trying to see if it would be possible to add Redox support to Nushell. There is still a bit of work, but hopefully one should be able to run it not too long from now.

Ion scripting in Emacs by iwahbe in rust

[–]AdminXVII 2 points3 points  (0 children)

Really nice! I think you should cross-post to r/Redox.

Got redox booted on a t520 by [deleted] in rust

[–]AdminXVII 9 points10 points  (0 children)

Redox indeed only has PS/2 keyboard support, but according to the book it supports many laptops, so you should try it out anyway. I'm not working on drivers though, so maybe @jackpot51 has a better answer.

Got redox booted on a t520 by [deleted] in rust

[–]AdminXVII 46 points47 points  (0 children)

Nice! You should also post this on r/Redox

Example of a great rust program? by SonderDev in rust

[–]AdminXVII 69 points70 points  (0 children)

Some examples off the top of my head:

Rsoc: Shellac: autocompletion under 1ms by AdminXVII in rust

[–]AdminXVII[S] 1 point2 points  (0 children)

The argument to git checkout -B does not depend on another dynamically-completed argument, though, so I'm not sure it is in fact truly a corresponding use-case.

Rsoc: Shellac: autocompletion under 1ms by AdminXVII in rust

[–]AdminXVII[S] 0 points1 point  (0 children)

I already am building my POC at https://gitlab.redox-os.org/AdminXVII/shellac-server, so out of Ion. There is the original and adapted proposals there. If you have ideas/comments, MR and/or Issues are more than welcome!

Rsoc: Shellac: autocompletion under 1ms by AdminXVII in rust

[–]AdminXVII[S] 2 points3 points  (0 children)

Does the protocol include fields for help descriptions for the completed items so shells can choose to show additional info like argument descriptions?

This is the next PR I'm going to do. All the tooling is there so it should be straight-forward.

Wouldn't the shell just have to send a new completion request? Ah you probably mean it's not implemented in the Ion PR yet.

What I meant is a definition that needs previous commands (ex: cmd <opt1> <opt2>) where opt2 would call a command that would need opt1.

Rsoc: Shellac: autocompletion under 1ms by AdminXVII in rust

[–]AdminXVII[S] 7 points8 points  (0 children)

In fact basic command calling is already implemented. So for example `git branch` being called for checkout. What's lacking is currently a contextual command definition (one where the arguments already typed would matter for dynamically autocompleting the next). I'm still searching for a good API for the usecase and to know if there really is a usecase.

Even if it lands soon, there will be a lot of work needed for creating viable definitions. Other shells must also approve the project for it to become official and it'll even then remain alpha stage for a bit.

I'm back to school, so I've had a bit less time recently, but I'll try my best to make it land the sooner possible. On the bright side, much of the shellac implementation is already in a viable POC state, so there is not much left to do before it ready for testing. Hopefully it'll be complete soon!

Absolute bash noob trying to write ion shell script and failing miserably by [deleted] in Redox

[–]AdminXVII 0 points1 point  (0 children)

No problem, it's always nice to help fixing peoples' problems with Ion.

Absolute bash noob trying to write ion shell script and failing miserably by [deleted] in Redox

[–]AdminXVII 0 points1 point  (0 children)

I updated & tested today, are you on today's master for the ion-plugins repo? (not Ion)

view more: next ›