#trinity-desktop < 2025/08/18 >
[00:11]micheleC: @charltonh: suer, any additional help is welcome :-)
[00:12]micheleC: @zubairs__: currently there aren't any direct shortcut for tiling, you need to do that with the mouse of the popup window menu
[00:13]micheleC: or you can create hotkeys and link them to dcop commands to tile windows
[00:13]micheleC: adding shortcuts for tiling is something on the TODO list, with lots of other TODOs...
[01:41]micheleC has quit (Read error: Connection reset by peer)
[02:43]a-865 has quit (Ping timeout: 244 seconds)
[03:02]a-865 has joined
[04:15]a-865 has quit (Ping timeout: 244 seconds)
[04:20]zubairs__: Ok, and how about the certificate renewal for the crash report domain? I was unable to send the crash report.
[04:32]a-865 has joined
[05:56]zubairs__ has quit (Ping timeout: 256 seconds)
[05:57]zubairs__ has joined
[06:19]zubairs__ has quit (Read error: Connection reset by peer)
[06:22]zubairs__ has joined
[06:23]zubairs_ has joined
[06:53]zubairs_ has quit (Quit: Konversation terminated!)
[07:34]pitriss has quit (Ping timeout: 248 seconds)
[07:38]a-865 has quit (Ping timeout: 244 seconds)
[07:39]pitriss has joined
[07:44]pitriss has quit (Ping timeout: 244 seconds)
[07:57]a-865 has joined
[08:07]neoncortex has quit (Quit: ZNC 1.8.2+deb3.1+deb12u1 - https://znc.in)
[09:28]Fat-Zer: zubairs__: AFAIK‌ there is no meaningful way for developers to access the crashreports anyway, so it unfortunately it's just shouting into the void... I myself was recently surprised that we don't send those to some old kde address.
[09:29]Fat-Zer: as for certificate, I agree we should upgrade it just to avoid such a papercut bug...
[09:29]Fat-Zer: SlavekB: ^
[09:51]Fat-Zer has quit (Ping timeout: 244 seconds)
[10:05]Fat-Zer has joined
[10:06]zubairs__: These will be ye crash dump or trace of a program right?
[10:11]Fat-Zer: ??
[10:13]zubairs__: I mean these are useful for the developers to debug right?
[10:25]Fat-Zer: yes, that's the idea. But as I sad there are no way to access them as for now... and even if there were a way, I suppose there wouldn't be enough manpower to proactively monitor them... so the most it could be useful is to look-up similar crashes you already encountered either if you stumbled upon them yourself or in a bugreport.
[11:54]zubairs__ has quit (Read error: Connection reset by peer)
[11:54]zubairs__ has joined
[12:17]zubairs__ has quit (Ping timeout: 256 seconds)
[12:17]zubairs__ has joined
[12:37]zubairs__ has quit (Read error: Connection reset by peer)
[12:37]zubairs__ has joined
[12:42]zubairs__ has quit (Read error: Connection reset by peer)
[12:42]zubairs__ has joined
[12:45]zubairs__ has quit (Read error: Connection reset by peer)
[14:12]pitriss has joined
[16:36]zubairs__ has joined
[16:48]zubairs__ has quit (Ping timeout: 256 seconds)
[16:48]zubairs__ has joined
[17:13]zubairs__ has quit (Ping timeout: 256 seconds)
[17:17]zubairs_ has joined
[17:24]a-865 has quit (Ping timeout: 272 seconds)
[17:42]a-865 has joined
[20:02]zubairs_ has quit (Ping timeout: 244 seconds)
[20:20]raso has quit (*.net *.split)
[20:20]zubairs__ has joined
[20:26]raso has joined
[21:03]pitriss has quit (Ping timeout: 244 seconds)
[21:39]pitriss has joined
[22:32]neoncortex has joined
[22:52]neoncortex has quit (Ping timeout: 245 seconds)
[22:53]neoncortex has joined

#trinity-desktop < 2025/08/18 >