Files
emacs/lisp
Jim Porter dc0839de9b Use generics to define Eshell output targets
This is more flexible than before, since third-party code can add new
output target types without advising these functions.  It also
resolves an issue where redirecting to a symbol that has a value in
its function slot doesn't work.

* lisp/eshell/esh-io.el (eshell-virtual-target): New struct.
(eshell-get-target, eshell-output-object-to-target): Reimplement via
'cl-defgeneric'.
(eshell-close-target): Reimplement via 'cl-defgeneric' and simplify
'process' method.
2023-08-21 11:43:24 -07:00
..
2023-08-20 18:39:51 +02:00
2023-08-08 19:53:18 +02:00
2023-08-10 12:09:56 +03:00
2023-08-13 17:00:53 +02:00
2023-08-20 18:39:51 +02:00
2023-08-03 05:46:21 +02:00
2023-06-17 05:02:55 -04:00
2023-07-01 06:29:52 -04:00
2023-06-03 05:50:58 -04:00
2023-08-12 13:50:38 -04:00
2023-08-10 13:25:29 +08:00
2023-05-30 17:44:53 +02:00
2023-05-26 13:57:02 +02:00
2023-08-08 19:07:00 +02:00
2023-08-04 03:17:49 -04:00
2023-08-12 13:50:38 -04:00
2023-08-12 13:50:38 -04:00
2023-05-31 17:50:53 +03:00
2023-08-16 16:55:38 +02:00
2023-08-16 20:32:38 +08:00
2023-07-26 17:30:21 +03:00
2023-07-21 12:23:08 +08:00
2023-08-20 09:47:00 +02:00
2023-08-05 18:18:30 +02:00
2023-07-07 10:00:56 +08:00
2023-07-08 17:05:05 +01:00
2023-08-17 08:45:57 +08:00
2023-07-02 15:15:17 -04:00

This directory contains source code for the parts of Emacs that are
written in Emacs Lisp.  *.el files are Emacs Lisp source, and the
corresponding *.elc files are byte-compiled versions.  Byte-compiled
files are architecture-independent.

The term subdirectory contains Lisp files that customize Emacs for
certain terminal types.  When Emacs starts, it checks the TERM
environment variable to get the terminal type and loads
'term/${TERM}.el' if it exists.

The other subdirectories hold Lisp packages grouped by their general
purpose.