Org-view-mode with new 'quick-edit' feature is now available from Melpa

[Org-view-mode](https://imgur.com/EziXHKO) is now available for installation from Melpa. Since my last post in this Reddit, it has got some new features, of which probably the most interesting is to remove read-only status, but still keep org markup hidden. It is meant for simple edits like fix a spelling mistake or add/remove a word or two. For bigger edits, drop back into org-mode. There are some other minor additions, hiding some agenda keywords and ellipses. The last one is not really recommended, but it can be useful only in some very special cases. For the usage info, check the [README file in the Github repository](https://github.com/amno1/org-view-mode).

The first installation recommendation in the README has a misleading comment above it. Straight.el does not work with use-package's :ensure keyword.

Ah yes, of course. Thank you. It was a copy-pasta leftover. Fixed!

You can use `:straight t` if you like, that'll ensure it's installed.

Ok. Thanks. I am not a user of straight.el myself. The part with straight was added by another user.

Nice! By the way, (in the dired-auto-readme description) > This was inspired by very nice [dired-show-readme](https://gitlab.com/kisaragi-hiu/dired-show-readme) by Kisaragi Hiu. However, dired-show-readme displays a Readme file as an image, and also uses external process to render a file to an image Thanks :) This is the first time [I've](https://kisaragi-hiu.com/about#links) been credited like that :) Although, dired-show-readme doesn't render to an image: it takes the readme file, throws it at pandoc to convert to html, then renders the html like EWW does (using shr.el). The rendered result is a string that I then stuffed into the `before-string` property of an overlay; I don't think it's ever meant to contain multiline content, let along entire files, which is why scrolling is broken.

> Thanks :) This is the first time I've been credited like that :) Thank you for making it in the first place and for the idea. And thank you for not being angry on me for stealing the idea :-). That was completely your idea. It was just a different implementation I had in mind, and really just an experiment to see if it was even possible. > Although, dired-show-readme doesn't render to an image: it takes the readme file, throws it at pandoc to convert to html, then renders the html like EWW does (using shr.el). The rendered result is a string that I then stuffed into the before-string property of an overlay; I don't think it's ever meant to contain multiline content, let along entire files, which is why scrolling is broken. Aha. I have to admit, back in time when you first posted your package, I wasn't so familiar with elisp, so I have misunderstood what was going on. I have also just glanced over it back then and never went back to it, so I have always thought you were rendering to an image. I took a look now, and it looks so simple and clean, but trust me, back then I didn't know what it did really :). I'll correct the text in my README file. Thank you taking your time and explaining it to me. Yes, the overlay appears just like one char to Emacs, so it can't scroll it. My solution is broken in other ways; font-lock handling needs to be rewritten, and the code has to be re-factored, but it works "mostly" for viewing.