w64devkit.exe: Support for "-c" and/or "--" to pass args through to busybox sh

Aperta
  • Qualcosa non va?
#273 1 commento 0 reazioni 0 assegnatari Vedi su GitHub

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
35/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Tranquilla
Stack tecnologico
c, shell
Ambito
cli, operating-systems

Direzione di ricerca

Start with w64devkit.exe's command-line handling and the linked discussion in issue #199, then trace how arguments reach BusyBox sh. Define the behavior for -c and/or --, including pass-through arguments, and verify that launching from Windows graphical shells preserves the expected environment and prompt behavior.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

After all the floundering in #199, the most straight forward solution seems to be as you described. I keep coming back and wanting this. Would you be open to implement this feature?

You see I have this nice logo that shows when I open the shell:

w64devkit [Version 2.1.0]
by skeeto (Christopher Wellons). Unlicense.

C:/Users/stian>

I made that logo when I first started out with w64devkit to add some familiarity from good old cmd.exe:

Microsoft Windows [Version 10.0.26100.4946]
(c) Microsoft Corporation. All rights reserved.

C:\Users\stian>

It's just a cute thing and I really like it. It was the first thing I did. Other than the familiarity I also like that it advertises your project when I'm streaming and coding.

But whenever I spawn shells through Windows' graphical shell (like Open in Terminal or my own Edit in Terminal), I can't use w64devkit.exe (as thoroughly explored in #199), so my logo gets all messed up, since it's lacking $W64DEVKIT & $W64DEVKIT_HOME:

Image

(Yes, I added red standout for dramatic effect.)

I also use $W64DEVKIT_HOME for managing w64devkit's tags file, which goes out the window when I spawn a shell this way.

Anyway :) If it's not counter to your desired design, please consider adding this functionality!

Lingua principale
C
Stelle
5k
Fork
408
Merge medio
4h 40m
PR unite (30g)
2

Preparare l'ambiente

  • Include un Dockerfile o un file Docker Compose
  • Nessun modello di pull request
  • Nessuna guida per i contributori

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di skeeto/w64devkit

Tutte le issue di skeeto/w64devkit

Issue simili

Altre issue su C

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.