55 lines
6.8 KiB
Org Mode
55 lines
6.8 KiB
Org Mode
* CLona no el contenido en sí sino tan sólo la esructura de ~/napi-data/ a ~/napi-data2/ , teniendo en cuenta que :
|
|
** en dicha carpeta se alojaran los datos de otro grupo de estudiantes : el de el módulo Programación. Es decir el grupo ASIR1.
|
|
** los cambios introducidos en el servidor Web deben ser compatibles con las aplicaciones existentes
|
|
** tendrán acceso a sus notas via notas.qu3v3d0.tech tras introducir, por obra del hack 'regexp-based-nginx-after-catch-all-content-redirect' ya desplegado en 'zzz', su usuario y contraseña
|
|
** TODO generar lista de alumnos - AKAs en el mismo fichero ~/napi-data2/programacion-seguimiento-de-practicas.md
|
|
* TODO , corregir/depurar mensaje : Claude, fíjate en @Screenshots/*.png s decir, que el chatbot no liste nada de "__pycache__/"
|
|
|
|
|
|
* TODO que el chatbot, en vez de :
|
|
|
|
** zzz@librebits.info 17:04
|
|
🐍 [jara] Entrega ASIR1: Practicas/adivina-el-numero.py (1812 bytes)
|
|
|
|
|
|
** diga : zzz@librebits.info 17:04
|
|
🐍 [maría jara] Entrega ASIR1: Practicas/adivina-el-numero.py (1812 bytes)
|
|
es decir, mencionar el/la autor/a de la entrega por ambos, nombre y apellido
|
|
|
|
|
|
|
|
* TODO Emacs packages using JSON-RPC o other kinda-API thing i could be using in a complementary way to streamline my interaction with the students via 'zzz' server where 'napi' is hosted / serving
|
|
|
|
|
|
---
|
|
Emacs Packages Using JSON-RPC / Structured Protocols
|
|
|
|
For napi/ Specifically (file-sync + notification)
|
|
|
|
┌──────────────────────────────────────────────────────────────────────────────────────────────┬──────────────────────────────────────────┬────────────────────────────────────────────────────────────────────┐
|
|
│ Package │ What It Does │ napi Complement │
|
|
├──────────────────────────────────────────────────────────────────────────────────────────────┼──────────────────────────────────────────┼────────────────────────────────────────────────────────────────────┤
|
|
│ https://github.com/legoscia/emacs-jabber │ XMPP client for Emacs │ Direct integration with your slixmpp notification system │
|
|
├──────────────────────────────────────────────────────────────────────────────────────────────┼──────────────────────────────────────────┼────────────────────────────────────────────────────────────────────┤
|
|
│ https://www.gnu.org/software/emacs/manual/html_node/elisp/File-Notifications.html (built-in) │ inotify/kqueue file watching │ Watch ~/napi-data/ for student uploads natively in Emacs │
|
|
├──────────────────────────────────────────────────────────────────────────────────────────────┼──────────────────────────────────────────┼────────────────────────────────────────────────────────────────────┤
|
|
│ https://github.com/jcaw/json-rpc-server.el + https://github.com/jcaw/porthole │ Expose Emacs functions via HTTP JSON-RPC │ Let external scripts (your inotify watchers) trigger Emacs actions │
|
|
└──────────────────────────────────────────────────────────────────────────────────────────────┴──────────────────────────────────────────┴────────────────────────────────────────────────────────────────────┘
|
|
|
|
** Explore the idea (as referred on above's gnu.org manual - link) "Notifications on File Changes", which states :
|
|
|
|
"Several operating systems support watching of filesystems for changes to files or their attributes. If configured
|
|
properly, Emacs links a respective library like inotify and others. These libraries enable watching of filesystems on the local machine.
|
|
|
|
**It is also possible to watch filesystems on remote machines**, see Remote Files in The GNU Emacs Manual. This does not
|
|
depend on one of the libraries linked to Emacs.
|
|
|
|
Since all these libraries emit different events upon notified file changes, Emacs provides a special library filenotify
|
|
which presents a unified interface to applications. Lisp programs that want to receive file notifications should always
|
|
use this library in preference to the native ones. [..]
|
|
|
|
|
|
the **bold** is mine ! ...
|
|
|
|
*** Am i crazy saying that ~/napi could be running remotely, as long as a 'emacs -daemon=napi' which i could hook into an 'emacsclient' ?
|