Steve Fink

Now that I know what's going on, I can't say this is a huge deal for me. It is rare that I'd want rr and the profiler running at the...

Heh. I happen to be working on something that requires running with the profiler on, and of course, I had forgotten about this bug. Running rr record -n is fine,...

I've run into this problem again, but this time `-n` wasn't good enough. I was trying to run firefox to debug a [crash in JS stackwalking](https://bugzilla.mozilla.org/show_bug.cgi?id=1874834#c17), but was getting the...

To reproduce: 1. download https://aapx.org/tarball/rr-issue-3400.tar.zst and replay 2. continue to the crash 3. `frame 8` 4. `call js::debug::GetMarkInfo(thing)`

(Comment originally written for issue #4468) I think @glehmann makes a good point in https://github.com/jj-vcs/jj/issues/7465#issuecomment-3282417086. It's not clear to me what `squash` should be doing in the edit workflow case....

> > * (3). abandon the commit and edit @- ([@glehmann](https://github.com/glehmann)'s suggestion). More generally, I think it would be `@-` for `-r @` and `REV` for `--from @ --into REV`:...

For the `allpredecessors` naming, we could implement the Kleene star operator. - `previous*(x)` - all previous incarnations of x - `parents*(x)` - equivalent to `ancestors(x)` - `ancestors*(x)` - redundant, still...

It gets a little weird when you use matching: I wouldn't expect `jj bookmark list 'glob:feat/*'` to fail even if it doesn't match anything. Special-casing might be too magical? As...

Came here to file this exact issue. I was also thinking that it would be handy if the commit message included directives specifying which of the new commits inherits the...

Anecdatum: The first and only time I've run into the need for `all:` so far was when doing `jj rebase -s X -d 'all:X-' -d Y`, and I found it...