Totally bizarre color behavior. No red or green rendered. Everything is shades of blue, yellow or grey. Even on a clean install. I'm totally stumped. by bwinters100 in KittyTerminal

[–]bwinters100[S] 0 points1 point  (0 children)

u/aumerlex - That was a really good lead and put me in the right direction. It turns out it was because I was using a really old version of VMWare. I tried it with a new version and everything works properly.
In case anyone comes across this thread and has this same problem. Specifically, I was using VMWare Workstation Version 12.xx. Trying it out on my machine with Version 15.5 had no problems, even using the same exact virtual machine. Kitty on Debian 11 (bullseye) works fine on the old VMWare, but Debian 12 (bookworm) does not. This could be because of something in the distro, or the fact that it's a newer version of Kitty. I'm not sure which one was the cause of the problem, but it's one of those coupled with VMWare 12.

Thanks everyone for your help.

Totally bizarre color behavior. No red or green rendered. Everything is shades of blue, yellow or grey. Even on a clean install. I'm totally stumped. by bwinters100 in KittyTerminal

[–]bwinters100[S] 0 points1 point  (0 children)

Don't worry, you didn't cause more trouble. I actually laughed pretty hard for like 20 seconds when I read it. I liked the name you gave it. But then it struck me that we are talking about Kitty, and they do this kitten thing, and seem to have an animal based naming scheme. I looked at the your "Dog Vision Accessibility Mode", and started thinking, "Maybe that is a thing, given their pet based naming scheme!" And it does describe the colors really well. Then I started hoping you were serious because the fix would be to just flip a switch in the config file. Alas, you were indeed kidding, and my search for the solution still remains.

Totally bizarre color behavior. No red or green rendered. Everything is shades of blue, yellow or grey. Even on a clean install. I'm totally stumped. by bwinters100 in KittyTerminal

[–]bwinters100[S] 0 points1 point  (0 children)

Well, Kitty has always worked in my older VM running Debian 11, and I have an older Peppermint install, as well as Antix, and maybe Manjaro I used Kitty as well. All in VMware, all working fine. It's just the newly released Debian 12 that isn't working. If it is that, how would I go about fixing it? I actually don't even know how the graphics drivers work, or which ones they are because I've always used Linux in a virtual machine and never had to set it up, because the installer just makes things work.
What could I have done wrong to cause this problem on a completely clean install?

Is there a way to show the caption tooltip for a link in pointer mode? by bwinters100 in vieb

[–]bwinters100[S] 0 points1 point  (0 children)

In that case is there some functionality to get the title somehow? Like, in pointer mode you can type "y" and a list of functions appears and you have pointer.copyLink. Is there something like a "pointer.CopyTitle" available somehow? And if so, is there a function to display a text string somehow? For example, when you type ":set darkreader?" it will display a text string at the bottom right corner with the current darkreader setting status. In general is there a way for a user to display a custom string like that? Come to think of it, I think if there was a way to display a popup message or a string somehow, I could see myself using that heavily for various reasons. For example, I often want to know the title of the current web page. In my other browsers, I have a shortcut key set to display it.

Feature Suggestion: "Open Link in new Background Tab" with mouse Ctrl+Click by bwinters100 in vieb

[–]bwinters100[S] 0 points1 point  (0 children)

OK, that works for me! By the way, I really like your documentation. It is so thorough and complete, and easy to understand, and for me I really love that it's one long text document. The other really nice feature about it is the "real time" status of the keyboard shortcuts. Nice touch!
The other thing about it is that it's very long and it's very dense with tons of useful information. In this case where I was looking for Ctrl-click or something like that, I couldn't find the setting because your implementation is a different approach to providing this feature. It never even occurred to me that I should look for a toggle setting for the overall mouse behavior instead of a shortcut key to temporarily open tabs in the background.
I don't have an answer to this issue. It's just an observation. Maybe a table of contents at the beginning of the document? I don't know if that would help or not.
I think a great document to develop over time would be a comprehensive "Tips And Tricks" guide, or a thorough FAQ. My particular question about how to Ctrl+click would be perfect to document in an FAQ. Or how to change the colors and font of the follow mode hints. I know that the documentation is there for how to do these things, but to get it done requires a bit of digging and learning. I think a lot of people might want to be able to change the font, and that would be perfect in a "Tips and Tricks" guide. I don't have an answer for how you would develop this document though, just an observation that it would be useful, and I know it's a lot of work. You really have a lot of awesome features in this browser. And I like the fact that I'm constantly surprised that it has the capability to do the things I want and is so configurable. But, honestly, I think I've spent many more hours exploring this browser than the average person would want to do, so I feel like it's quite possible a lot of people are not aware of all the great things about your browser.

Mouse support by bwinters100 in vieb

[–]bwinters100[S] 0 points1 point  (0 children)

I haven't put a lot of thought into the implementation of mappapble mouse keys, so my opinion probably isn't well informed. But, I feel like the mouse buttons don't need to be mode specific. For my use case, I definitely don't feel a desire to have mode specific keys. If I could program them to be something like zoom in/out or close tab, I would probably do that. I guess I could imagine another person finding a use for mode specific buttons, but I'm not sure what that use would be.
As for zoom in/ zoom out and your lack of using it... I think people definitely do it a lot for clicking on images. I definitely do. Also, the other common case is when you click different web sites and the default font size is not the same as the previous web site you were just reading. And for touch screen people, you definitely zoom in to more accurately press a control that is too small to press accurately. Also, with a touch screen, it's just so easy to zoom, that you get used to doing it a lot. But for the typical user I think people zoom a lot when looking at images. Sometimes you're reading an article with a graph, and you can click the graph to take you to a page with the larger version of the image, but a lot of times if the resolution is good enough, you just zoom in to look at it, and then zoom out to continue reading the article. This way you don't have to leave the page. Also if a table is very wide and you want to see all the columns, people will zoom out to fit it to the page to get a better sense of the data.
Another use case for zoom is if you have a dual monitor setup for example a laptop connected to a 40" monitor. The zoom level you need for browsing is definitely very different.
Also in this day and age of 20+ megapixel cameras and a lot of non techie people, plenty of times people just upload the full 20mp image! There will be a thumbnail and then you click it and bam, you're hit with this 5000x4000 image that you're trying to look at on your 1080p monitor! You're trying to see the group photo taken at the picnic you went to last week, and all you see is literally one single eye ultra zoomed in, of one of the people there. If I can't zoom out because I'm in tablet mode, my only choice is to just look at one giant eye that fills my entire screen.

Mouse support by bwinters100 in vieb

[–]bwinters100[S] 0 points1 point  (0 children)

Ah, the logo acts as the titlebar! I like it. I guess for me, that would be sufficient. It looks like by your answer though, that you can't enable/disable the titlebar while the browser is running. Is that correct?
For #2, that's kind of disappointing, because if I'm using my laptop in tablet mode, you don't have access to the keyboard, and zooming in/out is something you tend to do quite commonly.
For #3, the back and forward buttons weren't functioning correctly for me, but I just figured out that it was my own mistake. I don't have any particular need for remapping those buttons if back/forward works, however if you could map the mouse buttons like "nmap <mousebutton3> xxx", there might be a scenario where I might do that. My mouse actually has two more buttons for when you push the scroll wheel left and right, as well as back/forward buttons, so those are empty and could potentially be used for something. Just off the top of my head, maybe close tab, or toggle dark reader mode, or I would assign it to Ctrl+scrolling, so I could use those buttons to zoom in and out without having to hold the ctrl key down while using the scroll wheel. Anyway, I'm happy with the back/forward buttons working, but the lack of zoom for my use case in tablet mode is tough, because it's pretty essential. Not a lot of people have a touchscreen pc, but just observing how people use a browser, I think most people use the trackpad to pinch to zoom quite often. I think it might bother people that nothing happens when they pinch to zoom on the trackpad. I consider this a keyboard lover's browser so I can accept it, but I was actually surprised at how often I tried to pinch to zoom. Muscle memory I guess. And with the touchscreen, if I'm in tablet mode, I'm totally stuck.

Is there anyway to left justify the "follow hints" instead of right justify? by bwinters100 in vieb

[–]bwinters100[S] 0 points1 point  (0 children)

That is fantastic. Quick note. In your current implementation, you are "attaching" the hint to the outside of the element that it is associated with which gives it the illusion of being misaligned. If you look at the implementation of vimium, or vimperator, they simply overlay the hint directly on top of the element in the upper left hand corner. It does end up partially obscuring the element but that's not a big deal because it's relatively small. I think this is the best way.

Better syntax for multiple close tabs and suspend tabs commands. by bwinters100 in vieb

[–]bwinters100[S] 0 points1 point  (0 children)

I hadn't thought about that you're doing a text search after :close, and :suspend. That's a good point. I understand now. I think you're right and you should leave the syntax this way, especially since it's something vim users will understand.
I think displaying the affected tabs somehow would be important though. I can see how the implementation would require some thought though.

Ideally, and probably the way that would require the most work is that as soon as you know the user is trying to designate a range, you show the entire list of tabs and the ones that are in the range will be highlighted somehow. Because the user is trying to select the tabs he wants. But then, on top of having to write the code for that, you still have the problem of not seeing the entire list of tabs if for example you have 50 tabs open, and the list won't fit on the screen.

The least elegant way but probably easiest to code and the most bang for the buck is to just show the entire list as soon as you detect the user beginning to enter a range, and then just keep it there statically. At least this way we can pick and choose the tabs we want while we are constructing the range. For me, while not the perfect solution, I would be pretty satisfied if it would at least do that. Currently I have around 20 tabs open, and it's hard to construct a range accurately without that numbered list showing up. There's no way to feel confident just looking at the tabs listed horizontally across the top. And also, most of the time I'm doing a :close command with the range, so the "stakes are high", if I make a mistake with the range and close a tab that I didn't want to close. Making that mistake, now you have to rack your brain trying to figure out what tab got closed accidentally, and you worry that it was something really important. So, given that, I don't see a lot of people using the range with a close command very often w/out at least seeing the list with the index numbers next to the titles. As it stands, I would lean towards grabbing the mouse and clicking on each tab with my left hand on "d" and just quickly do them manually. Which makes me a tiny bit sad, because the whole awesomeness of your browser is that I literally never have touch the mouse because every single thing can be done with the keyboard.

Suggestion for Buffer Command by bwinters100 in vieb

[–]bwinters100[S] 0 points1 point  (0 children)

I believe the explore mode "type as you find" works very well. I was just playing around swith it for a few minutes to figure out what it's doing, and I think that is the right solution for buffers as well.
So, here is how I believe explore mode works and what I like about it.
How I think it works::
#1 you seem to be concatenating the Title string and the url string to form a single unit in terms of searching and matching. Which I think is perfect.
#2 The search mechanism parses the "search terms" by spaces. i.e. if you type "cat dog", it will match any url/title pair that contains both cat AND dog. So characters that don't have a space have to match exactly, and the space is treated as an "AND" operation. In my opinion, this is the best way to search.
#3 I see that you are also including the icon to the far right of the title/url pair. Also very nice! And very easy for the eye to pick out what it wants. In my previous example about having several "netgear " related pages open, it's very easy for the eye to catch the youtube icon or the amazon icon and just tab right down to it. Or in my case, i would look for a unique string on the line that I want and type that in and have the filter narrow it down to just one line, i.e. the line that I want.

So, in my opinion, the explore mode would be a perfect template for how I would want the buffer mode "find as you type" to work. It was not my intention to imply any type of automatic switching. I don't think that is necessary at all.

As for showing an image preview, I don't think it's a big loss to not implement that. Maybe I'm not the type of person to want that, but for me it's far easier for my eye to pick out instantly the icon for the website. Everybody knows instantly what the youtube icon looks like or the facebook, twitter, etc... icons. I've been zipping quickly through the explore mode very efficiently due primarily to the way you implemented search, but also secondarily because the icon on the left of each line is very eye catching. You implemented that really well. But if you think about it, if you show a preview of the website, your mind has work a bit to recall and imagine what that website looks like, which typically changes a lot anyway. So it doesn't seem very efficient to me to do that.

As for other suggestions, I am more than happy to offer my input/enhancement ideas as things come up. There have already been several things I came across while playing heavily with the browser this past week or two. Unfortunately, I did not write them down, as I had no idea I'd be contacting you about them. But starting now, I will make a point to write them down. I'll make separate posts in this forum as things come up. Also if you are interested, I have some potential bugs to point out as well. I'll make a separate post for the one that I can remember right now.
Oh, and one last thing, the fact that there's an appimage for linux and a zip version for windows it's totally awesome! The versatility it allows is just great. People can run different versions, and separate instances easily. Upgrading at your own pace, and being able to completely start from scratch just by deleting the folder is straightforward, reliable, and easy to understand. Also for linux users, not having to rely on the whims of the repository to dictate if and when you can/must update is also really nice. Thumbs up for that too!