summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorRené Genz <liebundartig@freenet.de>2022-01-28 15:47:09 +0200
committerAlexander Naumov <alexander_naumov@opensuse.org>2022-01-28 15:47:09 +0200
commitc5d53d69c08eeb69416af5bef8408d121f6c47ba (patch)
treed7cc02a051f94d01e42973e4c90df77663ac3ef5
parent797df7aa0dc1672418c7aa758d1ec9de24387a50 (diff)
downloadscreen-c5d53d69c08eeb69416af5bef8408d121f6c47ba.tar.gz
[PATCH] fix typing errors
-rw-r--r--src/.iscreenrc20
-rw-r--r--src/ChangeLog14
-rw-r--r--src/HACKING2
-rw-r--r--src/INSTALL6
4 files changed, 21 insertions, 21 deletions
diff --git a/src/.iscreenrc b/src/.iscreenrc
index 802afbd..7a937f9 100644
--- a/src/.iscreenrc
+++ b/src/.iscreenrc
@@ -17,7 +17,7 @@ markkeys "h=^B:l=^F:\$=^E" # some missing emacs style bindings in copymode
echo -n "booting screen"
# let it flash, not horn!
-#vbell on # "vbell" don't work any longer, sorry.
+#vbell on # "vbell" doesn't work any longer, sorry.
#vbell_msg " Wuff, Wuff!! " # this is the default message
#bell "Bimmmel No. %" # sounds the bell and shows a message
@@ -45,11 +45,11 @@ echo -n "."
# Printing in the leftmost column is not save. We express that fact as :LP@:
#
# Emacs tends to smear it's highlighted status bar across the screen, producing
-# ugly areas of bright background, if termcap is'nt perfectly sober.
+# ugly areas of bright background, if termcap isn't perfectly sober.
# Give a little :ms@: in the termcap, this may help.
#
# And who invented the initialisation for facit terminals? We tell him that
-# we non't like smooth scroll, by specifying :ti=\E[?l:.
+# we don't like smooth scroll, by specifying :ti=\E[?l:.
# \E[?3l 80 Zeichen
# \E[?3h 132 Zeichen
# LP Last column Printable
@@ -92,11 +92,11 @@ termcap xterm* WS=\E[8;%d;%dt
# ICL 6402 testing:
termcap icl* G0:S0=\E$[start]:E0=\E%[end]:C0=j9k<l6m3n?q\:t7u=v;w>x5 GS=\E(0^O:GE=\E(B^O:G1=k:G2=l:G3=m:G4=j:GV=x:GH=q:GR=u:GL=t:GU=w:GD=v:GC=n
-# Flowcontrol produces trouble. ^S und ^Q will never reach screen, as our
+# Flow control produces trouble. ^S und ^Q will never reach screen, as our
# terminals catch them locally. Who can explain that to me?:
#flow on|off|auto [interrupt]
-# Long Lines get wrapped around (the back of your terminal). This is the
+# Long lines get wrapped around (the back of your terminal). This is the
# default for vt100. But now programs make different asumptions about your
# terminal. You may find two linefeeds where you'd expect one, or you may
# be confronted with a truncated line. Currently there is no fix, but pressing
@@ -106,10 +106,10 @@ termcap icl* G0:S0=\E$[start]:E0=\E%[end]:C0=j9k<l6m3n?q\:t7u=v;w>x5 GS=\E(0^O:G
# the autoaka allows you to see the currently executing shell command in the
# window name field. To use that, your shell prompt must contain ^[k^[\ or
# you will see the string "(init)" as a name.
-# in my .cshrc I may use this for a wonderfull tcsh-prompt:
+# in my .cshrc I may use this for a wonderful tcsh-prompt:
# set prompt="%{^[k^[\\%}%h %c2(%m)%# "
#
-# defining a shellaka that contains a pipe-symbol (|) activites the
+# defining a shellaka that contains a pipe-symbol (|) activates the
# autoaka feature. To the left of that | you specify a constant part of
# your prompt as a trigger, to the right you may place a default string
# as in
@@ -121,8 +121,8 @@ shellaka '> |tc'
# ... now a little bit of key bindings
# In case we don't have write permission for /etc/utmp (no s-bit)
# we create even local windows via rlogin. -> Et voila: a utmp-slot
-# utmp-slots are strongly recomended to keep sccs and talk happy.
-# (thus we have ^A# or. ^Ac for windowcreation with or without utmp-slot.)
+# utmp-slots are strongly recommended to keep sccs and talk happy.
+# (thus we have ^A# or. ^Ac for window creation with or without utmp-slot.)
# but if we run suid-root, we produce all the rlogins with -ln,
# as nobody shall refer to these pty's.
bind '!' screen -ln -k faui41 rlogin faui41
@@ -151,7 +151,7 @@ bind 'L'
# What happens, when you 'think emacs' and want to erase a whole
# line? You type ^A^K right? Under screen it should be ^Aa^K. But...
# killing the window would be a real punishment for a little mistyping.
-bind k #wow! I even amange to type ^Ak by accident.
+bind k #wow! I even mange to type ^Ak by accident.
#bind ^k
#bind K kill
diff --git a/src/ChangeLog b/src/ChangeLog
index 98ca9a6..4b11ce7 100644
--- a/src/ChangeLog
+++ b/src/ChangeLog
@@ -369,8 +369,8 @@ screen 3.0 Patchlevel 6
=======================
.screenrc:
- screen now only opens the windows you explicitly ask for. if you
- specify none, you still get one window, of course.
+ screen now only opens the windows you explicitly ask for.
+ If you specify none, you still get one window, of course.
screen 3.0. Patchlevel 5
========================
@@ -388,7 +388,7 @@ markkeys "string"
by a colon. Oldchar and newchar are either single ascii characters,
or the two character sequence ^x, where x is an ascii character, or
a 3 digit octal value prepended with '\'. the string "\040=.:^M=q"
- rebinds '.' to set marks, and the return rey will abort copy mode.
+ rebinds '.' to set marks, and the return key will abort copy mode.
set scrollback 100
resizes the scrollback history buffer to 100 lines. a default of 50
@@ -423,7 +423,7 @@ screen -wipe
^A : set vbell_msg "Wuff Wuff"
-Thousand enhancements: help resizible, copy'n'paste in main
+Thousand enhancements: help resizable, copy'n'paste in main
socket loop, and no more '\0' hackin'. :WS=\E8;%d;%dt:
screen can now resize windows under sunview.
@@ -451,12 +451,12 @@ pow_detach_msg "text string"
bind 'O' set login off
is valid in your .screenrc as well as typed at the ':' prompt.
a bonus is ":set all" which is synonym to ":help".
- At the Colon prompt also KeyNames can be entered, alothough that makes
+ At the Colon prompt also KeyNames can be entered, although that makes
not always sense.
^A x uses a builtin lockprg, if
a) we don't find our lockprg, or
- b) user supplies us with the environmet variable LOCKPRG set to "builtin"
+ b) user supplies us with the environment variable LOCKPRG set to "builtin"
the builtin locks until your login password is typed. on systems using
"shadow password files" you are prompted for a password.
@@ -477,7 +477,7 @@ bug in SetForeWindow fixed.
rare markroutine bug fixed.
-we dont open every file the attacher tells us.
+we don't open every file the attacher tells us.
we have now our wonderful "Wuff, Wuff" visual_bell
diff --git a/src/HACKING b/src/HACKING
index b78d40f..9cd0d1a 100644
--- a/src/HACKING
+++ b/src/HACKING
@@ -4,7 +4,7 @@ WIP notes on hacking the Screen source.
The local variable nr is set to an integer value representing the
command to be evaluated; for every command `foo', there is an
integer value RC_FOO for use as nr's value to represent it. Find
- the matching case label to follow procesing of the command.
+ the matching case label to follow processing of the command.
The RC_FOO values are defined in comm.h, which is automatically
generated by comm.sh, based on the names of the commands
diff --git a/src/INSTALL b/src/INSTALL
index 3ad58a1..dd48ee0 100644
--- a/src/INSTALL
+++ b/src/INSTALL
@@ -40,7 +40,7 @@ sysadmins discuss the location of SOCKDIR, whether it should be in /tmp or
not. At least it must be on a filesystem that supports sockets/fifos.
SOCKDIR must not point into an AFS (Andrew File System) mounted directory.
If you are uncertain about your NFS implementation, use a UFS directory for
-SOCKDIR. Personally, I favour a users home directory and recommend the the
+SOCKDIR. Personally, I favour a user's home directory and recommend the the
/tmp/ area.
The path for ETCSCREENRC may also need to be adapted.
@@ -58,7 +58,7 @@ You can then try 'make install' (if you dare).
--------------------
You may well run screen from your private binary directory and with a
private socket directory like $HOME/.screen. But to have a full featured
-screen and (from a users point of view) more secure pty's you should
+screen and (from a user's point of view) more secure pty's you should
consult a system administrator and discuss installing screen setuid-root
in some globally accessible directory like /usr/local/bin.
@@ -94,7 +94,7 @@ If so, mail me.
The files screenrc and etc/etcscreenrc are instructive samples that
demonstrate what can/should be done from your private .screenrc and from
$ETCSCREENRC -- do not just copy them. Read them. Look through the
-etcscreenrc file for system wide defaults that you like to set. e.g.
+etcscreenrc file for system wide defaults that you like to set, e.g.
autodetach off, startup_message off, vbell on, ...
Since version 3.2.15 the screenrc file syntax changed slightly. All rc files
from previous versions should be run through the 'newsyntax' script that comes