Re: org-(un)fill-buffer

2024-01-10 Thread Psionic K
> smart fill prefix reliably. is that possible now? It's reasonably complete for several documents I'm converting, such as the transient showcase. Visual fill requires two modes right now: 1. visual-line-mode (usually with visual-fill-column-mode as well) 2. adaptive-wrap-prefix-mode Updating

Re: org-(un)fill-buffer

2024-01-10 Thread Samuel Wales
i lost track of all the visual fill stuff vs. emacs native filling vs. org filling vs. filladapt back before visual filling was able to fill with both a fill column and a reasonably smart fill prefix reliably. is that possible now? also, if a new command is to be introduced, presumably it would

fill-region-as-paragraph does not respect fill-paragraph-function (was: org-(un)fill-buffer)

2024-01-10 Thread Ihor Radchenko
[ CCing emacs-devel ] Psionic K writes: > If I run fill-region on a buffer, there's a lot of errors where the > lack of element awareness means filling is attempted on text that does > not fill properly, such as property drawers, keywords, and even > src-blocks without newline separations. The

Re: org-(un)fill-buffer

2024-01-10 Thread Psionic K
If I run fill-region on a buffer, there's a lot of errors where the lack of element awareness means filling is attempted on text that does not fill properly, such as property drawers, keywords, and even src-blocks without newline separations. The result requires way too much cleanup. It is

Re: org-(un)fill-buffer

2024-01-10 Thread Ihor Radchenko
Psionic K writes: >> You may instead just run >> (let ((fill-column most-positive-fixnum)) (fill-region (point-min) >> (point-max))) > No. That will have to be run manually on every element and every line > of every list. I suppose let's just not talk about it further and > I'll submit a

Re: org-(un)fill-buffer

2024-01-10 Thread Psionic K
This is the org-fill-buffer command, done generically for people who want to fill or unfill the entire buffer, as is required when alternating between hard newline filling and visual line mode filling. See attached patch for docstring and commit message. From

Re: org-(un)fill-buffer

2024-01-10 Thread Psionic K
> You may instead just run No. That will have to be run manually on every element and every line of every list. I suppose let's just not talk about it further and I'll submit a patch so there's no confusion. On Wed, Jan 10, 2024 at 9:31 PM Ihor Radchenko wrote: > > Psionic K writes: > > > I

Re: org-(un)fill-buffer

2024-01-10 Thread Ihor Radchenko
Psionic K writes: > I wrote up a small addition to the unfill package, which is very > convenient for switching hard newlines out in favor of tools like > visual-line-mode and adaptive-wrap. > > The command unfilled every list and paragraph in the entire buffer. PR is > here: >

org-(un)fill-buffer

2024-01-10 Thread Psionic K
I wrote up a small addition to the unfill package, which is very convenient for switching hard newlines out in favor of tools like visual-line-mode and adaptive-wrap. The command unfilled every list and paragraph in the entire buffer. PR is here: