zsh-workers
 help / color / mirror / code / Atom feed
From: Matt Chidambaram <mc@prismtech.co.uk>
To: zsh-workers@math.gatech.edu
Subject: problems with $WATCH / $WATCHFMT
Date: Mon, 4 Dec 1995 15:01:00 +0000 (GMT)	[thread overview]
Message-ID: <Pine.OSF.3.91.951204143311.561C-100000@alpha3.prismtech.co.uk> (raw)
In-Reply-To: <199505190544.PAA16613@werple03.mira.net.au>


i have recently (till this morning) been using zsh version 2.6 beta10, 
on the following setups:

 linux (486)
 hppa (hpux 9.05) 9000/715
 dec alpha osf/1 v3.x

now, (as of this afternoon) i have been using zsh version 2.6 beta12, on 
the same platforms.

all of the following apply to both beta10 and beta12 flavours....

i have recently discovered the following features:

export WATCH=all
export WATCHFMT="%n has %a %l from %m @ %T."
export LOGCHECK=1

however there seems to be a discrepency between the information (time)
displayed in identical xterms that display login/out info on the same 
machine, about users.

essentially, i have many xterms on my screen at once - but i only really 
work in two or three of them through the day.

in those xterms that i work in - sometimes when i press return (every few 
minutes), the screen displays various peoples id's tty's and login times.

in those xterms that i dont work in very often - nothing happens until i 
press return every so often (ie every couple of hours); in these xterms - 
when i get the very similar login/out information as the other xterms - 
its great - except for the fact that the login/out times are effectively 
(plus/minus a minute) the time of day when i pressed return in that 
xterm/shell on that machine.

is this a [bug|feature|error-on-my-part] ?

ok - here's a wish for zsh ....

is there any way of getting these login/out pieces of information to 
auto-interrupt my shell - without me having to press return before it 
displays the information? - say by setting an environemnt variable.

[ie similar action to biff command -> if biff is active, it will auto 
interrupt my application etc and inform me of new mail, and the first 
few lines of the mail/ if biff is inactive then it wont]

ok thats the first problem over with ...

the second problem is the one about installing zsh on dec alpha running 
osf/1 v3.x ....

after reading the FAQ and doing as it says about copying ypclnt.h and 
altering the yp_all() signature's third parameter; i still get errors 
concerning the zle_tricky.c call to yp_all();

i eventually altered the call from within zle_tricky.c ....
from:
    yp_all(domain, PASSWD_MAP, &cb);
to:
    yp_all(domain, PASSWD_MAP, cb);

it compiles and runs ok now. i havent tested it fully.
( - but it hasnt crashed as yet...)

is the change i made valid/correct?

ok.

any help on these matters would be most appreciated.

keep up the good work.

matt.

Thought for the Day: We are the people our parents warned us about.
__________________________________________________________________________
Prism Technologies Ltd.,    |                 Matt
KingFisher House, Kingsway, |  Tel No.    +44 (0)191 491 3983
Team Valley, Gateshead,     |  Fax No.    +44 (0)191 491 3973          
Tyne & Wear, England,       |  EMail.     mc@prismtech.co.uk
NE11  0JQ, U.K.             |  WWW Page   http://www.prismtech.co.uk/
__________________________________________________________________________


  parent reply	other threads:[~1995-12-04 15:27 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <9505180204.AA00391@redwood.skiles.gatech.edu>
1995-05-18 16:30 ` new zsh mailing list up and running Mark Borges
1995-05-18 21:52   ` Richard Coleman
1995-05-19  5:44     ` procmail recipes Geoff Wing
1995-05-20 16:49       ` Deliver script (was Re: procmail) Chip Salzenberg
1995-12-04 15:01       ` Matt Chidambaram [this message]
1995-12-04 16:53         ` problems with $WATCH / $WATCHFMT Zoltan Hidvegi
1995-12-04 17:12         ` Peter Stephenson
1995-05-19  7:07     ` new zsh mailing list up and running Samuel Tardieu
1995-05-19  9:51     ` Martin Hamilton

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Pine.OSF.3.91.951204143311.561C-100000@alpha3.prismtech.co.uk \
    --to=mc@prismtech.co.uk \
    --cc=zsh-workers@math.gatech.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/zsh/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).