emacs-elpa-diffs
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[nongnu] elpa/sesman fb4d2784f3 025/100: Fix typo in README


From: ELPA Syncer
Subject: [nongnu] elpa/sesman fb4d2784f3 025/100: Fix typo in README
Date: Tue, 28 Dec 2021 14:06:00 -0500 (EST)

branch: elpa/sesman
commit fb4d2784f3c4c11d8bacc488c5534da32f330e61
Author: Adam Frey <adam@adamfrey.me>
Commit: Vitalie Spinu <spinuvit@gmail.com>

    Fix typo in README
---
 README.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/README.md b/README.md
index 73edc8c56f..4efde3569b 100644
--- a/README.md
+++ b/README.md
@@ -7,7 +7,7 @@
 
 Sesman provides facilities for session management and interactive session 
association with the current contexts (e.g. project, directory, buffers). While 
sesman can be used to manage arbitrary "sessions", it primary targets the Emacs 
based IDEs ([CIDER][], [ESS][], [Geiser][], [Robe][], [SLIME][] etc.)
 
-For Emacs based IDEs, session are commonly composed of one or more physical 
processes (sub-processes, sockets, websockets etc). For example in the current 
implementation of [CIDER][] a session would be composed of one or more sesman 
connections (Clojre or ClojureScript). Each [CIDER][] connection consists of 
user REPL buffer and two sub-processes, one for user eval communication and 
another for tooling (completion, inspector etc).
+For Emacs based IDEs, session are commonly composed of one or more physical 
processes (sub-processes, sockets, websockets etc). For example in the current 
implementation of [CIDER][] a session would be composed of one or more sesman 
connections (Clojure or ClojureScript). Each [CIDER][] connection consists of 
user REPL buffer and two sub-processes, one for user eval communication and 
another for tooling (completion, inspector etc).
 
 ### Concepts:
 



reply via email to

[Prev in Thread] Current Thread [Next in Thread]