waleee-cl has quit [Quit: Connection closed for inactivity]
drakonis has joined #nixos-chat
drakonis_ has quit [Ping timeout: 276 seconds]
<ekleog>
fpletz: Looks like you're maintaining virtlyst, do you understand how to use it / is it documented somewhere?
<elvishjerricco>
Can someone with macos catalina send me the man page for `synthetic.conf`? I don't want to upgrade yet, but I really want to see the docs on that.
<ekleog>
fpletz: For now I've turned on libvirt, virtlyst, and added a local socket connection on virtlyst -- but I can't find a way to add a VM or anything, nor any kind of documentation… does it actually provide a way to view the screen over the webui, at least, as its paragraph of doc on libvirt.org suggests? (my use case is emulating an android application in a VM and making it available to
<ekleog>
multiple phones, so the webui with the VM screen is actually the main feature I'm hoping for from virtlyst)
fpletz has quit [Quit: ^D]
drakonis1 has joined #nixos-chat
drakonis1 has quit [Client Quit]
fpletz has joined #nixos-chat
drakonis1 has joined #nixos-chat
ajs124 has quit [Quit: Gateway shutdown]
das_j has quit [Remote host closed the connection]
das_j has joined #nixos-chat
evanjs has quit [Read error: Connection reset by peer]
evanjs has joined #nixos-chat
<drakonis1>
aw shiet i found a thing that needs java 7
<infinisil>
elvishjerricco: I have a mac disk where I have a separate partition for each release (but a shared one for the nix store)
<infinisil>
Can recommend :)
<infinisil>
(Didn't get cataline yet though)
<elvishjerricco>
infinisil: Oddly enough, you can't shrink an APFS container if you have time machine enabled, so I can't do that now :P
<elvishjerricco>
No idea why the hell time machine prevents that
drakonis1 has quit [Quit: WeeChat 2.6]
endformationage has quit [Ping timeout: 265 seconds]
chreekat has quit [Remote host closed the connection]
chreekat has joined #nixos-chat
atlas_ has joined #nixos-chat
tilpner_ is now known as tilpner
__monty__ has joined #nixos-chat
__Sander__ has joined #nixos-chat
__monty__ has quit [Ping timeout: 245 seconds]
__monty__ has joined #nixos-chat
drakonis has quit [Remote host closed the connection]
Jackneilll has joined #nixos-chat
Jackneill has quit [Ping timeout: 240 seconds]
<eyJhb>
etu: but NixWRT just builds a image you can flash, and if you want to change any settings, you reflash, right?
<eyJhb>
The joys of not having a standard for decimal separater... - https://i.imgur.com/DengWOM.png Thought that was one heavy package to begin with
<etu>
eyJhb: Yes
__Sander__ has quit [Ping timeout: 268 seconds]
vesper has quit [Ping timeout: 240 seconds]
vesper11 has joined #nixos-chat
__Sander__ has joined #nixos-chat
leons has quit [Read error: Connection reset by peer]
nocent has quit [Read error: Connection reset by peer]
arcnmx has quit [Read error: Connection reset by peer]
colemickens has quit [Write error: Connection reset by peer]
red[m] has quit [Remote host closed the connection]
atopuzov[m] has quit [Write error: Connection reset by peer]
aanderse has quit [Read error: Connection reset by peer]
dtz has quit [Remote host closed the connection]
thefloweringash has quit [Write error: Connection reset by peer]
tokudan[m] has quit [Remote host closed the connection]
jtojnar has quit [Remote host closed the connection]
<LnL>
I feel like I might be the only person still using slim
<__monty__>
clever and me are in that camp with you.
<adisbladis>
I wonder if we could reduce sddm to similar closure sizes as lightdm
<__monty__>
😭 as a user of a very memory starved machine this is bad news.. Lightdm has been an absolute memory hog while sitting on the login screen for me in the past.
<__monty__>
I usually remote into this machine when at home because it's not a pleasure to use. I don't always log in on the machine when I do this. I switched to slim because that way the machine at least stayed usable when on the login screen.
<__monty__>
I don't understand the maintenance argument either. Unmaintained software is stable software so it shouldn't be a burden for packagers?
<gchristensen>
nixpkgs isn't a repository for unmaintained software
<adisbladis>
__monty__: If you want to keep using slim you can pull it from older nixpkgs
<LnL>
yeah I agree, just have been happy with it and have not messed with anything else
<adisbladis>
__monty__: And as someone who does sweeping changes to nixpkg sometimes it _is_ a burden.
<LnL>
but who knows maybe my display sleep bug is caused by that
<etu>
__monty__: htop tells me that lightdm uses 0.0% memory on my system.
<__monty__>
etu: After logging in?
<etu>
__monty__: yes
<__monty__>
Well, that's not when it hogs the memory.
<etu>
I use autologin though
<etu>
I don't care that much about it's memory usage when I'm not logged in, because at that point I don't... really use any memory myself...
<__monty__>
Sure, I'm not saying this is an issue for everyone. It happens to be one for me though.
<__monty__>
Don't take away my spacebar heaters!
<etu>
gchristensen++ adisbladis++ :)
<{^_^}>
adisbladis's karma got increased to 24, gchristensen's karma got increased to 172
dtz has joined #nixos-chat
aanderse has joined #nixos-chat
leons has joined #nixos-chat
colemickens has joined #nixos-chat
tokudan[m] has joined #nixos-chat
thefloweringash has joined #nixos-chat
atopuzov[m] has joined #nixos-chat
nocent has joined #nixos-chat
jtojnar has joined #nixos-chat
arcnmx has joined #nixos-chat
worldofpeace has joined #nixos-chat
<gchristensen>
oh cool Matrix is back :)
<__monty__>
adisbladis: Doesn't seem like slim specifically is a burden though. Only 2-3 commits have touched it per year since 2015.
<etu>
__monty__: But unmaintained software doesn't belong
<gchristensen>
andi-, (flokli): after spending a week+ on your keyboard my own home keyboard feels so strange
<worldofpeace>
SLIM could live in an overlay
<__monty__>
Whether or not something's maintained doesn't really matter if it works though? If it was super buggy or something I'd agree.
<etu>
gchristensen: what keyboard did you borrow/use at home? :)
<__monty__>
worldofpeace: Yes, I'll do that. But that'll only work for as long as we live in this blissful world where the binary cache is never purged.
<etu>
worldofpeace: NUR possibly to have the modules as well
<gchristensen>
etu: a kinesis advantage, same one andi- let me borrow. but his was mapped differently
<etu>
gchristensen: ah :)
<gchristensen>
I think mine is mapped to be apple-compatible, which is maybe not ideal
<etu>
gchristensen: I had one of those for a short while but gave up on it. Then I got my ergodoxes and got used to that. I've been thinking of giving kinesis advantage another try.
<gchristensen>
mine has saved my life
<etu>
That's what I say about my ergodox
<etu>
But it's not perfect.
<gchristensen>
stick with what you know, imo
<etu>
I have two keyboard.io 's at home. They didn't work at all for me.
<worldofpeace>
etu: That was what I was thinking, nixpkgs isn't the place for unmaintained software. I think it could stay in nixpkgs if someone actually took on maintaining it and fixing the compat issues with systemd. but that probably isn't going to happen.
<__monty__>
They've been non-issues IME.
<adisbladis>
Anyway, it doesn't matter.
<gchristensen>
__monty__: that is fine. however, it is the policy of nixpkgs to drop unmaintained software.
<joepie91>
I'm currently borrowing a whitefox with gateron brown switches from someone, I don't care for the layout (still want a LY092-MINI....) but holy crap it types niec
<joepie91>
nice*
<adisbladis>
I just wish I could find a split keyboard with Topre switches
<__monty__>
Anyone using split keyboards? I've been wondering whether placement/shift's an issue? I'm rather specific about where I want my keyboard and I fear splits may be easier to accidentally move than a 100-key board.
<gchristensen>
do you consider the kinesis advantage to be split?
<__monty__>
No : )
<adisbladis>
gchristensen: I do
<joepie91>
__monty__: if they have good anti-slip feet (eg. the 3M silicone dome things), they won't move
<etu>
gchristensen: I do as well.
<gchristensen>
me too :)
<joepie91>
__monty__: that having been said, expect to need a while to adjust to the split
<etu>
__monty__: Yes, I'm on ergodoxes all day long. It happens that the parts move differently and that can be annoying sometimes. That's why I consider the kinesis advantage
<joepie91>
especially if the division of the keys on the keyboard doesn't exactly match which hands you use for what keys, you'll be pressing down into thin air for a while :)
<__monty__>
joepie91: How about alignment? It never bothers?
<joepie91>
__monty__: in what sense do you mean?
<__monty__>
Basically what etu just said I think?
<etu>
As long as the left and the right half of the keyboard have enough space in between (regardless if they are stuck together or not) I'll consider it to be "split"
<joepie91>
__monty__: still don't fully understand :P as in, the two halves not being exactly mirrored position and angle wise?
<__monty__>
Currently all that annoys me about the keyboard position is distance to me and whether it's centered horizontally. With a split there's double the moving parts so the combinatorics aren't great.
<etu>
joepie91: yeah, if one move but not the other it becomes off and your touch typing becomes funny :p
<joepie91>
__monty__: ah, in that sense. I get frustrated about non-centeredness as well, but I've found that for me that's mostly because it means that my shoulders are angled differently... and so with a split keyboard that problem goes away because I can individually move each half to perfectly match the angle I want my shoulder to be at
<joepie91>
etu: I've not had that issue with good anti-slip feet :P
<gchristensen>
adisbladis: kinesis sells something similar
<adisbladis>
gchristensen: It's about the switches for me
<adisbladis>
That's the only split keyboard with Topre switches
<etu>
joepie91: I would also be happy to only have one cable to my keyboard :p
<gchristensen>
oh I see
<joepie91>
speaking of which, I'm looking for a difficult-to-find version of the LY092-MINI. does anyone have any recommendations for a taobao agent that will let me speak to a human and have them find exactly the version I want?
<joepie91>
(I understand that it'll cost more than an automated ordering system)
<joepie91>
because presumably a version with gateron brown switches exists, but I have been unable to find it
<__monty__>
Anyone with hardware experience who could judge how hard that would be for someone without any?
<adisbladis>
joepie91: My experience is that most sellers on Taobao will customise things for you
<adisbladis>
The big problem is the language barrier
<joepie91>
adisbladis: right, the problem is that I don't speak Chinese, and therefore I need an agent who will handle the complexities of that
<joepie91>
machine translation has... not worked well, in my searches so far
<adisbladis>
joepie91: If you'd like I could have a stab at it (my partner is chinese, she does these things for me all the time)
<joepie91>
adisbladis: that would be very appreciated
<joepie91>
adisbladis: my goal is basically "a LY092-MINI with gateron brown switches" (ie. the two-halves version, not the single-handed version, and with gateron brown rather than cherry brown)
<joepie91>
which is enough nuance that it's probably going to be tricky to communicate :D
<joepie91>
the two-halves version is available off-the-shelf, I've seen some people refer to a version existing with gateron brown switches, but the listings I've found so far all only list cherry brown and various non-brown gateron switches
<joepie91>
and since there's basically no documentation on this thing outside of xahlee's site, I have no idea what the history is behind this and whether it's a deprecated version or what
<joepie91>
no English-language documentation*
waleee-cl has joined #nixos-chat
<joepie91>
adisbladis: anyway, how would this work, with someone like you (/ your partner) helping out of band? :P I haven't directly dealt with taobao before, the last time I ordered something off taobao was back in 2009 through an agent by e-mail who arranged everything
<adisbladis>
joepie91: Well... I would normally ship to her parents place in HK and get it when someone comes over to visit from there
<joepie91>
adisbladis: right, but you'd do the ordering part then?
rardiol has joined #nixos-chat
<adisbladis>
I have a friend coming over around christmas, so if we get this sorted before then that's a possibility.
<adisbladis>
joepie91: Yeah I'm fine with that
<joepie91>
okay, great :)
<joepie91>
is there anything you need from me to find it?
<joepie91>
or is it just a matter of "trawl taobao and talk to sellers until there's a hit"?
<adisbladis>
Yeah, something like that :)
<adisbladis>
joepie91: Mostly sellers on Taobao are incredibly helpful :)
<adisbladis>
It's like a 10x improvement over western online resellers
<joepie91>
ah, that I'm not used to :P
<joepie91>
yeah
<joepie91>
like, I've found western shops to be helpful to the point of figuring out whether a thing is possible
<joepie91>
but that doesn't extend to making it possible
<joepie91>
so I've occasionally purchased 'unpurchaseable' items, found 'unavailable' items, etc. - but overall you run into a lot of "sorry, we don't have that option in the ordering system" walls
<adisbladis>
joepie91: Last year me and a few friends ordered custom wifi usb adapters :)
<joepie91>
adisbladis: on which note, one scenario I'm expecting is that a seller will go "sure, we can put gateron brown switches in it for an extra fee of _____", in which case if the extra fee isn't insane, that's an acceptable option to me too :P
<joepie91>
adisbladis: ... custom?
<adisbladis>
We wanted to get some with UFL connectors
<adisbladis>
And there were no USB boards with that, so they customised it :)
<adisbladis>
Even for a small order of ~15-20 items
<adisbladis>
And it was only about 10% extra cost
<joepie91>
huh, neat
<joepie91>
adisbladis: did they do a custom board design, or just hotpatched them onto an existing boards and dremel'd out some holes in the casing?
<joepie91>
board*
psyanticy has joined #nixos-chat
<adisbladis>
joepie91: Hotpatched :)
<adisbladis>
Still though, pretty nice
<joepie91>
interesting
<joepie91>
I guess it was otherwise a high-volume product
<clever>
worldofpeace: :'(
<joepie91>
and so a new board design + assembly would be super expensive compared to the original board
<joepie91>
because it wouldn't benefit from the volume
endformationage has joined #nixos-chat
druidofluhn has joined #nixos-chat
<__monty__>
clever: I'm curious to know what your solution will be? Make slim work (using NUR maybe) or switch to something else?
druidofluhn has left #nixos-chat ["WeeChat 1.9.1"]
<clever>
__monty__: i already started writing a haskell display manager
<adisbladis>
But of course
<clever>
adisbladis: and i used slim as an example to base the ffi code on, lol
<clever>
adisbladis: main problem we ran into, is getting X11 usable in haskell, but i have since used brick, and am considering using a text console login, then starting X after you login
<joepie91>
adisbladis: anyway, please let me know if you need anything from me for the keyboard thing :P
<clever>
trying to find a second one, but i cant remember where it is, lol
<worldofpeace>
clever: yeah... I opened the PR with full knowing it does still have users. Outside of NixOS, it's already recommended that people find an alternative, and I think we need to be some of the first to actually remove it. If we get bugs related to slim in nixos, they'll never get fixed. It just seems like a burden nixos shouldn't have. Though a community member could move it outside of nixpkgs for people to use. There's
<gchristensen>
anyone good with prometheus queries? I have some tricky questions
<eyJhb>
Why is it that slim gets removed? Just unmaintained and old?
<samueldr>
the unmaintained part is the main issue; with unmaintained comes the fact that it doesn't respect the newer paradigms used for login
<__monty__>
Why does this actually matter? It seems to work perfectly fine on a systemd system so I don't get it. (I'm asking sincerely here, not trying to be adversarial.)
<samueldr>
that's where my knowledge of the situation is limited
<samueldr>
but I think it *appears* to work fine
<samueldr>
which for most users is alright
<eyJhb>
Isn't it like most software, if you use it and there are bugs, fix it yourself and don't expect anyone else to do it for you?
<infinisil>
Security vulnerabilities wouldn't show themselves in the UX
<__monty__>
See but that's my problem. I see "it's not compatible with systemd" as a reason it's bad everywhere. But no one seems to have a reason that matters.
<eyJhb>
infinisil: but should software be removed because of that?
<samueldr>
eyJhb: except that the issues seem to be integration issue, not end-user issues
<__monty__>
infinisil: What vulns in slim are there for situations without physical access to the box?
<samueldr>
that makes slim "the one bizarro DM" in nixos AFAIUI
<eyJhb>
samueldr: so we have custom stuff, for the integration to work correctly?
<samueldr>
that's my understanding of the issue
<__monty__>
eyJhb: Nope.
<__monty__>
It just works without the integration.
<eyJhb>
But isn't it then up to the users, to fix it if any issues appear?
<infinisil>
__monty__: Not saying there are, but if there were, it wouldn't get patched because it's unmaintained
<samueldr>
so, unless a user of slim is ready to fix those issues in slim, the maintainers of all graphical/login stuff of nixos can't spare their time to maintain the one bizarro DM
<eyJhb>
Hmmm...
<__monty__>
infinisil: Well if any showed up someone might pick up the task of fixing it. Not maintained just means no one's actively adding stuff.
<eyJhb>
But maybe just mark broken, or something?
<samueldr>
eyJhb: you're thinking black and white; there is more than the users here :)
<samueldr>
sure, but then the options in nixos, those can't be marked broken
<samueldr>
if the options in nixos are removed, what good is there to keep unmaintaind software in nixos?
<eyJhb>
True
<__monty__>
samueldr: But the slim derivation's only been touche 2 or 3 times a year since 2015. That hardly seems like a serious burden.
<eyJhb>
We need broken options!
<infinisil>
__monty__: The chance of somebody happening to pick up software that's been abandoned for 6 years is kind of low
<infinisil>
Why fix an old abandoned dm when there's better newer options?
<samueldr>
__monty__: proof that it might need to be picked up, nixpkgs is not an archive of all software
<samueldr>
(picked up and removed)
<__monty__>
Nix seems like an awesome place for software that'll work decades from now, except things that aren't changed (because they work fine) are dropped...
<__monty__>
infinisil: Newer sure, but better? There's not a bunch of people running slim because they felt like running an inferior DM.
<samueldr>
nix, the package manager, is still able to use those from older checkouts, or integration from external package sets
<samueldr>
so yes, it's awesome since it can be used that way
<__monty__>
And the chance isn't actually low. As long as it works people don't care. If it breaks some people'll migrate away but some will invest some time fixing it.
<samueldr>
but nixpkgs, the project where packages are maintained, shouldn't be used to stash unmaintained both upstream and in-nixpkgs, software
<eyJhb>
The chance of someone digging around finding a commit for slim to checkout/use two years from now is minimal :p I am just thinking of other packages that might end up with the same fate
<samueldr>
scream test
<samueldr>
unplug the machine from the network, wait until someone screams
<samueldr>
depending on the time it takes, you know how important the machine as
<samueldr>
was*
<eyJhb>
I want to do that with 1.500 servers, but my boss says no :(
<__monty__>
samueldr: I'd agree if it took effort. But since it doesn't. Just put it on probation "You're out the first time we hear trouble!"
<samueldr>
__monty__: what "doesn't" take effort?
<samueldr>
it's already been proven that slim is taking effort
<__monty__>
Has it?
<samueldr>
that's why it's going away as a nixos module
<samueldr>
well, that's what I assume from the context here
<__monty__>
It's been touched in a commit two times this year. That hardly seems like effort.
<__monty__>
clever's the only maintainer who *might* be interested in keeping slim alive afaik.
<infinisil>
__monty__: Do we know slim doesn't need maintenance? If it does, would the maintainer/owner maintain it?
<samueldr>
the fact it doesn't integrate with systemd/logind is an issue, an issue that needs fixing
<__monty__>
infinisil: I believe in foss enough to trust it'd get fixed if it needed fixing.
<__monty__>
samueldr: Is it though?
<samueldr>
while it is not for some of the users (most?), or they think it is not because they don't know what it means, it is still a fact about slim, compared to the alternatives
<__monty__>
None of the current users seem to care about that particular "feature"?
<__monty__>
It's more like rumour. Since no one can tell me *why* it matters, how can they tell it's not compatible?
<gchristensen>
if we want to keep Slim alive, it should get forked and a release issued with bugs fixed
<avn>
samueldr: what problems with slim and systemd? (I haven't see any problems ;))
<samueldr>
(inb4: but there's no bugs to fix)
<gchristensen>
it has been unmaintained for ~5 years
<samueldr>
welp, I should shut the heck up, it's not my battle to fight
<__red__>
if it works, does it need to be maintained?
<samueldr>
does it work?
<__red__>
(serious question - in a general case it's like softwrae is so inherently bad that we assume that anything that hasn't had a bugfix in X amount of time means that it must be abandoned)
<__red__>
I don't know... but I'm about to switch to it to find out
<infinisil>
For DE's, there are alternatives that are actively maintained
<joepie91>
from a quick search around, there were indeed some systemd integration issues
<avn>
infinisil: is a almost no alternatives for non-DE (only xdm really)
<samueldr>
and let's reiterate again, the package being removed is an artifact from the fact that integration work with the __nixos module system__ is removed
<joepie91>
so that may mean that "doesn't need maintenance" doesn't apply in this case
<joepie91>
especially since the site explicitly says it isn't maintained anymore
<joepie91>
I do agree that something getting no updates does not mean it isn't maintained anymore, but I don't think that that case is applicable here
<__monty__>
Yeah but joepie91, we've been using it just fine without those "features".
<gchristensen>
let's just drop it, samueldr (it = conversation, package, module. anyone who wants to do the work can start with https://github.com/iwamatsu/slim/issues/4)
<{^_^}>
iwamatsu/slim#4 (by cstrahan, 3 years ago, open): Slimlock Bug/Vulnerability: isn't guaranteed to grab keyboard
<__monty__>
Can't we just consider it a DM that lacks some features some people might want?
<gchristensen>
Montypkgs
<__red__>
brb - switching
<samueldr>
security?
<__monty__>
Slimlock has little to nothing to do with slim.
<__monty__>
And display locking's broken for basically every DM so maybe all of them should be removed?
<samueldr>
except that slimlock is part of slim?
<gchristensen>
sgtm
<__monty__>
samueldr: Just because it's a part of slim doesn't mean you need to use it. I don't install a DM so I can lock my display.
<samueldr>
great, we can ship insecure by default software because you don't need to use them
<samueldr>
hear that? we can ship old openssl versions!
<gchristensen>
perfect!
<avn>
samueldr: well, shiping insecture stuff is a bad solution
<__monty__>
Slippery slope much?
<samueldr>
slimmery slope
<samueldr>
an intrinsic part of the software is insecure
<samueldr>
so just that I think is reason enough
<eyJhb>
Insecure by default?
<samueldr>
even forgetting about the whole nixos integration maintainership
<eyJhb>
Can we make like, a distro for that
<samueldr>
I think there is
<__monty__>
If there was an actual issue with slim I wouldn't even have started discussing it. But there doesn't seem to be from a maintainer's pov.
<__red__>
there's an entire industry dedicated to that ;-)
<eyJhb>
samueldr: yes, but I want Damn Vulnerable NixOS :D
<eyJhb>
Just to screw with people
<__monty__>
Screen lockers are notorious for being vulnerable so I don't see that as a major reason to drop slim.
<__red__>
THere - switched to slim. Now there's three users :-)
<gchristensen>
that is not convincing
<samueldr>
right, doing something because it's popular always ends well
* samueldr
reinstalls windows
<gchristensen>
good grief it would be such a relief to deal with someone else's buggy OS instead of care about my own
* eyJhb
is just going to drive away with hot cocoa w/ heavy cream! Hope it works out well o/
<samueldr>
oh, just saw another issue, SLiM doesn't integrate with the nixos module for NVIDIA Optimus Prime
<samueldr>
(but *I* don't use nvidia optimus prime)
<__monty__>
Depends on how you define well. We'll have to fend for ourselves. It's just too bad a bunch of people have to expend effort to run what they want now for seemingly no reason other than being the first to officially drop support.
<samueldr>
is it really what you understand of the situation??
<samueldr>
that people are just dropping stuff as a popularity contest?
<samueldr>
that there is no rhyme or reason to remove this, except "yay I did it!"?
<gchristensen>
this is very off topic
<gchristensen>
-> -dev?
<__monty__>
I don't believe I can actually convince maintainers so I'm not interested in cluttering up -dev.
<samueldr>
(I approve of ↗️ #nixos-dev and will interact with the issue there only)
<__monty__>
I've accepted that I'll have to switch to plain old startx, which means I can't really show off NixOS to inexperienced linuxers because they need flashy to be convinced of anything.
<etu>
__monty__: Or fork slim and fix things and start doing releases? Which is the foss way if you care for something like that.
<__monty__>
But there's nothing to fix, it works great : )
<__monty__>
Let's say some people consider the lack of systemd integration (what is that even?) a bug, let's call those people A. Let's call the ones who don't people B. Currently only people B get to enjoy slim. Fixing that integration would be great, means that A+B get to enjoy it. Apparently none of the A people are motivated enough to do this though, and that's fine. Now, dropping the package means B can't
<__monty__>
enjoy it anymore either, reason "A people consider it buggy." Sounds pretty non sequitur to me.
<gchristensen>
andi-: just finished updating all my keyboards to use the new key layout inspired by yours. top thumbs: (ctrl, alt) (altgr, windows)
<andi->
gchristensen: *how* could you use that before? :D
<gchristensen>
huh?
<andi->
I mean before the modification
<andi->
I just couldn't use those keys in the original layout.
<samueldr>
top thumbs, opposed to the bottom thumbs? (how many thumbs do you emacs user need, 4, 6?)
<gchristensen>
I dunno, it was in whatever Mac mode got me
<gchristensen>
and I had just adopted to it
<gchristensen>
samueldr: lol, instead of the bottom four keys on both thumbs :P
<gchristensen>
anyway, nice to have an Alt-Gr now instead of reaching for my laptop keyboard when I want to type « and »
<__monty__>
How often do you type guillemets?
<samueldr>
if I had my 105th key, my layout would have « and » on a dedicated key :)
<gchristensen>
fairly often for nested quotes or to «quote --command-line="options"»
<__monty__>
Maybe consider a compose key. An extra key for guillemets but so many more symbols at your disposal.
<gchristensen>
that is what alt-gr does for me
<__monty__>
You nest quotes a lot?
<__monty__>
Then why call it alt-gr rather than compose? That's just confusing.
<gchristensen>
enough that I have alt-gr set as my compose key
<samueldr>
just alt gr to compose key?
<samueldr>
or is it _also_ third level?
<gchristensen>
alt-gr alone is my compose key
<samueldr>
I have altgr+rctrl as my compose key :)
<samueldr>
(once released)
<gchristensen>
ah, I don't have an rctrl
<samueldr>
on the diverse french canadian layouts, alt gr is used for many characters, so any time I abort using alt gr, I would end up being in compose mode and be annoyed :)
<__monty__>
I've never understood r-ctrl/option.
<gchristensen>
ah hehe
<ekleog>
gchristensen: just switch to bépo, «» are reachable without modifiers :3
<gchristensen>
perfect!
<ekleog>
(also, prtsc is my compose key)
<__monty__>
What's with you people and guillemets? I almost never see them and I live in a french speaking country!
<gchristensen>
oh I do have one of those
<ekleog>
__monty__: then you should use them, and show people they're beautiful :p
<__monty__>
ekleog: That doesn't sound verry ergonomic. prtsc's so far away?
<gchristensen>
hmm now my new-old problem is my right-click on my trackball doesn't work.
<__monty__>
On a mac? You could always ctrl-click?
<__monty__>
Not ideal, but workable.
<__monty__>
Well, nn, folks. Time to go mourn the passing of my dear friend SLiM in private.
<gchristensen>
have a good night!
<ekleog>
__monty__: it's at the symmetric of meta, here
<ekleog>
(lenovo laptop)
<ekleog>
like, where some other keyboards have the menu-or-I-don't-know-the-name key
<ekleog>
'night!
<__red__>
gchristensen: I had capslock as my compose key
<__monty__>
Hmm, the keyboards must've changed. Mine had a menu key there.
<__red__>
I actually need to re-configure a compose key - not gotten to it since I switched to i3
<__red__>
so I guess I have to work out how to do that
<__monty__>
CAPS can do double duty as ESC and ctrl though.
<__red__>
but on my beamspring, I use caps as ctrl
<__red__>
sway crashed my machine constantly, I don't know whyt
<__monty__>
Oh, that *is* neat.
<__red__>
but I started to enjoy it so much it moved me to i3
<__monty__>
#hardwaretoooldforwayland
__monty__ has quit [Quit: leaving]
<__red__>
also, gchristensen - if you can describe what you mean by "use the new key layout inspired by yours. top thumbs: (ctrl, alt) (altgr, windows)" to the class I'd sure appreciate it :-)
<gchristensen>
the kinesis advantage has reprogrammable keys, and before I was using the kinesis preprogrammed keys designed for macOS usage
<gchristensen>
I was borrowing his keyboard for a couple weeks and had a hard time adapting to it, and the a harder time adapting back to my regular keyboards
<__red__>
whoa - ctrl-a looks like I would die on that keyboard ;-)
<gchristensen>
ctrl-a?
<__red__>
yes - use in screen / tmux
<gchristensen>
is this more challenging than normal?
<__red__>
the A key on my mac keyboard is always the first to go
<__red__>
would you do ctrl-a with one hand or two?
<gchristensen>
one hand
<__red__>
I guess I'm trying to understand how my hand would fit
<__red__>
I probably need to see one
<gchristensen>
thumb on Ctrl, pinky on the a
<samueldr>
__red__: you need 4 to 8 thumbs
<__red__>
I'm glad it's awesome for you
<gchristensen>
lol me too, it would be really disappointing to not be able to use computers anymore
<__red__>
I think my greatest disadavtage would be that I don't touch-type properly - so split keyboard murder my brain alreadyu
<gchristensen>
yeah that is a thing
<adisbladis>
I can still touch type on qwerty 10 years after switching to dvorak :)
<adisbladis>
Takes a minute to readjust though
<infinisil>
I on the other hand couldn't use qwerty(z) at all anymore once I got used to dvorak
<infinisil>
Pun not intended
<gchristensen>
"Fixed the issue where a USB drive cannot be used as a bootable device when connected to a Type-C port."
<flokli>
gchristensen: where is that from?
<flokli>
don't tell me it's a bios update, and it needs windows. 🤦
<gchristensen>
fwupd gave me that one
<samueldr>
I think dells are fine for the *bios* update
<samueldr>
but the usb firmware? :)
<gchristensen>
well, it did some upgrades and rebooted, so