From: carlmarcos--- via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 56826@debbugs.gnu.org
Subject: bug#56826: Inserted text in docstrings and buffers not formatting text into full lines and paragraphs.
Date: Sat, 30 Jul 2022 15:55:15 +0200 (CEST) [thread overview]
Message-ID: <N8ENwTO--3-2@tutanota.com> (raw)
In-Reply-To: <87o7x6yb35.fsf@gnus.org-N8EKFpx----2>
Jul 30, 2022, 13:38 by larsi@gnus.org:
> carlmarcos@tutanota.com writes:
>
>> When I write a docstring, what is written in the buffer upon hitting
>> `C-h f fun` shows the same formatting as was coded in the docstring.
>> Last word on each line is the last word on each line printed in the
>> function documentation buffer.
>>
>
> Yes -- is this a problem?
>
Yes, if I want to use a link in the docstritng.
The same problem occurs when inserting into a buffer.
> If you want to reflow a paragraph, then call `fill-paragraph'.
>
Could you show an example that does that?
next prev parent reply other threads:[~2022-07-30 13:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-29 13:43 bug#56826: Inserted text in docstrings and buffers not formatting text into full lines and paragraphs carlmarcos--- via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-07-30 13:02 ` Lars Ingebrigtsen
[not found] ` <8735eizrcn.fsf@gnus.org-N8EC0_l----2>
2022-07-30 13:18 ` carlmarcos--- via Bug reports for GNU Emacs, the Swiss army knife of text editors
[not found] ` <N8EFWxZ--3-2@tutanota.com-N8EFhyQ----2>
2022-07-30 13:25 ` carlmarcos--- via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-07-30 13:38 ` Lars Ingebrigtsen
[not found] ` <87o7x6yb35.fsf@gnus.org-N8EKFpx----2>
2022-07-30 13:55 ` carlmarcos--- via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2022-07-30 13:58 ` Lars Ingebrigtsen
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=N8ENwTO--3-2@tutanota.com \
--to=bug-gnu-emacs@gnu.org \
--cc=56826@debbugs.gnu.org \
--cc=carlmarcos@tutanota.com \
--cc=larsi@gnus.org \
/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).