Post by Károly LÅrentey(I would be grateful if people running Emacs under other non-Linux
kernels would also do this test and report any problems. Thanks!)
FreeBSD 5.4-PRERELEASE i386
I did 'baz replay' on 16 June, not sure which patch version that is, or
how to find that out that (sorry).
Post by Károly LÅrentey(1) $ emacs -Q -f server-start &
# An X frame should appear.
yes
Post by Károly LÅrentey(2) $ emacsclient -t
# A tty frame should appear.
this fails, the terminal contains
============================= start ==================
$ emacsclient -t
[1]+ Stopped emacs -Q -f server-start
============================== end ===================
the X frame is indeed suspended, but the terminal frame does not
appear. (I also had an existing emacs running gnus so i can type thsi
reply. I'll exit that and try again in a minute---see very end of the
mail.)
Post by Károly LÅrenteyC-z # Send it to background.
So, just for fun let's continue from the [1]+Stopped bit, C-z suspends the terminal
frame that was never shown:
============================= start ==================
^Z
[2]+ Stopped emacsclient -t
============================= end ==================
Post by Károly LÅrentey# The frame should disappear, and you should get a shell prompt.
so we seem to be back on track here!
Post by Károly LÅrentey(3) $ emacsclient -t
# Another tty frame should appear.
i get nothing on the terminal now, perhaps the client process is
waiting in vain to contact the server?
Post by Károly LÅrenteyC-z # Send it to background.
# The frame should disappear, and you should get a shell prompt.
again this part works as expected
============================= start ==================
^Z
[3]+ Stopped emacsclient -t
============================= end ==================
Post by Károly LÅrentey(4) $ emacsclient -nce "(mapcar (lambda (term) (cons term (terminal-name term))) (terminal-list))"
((1 . ":0.0")
(2 . "/dev/pts/6") # Any device string is OK.
(3 . "/dev/pts/6")) # The same string should be repeated.
and again this just sits there, no output no error. I did C-c and it
terminated, with exit status (seen by doing 'echo $?') 130.
Post by Károly LÅrentey(5) $ jobs
[1] Running emacs -q -f server-start &
[2]- Stopped emacsclient -t
[3]+ Stopped emacsclient -t
$ jobs
[1] Stopped emacs -Q -f server-start
[2]- Stopped emacsclient -t
[3]+ Stopped emacsclient -t
Post by Károly LÅrentey(6) $ fg %2
# The first tty frame should reappear.
C-x C-c
# The frame should disappear, and you should get a shell prompt.
The frame didnt appear, but C-x C-c did manage to exit it:
============================= start ==================
$ fg %2
emacsclient -t
^X^C
$ echo $?
130
============================= end ==================
Post by Károly LÅrentey(7) $ jobs
[1] Running emacs -q -f server-start &
[3]+ Stopped emacsclient -t
============================= start ==================
$ jobs
[1]- Stopped emacs -Q -f server-start
[3]+ Stopped emacsclient -t
============================= end ==================
as expected
Post by Károly LÅrentey(8) $ fg
# The second tty frame should reappear.
C-x C-c
# The frame should disappear, and you should get a shell prompt.
============================= start ==================
$ fg
emacsclient -t
^X^C
============================= end ==================
exactly as in (6)
============================= start ==================
$ jobs
[1]+ Stopped emacs -Q -f server-start
$ fg
============================= end ==================
This now un-suspended the x frame, but also game me a terminal frame,
C-x C-c in the terminal gives
============================= start ==================
^X^CFatal error (6)Abort trap
$ echo $?
134
============================= end ==================
Post by Károly LÅrenteyThe tty should never be left in a confused state. The Emacs process
should not at any time become blocked on tty input/output.
the tty seems to be fine
Post by Károly LÅrenteyPost by Richard LewisIf you start emacs in a terminal (emacs -nw) then subsequent X frames
have tool-bar-mode switched off. (it sort of makes sense to do this,
but i think it would be less confusing to have tool-bar-mode turned on
when the first X frame starts, unless the user has explicitly disabled
it)"
This should now be fixed. (See patch-536 and patch-537.)
seems fine now, thanks.