|
|
| Author |
Message |
| 22 new of 115 responses total. |
janc
|
|
response 94 of 115:
| 
Feb 18 16:01 UTC 2005 |
There are a couple tools on Grex that are handy for accessing conferences
from scripts.
extract - prints out ranges of resposnes from any item
forget - forgets an item in a conerence
partname - prints participation file name for a conference
findconf - prints full pathname for a conference
These are mostly derived from the bbsread source, a long ago predecessor to
Backtalk. However, there is no post command. Jeff Poskanzer wrote a similar
set of commands, including a post command, for the Well long ago.
The easiest way to implement a post program would be as a Fronttalk client.
I should really do a set of little Perl programs with interfaces similar to
the ones above, that use the Fronttalk library functions to make fronttalk
requests to do simple operations like these. Probably not high on my priority
list right now though.
|
cross
|
|
response 95 of 115:
|
Feb 18 17:39 UTC 2005 |
Hmm, it would be nice to have the grexsoft commit messages logged into
BBS. Currently, I'm using the log_accum.pl and commit_prep.pl scripts
that the FreeBSD people use to send myself emails with commit messages;
it'd be nice to wrap that into BBS as well.
|
naftee
|
|
response 96 of 115:
|
Feb 18 20:32 UTC 2005 |
re 93 Thank you, that was interesting. I think it's sad when people say they
wrote too much :(
|
cross
|
|
response 97 of 115:
|
Feb 21 01:25 UTC 2005 |
Hmm, is there a way to get fronttalk to set the process title to something
more meaningful than, ``/usr/bin/perl /usr/local/bin/ft'' ? A perl
equivalent to secroctitle() or something?
|
cross
|
|
response 98 of 115:
|
Feb 21 15:16 UTC 2005 |
Regarding #46; Well, I specifically meant things like exceptions
to what `set supersane' does and things of that nature (see your
#43). I'd prefer that, moving forward, we go with behavior that
makes the most sense logically, even if that strays from what
picospan does when what picospan does is *illogical*. Building in
backwards compatibility for stupid behavior seems like misplaced
effort to me.
By the way, whate sites still actually use picospan? The Well is
the only one I'm aware of. Might it make sense to make them aware
of the fronttalk/backtalk combination? I haven't heard of many
bugs in fronttalk recently; it would seem we've gotten to the point
of semi-stability in that many of the requests we see now are
requests for additionally functionality of things that have long
been on individuals' picospan wishlists. Should we then try to
make the switch of the `bbs' symlink in /usr/local/bin to point to
fronttalk, installing a `picospan' symlink to /usr/local/bin for
those who encounter bugs or wish to run the older software?
|
cross
|
|
response 99 of 115:
|
Feb 27 08:48 UTC 2005 |
Regarding #94, #95; I figured out enough of fronttalk to write a
minimal `post' command for logging CVS commit messages into the
BBS. I've hooked it into the log_accum.pl stuff I'm using for the
grexsoft CVS repository; see item 9 in the garage group for an
example. Note that this is in addition to email.
This is all actually pretty easy and cool; the FreeBSD people did
a reasonable job of modularizing everything such that log_accum.pl
and commit_prep.pl use a configuration file to figure out where to
send their output. I wrote a simple shell script that acts as a
wrapper around sendmail to capture log_accum.pl's output and then
(a) email it to the address, `cvs-grexsoft' here on grex, and (b)
post it into item 9 in garage. I then changed the configuration
file such that log_accum.pl invokes my shell script instead of
sendmail.
The intention is that cvs-grexsoft should be a list of people
interested in getting these things via email, while others can read
them via BBS.
I'm fairly pleased with the result.
|
cross
|
|
response 100 of 115:
|
Feb 27 08:58 UTC 2005 |
I just found a bug somewhere. C-style character literals, such as
\ 0 0 7 or \ a don't get interpreted correctly; they're cut off. See
item 9 in this conference for an example.
Note: this is entered from fronttalk and I get the same error.
|
remmers
|
|
response 101 of 115:
|
Mar 8 17:57 UTC 2005 |
At the moment, Picospan and Fronttalk/Backtalk have radically different
ideas of how many newresponse items I have in Agora. Pico says 151,
FT and BT both say 21. I've been reading the conferences mostly with
Backtalk recently.
|
sholmes
|
|
response 102 of 115:
|
Mar 9 02:27 UTC 2005 |
On Fronttalk ,when you come to the "Respond, pass, forget, quit, or ? for more
options?" prompt andyou type 'forget' , the prompt comes back again and you
have to 'pass' that one. ideally I would like to say forget once and be done
with it.
|
cross
|
|
response 103 of 115:
|
Mar 9 02:35 UTC 2005 |
I think if you do, `set nomodestay' in your .cfonce file, it will
have the behavior you desire. That's what I did when I wanted to
do the same thing.
|
sholmes
|
|
response 104 of 115:
|
Mar 9 04:45 UTC 2005 |
Thanks, will try.
|
cross
|
|
response 105 of 115:
|
Mar 14 20:40 UTC 2005 |
I've modified the bbspost.pl command to do error checking, and put it
into grexsoft.
|
cross
|
|
response 106 of 115:
|
Mar 14 20:40 UTC 2005 |
Has anyone looked into #100?
|
davel
|
|
response 107 of 115:
|
Mar 31 19:58 UTC 2005 |
Another fronttalk bug (or unimplemented feature). In picospan, if I join a
conference I haven't previously joined, I am asked:
> You are not a member of /bbs/someconferenceorother
> Do you wish to:
>
> Join, quit or help?
Entering "join" (or "j") creates my participation file (& maybe some other
stuff), setting me up as a participant in the conference.
Entering "quit" gives me an "Ok:" prompt but (I think) back in whatever
conference I was in before. There's a "registration aborted" message.
Entering "help" gives the following:
> You have three main options at this point:
> join -- become a new member of this conference
> observe -- look in at this conference (you will no
> be able to enter anything new)
> quit -- quit out of this menu and select another conference
> There are also some other things you can do, try "help misc"
> for notes on those.
>
I frequently use the "observe" option. I do this when there's an item
I want to look at in a conference I normally don't want to read. I can
read, but no participation file is created & I can't post.
fronttalk appears to lack all this. I think the "resign" command is
broken as well.
|
gelinas
|
|
response 108 of 115:
|
Apr 1 00:08 UTC 2005 |
Hmm... "help resign" sounds reasonable, but as you note, "resign" doesn't
work.
|
naftee
|
|
response 109 of 115:
|
Apr 5 07:37 UTC 2005 |
I can't see the response that i've "hidden" using fronttalk. "hide' seems
to be interpreted as "scribble"
|
naftee
|
|
response 110 of 115:
|
Oct 28 03:06 UTC 2005 |
janc !
fronttalk 0.9.2 is installed on m-net, but not working too well !
can you help us brothers out ?!
|
kingjon
|
|
response 111 of 115:
|
Nov 10 02:36 UTC 2005 |
In Fronttalk, when using semicolons,
---
n;r
---
runs through the list of conferences, and if I don't have any with any new
items, it says "No items found in range." Picospan doesn't execute the "read"
command when the "next" command doesn't actually change conferences.
|
kingjon
|
|
response 112 of 115:
|
Nov 10 19:00 UTC 2005 |
My pager works for reading items, but for "disp conf" it just pours
everything on the screen, and if I try "disp conf | less" it does
the same thing and then says (after the output) "Bad parameter near
|" and "Bad parameter near less". I don't know if "b" uses the pager
automatically, but I tried "b | less", and it said (before the
output) "Don't understand |" and "Don't understand less".
|
kingjon
|
|
response 113 of 115:
|
Nov 11 18:31 UTC 2005 |
Just noticed this: "help read" includes the following:
" The using pager is "more" which will pause the display after
each full screen."
That seems rather awkwardly worded.
|
naftee
|
|
response 114 of 115:
|
Nov 12 05:10 UTC 2005 |
Ignore the word "using", kingjon. That should sort you out.
|
kingjon
|
|
response 115 of 115:
|
Jan 14 03:41 UTC 2006 |
In reading some *really* old items I came across to a reference to a help
section in picospan that I think would be helpful in ft but should be trivial
to add: the "help etiquette" section.
|