-
Notifications
You must be signed in to change notification settings - Fork 1
/
Copy pathNOTES
130 lines (108 loc) · 5.48 KB
/
NOTES
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
## various notes/documents about some common problems known in
## amnesiac/epic.
date: 2009/06/23 17:52:43; author: kreca; state: Exp; lines: +32 -21
Oki, did a bugfix to the old code
Can someone that _was_ affected by the bug please type /set_line_drawing 1
and check how the sbars look after that.
please switch between
/eval set_line_drawing 1;sbar 1;
and
/eval set_line_drawing 0;sbar 1;
to see if there is any difference
The above is another possible workaround for some terminals. seems to make
some europeans happy anyways, and thats what truly matters. ;p
## ansi/ibm437 hardcoding fonts/ugly looking etc..
-this is not a bug per se, it's just how the font handles ansi codes.
i do not know what fonts really support them, these are some of the
things you can try if your theme/colors/ansi etc.. in the client looks
screwed up, also for european/non western languages users. there is a
/latin1 alias which should fix your terminal to fix your native language
characters however you cannot use an ansi theme (in most cases)
best to use the vanilla or epic theme. for non-western language encodings.
/ibm437 will try and enable ansi-like encodings on your terminal/putty/
xterm/whatever. it is best to have a font that supports this, one such
font i do know that supports it for rxvt/aterm/etc.. is the vga11x19
font, most people do not like this font as this is huge on small screens
ie; 1024x768 or 15" or less monitors, it can be grabbed from
http://amnesiac.ircii.org/misc/
there are also some other fonts in there as well which may or may not work.
Note: artwiz-font types 'lime, smoothansi fonts works well'
## terminfo/termcap info.
-terminfo/termcap issues on FreeBSD not sure about DragonFly... possible fix
ln -s /usr/compat/linux/usr/share/terminfo /usr/share/misc
and cross your fingers? - help from |Rain| (naturally i presume this
requires the linux-compat libs installed.)
## multiserver in amnesiac.
-there has been some improvements since 1.1 release
it's been tested and known to work, at the time of this writing mjoin does
not support multiple servers. auto_reconnect is now back by popular demand.
## putty/other terminals etc..
in putty make sure you have a proper font, usually i use lucida console
however i have heard some complaints it will still not display ansi properly
even if one selects ansi/oem modes and set font translation character set to
'use font encoding' in that case try the terminal font. if all else fails
one can try /fixterm and or /latin1
[snippit from amn-faq.txt about utf-8]
Q: does amnesiac support utf-8?
A: since epic5 1.0.x release or better yet -cvs, if libiconv is installed
and properly working, try /addmod utf8 and /save (this has been minimal
tested by the amnesiac core scripters, we rely on reports from users of
amnesiac for improving utf8 and utf8 related issues)
'ldd /path/to/bin/epic5' to make sure it is linked to libiconv
an output may look similar to this.
/usr/local/bin/epic5:
Start End Type Open Ref GrpRef Name
1c000000 3c039000 exe 1 0 0 /usr/local/bin/epic5
02dd4000 22dde000 rlib 0 2 0 /usr/lib/libm.so.5.2
02413000 22417000 rlib 0 1 0 /usr/lib/libutil.so.11.0
065e6000 2661f000 rlib 0 1 0 /usr/lib/libc.so.53.1
0a4dc000 2a4ed000 rlib 0 1 0 /usr/lib/libncurses.so.11.0
0c676000 2c683000 rlib 0 1 0 /usr/lib/libssl.so.15.1
06841000 26881000 rlib 0 1 0 /usr/lib/libcrypto.so.18.0
0d510000 2d5ef000 rlib 0 1 0 /usr/local/lib/libiconv.so.6.0
## additional information provided from 'outputhelp' straight from
epic5/documentation source
## About gnu screen
People have often commented how they can get color and/or eight bit
characters working when running epic linked against ncurses and running
under gnu screen.
## wicked comment
Th:14:46|<@wicked> export LANG=C works for me mostly
Th:14:46|<@wicked> crtl+a+: c1 off
Th:14:46|<@wicked> and
Th:14:46|<@wicked> crtl+a+: utf8 off off
All of this information was graciously provided by [email protected]
(Starv@ircnet)
COLORS:
-------
To get colors under gnu screen, add these lines to your .screenrc file:
termcap vt102 'AF=\E[3%dm:AB=\E[4%dm'
terminfo vt102 'AF=\E[3%p1%dm:AB=\E[4%p1%dm'
If screen does not default to 'vt102', make sure you set TERM to vt102 before
you run epic.
EIGHT BIT CHARS:
---------------
If epic is linked against ncurses (it is by default), you can set some
ncurses options to make it accept eight bit characters more gracefully.
Add the following lines to your .inputrc:
set meta-flag on
set convert-meta off
set output-meta on
Then in EPIC, you may need to:
/set high_bit_escape 0
If you are using GNU screen, make sure you have "defc1 off" in your
screenrc file, because screen won't even display characters 128-159
with it on (and it is on by default). (from Ben Winslow, May 16, 1999)
DRAWING CHARACTERS:
-------------------
Fonts come with multiple character sets. Usually there is a character
set with european national characters ("latin-1"), and another character
set with box drawing characters ("vga"). These character sets are mutually
exclusive, and epic never forces you to use one or the other (unlike bx, or
amnesiac which forces you into vga mode unconditionally)
So if your font is in latin-1 mode, and your script wants vga mode, then you
will see lots of strange vowels and stuff. Exit epic, run this command
at your shell:
echo "X(U" | tr 'X' '\033'
and restart epic.
Good luck! Jeremy, Zak, Kreca