|
|
| Author |
Message |
cross
|
|
Fronttalk Discussion
| 
Jan 22 20:05 UTC 2005 |
This item is for reporting and discussing bugs in fronttalk.
|
| 115 responses total. |
cross
|
|
response 1 of 115:
|
Jan 22 20:06 UTC 2005 |
Fronttalk doesn't seem able to deal with being backgrounded using, e.g., ^Z.
Just FYI.
|
janc
|
|
response 2 of 115:
|
Jan 23 03:19 UTC 2005 |
I'm currently doing some work on Fronttalk. Version 0.3.7 will have many
fixes to the "read since" logic. It will also use "readline" to enable
command-line editing. There is fix to a bug that caused "slipped in" messages
to be printed inappropriately sometimes. Better error messages for bad shell
escapes.
There was an item someplace on Grex where various people entered Fronttalk
bug reports, but I can't remember where it was. I tried to do some searching,
but Grex was being too slow to make this possible. I should probably try
again now that things are working better.
|
janc
|
|
response 3 of 115:
|
Jan 23 03:21 UTC 2005 |
I tried ^Z in three places:
- Ok prompt
- Reponse or Pass prompt
- Response text entry
In the first two, it worked OK, but didn't redisplay the prompt when
returning, so it wasn't obvious where you were.
In the third case I had to do "fg" twice to get back in.
OK, needs a bit of work here.
|
janc
|
|
response 4 of 115:
|
Jan 23 03:40 UTC 2005 |
I guess that if we are a login shell, control-Z should be handled differently.
Looks like when picospan is a login shell, control-Z doesn't terminate it,
but it doesn't work right in sub processes either. You really don't have
job control when you use the bbs shell. Dunno if I can (or want to) do
better.
|
gelinas
|
|
response 5 of 115:
|
Jan 23 04:19 UTC 2005 |
The only report I can find right now that you've not addressed above is from
Kent Nassen:
Putting literal ANSI escape codes in picospan rsep/isep/ishort (via
.cfonce) doesn't work for changing colors in bbs any longer. All I get are
the raw codes. My terminal can show colors just fine otherwise.
Scott mentioned not getting certain characters (Norwegian, I think they
were), too.
|
janc
|
|
response 6 of 115:
|
Jan 23 04:58 UTC 2005 |
The failure to show escape does is a function of the "more" pager on the
new machine. It expands out those escape sequences. There is an option
someone described that causes it to not do this.
Norwegian characters are a research problem.
|
ryan
|
|
response 7 of 115:
|
Jan 23 14:35 UTC 2005 |
This response has been erased.
|
cross
|
|
response 8 of 115:
|
Jan 23 16:27 UTC 2005 |
Good to hear about readline; that was on my list of things to ask about.
It was me who figured out the trick with `more' and ANSI color escapes.
I remember that there was an item for discussing fronttalk bugs, but I
can't remember what it was now, either, so I entered this one.
|
janc
|
|
response 9 of 115:
|
Jan 24 18:00 UTC 2005 |
Well, it's not in garage1, which is where I expected it to be. Might have
been in agora.
At least part of the problem with suspending fronttalk was actually a problem
with suspending 'gate'. I've updated the signal-handling in gate to work with
modern BSD signal semantics (sigaction and whatnot). That has been installed
on Grex. Fronttalk's signal handling has also gotten better, but that hasn't
been installed here yet.
Adding readline to fronttalk has the sad side effect of making gate look
rather shabby. Now we have more powerful text editing when you are in command
mode than when you are entering responses! Arrow keys work in command mode,
but not in text entry mode!
I did once have a plan for a successor to be called 'sue' (Scroll Up Editor)
that would have given you full editing without clearing the screen. Wrote
some notes on how to do it, but never started coding it. It'd be easier today
than it would have been then, since the variety of different terminals has
been much reduced, but it would still be a fairly large programming project
and the demand for novice-friendly command-line text-entry tools isn't what
it used to be, so I don't think it will ever happen.
|
remmers
|
|
response 10 of 115:
|
Jan 24 18:07 UTC 2005 |
Is this item just for bugs, or can we talk about features too?
|
cross
|
|
response 11 of 115:
|
Jan 24 19:39 UTC 2005 |
I don't see why it can't be about features as well.
Maybe I should have titled the item, `fronttalk discussion'. Whoops.
|
remmers
|
|
response 12 of 115:
|
Jan 24 20:26 UTC 2005 |
(I believe that the person who entered an item can change its title,
using backtalk.)
|
remmers
|
|
response 13 of 115:
|
Jan 24 20:27 UTC 2005 |
(But maybe it would be more convenient for Jan to have features discussion
in a separate place...)
|
janc
|
|
response 14 of 115:
|
Jan 26 04:12 UTC 2005 |
I retitled the item, using the Fronttalk "retitle" command.
I've installed Fronttalk 0.3.7, which fixes a number of bugs including many
"read since" bugs, and some job control bugs. It adds readline support while
in command mode.
|
cross
|
|
response 15 of 115:
|
Jan 26 06:57 UTC 2005 |
Awesome! Readline support is definitely cool. Thanks, Jan!
|
remmers
|
|
response 16 of 115:
|
Jan 26 12:26 UTC 2005 |
|
gelinas
|
|
response 17 of 115:
|
Jan 26 12:27 UTC 2005 |
My macros for joining other conferences don't work. Is this because of the
"set sane" in my .cfonce? If so, it seems counter-productive to override
the macros defined in that same file.
|