aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorKaroly Lorentey2004-02-25 00:53:40 +0000
committerKaroly Lorentey2004-02-25 00:53:40 +0000
commit01d81f75b97d8e105f1a84be05f30d40b727ef6e (patch)
treed71936f950d006413f44fa799449039e9c8ca9ed
parente39e96544557e39200234f3f855f6567f9ea6bff (diff)
downloademacs-01d81f75b97d8e105f1a84be05f30d40b727ef6e.tar.gz
emacs-01d81f75b97d8e105f1a84be05f30d40b727ef6e.zip
README updates.
git-archimport-id: lorentey@elte.hu--2004/emacs--multi-tty--0--patch-95
-rw-r--r--README.multi-tty52
1 files changed, 36 insertions, 16 deletions
diff --git a/README.multi-tty b/README.multi-tty
index aeec31a5f6a..2853ae419de 100644
--- a/README.multi-tty
+++ b/README.multi-tty
@@ -185,27 +185,47 @@ See arch logs.
185THINGS TO DO 185THINGS TO DO
186------------ 186------------
187 187
188** There are frequent input-related coredumps, with inconclusive
189 backtraces. An example (from Mark Plaksin):
190
191 #0 0x40301571 in kill () from /lib/libc.so.6
192 #1 0x080eb371 in fatal_error_signal (sig=11612)
193 at /home/happy/src/emacs/multi-tty-cvs/src/emacs.c:385
194 #2 <signal handler called>
195 #3 0x40301571 in kill () from /lib/libc.so.6
196 #4 0x080eb3cc in abort () at /home/happy/src/emacs/multi-tty-cvs/src/emacs.c:418
197 #5 0x080c8f18 in handle_one_xevent (dpyinfo=0x862ebb8, eventp=0xbfffef20,
198 bufp_r=0xbfffefa4, numcharsp=0xbfffefa8, finish=0xbfffef1c)
199 at /home/happy/src/emacs/multi-tty-cvs/src/xterm.c:5884
200 #6 0x080ca531 in XTread_socket (display=0x862ee20, bufp=0xbffff0f4, numchars=1,
201 expected=1) at /home/happy/src/emacs/multi-tty-cvs/src/xterm.c:7221
202 #7 0x080f577a in read_avail_input (expected=1)
203 at /home/happy/src/emacs/multi-tty-cvs/src/keyboard.c:6609
204 #8 0x080f59fc in handle_async_input ()
205 at /home/happy/src/emacs/multi-tty-cvs/src/keyboard.c:6807
206 #9 0x0813aa41 in Fgarbage_collect ()
207 at /home/happy/src/emacs/multi-tty-cvs/src/alloc.c:4549
208 #10 0x0817c06d in Fbyte_code (bytestr=1, vector=131, maxdepth=-1073745424)
209 at /home/happy/src/emacs/multi-tty-cvs/src/bytecode.c:530
210 [...]
211
212 They seem to always happen in handle_one_xevent right after garbage
213 collection.
214
188** There is a flicker during the startup of `emacs -nw'; it's as if 215** There is a flicker during the startup of `emacs -nw'; it's as if
189 the terminal is initialized, reset and then initialialized again. 216 the terminal is initialized, reset and then initialialized again.
190 Debug this. (Hint: narrow_foreground_group is called twice during 217 Debug this. (Hint: narrow_foreground_group is called twice during
191 startup.) 218 startup.)
192 219
193** Dan Nicolaescu (dann at ics dot uci dot edu) suggests that -nw 220** Dan Nicolaescu suggests that -nw should be added as an alias for -t
194 should be added as an alias for -t in emacsclient. Good idea. 221 in emacsclient. Good idea. (Alas, implementing this is not
195 (Alas, implementing this is not trivial, getopt_long does not seem 222 trivial, getopt_long does not seem to support two-letter ``short''
196 to support two-letter ``short'' options.) 223 options.)
197 224
198** Robert J. Chassell reports: 225** Mark Plaksin suggests that emacsclient should accept the same
199 226 X-related command-line arguments as Emacs. Most of the X-related
200 > * After starting the frame in the VC, I saw this message in the 227 argument-handling is done in Lisp, so this should be quite easy to
201 > *Message* buffer 228 implement.
202 >
203 > error in process filter: server-process-filter: \
204 > Wrong type argument: sequencep,\
205 > framep
206 > error in process filter: Wrong type argument: sequencep, framep
207 >
208 > This also happens when I start a new frame in an xterm.
209 229
210** Very strange bug: visible-bell does not work on secondary 230** Very strange bug: visible-bell does not work on secondary
211 terminals. This might be something xterm (konsole) specific. 231 terminals. This might be something xterm (konsole) specific.