From: "Stefan Monnier" <monnier+lists/zsh/users/news/@tequila.cs.yale.edu>
To: zsh-users@sunsite.auc.dk
Subject: Re: Best place to put `mesg n` into?
Date: 22 Jun 1999 14:08:02 -0400 [thread overview]
Message-ID: <5l7low1531.fsf@tequila.cs.yale.edu> (raw)
In-Reply-To: <19990622092132.A18495@loriot.cs.uni-magdeburg.de>
>>>>> "Roland" == Roland Jesse <jesse@mail.CS.Uni-Magdeburg.De> writes:
> xterms opened in a way like `xterm -e wnewmail &`. This makes sense as the
I might be hopelessly confused, but I seemed to remember that
xterm -e foo bar
does *not* use any shell whatsoever. If you want a shell to be involved,
You'll have to call it explicitly:
xterm -e zsh -c 'blobla'
And then indeed, this zsh will not be interactive, etc...
Stefan
next prev parent reply other threads:[~1999-06-22 18:08 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
1999-06-22 18:08 ` Stefan Monnier [this message]
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=5l7low1531.fsf@tequila.cs.yale.edu \
--to=monnier+lists/zsh/users/news/@tequila.cs.yale.edu \
--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).