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

[Feature Proposal] Toggleable File Explorer & Opt-In AI Assistant (via C ABI Plugin)

Cerrado
  • ¿Algo no está bien?
#781 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
25/100
Tipo de issue
Nueva funcionalidad
Claridad
Necesita aclaración
Estado de actividad
Tranquilo
Stack tecnológico
c, cpp, rust
Área
cli, tooling

Línea de trabajo

Lee CONTRIBUTING.md para conocer los objetivos indicados sobre ligereza y plugins, y luego inspecciona src/tui.rs, src/framebuffer.rs y src/buffer. Este issue es una propuesta para dos funcionalidades amplias, no una tarea de implementación definida; para darlo por terminado primero sería necesario recibir comentarios de los maintainers sobre el alcance, la arquitectura y si el trabajo debería dividirse.

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

Descripción

Hello maintainers,

I have been exploring the edit repository and really appreciate the homage to the classic MS-DOS editor combined with the strict lightweight philosophy. I would love to contribute to the project by introducing two modern workflow features that respect the editor's minimal footprint: a toggleable file explorer and an AI assistant.

Because keeping the binary size small is a stated priority in CONTRIBUTING.md, I want to propose an architecture for these features before writing any code.

Feature 1: Toggleable File Explorer (Native UI)

Navigating multi-file projects currently requires leaning heavily on the terminal or file picker. I propose adding a lightweight, toggleable folder tree sidebar.

  • UI Integration: This would be built using the existing immediate mode UI primitives in src/tui.rs and drawn to src/framebuffer.rs.

  • Behavior: It would remain completely hidden by default to preserve the classic layout, toggleable via a specific hotkey or menu bar option.

  • State Management: It would read the local directory structure lazily to ensure it does not impact the editor's extremely fast startup time.

Feature 2: AI Assistant & Live Editing (Plugin Architecture)

Bringing AI-powered live editing and an AI chat tab to the editor would be highly valuable, but introducing an HTTP client and JSON parser directly into the Rust core violates the zero-dependency philosophy.

  • The Plugin Approach: I propose laying the groundwork for the plugin system mentioned in the contributing guidelines. We could expose a simple C ABI that allows external dynamic libraries to read from and write to the text buffer.

  • External Execution: The actual AI logic, network requests, and text parsing would live entirely in a separate, optional C/C++ dynamic library that the user must explicitly load. If the user does not load the plugin, edit retains its sub-megabyte size.

  • Capabilities: The ABI would allow the plugin to either open a dedicated "AI Tab" using the TUI or manipulate text directly in the active src/buffer at the current cursor position.

Proposed Next Steps

I am happy to take the lead on building these features. Would the core team prefer to see these as two separate pull requests?

Specifically, I would like feedback on:

  • Is the team open to adding a persistent, toggleable sidebar layout to tui.rs?

  • Would you accept a PR that introduces the initial FFI/C ABI bindings to support the external AI plugin concept?

Looking forward to your thoughts!

Lenguaje dominante
Rust
Estrellas
14.7k
Forks
737
Merge medio
1 d 3 h
PR fusionados (30 d)
15

Preparar el entorno

Abrir en Codespaces

Inicia el contenedor de desarrollo del proyecto en tu navegador, con tu propia cuenta de GitHub.

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 microsoft/edit

Todos los issues de microsoft/edit

Issues similares

Más issues de Rust

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.