9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Lucio De Re <lucio.dere@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] UI design | enhancements.
Date: Wed, 17 Apr 2019 05:57:35 +0200	[thread overview]
Message-ID: <CAJQ9t7ieF_9zWe+8_OoUue6sjK7s_40u2R0x18cUn9h0SXQN6w@mail.gmail.com> (raw)
In-Reply-To: <CAK0pxsEVo3qD3zTcFPS2dB9VukUni8RTsaP=H3+FderhMCa2eQ@mail.gmail.com>

On 4/16/19, Marshall Conover <marzhall.o@gmail.com> wrote:
> [ ... ]
> As an aside, Lucio, I'd second Ethan in that it's probably worth taking a
> look; I'd be surprised if there was more actual code to change than there
> was just ramp-up time to understand what you need to change, and a
> one-or-two hour excursion into the code would probably get you how much
> ramp-up time you need, at which point you could probably make the final
> call on whether to move forward.
>
Thanks to both of you for the hint. My problem, spelled out neatly
above, is that I have no idea how one targets the correct "window" in
X. I have completely swallowed the Plan 9 kool-aid of fine-grained
namespace separation and can't contemplate how xnest gets it wrong.

By the same token, incidentally, I've been wondering what the X
equivalent of 9's window could be: nowhere in X's user space have I
found a way to spawn a task in a window that matches the geometry I
specify, unless that task includes the geometry among the command line
arguments. That bit of philosophy shows so clearly how different Plan
9 and Unix really are.

I will look, however. Frankly, if rio could provide a "little" more
support, one may be able to run firefox (I'm assuming chrome/chromium
isn't quite as liberated) in a rio window, but my efforts a while ago
flopped completely - for which part of me is greatly relieved: somehow
a firefox window on a Plan 9 background would be a constant thorn in
my side.

Lucio.

PS: I did look at rio, not that long ago. But I think the problem
extends to individual graphic commands. I'll see if I can get catclock
to behave itself, next. Or shove the xnext magic into a rio option.



  reply	other threads:[~2019-04-17  3:57 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-15 20:59 Marshall Conover
2019-04-15 21:10 ` Ori Bernstein
2019-04-16 12:54   ` Marshall Conover
2019-04-17  3:57     ` Lucio De Re [this message]
2019-04-17  4:02       ` Michael Misch
2019-04-17  4:25         ` Lucio De Re
2019-04-16  8:17 ` Mart Zirnask
  -- strict thread matches above, loose matches on Subject: below --
2019-04-15 21:51 sl
2019-04-16  3:54 ` Lucio De Re
2019-04-16 10:21   ` Ethan Gardener
2019-04-15 15:47 ori
2019-04-02  4:41 [9fans] Git/fs: Possibly Usable ori
2019-04-03 18:29 ` Skip Tavakkolian
2019-04-03 20:23   ` Ori Bernstein
2019-04-04  1:22     ` Ori Bernstein
2019-04-14  9:58       ` [9fans] UI design | enhancements Darren Wise
2019-04-14 11:30         ` Ethan Gardener
2019-04-14 14:19         ` hiro
2019-04-15  5:07         ` Lucio De Re
2019-04-15  6:12           ` Bakul Shah
2019-04-15  6:25             ` Devine Lu Linvega
2019-04-15  6:41               ` Michael Misch
2019-04-15  7:24                 ` Bakul Shah
2019-04-15 11:20                   ` hiro
2019-04-15 14:27                   ` Kurt H Maier
2019-04-15 19:59                 ` Ethan Gardener
2019-04-15 20:04                   ` Michael Misch
2019-04-15 15:10         ` Chris McGee
2019-04-15 15:44           ` Darren Wise
2019-04-15 18:11         ` ab

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=CAJQ9t7ieF_9zWe+8_OoUue6sjK7s_40u2R0x18cUn9h0SXQN6w@mail.gmail.com \
    --to=lucio.dere@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).