Thanks, I would, and I’ve used it on my personal machines (it works great), but I’m trying to stick to the apt package repos on my $WORK machine.
Ubuntu has a fair number of elpa packages in its repos, so I’m trying to make it work if possible. Not sure if I’m missing anything config wise within the confines of vterm
I found my answer, I needed to be using page up and page down keys to “scroll” through the claude history - which is apparently required due to Claude capturing my C-v and M-v’s in its “text-box”.
Pressing “X” with your point at the file should essentially do this, no? Well, at least give you the option to open said file in an external program. Otherwise, yes, pressing “RET” will assume you want to open it in emacs, I think that is sane. But like BeetleB says, I have no issue opening an image in emacs (unless I’m on windows)
That said, lack of sane defaults elsewhere is indeed a bit frustrating, (see: littering backup and auto save files everywhere. It would be much nicer to throw it in a ‘temp’ directory within .emacs.d or similar)
There is a decent solution for this, you essentially define your own minor mode with key bindings you want to take precedence. I haven’t tried it myself yet, but seems useful in theory https://youtu.be/D99GB591Vgo
Does the average person know that a physical book they bought can deteriorate with age, and pages can tear or fall out as well? But as long as they have that book in their possession, it belongs to them, and they can read it, lend it to someone else, to their heart’s content. How are discs any different? Surely a physical book is not “permanent” but it certainly has its own merit, as compared to a DRM ridden copy of a book from Amazon. Also, some people just enjoy collecting physical media.
Books are an interesting analogy: We do have books and scrolls that are hundreds of years old. And technically, those books did "deteriorate": The colors faded, pages were damaged or went missing, the whole book became much more sensitive to environmental conditions - and the scripts and languages they were written in became outdated or even lost.
And yet we can restore and preserve those books today, and experts can still read them. And occasionally, even a language that was lost completely is recovered - or a scroll that was burned in the eruption of Vesuvius: https://www.smithsonianmag.com/smart-news/scientists-have-de...
Tear a page off a book and the rest remains readable. Spill coffee on a book and you can still see the letters through the stain.
In the meanwhile make a single scratch and you can't read your CD anymore. I'm sure there are forensic technologies that restores the content of the disc but if you are just a random nobody your disc is as good as nothing.
Not to mention CD drives fail, too.
You may interpret the OP as being against physical media. But I think what he is actually after is the idea that if you have a piece of physical media, it lasts forever which is false.
Scratching discs doesn't typically render them permanently unreadable, unless the scratch gets to the metal. There are tools which resurface the discs.
> The problem is most people don’t realize how short disc media’s lifespan is.
I have audio CDs from 1990 that play just fine and look to be in tip-top condition. Not so much CDs I have burned in the 2000s, they seem to fade, clearly a different manufacturing process. However, based on my older audio CDs, it seems that, if manufacturers want to produce quality, they certainly can.
I’m curious as to why - is it a matter of stability/feature completeness in 30.2 that you don’t need or want to bother with new releases? Or that you don’t like the direction of the project past that point?
Wow, auto install treesitter grammars, editable xref, transposing window layouts, speed bar as a side window in frame, I had no idea any of these things were coming and were all some passing thoughts I’ve had in the last few weeks “it would be cool if this was supported OOTB”. Some dreams do come true!
They probably mean ‘C-x C-Q’, which toggles a buffer with its read-only state. In this case it lets you edit the contents of the dired buffer (i.e directory or file names) to changing the buffer to wdired-mode, and then ‘C-x C-s’ to save the contents of the buffer, which changes the names and places the buffer back into read-only (dired-mode)
My use case is resuming a session and not being able to scroll back to the past history. Otherwise if I start a new session, it works fine.
It’s probably related to me being on an old version of vterm, but I’m just wondering if you ever have come across this.