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

Abierto
  • ¿Algo no está bien?
#273 1 comentario 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
35/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Tranquilo
Stack tecnológico
c, shell
Área
cli, operating-systems

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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!

Lenguaje dominante
C
Estrellas
5k
Forks
408
Merge medio
4 h 40 min
PR fusionados (30 d)
2

Preparar el entorno

  • Incluye un Dockerfile o un archivo de Docker Compose
  • Sin plantilla de pull request
  • Sin guía de contribución

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de skeeto/w64devkit

Todos los issues de skeeto/w64devkit

Issues similares

Más issues de C

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.