From: ori@eigenstate.org
To: fshahriar@gmail.com
To: 9front@9front.org
Subject: Re: [9front] [PATCH] vt: rfork environment varibles
Date: Fri, 18 Dec 2020 19:26:19 -0800 [thread overview]
Message-ID: <6A6072FFF7BB1AD15957D3AD7B60053B@eigenstate.org> (raw)
In-Reply-To: <X91gRjqih+5SbhOx@delta.localdomain>
Quoth Fazlul Shahriar <fshahriar@gmail.com>:
> Hi,
>
> The patch below fixes the issue of vt(1) leaving behind some
> environment variables defined (e.g. $TERM, $COLS, $LINES) after
> it exits.
Seems good, committed.
> Incidentally, is there a better way to check if a program is
> running inside vt(1) besides checking if $TERM is defined?
>
Not that I'm aware of. I think $TERM is the best option,
and it's fairly portable to unix.
prev parent reply other threads:[~2020-12-19 3:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-19 2:07 Fazlul Shahriar
2020-12-19 3:26 ` ori [this message]
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=6A6072FFF7BB1AD15957D3AD7B60053B@eigenstate.org \
--to=ori@eigenstate.org \
--cc=9front@9front.org \
--cc=fshahriar@gmail.com \
/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.
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).