zsh-workers
 help / color / mirror / code / Atom feed
From: Steven Lumos <steven@lumos.us>
To: zsh-workers@sunsite.dk
Subject: Re: idea for new feature (was: Re: sticky-note and zle bindings)
Date: Fri, 18 Jan 2008 12:02:59 -0800	[thread overview]
Message-ID: <x6r6ge52bw.fsf@bitty.lumos.us> (raw)
In-Reply-To: <691a5d910801180119p32d48643wa55fd2aefaa3bf6a__27696.5395118625$1200648096$gmane$org@mail.gmail.com>

"Bart Schaefer" <schaefer@brasslantern.com> writes:

> On 1/17/08, Andy Spiegl <zsh.Andy@spiegl.de> wrote:
>> > The upshot is that this isn't a zsh feature -- it's a cooperative
>> > feature that requires effort from both the shell and whatever other
>> > user interface environment it's running inside.
>> Right, so let's start. :-)
>
> Here's something that may be of use.  Recent xterm has adopted window
> control sequences from dtterm, according to
> http://www.xfree86.org/current/ctlseqs.html, so zsh might have a
> chance at saving/restoring some window state.  I haven't tried Konsole
> but Gnome-terminal pays attention to a subset of this.  Other
> terminals I don't know.

I guess "recent" may be relative (Sun 1 you say?), but I've been using
the following for at least 7 years.  I do something like

  % xtctl size 100 60 move 0 0

all the time on XTerm, rxvt (cygwin no less), OSX Terminal.app, and
PuTTY.  That ctlseqs.ms certainly does get around....

(If it looks naive, it's because I was limiting it to Bourne shell,
mostly for fun.  At some point while implementing 'get' I gave up and
switched to bash, but it's been so long now that I don't remember why.)

Err, Gnus helpfully informed me that there was a literal ^[ and ^G in
there (Bourne shell...), so here's a link instead:
http://www.isri.unlv.edu/~slumos/hacks/xtctl.  It's mostly a curiosity
at this point anyway...

Steve


      parent reply	other threads:[~2008-01-18 20:25 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20080104105900.37a87f7e@news01>
     [not found] ` <237967ef0801040304h494987bv939bf6ff9541123f@mail.gmail.com>
     [not found]   ` <477E177A.3060303@kotiportti.fi>
     [not found]     ` <Xns9A20C0F173D23zzappergmailcom@80.91.229.13>
     [not found]       ` <080113000048.ZM15017@torch.brasslantern.com>
     [not found]         ` <20080116131048.GC16058@spiegl.de>
     [not found]           ` <080116075915.ZM12209@torch.brasslantern.com>
     [not found]             ` <20080116171253.GF16058@spiegl.de>
     [not found]               ` <080116191103.ZM12889@torch.brasslantern.com>
     [not found]                 ` <20080117172603.GA664@spiegl.de>
     [not found]                   ` <691a5d910801180119p32d48643wa55fd2aefaa3bf6a@mail.gmail.com>
2008-01-18 17:38                     ` Misbehavior of "read" or ...? Bart Schaefer
2008-01-18 18:05                       ` Peter Stephenson
2008-01-18 18:26                         ` Bart Schaefer
     [not found]                   ` <691a5d910801180119p32d48643wa55fd2aefaa3bf6a__27696.5395118625$1200648096$gmane$org@mail.gmail.com>
2008-01-18 20:02                     ` Steven Lumos [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=x6r6ge52bw.fsf@bitty.lumos.us \
    --to=steven@lumos.us \
    --cc=zsh-workers@sunsite.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).