From: Roland Jesse <jesse@mail.CS.Uni-Magdeburg.De>
To: zsh-users@sunsite.auc.dk
Subject: Re: Best place to put `mesg n` into?
Date: Tue, 22 Jun 1999 09:59:51 +0200 [thread overview]
Message-ID: <19990622095951.A18723@loriot.cs.uni-magdeburg.de> (raw)
In-Reply-To: <990622075325.ZM28012@candle.brasslantern.com>; from Bart Schaefer on Tue, Jun 22, 1999 at 07:53:25AM +0000
Bart Schaefer wrote:
> If you put "mesg" in .zshenv, you'll have to protect it with something
> like
>
> [[ -t 0 ]] && mesg n
Which is exactly what I wanted to avoid.
> A better solution is
>
> xterm -ut -e wnewmail &
Man, you are just it. Thanks a lot.
Roland
next prev parent reply other threads:[~1999-06-22 8:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-06-22 7:21 Roland Jesse
1999-06-22 7:53 ` Bart Schaefer
1999-06-22 7:59 ` Roland Jesse [this message]
1999-06-22 18:08 ` Stefan Monnier
1999-06-22 21:55 ` Roland Jesse
1999-06-22 22:29 ` Thomas Koehler
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=19990622095951.A18723@loriot.cs.uni-magdeburg.de \
--to=jesse@mail.cs.uni-magdeburg.de \
--cc=zsh-users@sunsite.auc.dk \
/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).