unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Kangas <stefan@marxist.se>
To: Radon Rosborough <radon.neon@gmail.com>
Cc: 29003@debbugs.gnu.org, "Charles A. Roelli" <charles@aurox.ch>
Subject: bug#29003: 25.3; Docstring from PEP 257 is filled incorrectly by Emacs
Date: Mon, 11 Nov 2019 03:43:49 +0100	[thread overview]
Message-ID: <87tv7bqgii.fsf@marxist.se> (raw)
In-Reply-To: <CADB4rJHhKQDte_=8qckgyiWZ5A=odei_VuiSMhmhBXJeNnybiw@mail.gmail.com> (Radon Rosborough's message of "Thu, 26 Oct 2017 12:23:20 -0700")

Radon Rosborough <radon.neon@gmail.com> writes:

>> I think all Emacs fill commands will fill this as one continous
>> line,
>
> As it currently stands, yes. That doesn't have to be the case,
> however. For example, package `python-docstring' can understand reST
> syntax, so that:
>
>     def example_function():
>         """Initialize engine.
>
>         :param holes: Number of holes.
>         :param rounds: Number of rounds.
>         :param colors: Number of colors.
>
>         :returns: Game engine instance.
>         """
>         pass
>
> is not modified when filled. The question is whether the example given
> by PEP 257 should be considered "standard" syntax for introducing
> keyword arguments, and whether such syntax should be supported by
> Emacs in a similar way to how `python-docstring' supports reST syntax.

I think this should ideally be supported by Emacs, but it should be
configurable and disabled by default.

Best regards,
Stefan Kangas





  parent reply	other threads:[~2019-11-11  2:43 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-26  2:08 bug#29003: 25.3; Docstring from PEP 257 is filled incorrectly by Emacs Radon Rosborough
2017-10-26 19:03 ` Charles A. Roelli
2017-10-26 19:23   ` Radon Rosborough
2017-10-26 19:41     ` Charles A. Roelli
2019-11-11  2:43     ` Stefan Kangas [this message]
2021-11-30 14:56       ` bug#29003: [python.el] " 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=87tv7bqgii.fsf@marxist.se \
    --to=stefan@marxist.se \
    --cc=29003@debbugs.gnu.org \
    --cc=charles@aurox.ch \
    --cc=radon.neon@gmail.com \
    /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).