From: Stefan Kangas <stefankangas@gmail.com>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: Phil Sainty <psainty@orcon.net.nz>,
38665@debbugs.gnu.org, Eli Zaretskii <eliz@gnu.org>,
jefferson@aoeu2code.com
Subject: bug#38665: [PATCH] Add nosqueeze for fill-paragraph
Date: Thu, 24 Nov 2022 17:36:48 -0800 [thread overview]
Message-ID: <CADwFkm=yjvvtNE7RLGSPR3FXSHgJFRtAfzB5pcJvsTzC_DuYFw@mail.gmail.com> (raw)
In-Reply-To: <87v9fuu0l1.fsf@gnus.org> (Lars Ingebrigtsen's message of "Thu, 01 Oct 2020 04:44:26 +0200")
Lars Ingebrigtsen <larsi@gnus.org> writes:
> Phil Sainty <psainty@orcon.net.nz> writes:
>
>> My suggestion there for C-u C-u was:
>>
>>>>> That could mean "prompt for the fill-prefix, and use the default
>>>>> column and justify values", but it might be more useful to instead
>>>>> make it prompt for *everything* -- justify, fill-column,
>>>>> fill-prefix, and maybe left-margin too.
>>>>> The default value would be provided in each case, so you could
>>>>> just RET your way past the ones you didn't want to change.
>>
>> I think we could blend the 'nosqueeze' option into all this, but if
>> the new changes could happen in a way which wouldn't create any serious
>> conflicts for the other changes I'm still hoping to get made, that
>> would be grand.
>>
>> Or if someone is motivated, please feel free to run with what I'd
>> already done. I may have some more-recent local WIP on my other
>> machine; I'll have a look for that later.
>
> I think the idea is sound -- there's so many variations of what you'd
> possibly want this command to do, so prompting seems good: Neither user
> options nor adding more prefix combinations would help, I think.
>
> If you could finish up the WIP and post the patch, that'd be great.
That was 2 years ago. Phil, did you make any progress with your patch?
next prev parent reply other threads:[~2022-11-25 1:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-18 22:29 bug#38665: [PATCH] Add nosqueeze for fill-paragraph Jefferson Carpenter
2020-05-19 4:13 ` Stefan Kangas
2020-05-19 14:15 ` Eli Zaretskii
2020-05-19 14:22 ` Stefan Kangas
2020-05-19 23:59 ` Phil Sainty
2020-05-21 1:51 ` Phil Sainty
2020-10-01 2:44 ` Lars Ingebrigtsen
2022-11-25 1:36 ` Stefan Kangas [this message]
2024-01-10 22:16 ` Stefan Kangas
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CADwFkm=yjvvtNE7RLGSPR3FXSHgJFRtAfzB5pcJvsTzC_DuYFw@mail.gmail.com' \
--to=stefankangas@gmail.com \
--cc=38665@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=jefferson@aoeu2code.com \
--cc=larsi@gnus.org \
--cc=psainty@orcon.net.nz \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).