9front - general discussion about 9front
 help / color / mirror / Atom feed
From: Jacob Moody <moody@posixcafe.org>
To: 9front@9front.org
Subject: Re: [9front] [PATCH] rio: resize border and scrollbar based on font
Date: Fri, 10 May 2024 09:17:13 -0500	[thread overview]
Message-ID: <0c6eecea-5793-4032-96d2-e01ca0e19317@posixcafe.org> (raw)
In-Reply-To: <86F1A5CD218EFDC622FF2D79D79DD44D@smtp.pobox.com>

On 5/10/24 01:13, Romano wrote:
> Thanks for the feedback, moody.
> 
> While it may be a band-aid, it does improve things from where I sit.
> When I drawterm from a mac w/2560x1664 resolution, it's unbearable
> with the default font. So I'm currently using /n/ttf/unifont.ttf.32/font
> which makes everything pretty usable. The one thing that bothered me
> was the scrollbar, and then I noticed the border width was super thin
> too so tweaked that.

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.
I am not interested in merging this as is.

> 
> If this just modified the scroll bar to account for the font size,
> would that be more palatable to you?

No, I don't want rio having code for scaling.

> 
> I also can't imagine trying to go through all programs to see which
> rely on a specific rio border-width. It would be nice to address that
> along with magnification. But I think this is a start, and makes things
> more bearable at least for me.

I don't want to merge "a start" just because it exists, let's us figure
the correct solution to the problem. 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.

> 
> Anyway, what do you think about just modifying the scroll bars? And
> do you have thoughts on how to do scaling generally?


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 do not like this solution though, I am rejecting this patch.



  parent reply	other threads:[~2024-05-10 14:20 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 [this message]
2024-05-10 18:43   ` Romano
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=0c6eecea-5793-4032-96d2-e01ca0e19317@posixcafe.org \
    --to=moody@posixcafe.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).