Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

Introduce a conceptual help topic about calling external programs (native applications)

Abierto
  • ¿Algo no está bien?
#5,152 6 comentarios 8 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
48/100
Tipo de issue
Documentación
Claridad
Bastante claro
Estado de actividad
Estancado
Stack tecnológico
powershell
Área
documentation

Línea de trabajo

Comienza revisando about_Parsing, about_Quoting_Rules, about_Redirection, about_Pipelines, about_pwsh y about_Operators, junto con los issues relacionados y el RFC. Redacta el tema propuesto about_Native_Calls para la sección about_*, cubriendo el comportamiento de los programas nativos indicado y enlazando esos artículos; se considera terminado cuando se haya añadido la guía completa y se haya incluido en el TOC.

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

Descripción

area-about area-conceptual area-native-cmds issue-doc-idea

Related: #2361, https://github.com/PowerShell/PowerShell/issues/13068#issuecomment-653526374, and #6239

Summary of the new document or enhancement

Many special considerations apply when you call an external command-line executable (aka native application / utility), which aren't currently covered comprehensively, in one place:

  • That the only data type supported is text ([string]), both on input and output, and how raw byte data is fundamentally unsupported - both when collecting the output in PowerShell and when piping between native programs.

    • Update: v7.4 introduced raw byte support.

  • How there are syntax pitfalls due to PowerShell's extended set of metacharacters (compared to other shells) causing potential misinterpretation of arguments, which must be avoided with quoting (e.g., To pass literal @foo, which works unquoted in cmd.exe and bash, you must use '@foo' in PowerShell).

    • How --% can be used (primarily on Windows) to selectively deactivate PowerShell's parsing.

  • How "native globbing" is automatically applied to arguments such as *.txt on Unix-like platforms; that is, *.txt is implicitly replaced with the array of file names / paths matching that wildcard pattern.

  • How output data is sent through the pipeline line by line, resulting in an array of strings (lines), if collected in a variable.

  • How stderr (standard error) output is passed through to the host rather than going through PowerShell's error stream and can only be captured with a 2> redirection.

  • How redirections (>) generally do not pass the native program's output through as-is, but invariably treat it as [Console]::OutputEncoding encoded text that on writing to the target file is written with PowerShell's default encoding (BOM-less UTF-8 in PowerShell 6+, UTF-16LE in Windows PowerShell).

  • How external-program calls aren't integrated with PowerShell's error handling and require explicit checking of $? / $LASTEXITCODE to detect failure, except in PowerShell 7, where pipeline chain operators && and || can now be used. See also: the RFC that proposes improvements to the integration.

  • How &, the call operator, must be used to invoke executables whose paths are / must be quoted (as a whole) and/or contain variable references or subexpressions (this requirement isn't specific to external programs, but most likely to surface in that context).

  • How Start-Process is typically not the right tool for invoking external programs - see #6239.

Details of requested document:

  • Proposed title: about_Native_Calls
  • Propose location in the TOC: Among the `about_* topics
  • Target audience: end users
  • Purpose or scenario: guidance for invoking native command-line programs
  • List of related articles to link to: about_Parsing, about_Quoting_Rules, about_Redirection, about_Pipelines, about_pwsh, about_Operators (section "Pipeline chain operators && and ||")
Lenguaje dominante
PowerShell
Estrellas
2.5k
Forks
1.7k
Merge medio
6 h 58 min
PR fusionados (30 d)
31

Preparar el entorno

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 MicrosoftDocs/PowerShell-Docs

Todos los issues de MicrosoftDocs/PowerShell-Docs

Issues similares

Más issues de Documentation

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.