From: Nick Owens <mischief@9.offblast.org>
To: 9front@9front.org
Subject: Re: [9front] Vt sucks more cock than I do.
Date: Tue, 17 Dec 2013 15:35:31 -0800 [thread overview]
Message-ID: <20131217233531.GW4672@iota.offblast.org> (raw)
In-Reply-To: <54B4C1BE-7B08-431A-A462-427F3532D11C@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 583 bytes --]
On Tue, Dec 17, 2013 at 06:27:56PM -0500, Matthew Veety wrote:
> I've been working on making vt more vt100 compliant and work better with sys=
> tems that "take advantage" of features that aren't implemented. Do you guys h=
> ave bugs and shit that are bugging you that you would like me to work on whi=
> le I'm fixing it?
>
resizing, how does it work?
this is kind of a pipe dream since we have no SIGWINCH, but it would be neat if you can figure out a way get vt (and maybe ssh) to tell the remote end a resize occurred by sending a note, or something.
mischief
[-- Attachment #2: Type: application/pgp-signature, Size: 834 bytes --]
next prev parent reply other threads:[~2013-12-17 23:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-17 23:27 Matthew Veety
2013-12-17 23:35 ` Nick Owens [this message]
2013-12-17 23:44 ` [9front] " Kurt H Maier
2013-12-18 0:01 ` Matthew Veety
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=20131217233531.GW4672@iota.offblast.org \
--to=mischief@9.offblast.org \
--cc=9front@9front.org \
/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).