9front - general discussion about 9front
 help / color / mirror / Atom feed
From: Romano <unobe@cpan.org>
To: 9front@9front.org
Subject: Re: [9front] [PATCH] rio: resize border and scrollbar based on font
Date: Fri, 10 May 2024 11:43:42 -0700	[thread overview]
Message-ID: <D4EA84F3C06801EC3D10C95E99BC0690@smtp.pobox.com> (raw)
In-Reply-To: <0c6eecea-5793-4032-96d2-e01ca0e19317@posixcafe.org>

For whatever reason, I'm getting delayed mails from the mailing list. I
haven't investigated further.

> I do not like merging hacks, I want to find solutions. This is only
> a problem when using the system over drawterm from a mac.

No, it also is when I hook up my extrawide LG monitor, not via drawterm.
I gave one example. I also want to find general solutions but I don't
want to make the perfect the enemy of the good: sometimes things may not
be the best, but they do help with a large chunk of the problem. That's
probably why there are so many commits already to 9front that are self-
described hacks: they're not ideal, but they are better than before.

> If all this discussion is going to be
> is you hamfisting this despite all these problems for it just being "well
> it kinda works not really but its a start" then we're going nowhere.

That's not what I said: it works for me, not "it kinda works not really".
And it's not me ham-fisting (which is the first time I've seen it used as a
verb not an adjective) the patch by giving more details about how it helps
in my setup. That's not "all this discussion" is about. I think there has
been a good discussion, particularly the suggestion about using environment
variables and /dev/theme. Whether or not either of those is an approach that
would be acceptable is another matter.

> I find scaling based on the font a bit silly. Maybe some $scale or
> something would make more sense to me, and be more general to every
> program.

I agree, but it was addressing a good chunk of the problem I had at hand
so figured something is better than nothing. The thoughts about /dev/theme and
using environment variables are better than my submission, for sure, as
they're more general. But yeah, a general scaling UI would be nice. Some
programs might never be so general, like vnc. That's why I created the vnc
auto-scaling patch (which I'm glad was not rejected), because that was
scratching my most immediate itch at the time.

> I do not like this solution though, I am rejecting this patch.

Thank you for your consideration. At least if anyone has a large monitor
and finds this helpful while the ideal solution is hammered out, it's
here for the taking.

  reply	other threads:[~2024-05-10 18:46 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-10  6:13 Romano
2024-05-10 13:27 ` Kristo
2024-05-10 14:01   ` Stanley Lieber
2024-05-10 14:17 ` Jacob Moody
2024-05-10 18:43   ` Romano [this message]
2024-05-10 19:15     ` Jacob Moody
2024-05-10 19:40       ` ori
2024-05-11 16:45         ` hiro
2024-05-11  4:31       ` Romano
2024-05-11 15:00         ` Jacob Moody
2024-05-11 16:54           ` hiro
2024-05-13  5:18           ` Romano
2024-05-11 16:42       ` hiro
2024-05-10 21:00     ` sl
2024-05-11  4:34       ` Romano
2024-05-13  5:38         ` Romano
  -- strict thread matches above, loose matches on Subject: below --
2024-05-09 21:04 Romano
2024-05-10  0:14 ` Jacob Moody
2024-05-10  0:34   ` sl
2024-05-10  6:20   ` Kurt H Maier
2024-05-10 14:10     ` Jacob Moody
2024-05-10 14:16       ` Stanley Lieber
2024-05-10 14:20         ` Jacob Moody
2024-05-10 14:23           ` Stanley Lieber
2024-05-10 14:21         ` ori
2024-05-10 14:33           ` Stanley Lieber
2024-05-10 14:37             ` Stanley Lieber
2024-05-10 14:58       ` Kurt H Maier
2024-05-10 15:28         ` Stuart Morrow
2024-05-10 16:11           ` Stanley Lieber
2024-05-10 16:43             ` Stuart Morrow
2024-05-10 16:50               ` Stuart Morrow
2024-05-11 16:36               ` hiro
2024-05-11 16:30             ` hiro
2024-05-11 16:27       ` hiro
2024-05-11 16:36         ` Jacob Moody

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=D4EA84F3C06801EC3D10C95E99BC0690@smtp.pobox.com \
    --to=unobe@cpan.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).