9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Skip Tavakkolian <skip.tavakkolian@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] How to take a portion of a screenshot
Date: Sat, 26 Nov 2016 07:27:37 +0000	[thread overview]
Message-ID: <CAJSxfmLEaW+LkpDTOX9ob-Ja53wrw4HDMk4j4UHNcG3RK25FFQ@mail.gmail.com> (raw)
In-Reply-To: <2C6DF5C3-ED25-409B-B835-A07E4FCEBC20@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1625 bytes --]

Nice. Looking at jpg(1) sources, it's not obvious where the allocation
limit comes in. Too bad there isn't an encoder for vp8.

for mouse position, you may need to write a shim to snoop on the mouse;
something like this:
https://github.com/9nut/plan9/tree/master/tippy



On Fri, Nov 25, 2016 at 8:23 PM Chris McGee <newton688@gmail.com> wrote:

> Thanks Skip, Cinap,
>
> This command seems to be working quite nicely (except for the memory
> allocation problem in gif(1) for larger recordings):
>
> for (i in `{seq -w 1 25}) { sleep 0.01; cat /dev/screen >
> /tmp/screen-$i.img }; togif -l -1 -d 300 /tmp/screen-*.img >
> /tmp/recording.gif; rm /tmp/screen-*.img; echo Done
>
> It would be easy enough to introduce a crop to restrict the recording to a
> particular window or area of the screen.
>
> Is there a way to capture the current mouse position without blocking to
> wait on an event from /dev/mouse? I was thinking that it would be
> interesting to crop around the current mouse position.
>
> Chris
>
>
> > On Nov 24, 2016, at 3:56 AM, cinap_lenrek@felloff.net wrote:
> >
> > rc variables are lists, and $#var evalulates to the
> > length of the list... you can use that to make counters
> > by concatenating elements to a list:
> >
> > term% a=() while(! ~ $#a 13){echo $#a $a; a=(1 $a);}
> > 0
> > 1 1
> > 2 1 1
> > 3 1 1 1
> > 4 1 1 1 1
> > 5 1 1 1 1 1
> > 6 1 1 1 1 1 1
> > 7 1 1 1 1 1 1 1
> > 8 1 1 1 1 1 1 1 1
> > 9 1 1 1 1 1 1 1 1 1
> > 10 1 1 1 1 1 1 1 1 1 1
> > 11 1 1 1 1 1 1 1 1 1 1 1
> > 12 1 1 1 1 1 1 1 1 1 1 1 1
> >
> > --
> > cinap
> >
>
>
>

[-- Attachment #2: Type: text/html, Size: 2913 bytes --]

      reply	other threads:[~2016-11-26  7:27 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-23 12:28 Chris McGee
2016-11-23 15:34 ` Adriano Verardo
2016-11-23 16:06 ` Richard Miller
2016-11-23 16:28   ` hiro
2016-11-23 18:39   ` Chris McGee
2016-11-23 20:07     ` Skip Tavakkolian
2016-11-23 20:31       ` Benjamin Purcell
2016-11-23 20:36         ` James A. Robinson
2016-11-23 20:41           ` hiro
2016-11-23 20:56             ` Skip Tavakkolian
     [not found]               ` <CAEVxPTOrWFf2hd-nWDeP8GE5qSjhqB6Ox=W1C9FhrVt9S70V-g@mail.gmail.com>
     [not found]                 ` <CAEVxPTP5L2=SpYEn96QUpsZ1VDjUwTKUzxCNp+WVoJqVCDocvg@mail.gmail.com>
2016-11-23 21:30                   ` Jules Merit
2016-11-23 21:57                     ` Steve Simon
2016-11-23 22:16                       ` Jules Merit
2016-11-28  6:30                     ` erik quanstrom
2016-11-23 20:48           ` Skip Tavakkolian
2016-11-24  5:06       ` Chris McGee
2016-11-24  7:23         ` Skip Tavakkolian
2016-11-24  8:56         ` cinap_lenrek
2016-11-26  4:23           ` Chris McGee
2016-11-26  7:27             ` Skip Tavakkolian [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=CAJSxfmLEaW+LkpDTOX9ob-Ja53wrw4HDMk4j4UHNcG3RK25FFQ@mail.gmail.com \
    --to=skip.tavakkolian@gmail.com \
    --cc=9fans@9fans.net \
    /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).