More updates

1 files changed, 35 insertions, 15 deletions

diff --git a/vim-acme-design.rst b/vim-acme-design.rst
index ca11f3d..aedf34e 100644
--- a/vim-acme-design.rst
+++ b/vim-acme-design.rst
@@ -6,15 +6,19 @@ Design notes on plan9-for-vimspace
 :category: computer
 :tags: vim, plan9, ACME
 
+.. komentovaný článek je lokálně dostupný na
+    file:///home/matej/Dokumenty/clanky/ACME/index.html
+
 When I have seen for the first time the screencast_ presenting ACME,
 modular text editor from Plan9, I was intriguied by its design which
-seemed to put Unix philosophy on steroids. However, in the same I was
-driven away by the mouse-driven nature of the result. I am a strong
-believer in Zenclavier_ and mouse is the first thing which breaks any
-attempts of learning my fingers patterns of behavior. I remember I was
-thinking when I saw the screencast whether it would be possible to
-transfer somehow the modular nature of ACME to the vim world. I haven’t
-came with anything, so I gave up then and forgot whole thing.
+seemed to put Unix philosophy on steroids. However, in the same time
+I was driven away by the mouse-driven nature of the result. I am
+a strong believer in Zenclavier_ and mouse is the first thing which
+breaks any attempts of learning my fingers patterns of behavior.
+I remember I was thinking when I saw the screencast whether it would be
+possible to transfer somehow the modular nature of ACME to the vim
+world. I haven’t came with anything, so I gave up then and forgot whole
+thing.
 
 .. image:: {filename}/images/glenda_sshot.png
     :width: 66%
@@ -28,11 +32,12 @@ didn’t give much of description on what’s going on (or what’s at least
 planned to go on). So, I have asked_ for help, but then I decided that
 actually what I was asking for (to summarize the screencast, separate
 individual ideas, and try to relocate them to the vim universe) could be
-done by myself. Better for annotation than screencast is actual paper,
-so I have found (because of the great Bell Labs tradition of documenting
-their design in standalone papers) Rob Pike’s paper_ describing design
-of ACME. This article is basically commentary on this paper, trying to
-identify individual features, and translate them to the vim universe.
+done by myself. For annotation the actual paper is better than
+screencast, so I have found (because of the great Bell Labs tradition of
+documenting their design in standalone papers) Rob Pike’s paper_
+describing design of ACME. This article is basically commentary on this
+paper, trying to identify individual features, and translate them to the
+vim universe.
 
 User Interface
 ==============
@@ -46,7 +51,7 @@ Tag
 
 The tag looks very much like our good bad friend, toolbar, which can be
 found in all GUI text editors and wordprocessors (including gvim). As
-such opinions on it are rather mixed and some people (including me)
+such, opinions on it are rather mixed and some people (including me)
 immediately switch them off. It is possible though that if the tag was
 done right, it could be actually useful. ACME’s design offer one
 possibly large advantage against normal toolbar in being very easily
@@ -127,19 +132,34 @@ Among programmers and Unix users it is quite common to use ``man(1)``
 style of links between two manpages, so it is possible it could be used
 as well.
 
-However, the biggest power of the system should line in fact that it
+However, the biggest power of the system should lie in fact that it
 should be extendable. Somehow. Most likely some kind of RE for
 identifying anchors of links in the body of text (possible with passing
 some kind of parameters of a link) and something looking like a very
 simple scripting language to define the action generated by the
 activating the link.
 
+Acme-specific programs
+----------------------
+
+    Although Acme is in part an attempt to move beyond typescripts, they
+    will probably always have utility. The first program written for
+    Acme was therefore one to run a shell or other traditional
+    interactive application in a window, the Acme analog of xterm. This
+    program, win, has a simple structure: it acts as a two-way
+    intermediary between Acme and the shell, cross-connecting the
+    standard input and output of the shell to the text of the window.
+
+Obviously plenty of commands mentioned in the original document are
+pointless, because vim already contains functionality provided by them
+(``g`` command) or there are other means of achieving the functionality. 
+There is an interesting question of the internal term. I guess there are 
+
 
 .. [#] Befing a leftie, I don’t like to assume that the left button is
     a primary button, so instead of left, middle, and right labels I use
     primary, middle, and secondary buttons.
 
-
 .. _project:
     https://github.com/plan9-for-vimspace/plan9-for-vimspace/
 .. _screencast: