Logs: liberachat/#xmonad
| 2022-01-28 17:36:45 | <liskin> | definitely multiple ways to do it |
| 2022-01-28 17:36:50 | <liskin> | the way I'd probably do it: |
| 2022-01-28 17:37:38 | <liskin> | given you now have a branch X1 with the one commit, you'd start a branch X2 at a commit before that using git checkout -b X2 X1^ |
| 2022-01-28 17:38:31 | <liskin> | and then you can pick individual changes from X1 using: git checkout -p X1, git commit -m 'some changes', git checkout -p X1, git commit -m 'some additional changes' |
| 2022-01-28 17:39:23 | <liskin> | you can also probably do git checkout X1 -- file1 |
| 2022-01-28 17:39:31 | <noex> | liskin: i didn't even know you could do that. that doesn't sound too bad. |
| 2022-01-28 17:39:36 | <liskin> | (I don't use this, I always do the interactive -p thing) |
| 2022-01-28 17:41:21 | <liskin> | the other way to do this is to use git reset to uncommit and unstage the changes, and then git add -p/git commit -p them |
| 2022-01-28 17:41:39 | <liskin> | but I'd still do the extra branch especially if this is the first time you're doing this |
| 2022-01-28 17:41:59 | <liskin> | https://stackoverflow.com/a/6217314/3407728 explains the git reset method |
| 2022-01-28 17:43:49 | <noex> | i tried something like that at work and went down a rabbit hole because I had to rewrite history and force push which was disabled |
| 2022-01-28 17:44:01 | <noex> | even for like my own personal branches |
| 2022-01-28 17:44:30 | <noex> | seems like everyone is terrified of force pushing, but I didn't really understand why for a personal branch |
| 2022-01-28 17:45:14 | <geekosaur> | force pushing does bad things when a commit has gone upstream. but in this case upstream has rejected it so you should be fine |
| 2022-01-28 17:47:11 | <liskin> | a couple years ago forcepushing to github meant review comments got lost, so it kind of makes sense that someone would disable that |
| 2022-01-28 17:47:56 | <liskin> | (arguably that's just a workaround for a tooling bug, and it's better for everyone to fix the tooling and scrap the workaround) |
| 2022-01-28 17:48:30 | <geekosaur> | gitlab doesn't seem to have that bug, at least, comments are retained but marked as out of date |
| 2022-01-28 17:49:44 | <liskin> | github doesn't suffer from this any more either, it's been quite a while since it did |
| 2022-01-28 17:50:54 | <geekosaur> | they do still partially have it, I've tried to load a commit that had been force-pushed-over and it straight up failed. only reachable from the PR, not directly |
| 2022-01-28 17:58:13 | <Solid> | noex: i think if you would communicate that you're not sure how to go about things with the person who reviewed your PR they would offer some help |
| 2022-01-28 18:54:13 | → | skewerr joins (spoonm@inaba.spoonm.org) |
| 2022-01-28 18:55:14 | × | koluacik quits (~koluacik@165.227.171.188) (Ping timeout: 256 seconds) |
| 2022-01-28 18:55:14 | × | spoonm quits (spoonm@inaba.spoonm.org) (Ping timeout: 256 seconds) |
| 2022-01-28 18:55:41 | × | Forkk quits (~forkk@li926-228.members.linode.com) (Ping timeout: 256 seconds) |
| 2022-01-28 18:56:59 | × | sogens quits (~sogens@pa49-197-169-154.pa.qld.optusnet.com.au) (Quit: WeeChat 3.4) |
| 2022-01-28 18:57:21 | → | koluacik joins (~koluacik@165.227.171.188) |
| 2022-01-28 19:00:25 | → | ElKowar5 joins (~ElKowar@srv-fin.xware-gmbh.de) |
| 2022-01-28 19:00:28 | → | Forkk joins (~forkk@li926-228.members.linode.com) |
| 2022-01-28 19:00:38 | × | ElKowar quits (~ElKowar@srv-fin.xware-gmbh.de) (Quit: Ping timeout (120 seconds)) |
| 2022-01-28 19:00:38 | ElKowar5 | is now known as ElKowar |
| 2022-01-28 19:33:52 | × | werneta quits (~werneta@70-142-214-115.lightspeed.irvnca.sbcglobal.net) (Ping timeout: 256 seconds) |
| 2022-01-28 19:35:28 | → | werneta joins (~werneta@70-142-214-115.lightspeed.irvnca.sbcglobal.net) |
| 2022-01-28 19:50:56 | × | jao quits (~jao@cpc103048-sgyl39-2-0-cust502.18-2.cable.virginm.net) (Remote host closed the connection) |
| 2022-01-28 19:58:42 | → | jao joins (~jao@cpc103048-sgyl39-2-0-cust502.18-2.cable.virginm.net) |
| 2022-01-28 21:29:14 | → | kr1x joins (~kr1x@170.249.0.122) |
| 2022-01-28 21:30:13 | × | edun quits (~qbt@user/edun) (Quit: Leaving.) |
| 2022-01-28 21:45:44 | × | gdd quits (~gdd@129.199.146.230) (Ping timeout: 250 seconds) |
| 2022-01-28 21:47:48 | → | gdd joins (~gdd@129.199.146.230) |
| 2022-01-28 21:52:42 | × | jao quits (~jao@cpc103048-sgyl39-2-0-cust502.18-2.cable.virginm.net) (Ping timeout: 256 seconds) |
| 2022-01-28 21:54:52 | → | jao joins (~jao@static-68-235-44-25.cust.tzulo.com) |
| 2022-01-28 21:55:14 | → | RMSBach joins (~user@cpe-76-177-52-136.natcky.res.rr.com) |
| 2022-01-28 22:06:08 | <RMSBach> | Has anyone here ever experimented with speech synthesis to make hackable accessibility for xmonad? |
| 2022-01-28 22:17:13 | × | RMSBach quits (~user@cpe-76-177-52-136.natcky.res.rr.com) (Quit: ERC 5.4 (IRC client for GNU Emacs 28.0.90)) |
| 2022-01-28 22:18:36 | → | RMSBach joins (~user@cpe-76-177-52-136.natcky.res.rr.com) |
| 2022-01-28 22:21:11 | ← | RMSBach parts (~user@cpe-76-177-52-136.natcky.res.rr.com) () |
| 2022-01-28 22:38:22 | → | RMSBach joins (~user@cpe-76-177-52-136.natcky.res.rr.com) |
| 2022-01-28 22:56:28 | → | mestre joins (~mestre@191.177.181.194) |
| 2022-01-28 23:30:35 | × | mc47 quits (~mc47@xmonad/TheMC47) (Remote host closed the connection) |
| 2022-01-29 00:13:34 | ← | RMSBach parts (~user@cpe-76-177-52-136.natcky.res.rr.com) (ERC 5.4 (IRC client for GNU Emacs 28.0.90)) |
| 2022-01-29 00:16:00 | × | seschwar quits (~seschwar@user/seschwar) (Quit: :wq) |
| 2022-01-29 00:38:17 | × | jao quits (~jao@static-68-235-44-25.cust.tzulo.com) (Ping timeout: 240 seconds) |
| 2022-01-29 01:18:34 | × | steve__ quits (~steve@ool-182c2b80.dyn.optonline.net) (Ping timeout: 260 seconds) |
| 2022-01-29 02:16:22 | × | thunderrd quits (~thunderrd@183.182.111.124) (Ping timeout: 268 seconds) |
| 2022-01-29 03:03:22 | × | banc quits (banc@gateway/vpn/airvpn/banc) (Ping timeout: 250 seconds) |
| 2022-01-29 03:24:33 | → | banc joins (banc@gateway/vpn/airvpn/banc) |
| 2022-01-29 03:29:33 | → | thunderrd joins (~thunderrd@183.182.114.22) |
| 2022-01-29 03:38:08 | → | RMSBach joins (~user@cpe-76-177-52-136.natcky.res.rr.com) |
| 2022-01-29 03:40:14 | × | RMSBach quits (~user@cpe-76-177-52-136.natcky.res.rr.com) (Remote host closed the connection) |
| 2022-01-29 03:48:57 | × | td_ quits (~td@94.134.91.203) (Ping timeout: 240 seconds) |
| 2022-01-29 03:50:52 | → | td_ joins (~td@muedsl-82-207-238-224.citykom.de) |
| 2022-01-29 03:59:39 | × | thunderrd quits (~thunderrd@183.182.114.22) (Remote host closed the connection) |
| 2022-01-29 04:03:05 | → | RMSBach joins (~user@cpe-76-177-52-136.natcky.res.rr.com) |
| 2022-01-29 04:40:35 | ← | RMSBach parts (~user@cpe-76-177-52-136.natcky.res.rr.com) (ERC 5.4 (IRC client for GNU Emacs 28.0.90)) |
| 2022-01-29 05:01:04 | → | arjun joins (~arjun@user/arjun) |
| 2022-01-29 05:01:11 | <arjun> | hi |
| 2022-01-29 05:01:19 | <arjun> | been doing some tinkering |
| 2022-01-29 05:01:21 | <arjun> | almost there |
| 2022-01-29 05:01:58 | <arjun> | how do i close the laptop display when i close the lid? there is an external monitor connected |
| 2022-01-29 05:02:26 | <arjun> | when i close the lid with the laptop docked, i want the laptop screen (with its bar) to come to the external monitor |
| 2022-01-29 05:02:34 | <arjun> | basically make it screen 0 |
| 2022-01-29 05:02:50 | <arjun> | i could do that with manually switching of the display in arandr |
| 2022-01-29 05:03:07 | <arjun> | but i'd like it to do that automatically when i shut the lid |
| 2022-01-29 05:03:23 | <arjun> | any pointers where do i go from here? |
| 2022-01-29 05:04:35 | <arjun> | i've already added this -> https://pastebin.com/P0FhCCKX from the rescreen hooks thing here -> https://xmonad.github.io/xmonad-docs/xmonad-contrib-0.16.999/XMonad-Hooks-Rescreen.html#v:addRandrChangeHook |
| 2022-01-29 05:46:27 | → | jao joins (~jao@68.235.43.13) |
| 2022-01-29 06:24:39 | → | DangerBird joins (~DangerBir@dhcp-v215-170.vp.reshsg.uci.edu) |
| 2022-01-29 07:06:18 | <Solid> | arjun: the laptop probably wants to hibernate on lid close |
| 2022-01-29 07:06:42 | <Solid> | I reckon you need to tell acpi not to do that |
| 2022-01-29 07:10:31 | <arjun> | Solid: xfce4-power-manager-settings -> display off on lid down |
| 2022-01-29 07:10:49 | <arjun> | so it doesn't suspend anymore when on power |
| 2022-01-29 07:15:11 | → | steve__ joins (~steve@ool-182c2b80.dyn.optonline.net) |
| 2022-01-29 07:17:57 | <Solid> | so what happens? |
| 2022-01-29 07:18:24 | <arjun> | nothin really |
| 2022-01-29 07:18:45 | <arjun> | i close the lid, the display is physically powered off on the machine |
| 2022-01-29 07:19:12 | <arjun> | but the external monitor still renders as the secondary screen |
| 2022-01-29 07:19:29 | <arjun> | and xmonad thinks the laptop screen is still active and i can send stuff to it |
| 2022-01-29 07:19:36 | <arjun> | but the lid is down |
| 2022-01-29 07:19:55 | <arjun> | and if i switch it off in arandr |
| 2022-01-29 07:20:00 | <arjun> | then it works as it should |
| 2022-01-29 07:20:26 | <Solid> | does xrandr still think it's active? |
| 2022-01-29 07:20:43 | <arjun> | yes |
| 2022-01-29 07:20:57 | <Solid> | then I guess your power manager does something wrong |
| 2022-01-29 07:21:07 | <arjun> | i guess |
| 2022-01-29 07:21:30 | <arjun> | i am using gdm rn |
| 2022-01-29 07:21:46 | <arjun> | i think i'll try switching to lightdm |
| 2022-01-29 07:22:05 | <arjun> | apart from that, am i missing something? |
| 2022-01-29 07:22:30 | <Solid> | I don't think it's your display manager |
| 2022-01-29 07:22:41 | <Solid> | (I hope not, anyways) |
| 2022-01-29 07:22:52 | <arjun> | what else should i look into? |
| 2022-01-29 07:23:26 | <Solid> | I would guess "xfce4-power-manager-settings -> display off on lid down" would be a good starting point |
All times are in UTC.