2026-02-04 00:03:31 <sojasoss    > debout la dedans !
2026-02-04 02:36:16 <KipIngram   > Yeah.  There's even a special software package that will correct for the rotation of Jupiter.  So, not a uniform shift across the whole frame, but one designed to account for the oblate spheroid shape rotating.
2026-02-04 17:15:03 <veltas      > There's one thing in Bash I hate, that the reverse incremental search fail doesn't rewind to the last matched line as you hit backspace, it essentially skips the first item if you typo + correct your search
2026-02-04 17:15:47 <veltas      > I know how to search forwards in bash too, but it's just not in my muscle memory, it's usually faster to wrap round or hit ^C and try again
2026-02-04 20:00:08 <KipIngram   > The thing that has bothered me most about it is that if you a) scroll back to an earlier line in your history, b) edit that line, and c) SCROLL AWAY (rather than hitting enter) that line is permenently changed in your history.  It no longer reflects what you actually ran.
2026-02-04 20:00:40 <KipIngram   > It will if you hit enter on it after editing - without leaving.  The edited command will be a new latest entry, and the original line will be unchanged.  But if you scroll away it alters the history.
2026-02-04 20:00:45 <KipIngram   > That feels like a flaw to me.
2026-02-04 20:01:44 <KipIngram   > The "history" should be a sacrosanct record.
2026-02-04 20:02:16 <KipIngram   > I've implemented command history in a Forth one time, and I made sure to fix that.
2026-02-04 20:05:35 <iv4nshm4k0v > Heh; I do find that feature useful on occasion myself, but it sure made lots of my students stumble.
2026-02-04 20:10:19 <iv4nshm4k0v > Then again, "set -H" (Bash's default) is probably even more confusing, such as when you do something like $ foo | sed -e "/bar/!d; /baz/!d;" .  FWIW, when I need 'history,' I use script(1) or, even more often, GNU Screen's "log" option.
2026-02-04 20:17:05 <veltas      > KipIngram: I think that behaviour is configurable
2026-02-04 20:19:35 <KipIngram   > Okay, then my complaint is about the default.
2026-02-04 20:21:55 <veltas      > You're right though
2026-02-04 20:30:39 <iv4nshm4k0v > Might be a behavior inherited from Korn shell.
2026-02-04 21:20:20 <KipIngram   > Well, you do have to decide how "luxurious" you're going to be.  What if you scrolled around and modified several lines before Entering one?  If you came back to one of those lines after having left it, would you want your changes to still be there, or to have to start all over with it?  If you want all the modifications to persist while you're mucking around, but not persist after you're done,
2026-02-04 21:20:21 <KipIngram   > then you need a whole bunch of scratch buffers, in addition to the one for your "new line."  I imagine they just didn't want to swallow that pill.  I didn't either - I forget exactly how I did it, but I did something that involved two buffers.  One was the "new" line, initially empty unless I typed in it, and the other just got loaded with the history line I had the cursor on.  If I left it without
2026-02-04 21:20:23 <KipIngram   > Entering it that buffer got re-loaded, so I'd have to start over if I came back again.  It just turns out to get a little involved.
2026-02-04 21:21:12 <KipIngram   > So my "new" line was protected - it held its current state if I left it for a while.  Other lines didn't - they "held" their original state.