From: Skip Tavakkolian <skip.tavakkolian@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Rio: possibility to forbid resizing a window?
Date: Thu, 31 Dec 2015 19:33:42 +0000 [thread overview]
Message-ID: <CAJSxfmK1j7p9soZuGZjLTcs9N5MjuTk-V-x+WKg_K0_sfN0wRQ@mail.gmail.com> (raw)
In-Reply-To: <20151231170815.GA106@polynum.com>
[-- Attachment #1: Type: text/plain, Size: 1241 bytes --]
I wonder if it would work if wctl was chmod to read-only? Might break other
things.
On Thu, 31 Dec 2015, 9:08 a.m. <tlaronde@polynum.com> wrote:
> Hello,
>
> After a long delay, I'm working back on kerTeX and I'm adding the
> display for METAFONT (it's more interesting than one could think, since
> METAFONT is the program mainly ignored while being a drawing program
> and a rasterizer engine...).
>
> But once the size of the root window for display (the user can subdivise
> this root window from METAFONT) is given and the window created, the
> dimension should not be altered.
>
> There is the possibility, in X11, to give the window manager hints and
> to disallow resizing the window.
>
> Is there such possibility with rio?
>
> TIA
> --
> Thierry Laronde <tlaronde +AT+ polynum +dot+ com>
> http://www.kergis.com/
> http://www.arts-po.fr/
> Key fingerprint = 0FF7 E906 FBAF FE95 FD89 250D 52B1 AE95 6006 F40C
>
> --
> Thierry Laronde <tlaronde +AT+ polynum +dot+ com>
> http://www.kergis.com/
> http://www.arts-po.fr/
> Key fingerprint = 0FF7 E906 FBAF FE95 FD89 250D 52B1 AE95 6006 F40C
>
>
[-- Attachment #2: Type: text/html, Size: 1882 bytes --]
next prev parent reply other threads:[~2015-12-31 19:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-31 17:08 tlaronde
2015-12-31 19:33 ` Skip Tavakkolian [this message]
2015-12-31 20:22 ` tlaronde
2016-01-01 22:58 ` erik quanstrom
2016-01-02 0:05 ` tlaronde
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=CAJSxfmK1j7p9soZuGZjLTcs9N5MjuTk-V-x+WKg_K0_sfN0wRQ@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).